An employment dispute rarely begins with a clean question. One person remembers the offer, another points to payroll, a manager has a different commission plan, and HR discovers that the worker moved months ago. Evidence work is the discipline of rebuilding that relationship from dated records rather than from the loudest recollection.

The useful employment file answers four things: what role and terms were offered, how the relationship actually operated, what changed, and who authorized the change. The file should also identify the worker’s actual location because local law can affect classification, pay, leave, termination and other mandatory rights.

This is why a signed agreement is only one layer. Job descriptions, recruiting records, policy acknowledgments, compensation versions, time or payroll records and manager approvals can show whether daily reality matched the paperwork.

Records to keep and the question each one answers

1. Recruiting and job description

This record helps answer shows the role originally offered, essential functions and stated qualifications. Save the version actually used, not only the current careers page. In an employment file, connect it to the worker’s location, effective date and the manager or HR owner who relied on it. If a later version replaced it, keep the earlier version rather than silently overwriting history.

2. Application/interview record

This record helps answer shows selection criteria and what was communicated. Keep lawful, role-related notes; avoid speculative or discriminatory comments. In an employment file, connect it to the worker’s location, effective date and the manager or HR owner who relied on it. If a later version replaced it, keep the earlier version rather than silently overwriting history.

3. Offer letter and signed agreement

This record helps answer shows agreed title, pay, start date and contractual terms. Preserve signed version and every later amendment. In an employment file, connect it to the worker’s location, effective date and the manager or HR owner who relied on it. If a later version replaced it, keep the earlier version rather than silently overwriting history.

4. Classification analysis

This record helps answer shows why employee/contractor status was chosen. Record actual operating facts and the legal standard checked at that date. In an employment file, connect it to the worker’s location, effective date and the manager or HR owner who relied on it. If a later version replaced it, keep the earlier version rather than silently overwriting history.

5. Compensation plan

This record helps answer shows bonus/commission mechanics. Archive each version with effective dates and acceptance. In an employment file, connect it to the worker’s location, effective date and the manager or HR owner who relied on it. If a later version replaced it, keep the earlier version rather than silently overwriting history.

6. Policies/handbook acknowledgments

This record helps answer shows rules communicated to the worker. Track which version applied during the relevant period. In an employment file, connect it to the worker’s location, effective date and the manager or HR owner who relied on it. If a later version replaced it, keep the earlier version rather than silently overwriting history.

7. Payroll/time/expense records

This record helps answer shows what actually happened. Do not rely on the contract when operational records tell a different story. In an employment file, connect it to the worker’s location, effective date and the manager or HR owner who relied on it. If a later version replaced it, keep the earlier version rather than silently overwriting history.

8. Change approvals

This record helps answer shows who authorized a new title, territory, schedule or pay term. Preserve email/ticket approvals with date and decision maker. In an employment file, connect it to the worker’s location, effective date and the manager or HR owner who relied on it. If a later version replaced it, keep the earlier version rather than silently overwriting history.

Build a relationship timeline

Put the job posting, offer, start date, classification decision, policy acknowledgments, compensation changes, location changes, performance events and exit steps on one chronology. Link each event to the original document. The timeline should show when the paper record and actual management started to diverge.

Preserve operational reality

Payroll records, timekeeping, expense approvals, manager instructions and system access can matter because they show how the relationship operated. Do not assume the contract label answers every classification or wage question. Current federal, state and local rules need fact-specific review.

Keep sensitive data disciplined

Employment evidence can contain personal or sensitive information. Preserve what is needed, restrict access, and follow applicable privacy, retention, litigation-hold and employee-record rules. Evidence preservation is not permission to collect everything indefinitely.

Counsel handoff

Give local counsel a one-page issue summary, worker location, entity chart, controlling agreement, chronology, disputed terms and the records that show actual operation. Put any deadline or proposed termination date at the top.

Jurisdiction note

Employment obligations can change with the worker’s location, employer entity, role, pay basis and local mandatory law. Federal U.S. guidance cited here is a reference point, not a substitute for state, local or non-U.S. analysis. This is general information, not legal advice. For a material hire, classification change or termination, confirm the current rules in the actual work location with qualified counsel. For an evidence file, preserve the dated source that supports the conclusion; a recollection created after a dispute is weaker.

Employment evidence audit: five practical questions

Does the file show what the candidate was originally told? Save the job description or requisition version used during recruitment, the offer letter, and any written negotiation that changed pay, title, work location or start date. A current job description created after a dispute does not answer what was represented at hiring.

Does the file show who could approve a change? Compensation plans, remote-work arrangements and reporting lines often change through managers. Preserve the approval path and the effective date. Where an informal message conflicts with the signed file, do not silently choose the version the company prefers; flag the inconsistency for review.

Does the file show the worker’s real operating conditions? For classification or wage issues, records of schedule, supervision, tools, expenses, time, payment method and business independence can be more informative than the contract label. The relevant test depends on current law and location.

Does the file contain the policy version that actually applied? Keep historical handbook, leave, expense and commission versions with acknowledgment dates. Replacing an old policy file with the newest PDF destroys context.

Can the file survive a manager change? If the only explanation lives in the memory of a departing supervisor, the record is fragile. Turn recurring approvals and exceptions into system fields or dated notes.

What not to do when the dispute begins

Do not backfill missing approvals, rewrite interview notes, change timestamps, or delete embarrassing messages. Preserve the existing state and create a separate remediation record. If litigation is anticipated, document-preservation duties may change; obtain local legal advice promptly.

The evidence file should also avoid irrelevant overcollection. More personal data creates privacy and security exposure without necessarily improving the legal analysis. Keep collection proportionate to the issue and the applicable recordkeeping obligations.

Final employment-file check

Before the file leaves HR, confirm that every compensation document has an effective date and that payroll reflects the same version. Confirm the work location in the HR system, the reporting line, and whether the worker’s status or role changed after hire. If a local-law question remains open, identify it explicitly rather than hiding it inside a generic “legal reviewed” label.

A reviewer should be able to distinguish the signed terms from day-to-day practice. If those layers disagree, the mismatch is the issue; the evidence package should make it visible.

Sources

Related Reading