Human Resources Outsourced research
Testing evidence completeness in I-9 record without a convenience sample
A grounded HR outsourcing note for HR and people operations leaders: I-9 record with explicit evidence, decision rights, and a verified close.
Question and scope
Write the primary question and one supporting question, then stop; a long list of questions usually hides an undefined unit. If the population is too small to sample, say so and report the complete set rather than implying a larger study. Define the start event, the stop event, the pause rule, and the treatment of a missing benefits enrollment before collecting data. Record the exclusions in advance so a difficult case cannot be removed after the result is known. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. This protocol asks how I-9 record can be described from the operational record in HR outsourcing without turning a completion count into a quality claim. Exclude a reopened case only when the reopening did not create a new requirement; keep the exclusion count and reason. Record how corrections, reopens, and duplicate requests are treated so benefits change cycle cannot be inflated by reclassification. State whether the study covers one team, one client, or all cases in the defined service. At Human Resources Outsourced, the I-9 record review should end with a dated note and a named owner for the next check.
Population and unit
Record how duplicate requests were matched, merged, or kept separate, because that choice changes the denominator. Record the queue at the start and end of each observation day so additions and withdrawals are visible. The stop event should be the verified destination update, not the last message in the thread. Separate cases opened before the window from cases opened and closed inside it, and report both counts. If the evidence is sensitive, record the approved reference and access path rather than copying the content. The unit is one I-9 record case, from the opening request to the verified close, and linked events stay with that case. Define whether a request that generates several performance review updates is one case or several before counting begins. If the definition of offboarding closure changes, keep the old and new values side by side for the transition period. If the queue was archived during the window, report the loss and exclude the affected period rather than assuming the cases were resolved. The note should distinguish what was observed, what was inferred, and what still needs an owner decision.
Definitions and measures
Define how a correction after close is linked to the original case and whether it creates a new case. Do not store sensitive content in the analysis file when a reference to the approved repository is enough. A duplicate request is a separate intake event even when it points to the same underlying need; record the link. Give one concrete example and one boundary case to each reviewer before collection begins. Record this decision in the study log with the case key, the review date, and the person who approved the classification. Name the owner who can declare a case complete, and record that role in the data dictionary. Test the data dictionary on a small set of cases and revise ambiguous fields before the main sample. A completeness measure should name the required fields and the evidence state; an overall percentage is not reproducible. If two reviewers disagree, preserve both classifications until the definition is clarified. Keep the evidence reference beside the coded value so a reviewer can test the same case without rebuilding the queue.
Data dictionary and evidence
Use a pseudonymous case key and keep the identity crosswalk in an approved system with restricted access. Use a controlled list for exception reasons; do not let free text become the analysis category. 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. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it. Keep free-text notes separate from coded fields so the analysis does not depend on inconsistent wording. Test the dictionary on a case with a missing employee file and a case with a corrected value. Run a five-case pilot before the full sample and revise any field that two reviewers interpret differently. A case key should remain stable if the case moves between owners or changes status. At Human Resources Outsourced, the reviewer should be able to explain this step to client HR lead from the case record alone. Keep free-text notes separate from coded fields so the analysis does not depend on inconsistent wording. Use a controlled list for exception reasons; do not let free text become the analysis category. Record the source identifier, the field name, the observation time, and the reviewer for every extracted value. Archive the dictionary with the study so a later reviewer can reproduce the categories. Use the same note in the case file and the study extract; do not create a second version in a personal document.
Sampling and collection
Sample across the full observation window, including the days when the queue was busiest and the days when coverage changed. Use the same collection form for every case and keep the original record linked to the extracted fields. A sample of recent closures can miss the oldest unresolved work, which is often the most informative. Use a random start and a fixed interval when the frame is ordered, and record both. When a case needs an exception, record the reason, the owner, and the date before continuing the review. A convenience sample of recently closed cases will overrepresent easy work and underrepresent the tail that needs attention. Collect the case from the HRIS, the I-9 record, and the approval record, and stop at the verified close. If a stratum has fewer cases than planned, report the smaller count instead of replacing it with a convenience case. If a selected case is out of scope, replace it only with the next case in the same stratum and record the substitution. Keep the measurement note short enough to read with the case and specific enough to support the reported offboarding closure. Use consecutive I-9 record cases where possible, then stratify by owner, channel, and risk class. A second reviewer should re-extract a small subsample and record disagreements before the full analysis. Stratify by risk, channel, and owner so the sample is not dominated by the easiest queue. Keep a table of planned, eligible, selected, and reviewed counts for each stratum. If two reviewers disagree, preserve both classifications until the definition or the evidence is resolved.
Analysis and reporting
Keep case-level detail available for review, because a summary chart without records cannot support a decision. For I-9 record, report the age distribution and the share of cases waiting on a named owner. Report the number of cases that changed status after the first extraction and how the change was handled. Report the number of cases that drive a small-sample result and the direction of the effect. Link the observation to the exact field in the HRIS and to the I-9 record that supports it. Separate observation from interpretation; a high completion rate on a small easy sample is not evidence of a strong control. For I-9 record, report the age distribution and the share of cases waiting on a named owner. 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. Do not let a summary written later replace the evidence that was available at the first decision.
Limitations
The record may be incomplete, delayed, or maintained outside the team, so the method cannot infer missing work from a clean summary. Selection bias remains when the team chooses cases that are easy to open or owners who are likely to cooperate. Do not treat a missing record as proof that the work did not happen; it is evidence about the record. State what a follow-up study would measure and which population it would include. If the case moved between owners, include both owner periods in the review note and name the handoff time. Small samples are sensitive to one case; report the instability instead of presenting a percentage as a stable rate. Changes in staffing, access, or the benefits portal during the window can create a difference that is not a process effect. Report the limits of the benefits portal data, including fields that were unavailable or changed during the window. State what a follow-up study would measure and which population it would include. Keep the review note with the case so the next sampler does not have to reconstruct the decision from memory.
Review and next action
Report what moved, what did not, and which result is still unexplained. If the result is inconclusive, say so and choose a narrower question rather than claiming a trend. Report the action result even if the change did not work; a failed test is still evidence. If the action needs approval, record the approver and the date before the change is applied. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. If the action affects incorrect employee record, route it to client HR lead and record the approval before implementation. A quality review should end with a testable next step, not a general instruction to improve. Close the review only when the owner has accepted the result and the next check is scheduled. Link the action to the case evidence that prompted it, not only to the meeting notes. At Human Resources Outsourced, the I-9 record review should end with a dated note and a named owner for the next check.
Sources
HR operations support
Use the method to define evidence and ownership. Review the service scope.