Reference
Where does wage-and-hour exposure actually sit?
The short answer
Most wage-and-hour exposure sits in three places: exempt classifications made years ago against federal thresholds and never revisited against state thresholds that have since moved; overtime calculated on base rate when bonuses or shift differentials should be in the regular rate; and time records that cannot substantiate what was paid. The first is the most expensive because the remedy is retroactive, and the third is what decides the outcome when a claim arrives.
Classification, first and largest
Exempt-versus-non-exempt decisions are frequently made once, at hire, against the federal salary threshold, and never revisited. Several states set higher thresholds and adjust them on their own schedule. A role that was properly exempt three years ago may not be today, in one state and not another, without anything about the job changing.
The duties test is the second half and the more commonly failed one. Exemption depends on duties as actually performed, not on the job description or the title. A salaried supervisor spending most of their week doing the same work as the people they supervise is a classic exposure, and it is invisible from an org chart.
This category is expensive because the remedy is retroactive, often with liquidated damages, and because a misclassification is rarely singular — where one role is wrong, everyone in that role is wrong, for as long as the classification stood.
The regular rate problem
Overtime is owed on the regular rate, not the base rate, and the regular rate includes more than most payroll configurations assume. Non-discretionary bonuses, shift differentials, and certain incentive payments generally have to be folded in and the overtime recalculated.
Where a production bonus is paid quarterly, the recalculation reaches back across the whole period. Systems configured to run overtime at base rate produce an underpayment every single cycle, quietly, at scale, and the error compounds rather than being noticed.
Records are what decide it
When a claim or an audit arrives, the question is not whether you meant well. It is what you can produce. The burden of proof on hours worked sits with the employer, and where records are absent or unreliable an employee’s reasonable estimate can carry considerable weight.
Records that show identical start and stop times every day, or that were edited without an audit trail, are worse than sparse records — they invite the inference that they were created for the occasion. Automated capture with a visible edit history is the difference between substantiating a position and arguing one.
The state-specific layer
Meal and rest break requirements, daily overtime thresholds, and reporting-time or call-in pay all vary by state, and several carry penalty payments rather than merely requiring the break. In shift-based operations these are the rules most often configured wrong, because they were configured once for the home state and replicated outward.
Why this accumulates rather than being caught
Almost nobody fails these deliberately. They fail by growing faster than their record-keeping — adding states, adding shift patterns, adding one more pay rule as an exception — while the underlying configuration and the classification decisions stay where they were set at a smaller size.
| Exposure | How it arises | Why it is expensive |
|---|---|---|
| Misclassification | Set once at hire; state thresholds move; duties drift | Retroactive, and applies to everyone in the role |
| Regular-rate errors | Overtime run on base rate despite bonuses or differentials | Recurs every cycle, compounds silently |
| Inadequate records | Manual entry, uniform times, untracked edits | Shifts the burden of proof against you |
| State break and premium rules | Home-state configuration replicated to other states | Penalty pay per occurrence, at scale |
Common questions
Does paying a salary make someone exempt?
How far back can a claim reach?
Does a PEO take on this liability?
What is the single most useful thing to check first?
Where this sits
This page supports Compliance — the practice that does this work.

