Human Resources Outsourced research
How consistent is termination documentation?
A proposed protocol for comparing how different managers document a termination.

Question and scope
This is a proposed research protocol, not a report of completed findings. It asks how consistently terminations are documented. The result would describe the documentation, not the manager. Record the exception and the person who approved it.
The protocol does not measure whether the termination was fair. It measures whether the record was complete. Ask whether a new reviewer could act on the record without a conversation. Record the exception and the person who approved it.
Population and unit of analysis
Define the population as terminations during a stated window. The unit is one termination, with the decision, notice, access, and final pay recorded. Separate what was observed from what was assumed. Review the first few notes together before the process expands.
Link the termination to the employee so the same event is not counted twice. Separate what was observed from what was assumed. A control that depends on memory is not yet a control. If the source is unclear, route the question instead of guessing.
Definitions and measures
Define consistency as the same fields and approvals across managers. Define completeness as the presence of the required records. Use the same format for every handover so the next reader can scan it. Review the first few notes together before the process expands.
Report both separately. Name the owner in the same line as the action. A control that depends on memory is not yet a control. Use the same format for every handover so the next reader can scan it.
Evidence standard
Use the termination file and the access log. A file without the approval is weak. Record the exception and the person who approved it. Ask whether a new reviewer could act on the record without a conversation.
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 terminations. If sampling is necessary, stratify by department. Ask whether a new reviewer could act on the record without a conversation. If the source is unclear, route the question instead of guessing.
Pilot the review on a few files and compare the reviewers. Clarify how a resignation is treated. Record the date and the source so the next reviewer can repeat the check. Ask whether a new reviewer could act on the record without a conversation.
Analysis and reporting
Report consistency and completeness by department. Show the files without the approval. Ask whether a new reviewer could act on the record without a conversation. Keep the boundary visible in the place where the work is assigned.
Present the results as a description of the documentation, not a judgment about the manager. Record the date and the source so the next reviewer can repeat the check. Write the deadline as a date and a local time. Ask whether a new reviewer could act on the record without a conversation.
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 access removal may be recorded by IT. Update the template when the same question appears twice. Record the date and the source so the next reviewer can repeat the check. If the source is unclear, route the question instead of guessing.
Review cadence
Repeat the review after a process change or at the same interval each year. Compare the same departments. Record the date and the source so the next reviewer can repeat the check. Test the rule on one real file before applying it to the team.
Assign the follow-up to the HR lead and set a date. The protocol should produce a specific decision about the termination checklist. Record the exception and the person who approved it. A control that depends on memory is not yet a control.