Time Tracking Policy: When to Require It and When Not To

Whether to require time tracking, and for whom, is really two different questions wearing the same name: a legal compliance question for non-exempt employees, and a business-information question for everyone else. Conflating the two is where a lot of time-tracking policy confusion — and resentment — comes from.

The legal question: non-exempt employees

For non-exempt employees, accurate time tracking isn't optional — their pay, including overtime, depends directly on actual hours worked, and federal law places the burden of maintaining accurate records on the employer, not the employee. If a wage dispute arises and records are incomplete or inaccurate, the default tends to favor the employee's own reasonable account of hours worked, precisely because the employer had the legal responsibility to track it properly and didn't.

This isn't a judgment call to weigh — if a role is properly classified as non-exempt, accurate time tracking is a legal requirement, and the only real decision is which method to use, not whether to track at all.

The business question: exempt, salaried employees

Exempt employees don't need time tracking for overtime purposes, since their pay doesn't vary with hours worked. But plenty of businesses track salaried hours anyway, for reasons that have nothing to do with wage compliance:

Project or client billing. A services business that bills clients based on hours worked needs accurate time data regardless of how the employee doing the work is classified internally.

Capacity and workload planning. Understanding where time is actually going — which projects, which types of work — can surface workload imbalances or inefficiencies that wouldn't otherwise be visible.

Cost allocation. Businesses tracking profitability by project or client need labor hours as an input, independent of payroll classification.

These are legitimate reasons, but they're different from "we need this for legal compliance," and it's worth being explicit about which reason actually applies — the two require different framing when introduced to a team.

Why tracking salaried staff can read as distrust

Time tracking has a strong cultural association with hourly, closely-supervised work, so applying it to salaried employees — often for the first time in a company's history — can land as a signal that autonomy is being reduced or that management doesn't trust people to manage their own time. This reaction is understandable and worth taking seriously rather than dismissing, since it affects how the policy is actually received regardless of the underlying business logic.

Introducing it well

Name the actual reason, specifically. "We're introducing time tracking so we can bill clients accurately and understand where our capacity is going" is a fundamentally different message than an unexplained new requirement, and it's the truth in most cases where salaried tracking is being introduced for business reasons.

Make the tool as low-friction as possible. A time-tracking method that takes real daily effort to maintain accurately generates resentment independent of the underlying reason for it. Simple, fast tools — even rough time-blocking rather than minute-by-minute logging — reduce this friction considerably.

Apply it consistently. Tracking some salaried roles but not others, without a clear and explained reason for the distinction, invites a fairness question that's hard to answer well if the real reason is simply that leadership decided some roles' time mattered more to measure than others'.

Separate it clearly from performance evaluation, unless it's genuinely meant to inform that. If time data starts being used to judge someone's dedication or work ethic in a way that wasn't communicated upfront, that's a meaningful, trust-damaging shift from the original stated purpose.

Choosing a tracking method

For non-exempt employees, the method needs to produce an accurate, verifiable record — a proper time clock system or app, not an honor-system estimate filled in at the end of the week from memory, which is both less accurate and weaker as a legal record if it's ever challenged.

For exempt employees tracked for business reasons, the method can reasonably be lighter-weight — project or category-level time allocation rather than minute-by-minute logging — since the goal is aggregate business insight, not a legally defensible record of exact hours.

When not to introduce time tracking at all

If there's no genuine legal requirement (properly classified exempt staff) and no specific, concrete business use for the data — no client billing, no active capacity planning initiative, nothing that will actually be done with the information — introducing time tracking purely because it feels like good practice tends to add friction without adding real value. Time tracking that's collected but never actually used for anything is one of the more common, most easily avoided sources of unnecessary process overhead on a small team.

Handling a mixed team

Many small businesses have both exempt and non-exempt employees working closely together, sometimes on the same projects. In this situation, it's worth being explicit that different roles are tracked differently for different, specific reasons — non-exempt staff for legal accuracy, exempt staff (if tracked at all) for project costing or capacity data — rather than leaving the distinction unexplained and letting people draw their own, possibly incorrect, conclusions about why some colleagues track hours and others don't.

Auditing classification before auditing time tracking

If there's ever genuine uncertainty about whether a role is properly classified as exempt or non-exempt, that classification question needs to be resolved before finalizing a time-tracking policy, not after — a misclassified role means the "no time tracking needed" assumption for that position may be legally wrong regardless of what the job title or pay structure suggests. Getting classification right in general is closely related to this same underlying question, even though that piece focuses on employee-versus-contractor rather than exempt-versus-non-exempt specifically.

The short version

Time tracking is a legal requirement for non-exempt employees and a business choice for everyone else — conflating the two, or introducing tracking for salaried staff without naming the real reason, is what turns a reasonable business decision into something that reads as distrust. Track accurately where the law requires it, track deliberately and transparently where there's a genuine business reason, and skip it entirely where neither applies.