Last updated: June 2026
Not legal advice. Recordkeeping and retention requirements vary by jurisdiction and change over time. Confirm your obligations in each location with qualified counsel.
TL;DR: A workforce record is audit-ready when it can show, for any single time or pay decision, what was decided, by whom, when, on what basis, and what changed. As of 2026, a U.S. Department of Labor wage-and-hour investigation typically requests two to three years of payroll and time records, and a willful violation extends that review from two years to three. Build every record around nine elements (the people, the raw time facts, the pay basis, the computation inputs, the schedule story, the change history, overrides with reasons, supporting notes, and retrievability), retain to the longest window that applies across your jurisdictions (under the FLSA, payroll three years and time records two; Canada three; Ontario vacation five), and capture overrides with a documented reason and a full audit trail rather than silently blocking them.
In this post:
A workforce record is audit-ready when, for any single time or pay decision, it shows what was decided, by whom, when, on what basis, and what changed. As of 2026, regulators, auditors, and unions can all ask an employer to reconstruct one such decision years after it was made. Most systems capture the decision. The defensible ones capture the full history behind it.
Picture the request that forces the question. A former employee files a wage claim, and you have ten days to show exactly why one worker was paid what they were paid on a shift worked twenty-six months ago. Not your policy. Not your intentions. The record: the hours, the rate, the overtime math, who approved it, and every change made since. That is the real test of a workforce system, and it is the one this guide is built to answer.
Wage-and-hour enforcement is active and records-driven, which raises the cost of a thin record. Recent recoveries run into the billions, and an investigation reaches directly into an employer's time and payroll files going back two to three years. A record that cannot answer the request is the exposure.
The Economic Policy Institute reports more than $1.5 billion in stolen wages recovered for workers between 2021 and 2023 across federal, state, and local efforts. The U.S. Department of Labor's Wage and Hour Division alone recovered more than $1 billion for over 615,000 workers in investigations concluded between January 2021 and September 2024.
When an investigation opens, it reaches into your files. Under the Fair Labor Standards Act, WHD investigators inspect and transcribe records and interview employees to verify time and payroll. They typically request two to three years of payroll and time records for current and former staff, then look for unpaid overtime, overtime calculated on base wage only, auto-deducted meal breaks that were actually worked, and minimum-wage shortfalls. A willful violation extends the back-wage window from two years to three.
An audit-ready workforce record contains nine elements: the people involved, the raw time facts, the pay basis, the computation inputs, the schedule story, the change history, any overrides with reasons, the supporting notes, and retrievability within the retention window. Together they let any single decision stand on its own, without reconstruction after the fact.
Items six and seven are where most systems quietly stop. They store the final value but not the history behind it, or they treat an override as an error to suppress rather than an event to record.
Retention is not one number. It varies by jurisdiction and record type, and a multi-jurisdiction employer must retain to the longest applicable window for each. Under the FLSA, that means three years for payroll records and two for the underlying time records, with Canadian, provincial, and Fair Workweek rules layering their own minimums on top.
| Jurisdiction | Record type | Retention period |
|---|---|---|
| US Federal (FLSA) | Payroll records, CBAs, sales/purchase records | At least 3 years |
| US Federal (FLSA) | Time cards, schedules, wage-rate tables, deduction records | At least 2 years |
| US Federal (FLSA) | Plain-language summary: payroll vs. supporting records | 3 yr / 2 yr |
| Canada (federal) | Hours and wage information after work is performed | At least 3 years |
| Canada (federal) | Employment record after termination | At least 36 months |
| Ontario (ESA) | Hours worked, wage statements | 3 years |
| Ontario (ESA) | Vacation time and vacation pay records | 5 years |
| US local (Fair Workweek: SF, LA, Evanston) | Schedules, changes, consent, predictability pay | 3 years (Evanston: or the duration of any claim) |
| EU/UK (GDPR) | Worker personal and payroll data | No fixed period: a documented, justified policy |
GDPR is the instructive one. It sets no fixed period and instead requires a documented retention policy that you can justify per category of data. So the operating standard across a complex footprint is simple to say and hard to fake: keep everything, keep it organized, keep it producible.
In a unionized workplace, the workforce record becomes evidence. When discipline or a pay decision is challenged, the employer carries the burden of proof and must produce the records and notes behind the decision, including informal ones. A record that shows the rule applied and the steps followed is the defense.
The employer carries the burden of proof, and the union is entitled to the notes and records the employer used to make the decision. The widely cited Seven Tests of Just Cause, drawn from a 1966 arbitration, ask whether the employer ran a fair investigation and held substantial proof before acting.
For an operation running multiple collective bargaining agreements across sites, that is a daily reality, not a rare event. The seniority rule, the overtime offer, the shift bid: each one can be grieved, and the defense is the record. If the system that made the decision can also show the rule it applied and the steps it followed, the grievance gets shorter.
Turn the nine-element anatomy into a checklist and hold any system against it.
Does it keep the full change history, not just the latest value?
Does it record an override with the reason and the person behind it, rather than discarding it?
Can it produce a complete record for one worker, on one shift, across every jurisdiction you operate in, inside the retention window?
Two of those are where evaluations should focus, because they are where tools most often fall short: the override captured with its reason, and the record that survives the full retention window. That focus on the override and the trail is a design choice, and it is the one WorkAxle made. When a scheduling or pay rule is at risk of being broken, the platform warns and lets an authorized manager proceed, then captures the override, the reason, and the full audit trail behind it. Nothing is silently blocked, and nothing is silently overwritten. The record explains itself later. That model is what let a national guarding firm go live in about two months while automating 13 collective agreements in a single deployment, and it is the discipline behind a SOC 2 examination completed with zero deficiencies.
Audit-readiness is easiest to lose at the worst moment: during a vendor change, when years of history can be orphaned in the old system. Anyone planning a migration off a legacy WFM platform should treat record continuity as a first-class requirement, not an afterthought.
An audit-ready record is not a feature you switch on the week an auditor calls. It is the byproduct of a system that treats every time and pay decision as something it may have to explain years later. Build on that, and the request that lands on your desk stops being a fire drill and becomes a query you can answer.
Investigators typically request two to three years of payroll and time records for current and former employees, then verify overtime, break handling, deductions, and minimum-wage compliance against them. Willful violations extend the back-wage review period from two years to three.
Under the FLSA, payroll records for at least three years and supporting time records for at least two. Canada's federal code requires hours and wage data for at least three years. Fair Workweek scheduling records are commonly three years. Multi-jurisdiction employers should retain to the longest window that applies.
A workforce audit trail is a chronological, tamper-evident, timestamped log of every change to a time or pay record: the prior value, the new value, who made it, when, and why, so the decision can be reconstructed later.
Leading workforce management systems warn when a rule is at risk and allow an authorized override, capturing the reason and a full audit trail. The value is the defensible record of what happened and why, not silent blocking that hides the exception.
WorkAxle is a compliance-first enterprise workforce management platform built for multi-jurisdiction, multi-union operations. It warns when a scheduling or pay rule is at risk, allows an authorized override, and captures the override, the reason, and a full audit trail, so each time and pay decision is documented and can be reconstructed later.
The employer carries the burden of proof and must produce the records and notes behind the decision. A record showing the rule applied, the steps followed, and any override with its reason is the defense.
This article is for general information and is not legal advice. Recordkeeping and retention requirements vary by jurisdiction and change over time. Confirm your obligations in each location with qualified counsel.
Related reading:
If your operation spans multiple jurisdictions or collective agreements, bring one real pay decision to a demo. We will show you how WorkAxle captures the rule that applied, the override and its reason, and the full audit trail behind it, so the record holds up two years later when someone asks.