It’s 7:30 AM on a Monday in late April. You walk into your office in Phoenix, coffee in hand, and the receptionist hands you a certified letter from the Department of Labor. A former employee, the guy you let go six months ago for chronic lateness, has filed a §216 collective action alleging unpaid overtime against your construction company. He’s not alone on the complaint: he claims to represent forty-seven similarly situated workers. His lawyer is asking for two years of time records, payroll stubs, and the company’s written timekeeping policy. The DOL investigator wants to schedule a site visit by Friday.
You walk back to the warehouse. The foreman pulls a banker’s box from a shelf, paper timesheets going back twenty-four months, written in three different handwritings, some entries in pencil that have smudged into the ones below. About a third of the sheets are missing for months when the original foreman quit. The remaining ones are inconsistent: some show clock-in to the minute, others say “8 to 4-ish.” You realize, with a feeling that drops your stomach to the floor, that you can’t actually prove what any of those forty-seven workers did. You can only argue.
This is the moment FLSA compliance becomes existential instead of theoretical. The Fair Labor Standards Act doesn’t require a specific timekeeping technology. It doesn’t require GPS, biometrics, fingerprints, or any particular software. What it requires, and what the DOL investigator will measure your defense against, is contemporaneous, accurate, retainable evidence of hours worked. In 2026, the cheapest and most defensible way to produce that evidence is GPS-stamped clock-ins from a mobile app. Everything else is a slower, weaker version of the same thing.
Run one real pay period of GPS-stamped clock-ins, and see what your FLSA defense actually looks like before the next DOL letter.
No credit card, up and running in 2 minutes.
Open your trialWhat the DOL audit playbook actually looks like
Wage and Hour Division investigators follow a documented protocol. The first request, almost always, is for time records under 29 CFR §516.2, daily start time, end time, total hours, all meal periods, and any other intervals of non-work time. They want them by employee, by day, for the period under investigation. If you produce typed timesheets that were generated after the fact, even if the underlying paper sheets exist, the DOL treats them as reconstructed records. The burden of proving accuracy now sits with you, not with the worker. And reconstructed records carry a credibility penalty that you cannot recover from with adversarial litigation tactics.
The Supreme Court’s decision in Anderson v. Mt. Clemens Pottery (1946) established the rule that still governs FLSA cases: when the employer’s records are inadequate, the worker can prove damages by “just and reasonable inference.” Federal judges read this as a presumption against the employer who can’t produce clean records. With GPS-stamped clock-ins, the record is created at the moment of clock-in, on the employee’s own phone, at a geocoordinate the worker physically had to be at to register. That’s primary evidence. The presumption against you evaporates.
Overtime under FLSA §207: where the money actually flows
The most expensive FLSA mistake employers make isn’t paying the wrong rate, it’s not knowing a worker crossed the 40-hour threshold in a workweek. Multi-site field operations get burned by this every quarter. A tech does 35 hours on a residential job in his home market through Thursday. On Friday his supervisor sends him to a sister job site two hours away and bills 8 more hours under a different cost code. The two sets of hours sit in different binders, allocated to different jobs, processed by different bookkeepers. The worker hit 43 hours; the company owes him 3 hours at 1.5x. Six months later, when the DOL or the plaintiff’s lawyer adds up both jobs, the back wages come due, plus liquidated damages of an equal amount under §216(b), plus the worker’s attorney fees.
For a single technician this is a few hundred dollars. For a fifty-person field force operating across three or four job sites simultaneously, the cumulative exposure over two years routinely hits six figures. GPS time tracking aggregates hours across jobs automatically. Every clock-in segment carries the worker’s unique identifier; the system computes weekly totals and flags overtime in real time. Your dispatcher gets a notification when a tech is about to cross 40 hours, not six months after the fact when fixing it costs three times as much.
The state-law overlay: California, New York, Washington
FLSA is the floor. About a dozen states pile additional rules on top, and the rules don’t preempt, they stack. California requires daily overtime over 8 hours and double-time over 12 hours in the same workday, regardless of weekly total. New York requires spread-of-hours premiums when a shift exceeds 10 hours from start to finish, even if some of that time was unpaid. Washington state mandates paid sick leave that accrues at one hour per 40 hours worked, tracked to the minute and forfeitable only under narrow conditions. Massachusetts has Sunday and holiday premium rules for retail. Oregon now has predictive scheduling laws with penalty pay for last-minute shift changes.
