Time Tracking Compliance: What Labor Laws Mean for Your Timesheets

What Labor Law Actually Requires From a Timesheet

The FLSA doesn't tell you which software to use. It tells you what the record has to show: hours worked each day, total hours each workweek, the basis on which wages are paid, and any overtime earned at time-and-a-half for hours over 40 in a week for non-exempt staff. That sounds simple until you look at how most services firms actually capture time. A consultant logs "8 hours, client project" once a day, at the end of the week, from memory. That entry satisfies nobody in an audit. Regulators want start and stop patterns that are at least plausible, not a single daily lump sum reconstructed five days later.

Several states go further than the federal floor. California requires meal and rest break tracking alongside hours, and a missed break can trigger a premium payment even if total hours look fine. New York and a handful of other states have added predictive scheduling or "know your pay" style disclosure rules that assume accurate, timely time records exist. If your firm has remote staff in multiple states, or contractors in other countries, you're not dealing with one rulebook, you're dealing with whichever is strictest for each person on payroll. A 35-person consulting firm with staff in California, New York, and Ontario is effectively running three different timesheet policies whether anyone documented that or not.

The Exempt/Non-Exempt Mistake That Costs the Most

Here's the pattern that shows up again and again in wage claims against agencies: someone gets promoted to "Senior Coordinator," moved to salary, and told they no longer need to track hours because they're exempt now. Except exemption isn't about title or pay structure, it's about actual job duties meeting a specific test (executive, administrative, professional, or a handful of narrower categories), and a coordinator approving expense reports and scheduling meetings usually doesn't clear that bar no matter what the offer letter says. When that person works 55-hour weeks for two years and eventually leaves on bad terms, the unpaid overtime claim can run into five figures per employee, and it rarely stays at one employee once a labor department starts looking at job titles across the firm.

The fix is unglamorous: track hours for everyone by default, including people you believe are exempt, until a proper duties test says otherwise. It costs almost nothing to have a "salaried" person clock hours in the same system as hourly staff. It costs a great deal to reconstruct two years of a disputed schedule from memory and calendar invites after the fact.

• Job title is not a legal test. "Manager," "Lead," and "Senior" carry no exemption weight on their own, the actual duties performed each week are what matters.
• Salary threshold rules change. Federal and state minimum salary levels for exemption are periodically updated, a classification that was safe in 2022 may not be safe today.
• Misclassification is rarely a single-employee problem. If one coordinator was misclassified, every coordinator with the same duties usually was too.
• Contractors get scrutinized the same way. A "1099 contractor" working set hours under direct supervision on your tools looks like a misclassified employee to most labor departments, regardless of the contract's label.

Recordkeeping, Edits, and the Audit Trail Problem

Retention periods matter, but they're the easy part. The harder part is what happens between the moment an employee enters time and the moment that entry becomes the "official" record used for payroll and billing. If a project manager can open last week's timesheet and change a 9-hour Tuesday to a 6-hour Tuesday with no log of the original number, who made the edit, or why, that spreadsheet is not a defensible record. It's a document that looks clean and is, functionally, unverifiable. In a dispute, "we don't keep a history of edits" reads to a regulator as "we can't prove we didn't alter this."

This is also where a lot of firms discover their tooling was never built for this. A shared spreadsheet has no native audit trail. A basic timer app might log hours but not who edited what. If your firm has grown past the point where "we trust everyone" is an adequate control, it's worth reading through the specifics on the time tracking best practices guide we put together for agencies and consulting firms, since a lot of the fixes for compliance risk and the fixes for messy, inaccurate billing turn out to be the same changes.

Building a System That Holds Up, Not Just a Policy That Sounds Good

A written time tracking policy is worth having, but a policy is only as good as whether the system underneath it actually enforces it. Three things separate a defensible setup from a paper one. First, entries need timestamps close to when the work happened, not end-of-week reconstruction. Second, every edit after submission needs a visible history. Third, overtime calculations for non-exempt staff need to run automatically against actual state rules, not get eyeballed by whoever runs payroll that month, because daily overtime thresholds in a state like California differ from the federal weekly-only rule, and a manual process misses that distinction constantly.

This is the kind of thing worth checking before you're forced to, not after a demand letter arrives. Autovella's approach on the features page covers how time entries, approvals, and edit history connect directly to invoicing so the record used to bill a client and the record used to pay an employee are the same auditable source, not two spreadsheets that quietly drift apart over a few months. If you're comparing tools, it's also worth looking at the pricing page to see what compliance-relevant features (audit logs, approval workflows, retention) come standard versus what's gated behind an enterprise tier, since that gap is where a lot of smaller firms end up under-protected without realizing it.

Frequently asked

Related reading