Published October 16, 2026. A primary-source framework for separating employment records, calculating retention triggers, restricting access, and routing lawful-disposal decisions.
Decision this research supports
An HR assistant may administer files, but no single “keep personnel records” rule covers every document. Records have different legal sources, triggers, retention periods, access needs, and disposal holds. This review supports a control map that prevents accidental deletion and indefinite undifferentiated storage. It does not decide coverage or prescribe a universal schedule. The employer’s authorized HR and legal owners must approve the schedule; the assistant can operate it consistently and surface conflicts.
Different sources govern different records
EEOC recordkeeping guidance describes retention obligations for personnel and employment records under federal equal employment opportunity laws. DOL Fact Sheet #21 identifies payroll and time records required under the Fair Labor Standards Act. USCIS provides a distinct retention rule for Form I-9. Their coexistence is the central operational lesson: a folder label such as “employee file” is not a retention category. Each record type needs a source, trigger, minimum period, owner, access class, and hold override.
Create a retention register
The register should list record family, examples, governing source, coverage assumptions, start event, end event, calculation rule, ordinary disposal eligibility, legal-hold override, storage location, and approving owner. Use dates from authoritative systems, not filenames. For event-based rules, preserve the underlying hire, termination, payroll, charge, or case date used by the calculation. If two rules may apply, do not select the shortest by default; route the conflict to the policy owner and record the resolution.
Separate files by access need
Form I-9, medical or accommodation information, payroll records, recruiting materials, performance records, and general personnel documents can expose different information and serve different reviewers. Logical separation supports least privilege and faster production without implying that separation alone satisfies law. Assign individual access, prohibit convenience copies, and log exports where the system allows. The assistant should know whom to contact when a manager requests a category outside the manager’s normal access.
Calculate dates reproducibly
A retention engine can be a controlled spreadsheet or system rule, but it must show its work. Record the source date, calculation version, resulting eligibility date, and any override. Test edge cases such as rehiring, amended payroll, open charges, multiple locations, leave, and late-discovered records. A monthly exception report should identify missing source dates, contradictory employment status, expired holds, and items eligible for owner review. Automatic deletion from incomplete metadata is unsafe.
Holds and investigations supersede routine disposal
A complaint, charge, audit, litigation hold, or agency inquiry may change ordinary handling. The assistant should have a clear stop instruction and confidential escalation route. The hold record needs scope, issuing owner, effective time, custodians or systems, acknowledgement status, and release authority. Do not infer that a matter is closed because normal retention elapsed. Only the authorized owner releases the hold, after which ordinary eligibility can be recalculated and documented.
Disposition needs evidence too
A defensible disposal workflow shows what category was reviewed, which rule and version applied, what holds were checked, who approved, when destruction occurred, and whether backups or downstream systems require additional action. Avoid listing unnecessary personal data in the disposition log. Sampling should confirm both sides of the control: records are not removed early, and eligible records do not remain indefinitely without reason. Exceptions should feed a schedule or metadata correction, not remain a permanent manual workaround.
Method
We reviewed the named primary government sources on October 16, 2026, extracted statements relevant to the workflow, and separated those statements from our operational analysis. We compared the source requirements or guidance with the records an assistant can realistically prepare, route, and preserve. This is desk research, not an experiment, legal opinion, audit, or vendor comparison. A recommendation below is an inference about safer process design; it is not a claim that a checklist guarantees compliance, accuracy, security, or a business outcome.
What an assistant can and cannot own
An assistant can maintain the intake queue, check required fields, attach source records, identify missing information, calculate a due date from an approved rule, route an exception, and preserve the decision trail. The accountable owner must set policy, interpret disputed requirements, approve exceptions, and decide any legal, tax, employment, accounting, security, or customer remedy. Write that boundary into the procedure. A well-run handoff makes retained judgment visible instead of quietly shifting it to the person doing the administrative work.
Implementation pattern
Pilot one representative workflow for two weeks. Give it a named owner, a versioned instruction, a controlled source of truth, required fields, permitted actions, stop conditions, and an escalation route. Collect both ordinary cases and exceptions. At review, examine missing-input rate, queue age, correction rate, approval delay, and whether another authorized person can reconstruct each outcome. Change one control at a time where practical, record why it changed, and set the next review date before expanding scope.
Evidence packet design
A useful evidence packet begins with a stable case identifier and a short cover record: request received, applicable workflow version, current owner, status, due date, and unresolved questions. Attach source records without rewriting them, and create a separate activity log for checks, calculations, communications, approvals, and corrections. Each derived value should point to its inputs and method. Each exception should show what is missing, why it matters, who can decide, and when the case will be revisited. Preserve the submitted version as well as the approved outcome. Restrict sensitive fields to the smallest audience that needs them, and use links to controlled records instead of scattering copies across chat, email, and personal storage. A backup reviewer should be able to locate the governing instruction, reproduce material calculations, distinguish facts from interpretation, and see exactly where accountable judgment entered the process. If that reconstruction depends on memory, the packet is not ready.
Quality assurance and change control
Quality review should combine field validation with consequence-based sampling. Automated checks can detect missing identifiers, invalid dates, duplicate amounts, broken links, and status contradictions; they cannot decide whether a purpose is legitimate, an exception is reasonable, or a conclusion is sound. Define which outputs require pre-release approval and which may be sampled later. Track corrections by category and denominator so a changing workload does not distort the trend. When a rule, source, or system changes, record the change owner, effective date, affected cases, migration decision, and communication. Retest the workflow with an ordinary case, an exception, an unavailable approver, and a correction. The goal is not a perfect-looking dashboard. It is early detection, a recoverable record, and a clear route from evidence to an authorized decision.
Limitations
The cited materials have different purposes and coverage. Federal tax, employment, statistical, consumer-protection, security, and internal-control sources do not automatically apply to every organization, worker, transaction, or jurisdiction. Source pages and underlying rules can change after the checked date. Local law, contracts, industry rules, system design, and the facts of a case may require a different process. Readers should validate applicability with qualified owners and use this framework to organize evidence, not to replace professional judgment.
Buyer conclusion
The staffing decision is strongest when the buyer can name the output, source, authority boundary, acceptance check, and exception owner before delegating. That design lets an assistant contribute useful coordination without being asked to invent policy or make an unreviewed high-consequence decision. Buyers comparing providers should ask to see how work is queued, evidenced, reviewed, corrected, and handed back. The useful proof is a traceable sample and a functioning escalation path, not a broad promise that an assistant can handle everything.
Sources
- Recordkeeping Requirements - U.S. Equal Employment Opportunity Commission. Checked October 16, 2026.
- Fact Sheet #21: Recordkeeping Requirements under the Fair Labor Standards Act - U.S. Department of Labor, Wage and Hour Division. Checked October 16, 2026.
- Retaining Form I-9 - U.S. Citizenship and Immigration Services. Checked October 16, 2026.
