Batch 7 County-Code Errors
You are a data-entry clerk entering 60 new client records from paper forms into a case-management system. At 4:30 p.m. you submit batch 7. At 4:50 p.m. you realize that for records 31 through 45 you used the old county-code list. Last month, county code 14 changed to 19 and code 22 changed to 23. In that range you entered code 14 on eight records and code 22 on six records; the remaining one record had code 19 already. The batch is locked for overnight processing, but the system allows corrections until 9:00 a.m. the next business day through an error log, and each corrected record needs a supervisor's initials. You also notice that record 38 has the same client ID as record 12, which was entered in an earlier batch. Your supervisor left at 4:45 p.m. and will return at 8:00 a.m.
1. Determine the scope of the errors. How many records are affected and which errors are most urgent?
Read the worked answer
County-code errors in records 31–45:
- 8 records entered as code 14 should be code 19.
- 6 records entered as code 22 should be code 23.
- 1 record already has code 19 and is correct.
That is 14 records affected by the county-code change.
Additional error: Record 38 has the same client ID as record 12 from an earlier batch. Record 38 is also inside the 31–45 range, so it may have both a county-code error and a duplicate-ID error.
Most urgent: The duplicate client ID is the highest priority because it can cause records to merge, overwrite, or link the wrong client's data. The county-code errors are next because they affect reporting, funding, and county assignment. The 8 code-14 records and 6 code-22 records should be corrected before the 9:00 a.m. cutoff, but the duplicate must be flagged first so no one merges or deletes the wrong record.
2. Outline the steps you would take between 4:50 p.m. and 9:00 a.m., including who you contact and what you submit.
Read the worked answer
- Stop entering new batches until the code list is verified.
- Pull the paper forms for records 31–45 and mark the 14 suspected county-code errors.
- Verify each code against the current code list, not memory.
- Enter error-log corrections for the 14 county-code records before 9:00 a.m.; note that each needs supervisor initials.
- Flag record 38 and record 12 as a possible duplicate. Do not delete or merge either record. Note which paper form is correct and whether one is a true duplicate or a data-entry error.
- Email your supervisor before leaving with the list: 8 code-14 to 19, 6 code-22 to 23, and the duplicate ID. Ask her to initial the error log at 8:00 a.m.
- At 8:00 a.m., meet the supervisor, obtain initials, and confirm the corrections were accepted. If she is unavailable by 8:30, escalate to the backup supervisor before the 9:00 cutoff.
- Document what was corrected and what remains pending.
3. What process change would you recommend to prevent this in future batches?
Read the worked answer
Recommendations:
- Replace the old county-code list at every workstation and in the shared drive; archive the old list so it cannot be selected by mistake.
- Add the effective date to the top of the code list and require clerks to check it at the start of each batch.
- Build a system warning when an inactive code such as 14 or 22 is entered, or remove those values from the drop-down menu.
- Add a second-person check for county codes on batches over a set size, or a sample check on every batch.
- Use a batch cover sheet listing the code version used and the date.
- Add a duplicate-client-ID check before submission, not only after overnight processing.
These changes address the two root causes: an outdated reference list and no pre-submission duplicate check.