Two people can argue for weeks about whether overtime or commission is owed and still be no closer to an answer. The file usually moves when the right records appear: the workweek definition, the actual hours, the compensation plan in force, the payroll calculation, and the communications that show what management knew.

The most useful evidence is not necessarily the most dramatic. A routine system log can be more important than a heated email. A version-controlled commission plan can matter more than a manager’s memory. The purpose of an evidence file is to make the wage question reproducible.

Start with the symptom, then identify the record that can test it

If the complaint is “my overtime is short,” you need workweek and regular-rate records. If it is “I worked after clocking out,” you need evidence of activity and employer knowledge. If it is “my commission disappeared,” you need the plan version, sale history and any cancellation or clawback event.

A useful evidence map looks like this:

Symptom Records that usually matter
Missing overtime workweek definition, timecards, schedules, payroll detail, bonuses/commissions
Off-the-clock work system logins, messages, tickets, call logs, manager instructions
Commission dispute signed/acknowledged plan, plan amendments, CRM records, shipment/payment data
Wrong regular rate payroll earning codes, incentive reports, bonus terms, overtime calculation
Late payment earning date, payroll cutoff, statutory pay date, bank/payment confirmation

The table does not decide the law. It prevents the investigation from collecting documents at random.

Keep the workweek record and the pay-period record separate

One of the most common evidence mistakes is assuming the pay period proves the overtime unit. Federal overtime generally uses a fixed workweek. A payroll system may pay every two weeks, twice a month or monthly, but the overtime analysis still needs the underlying workweek.

Save the employer’s written workweek rule, configuration screenshots, time-system settings and any historical changes. If the business changed its workweek, keep records showing when the change occurred and whether it was intended to be permanent.

Preserve raw time evidence before it is summarized

A spreadsheet that says “42 hours” is less useful than the records from which 42 was calculated. Keep the original time entries, edit history, approvals and exception reports where available.

For off-the-clock questions, preserve records that independently show activity. A VPN login does not prove continuous work for three hours, but it can corroborate that work occurred. A single message may not establish duration, but a sequence of customer calls, ticket updates and manager replies may create a clearer timeline.

Do not convert everything into screenshots if an export exists. Native CSV, system reports and audit trails are easier to sort and verify.

Commission plans need version control

A commission plan should be treated like a contract record, not a sales presentation. Preserve the exact version applicable to the disputed sale and note when each revision became effective.

Important fields often include:

  • what event makes a commission earned;
  • whether customer payment is required;
  • treatment of refunds, returns and cancellations;
  • territory or account ownership rules;
  • split-credit rules;
  • timing of payment;
  • clawback provisions;
  • treatment on resignation or termination;
  • who has discretion to modify or approve exceptions.

If a manager says, “That has always been our rule,” find the written plan and historical evidence. Memory is especially unreliable after incentive plans change.

Payroll earning codes are evidence too

Many disputes come from a mapping error rather than a policy dispute. A nondiscretionary bonus may have been paid but coded in a way that kept it out of the regular-rate calculation. A commission may have been attributed to the wrong period. A shift premium may have been mislabeled.

Keep the payroll register, earning-code definitions, calculation logic and any manual adjustments. If possible, rebuild one representative week from raw records to final net pay. Another reviewer should be able to follow the same path and get the same number.

Manager knowledge can be the hidden fact

For an hours-worked claim, the employee’s activity is only part of the file. Ask what supervisors saw, approved, encouraged or could reasonably observe.

Preserve:

  • repeated late-night assignments;
  • instructions to finish tasks after clock-out;
  • staffing levels that made unpaid extra work foreseeable;
  • edits to time records;
  • messages refusing overtime approval after work was already performed.

This evidence can matter more than a policy that says “no unauthorized overtime.” A policy is relevant, but it is not a substitute for what actually happened.

Do not destroy context when exporting messages

A screenshot of one sentence can be misleading. Keep enough of the thread to show the date, participants and what the message responded to. For chat systems, use an export where available and record the collection date.

If privacy or unrelated employee information is mixed into the thread, preserve the original under appropriate access controls and create a review copy with irrelevant personal information minimized. Evidence integrity and privacy can coexist.

Keep a chronology, not just a folder

Create a dated timeline with five columns: event, source record, amount/hours involved, person responsible, and unresolved question.

For example, “March 4: customer paid invoice; CRM marks sale complete; plan says commission earned after payment; payroll cutoff was March 6; commission not on March 13 payroll.” That entry turns several documents into a testable question.

Chronology is especially valuable when a dispute spans plan amendments, leave, a promotion, territory changes or termination.

Separate originals, working copies and conclusions

Use three folders:

  1. Original evidence — unchanged exports and documents.
  2. Working analysis — spreadsheets, calculations and annotations.
  3. Conclusions/communications — letters, findings and settlement drafts.

Do not overwrite original files with highlighted or renamed versions that make provenance unclear. Hashes or document-management logs are helpful for sensitive or high-value disputes.

What to request if records are incomplete

Employees may not have access to payroll configuration or internal logs, and employers may not have perfect personal records. Make a gap list rather than guessing.

A useful gap request says exactly what is missing: “commission plan version effective April 1–June 30,” “audit history for time edits on May 12,” or “earning-code definition for bonus code NDB.” Specific requests are easier to answer than “send all payroll records.”

The legal boundary

Under the FLSA, employers have recordkeeping obligations, and the Wage and Hour Division asks complainants for basic employer, work and pay information; pay stubs and personal hour records can also be useful. State and local laws may impose additional records, retention periods or wage-statement rules.

This article is general information, not legal advice. Evidence relevance, preservation duties, discovery rules and privacy requirements vary by jurisdiction and by whether a dispute is internal, before an agency, in arbitration or in court. For a live dispute, confirm local requirements before deleting records, contacting witnesses or making a final admission.

The practical rule is simple: if another reviewer cannot reconstruct the disputed week or commission event from the file, the evidence package is not finished.

Build an evidence map, not an evidence dump

A large folder can still be a weak file if nobody can explain why each record matters. Add a one-page evidence map with four columns: issue, record, what the record can establish, and what it cannot establish. A badge-swipe report may help show presence at a facility, for example, but it does not automatically prove compensable work for every minute between entry and exit. A CRM timestamp may show that an employee was active after scheduled hours, but it may not show how long the activity took. A payroll register can show what was paid, but it may not reveal what should have been included in the regular rate.

This distinction keeps circumstantial evidence useful without overstating it. The map should also identify conflicts. If a manager says after-hours email was discouraged but weekly messages repeatedly assign deadlines for early the next morning, link both items to the same issue. If a commission plan says credit is earned on shipment but payroll reversals appear after customer returns, record the version of the plan and the reversal data together. Contradictory records are not a reason to discard the file; they are a reason to document the factual question precisely.

Preserve the audit trail when calculations change

Wage calculations often evolve. A first pass may omit a bonus, a later pass may add reconstructed time, and a third may correct a commission allocation. Never overwrite the only copy of the prior calculation. Save dated versions and keep a short change log stating what changed, why it changed, and which source record triggered the revision.

That audit trail matters because a clean final spreadsheet can otherwise hide how much judgment went into it. It also makes settlement discussions safer: the parties can discuss the effect of one disputed assumption without accidentally changing five others. For an employer, it helps payroll and legal teams distinguish a system correction from a litigation position. For a worker, it helps preserve the difference between personal estimates and amounts later supported by records.

The best evidence file therefore has three layers: originals that are preserved unchanged, working copies used for sorting and calculation, and a concise explanation that links the two. That structure is more valuable than collecting every possible screenshot.

Sources

Related Reading