Human Resources Outsourced research
Measuring cycle time for employee file from request to verified close
A grounded HR outsourcing note for HR and people operations leaders: employee file with explicit evidence, decision rights, and a verified close.
Question and scope
A useful scope is narrow enough to reproduce and specific enough to show whether missing I-9 is being detected. State how duplicate requests are identified and whether they are merged, linked, or counted separately. Record how corrections, reopens, and duplicate requests are treated so file completeness cannot be inflated by reclassification. Record the exclusions in advance so a difficult case cannot be removed after the result is known. If the case moved between owners, include both owner periods in the review note and name the handoff time. The scope is one defined population of employee file cases observed from first request through verified close in the applicant tracking system. The unit definition should be stable enough that two reviewers can classify the same case the same way. The definitions should be short enough to use at the queue and precise enough to defend in a review with employee. Write the decision the study is meant to inform before choosing the measure. Keep the review note with the case so the next sampler does not have to reconstruct the decision from memory.
Population and unit
When several I-9 record updates belong to one request, state whether the request or each update is the unit and apply that rule consistently. A denominator that changes during the window should be reported separately for each period. The definition should make it possible to classify a case without asking the person who did the work. If a request was reopened after the window, keep it in the original population and report the later event separately. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. Record the opening count by owner and channel, because a single total can hide a queue concentrated in one person. A denominator that changes during the window should be reported separately for each period. If the definition of leave response time changes, keep the old and new values side by side for the transition period. Separate cases opened before the window from cases opened and closed inside it, and report both counts. At Human Resources Outsourced, the employee file review should end with a dated note and a named owner for the next check.
Definitions and measures
Measure elapsed time from the first recorded request to the verified destination update, and report waiting intervals separately. Test the data dictionary on a small set of cases and revise ambiguous fields before the main sample. Record the person who approved the definition and the date it became effective. Keep a change log for every definition adjustment and the date it took effect. If the evidence is sensitive, record the approved reference and access path rather than copying the content. If the definition of completion changes, keep the old and new rules side by side for the transition period. Use a stable case key and a separate identity crosswalk stored in an approved system. A completeness measure should name the required fields and the evidence state; an overall percentage is not reproducible. State how duplicate, cancelled, and reopened cases enter the numerator and denominator. The note should distinguish what was observed, what was inferred, and what still needs an owner decision.
Data dictionary and evidence
The data dictionary should name the allowed values for status, exception reason, owner, and close evidence. Record the extraction time separately from the event time so a late entry is visible. Store sensitive evidence in the approved repository and keep only the reference in the analysis file. Keep the original request, the approval, and the destination value linked to the same key. Record this decision in the study log with the case key, the review date, and the person who approved the classification. Record the version or date of the performance review and the policy library value so a later reviewer can see what was known at the first action. Name the required fields for each article type and mark conditional fields in the dictionary. Record the source identifier, the field name, the observation time, and the reviewer for every extracted value. Do not use a zero or an empty string to represent missing evidence. Keep the evidence reference beside the coded value so a reviewer can test the same case without rebuilding the queue. The data dictionary should name the allowed values for status, exception reason, owner, and close evidence. Give every case a study key that is not the client name, member number, or candidate email. Keep the source reference and the coded value in the same row, and do not overwrite the original with a later correction. Record the source location, not just the file name, so a reviewer can reopen the exact evidence. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it.
Sampling and collection
Use a random or systematic start rule for the first case, then take consecutive cases within each stratum. Collect the exception reason and the action taken before the close so the analysis can separate detection from resolution. Use a random or systematic start rule and then take consecutive cases within each stratum. Record the date of the sample and the version of the queue export. At Human Resources Outsourced, the reviewer should be able to explain this step to client HR lead from the case record alone. Stop expanding the sample only when the review question is answered, not when the result starts to look favorable. A second reviewer should re-extract a small subsample and record disagreements before the full analysis. A sample of recent closures can miss the oldest unresolved work, which is often the most informative. Keep a table of planned, eligible, selected, and reviewed counts for each stratum. Use the same note in the case file and the study extract; do not create a second version in a personal document. A convenience sample of recently closed cases will overrepresent easy work and underrepresent the tail that needs attention. Use the same collection form for every case and keep the original record linked to the extracted fields. Stratify by risk, channel, and owner so the sample is not dominated by the easiest queue. A case that is difficult to access is still part of the frame; report the access failure rather than replacing it silently. When a case needs an exception, record the reason, the owner, and the date before continuing the review.
Analysis and reporting
If the sample is small, report the instability and the cases that drive the result instead of a precise-looking percentage. The analysis should end with the decision the evidence can support and the decision it cannot support. Show the unresolved cases by owner, age, and dependency instead of reporting a single completion percentage. End with the decision the evidence supports and the decision it does not support. Keep the measurement note short enough to read with the case and specific enough to support the reported offboarding closure. Separate observation from interpretation; a high completion rate on a small easy sample is not evidence of a strong control. Report denominators with every rate and separate missing evidence from negative evidence. Use a simple before-and-after comparison only when the definitions and observation window are the same. When a measure is based on a small sample, state the case count and avoid ranking owners by the result. If two reviewers disagree, preserve both classifications until the definition or the evidence is resolved.
Limitations
Small samples are sensitive to one case; report the instability instead of presenting a percentage as a stable rate. The cited sources describe recordkeeping, privacy, security, or control practice; they do not supply a local benchmark. Name the follow-up evidence that would reduce the largest uncertainty. If the reviewer performed the work, use a second reviewer for a subsample and report the disagreement. Link the observation to the exact field in the HRIS and to the employee file that supports it. The cited public sources frame recordkeeping, privacy, security, or control practice; they do not provide a local result. Changes in staffing, access, or the applicant tracking system during the window can create a difference that is not a process effect. Record the response or access problems that prevented a case from being reviewed. Report the limits of the applicant tracking system data, including fields that were unavailable or changed. Do not let a summary written later replace the evidence that was available at the first decision.
Review and next action
Name the owner who will read the result and set a review date before the sample is collected. Choose one change and one measure to test it; a long action list is hard to evaluate. Set the next sample date before closing the review, so the action does not drift. Schedule the next review before the action begins, not after the result arrives. If the case moved between owners, include both owner periods in the review note and name the handoff time. Choose one next action: fix the source, simplify the benefits enrollment, change the queue, adjust access, or pause the work until the owner decides. Choose one change and one measure to test it; a long action list is hard to evaluate. If the action requires a policy or access change, route it to the owner and record the decision. Link the action to the case evidence that prompted it, not only to the meeting notes. Keep the review note with the case so the next sampler does not have to reconstruct the decision from memory.
Sources
HR operations support
Use the method to define evidence and ownership. Review the service scope.