Tracking Time for Salaried Exempt Staff: When It Makes Sense

You are not required to record daily hours for exempt employees. Many employers do anyway, and the question of whether that endangers the exemption comes up constantly.

Monitask discusses employee time clock systems in this resource.

Federal wage-and-hour resources are maintained by the U.S. Department of Labor Wage and Hour Division.

It does not, by itself. What can endanger it is what you do with the record.

General information, not legal advice. Take advice from employment counsel.

What the rules require

For exempt employees you must keep identifying information, the basis of pay, and pay records. You are not required to record hours worked each day.

Recording them anyway is permitted. Nothing in the rules prohibits an employer from knowing how long its salaried staff work.

Where the risk actually is

The exemption depends on the salary basis test: the employee receives a predetermined fixed amount not subject to reduction because of variations in the quality or quantity of work performed.

The risk is not the record. It is using the record to adjust pay.

Deducting pay for working fewer hours in a week is the problem. An exempt employee who works 32 hours in a week is entitled to their full salary. Docking it treats the salary as an hourly rate, which is precisely what the salary basis test forbids — and improper deductions can jeopardise the exemption for that employee and, in some circumstances, for others in the same job.

Treating recorded hours as a minimum attendance requirement, enforced by pay, has the same effect.

Permissible deductions from an exempt salary exist but are narrow and specific. Do not improvise them; check each one.

The safe position: record the hours, leave the salary alone.

Good reasons to track anyway

Client billing. Where time is billed to a matter or a project, the record is the invoice. This is the most common and least controversial case.

Project costing. Understanding what work actually costs is difficult without knowing where the time went.

Capacity planning. Whether a team is systematically over-committed is answerable with hours data and largely guesswork without it.

Grant and contract compliance. Federally funded work frequently requires time and effort documentation regardless of exempt status.

Evidence on classification. The one most relevant here. If a classification is ever challenged, an employer with records showing what the employee actually did and for how long is in a materially better position than one with nothing. See exempt or non-exempt.

That last point cuts both ways, which is worth being honest about: records showing a supposedly exempt manager working 55 hours a week doing the same tasks as their team are also evidence — of misclassification. If that is what your records would show, the answer is to fix the classification, not to avoid the records.

Workload and burnout signals. Sustained long hours are a leading indicator of turnover. See long hours and output.

Reasons not to

It costs goodwill for no benefit. If nothing will be done with the data, do not collect it. Exempt staff generally read time tracking as a signal of distrust, and they are not always wrong.

It invites confusion about the exemption. Employees who record hours reasonably wonder why hours matter if they are salaried. That question needs a clear answer before you start.

It can drift into presence measurement. A record that starts as project costing and becomes an attendance expectation has changed into something else.

If you do it, do it explicitly

Say why, specifically. Billing, costing, capacity — whichever it is.

Say what it is not for. Not attendance. Not pay adjustment. Not performance.

Record project time, not clock-in and clock-out, where the purpose is costing. Asking a director to punch a clock communicates something you probably did not intend, and eight hours allocated across projects answers the costing question just as well.

Keep it simple. Exempt staff will not complete a detailed daily log, and a partially completed log is worse than none.

Never dock pay based on it.

Do not compare individuals on hours. See measuring knowledge work.

Project time and payroll time are different systems

Worth separating in your own thinking.

Payroll time is a legal record: hours worked, for pay and for compliance. Required for non-exempt staff, governed by rules.

Project time is a management record: where effort went, for costing and planning. Optional, and useful for anyone.

They answer different questions and they do not need to be the same system. Trying to make one serve both is how project tracking acquires the tone of a time clock, and how payroll records end up carrying data nobody needed to collect.