Overtime exemption duties audit: build the file before 2027
With federal rulemaking unsettled and state salary floors resetting every January, the strongest defense of an exempt classification is current duties documentation, not the number on the offer letter.
Most HR teams treat exempt status as a field in the HRIS. Regulators and plaintiffs' lawyers treat it as a legal position that has to be proven, role by role, with evidence. That gap is the reason an overtime exemption duties audit belongs on the Q4 agenda rather than on the someday list, because the salary number is the easy part and the duties test is where classifications actually fail.
Why the duties test is the live issue, not the salary threshold
The public conversation about overtime almost always centers on a dollar figure. That is the part that makes headlines, and it is the part payroll can fix in an afternoon. But raising someone above a salary floor does nothing for an exemption if the role does not satisfy the executive, administrative, professional, outside sales, or computer employee duties criteria. A well-paid coordinator with no independent judgment and no supervisory authority is still a misclassification risk.
The regulatory picture reinforces the point. The Department of Labor has signaled rulemaking touching both overtime and independent contractor standards, and employment firms including Jackson Lewis have been publishing standing regulatory roundups rather than one-off alerts, which is what an unsettled agenda looks like. HR Dive has also reported DOL clarifying overtime pay obligations through opinion letters. Opinion letters are useful cover when the facts match, but they are issued and withdrawn as administrations change, so they are a supplement to your own file and not a substitute for it.
HR leaders should verify the current federal salary threshold and the exact stage of any pending rulemaking directly with the DOL Wage and Hour Division before acting on any secondary reporting. The strategic posture, though, does not depend on that answer. Whatever the number turns out to be, the defense is the duties documentation.
Raising someone above a salary floor does nothing for an exemption if the role does not satisfy the duties test.
The January 1 clustering problem for multi-state employers
State legislatures keep bunching effective dates on January 1. SHRM's New Year, New Employment Laws roundups and trackers such as SixFifty's annual changes list both treat that date as the forcing function, and several states maintain exempt salary floors well above the federal level that step up automatically. California runs its own parallel feed of cases and rules through CalChamber's HRCalifornia, a standing reminder that federal alignment is not the same thing as compliance.
For a multi-state employer, this produces a quiet annual failure mode. A national job family is priced once, at a national midpoint, and then a handful of incumbents in two or three states fall below the local floor on January 2. Nobody notices until an exit interview turns into a wage claim. The same cycle covers required workplace postings and labor law notices, which is a smaller exposure but an easy one to get caught on.
The practical consequence is a calendar decision. If the next wave of state changes lands on January 1, 2027, the usable working window is the fourth quarter of 2026, before merit increases and promotion decisions lock salaries into place for another year. Running the audit after the comp cycle closes means paying twice.
What a defensible exempt-population reconciliation contains
Start with a list, not a legal memo. Pull every exempt employee and flag each one whose base salary sits within striking distance of any floor that applies to their work location, using a buffer wide enough to absorb a plausible threshold increase. That gives leadership a costed picture instead of an abstract risk.
Then get a current duties statement for each exempt job family, owned and signed by the manager who supervises the work. This is the step most organizations skip, because they assume the job description already does the job. It usually does not. Job descriptions are written for recruiting and internal equity, they list responsibilities aspirationally, and they go stale the moment a team reorganizes. A duties statement written for the FLSA describes what the person actually does in a typical week, how much discretion they exercise, what they decide without approval, and who reports to them.
Add a record retention rule so the file survives turnover in both HR and the business. Wage and hour claims arrive years after the fact, and the manager who signed the statement is frequently gone. If the documentation lives in one person's drive, it does not exist.
Treat reclassification as a communications event, not a payroll change
When an audit concludes that a role should move to non-exempt, the technical work is straightforward and the human work is not. Employees read reclassification as a demotion. They hear that they are no longer trusted with autonomy, that they now have to punch a clock, and that their status inside the organization has been downgraded, regardless of what the pay math says.
Build the playbook before the first conversation. It should cover timekeeping rollout and training, how overtime will be approved and budgeted, what happens to bonus eligibility and benefits, and a scripted explanation that frames the change as a legal standard the company is applying consistently rather than a judgment about the individual. Managers need that script, because they will be asked first.
Back-pay exposure deserves a separate track and usually a privileged one. Deciding to reclassify is, in effect, a statement about the prior period, so involve counsel early and decide deliberately how far back to look and what, if anything, to remediate. That is a legal judgment with financial consequences, and it should not be made by someone reconciling a spreadsheet.
