Human Resources Outsourced research
How complete is the employee file at audit?
A proposed protocol for measuring whether each required employee document is present, dated, and owned.

Question and scope
This is a proposed research protocol, not a report of completed findings. It asks how complete the employee file is at audit. The result would describe the file, not the employee. A short note with four fields is easier to use than a long narrative.
The protocol does not measure whether the employee was a good hire. It measures whether the required records were present. Keep the boundary visible in the place where the work is assigned. Separate what was observed from what was assumed.
Population and unit of analysis
Define the population as employee files active on a stated date. The unit is one file, with the required documents, the dates, and the owner recorded. Keep the original note beside the corrected version. Use the same format for every handover so the next reader can scan it.
Link the file to the employee so the same document is not counted twice. Name the owner in the same line as the action. Separate what was observed from what was assumed. Review the first few notes together before the process expands.
Definitions and measures
Define completeness as the presence of the required documents. Define currency as the document being dated within the required window. A short note with four fields is easier to use than a long narrative. Keep the evidence with the record rather than in a separate log.
Report completeness and currency separately. Keep the boundary visible in the place where the work is assigned. A control that depends on memory is not yet a control. Update the template when the same question appears twice.
Evidence standard
Link each document to the file and the rule. A note that says on file without the document is weak evidence. Separate what was observed from what was assumed. If the source is unclear, route the question instead of guessing.
Record the date and the reviewer. Keep the boundary visible in the place where the work is assigned. Keep the evidence with the record rather than in a separate log. Test the rule on one real file before applying it to the team.
Sampling and collection
Use a census of the files if the volume is manageable. If sampling is necessary, stratify by role and location. Keep the original note beside the corrected version. Separate what was observed from what was assumed.
Pilot the review on a few files and compare the reviewers. Clarify how a pending document is treated. Ask whether a new reviewer could act on the record without a conversation. Keep the evidence with the record rather than in a separate log.
Analysis and reporting
Report completeness and currency by role and location. Show the files with no owner. Write the deadline as a date and a local time. A short note with four fields is easier to use than a long narrative.
Present the results as a description of the file, not a judgment about the employee. Ask whether a new reviewer could act on the record without a conversation. Name the owner in the same line as the action. Update the template when the same question appears twice.
Limits and sources of error
The file may be stored in a different system. State the systems included. Ask whether a new reviewer could act on the record without a conversation. If the source is unclear, route the question instead of guessing.
The document may be missing but the employee may have completed the requirement. State the evidence used. Keep the original note beside the corrected version. If the source is unclear, route the question instead of guessing.
Review cadence
Repeat the review after a rule change or at the same interval each quarter. Compare the same roles and the same definition. Record the date and the source so the next reviewer can repeat the check. Keep the boundary visible in the place where the work is assigned.
Assign the follow-up to the HR owner and set a date. The protocol should produce a specific decision about the file checklist. If the source is unclear, route the question instead of guessing. Separate what was observed from what was assumed.