A $58K Salary Is Exempt in Colorado but Not in California — Here's Why
A minimum wage increase just quietly raised the salary threshold for your exempt employees. Here's where the 2026 numbers land — and why checking once in January isn't enough.
The Salary Threshold Cascade
How Minimum Wage Increases Raise the Bar for Exempt Employees — and What Employers Must Do About It
Here's something that surprises a lot of payroll teams: in several states, when the minimum wage goes up, the salary threshold for exempt employees goes up with it — automatically, by design. But the relationship isn't universal. Some exempt thresholds update independently of the minimum wage entirely. The federal exempt salary threshold, for instance, was last updated in 2025, even though the federal minimum wage hasn't changed since 2017. The two move on completely separate tracks.
In either case, the result is the same: teams that only monitor hourly wage changes can miss an exemption threshold update entirely. For organizations managing salaried workforces across multiple states, that gap — however it's created — can quietly trigger a reclassification obligation for exempt employees on the payroll. Miss it, and those employees may be retroactively eligible for overtime.
This piece walks through how the salary level test works, where the 2026 thresholds stand, and what compliance teams need to do about it.
The Salary Level Test: How Exemption Status Is Determined
The "white collar" overtime exemptions — covering executive, administrative, and professional employees—require two things: a duties test and a salary level test. The duties test is about what someone actually does. The salary level test is a hard dollar floor: earn less than the threshold, and the exemption doesn't apply, regardless of job title or responsibilities.
At the federal level, the current exempt salary threshold is $35,568.00 per year ($684 per week) — the baseline in states that haven't set their own. Several states have gone further, establishing thresholds that significantly exceed the federal floor. In some of those states, the threshold is explicitly indexed to the state minimum wage; in others, it's set independently by regulation.
In Washington and California, the exempt salary threshold is a formula tied directly to the state minimum wage. When the minimum wage increases, the exemption threshold moves with it—same date, same mechanism, no separate action required. Not every state works this way, but these two represent the highest thresholds in the country.
2026 Exempt Salary Thresholds by Jurisdiction
| Jurisdiction | 2026 Exempt Threshold (Annual) | Weekly Minimum | Notes |
|---|---|---|---|
$35,568.00 | $684.00 | Baseline for standard states | |
$80,168.40 |
| Highest in the nation (2.25x min wage) | |
$70,304.00 | $1,352.00 | Applies to all employers | |
$66,300.00 | $1,275.00 | Higher downstate mandate | |
$57,784.00 | $1,111.23 | State-indexed, mirrors federal | |
$54,080.00 | $1,040.00 | Increasing to $58,240 on July 1, 2026 |
The Indexed Multiplier: Washington and California
Washington's exempt threshold — $80,168.40 annually — is set at 2.25 times the state minimum wage, the highest in the nation. California applies the same logic at 2x the minimum, currently landing at $70,304 for all employers regardless of size.
What this means practically: a salary that clears the exemption bar one year may fall below it the next — not because anything changed about the employee's pay or role, but because the minimum wage increased and pulled the threshold up with it. For distributed teams with employees in these states, this is a moving target that needs active monitoring, not a one-time setup.
Mid-Year Increases: The January 1 Assumption Is Wrong
It's easy to treat wage compliance as a January 1 exercise — set the rates, update the thresholds, move on. But several high-activity wage states don't follow that schedule:
- Alaska's exempt threshold increases to $58,240 on July 1, 2026—a mid-year change that requires a Q2 review, not a Q1 one.
- California, Nevada, and Illinois have historically made adjustments outside the standard January cycle.
- Dozens of local jurisdictions have their own effective dates scattered throughout the year.
An organization that audits exempt salaries once in January and calls it done may be compliant through June and quietly out of compliance from July forward—with no notice from the jurisdiction that anything changed.
The Practical Compliance Implications
Three things need to be part of any proactive approach:
- Audit exempt salaries against current thresholds, not last year's. In Washington and California especially, the threshold today may be different from the one in place when an employee was last reviewed.
- Include exempt threshold research whenever you're tracking minimum wage changes — but don't treat one as a complete proxy for the other. In indexed states like Washington and California, the two move together. But thresholds can also update independently, as the federal threshold has. Building exempt threshold checks into your minimum wage research workflow ensures neither gets missed, regardless of what triggered the change.
- Build mid-year checkpoints in. Any state with a non-January effective date needs a corresponding review task on that date. Alaska's July 1, 2026 adjustment is a current example that requires action before year-end.
An employee earning $58,000 annually is exempt from overtime in Colorado — but not in California or Washington. Same salary, same role, different legal status. The only variable is where the work is performed.
Keeping Up with the Cascade: Symmetry's Minimum Wage Finder
The challenge with the salary threshold cascade isn't understanding it — it's operationalizing it. Manually tracking minimum wage changes, calculating indexed multipliers, and mapping non-January effective dates across dozens of jurisdictions is exactly the kind of maintenance burden that pulls teams away from higher-value work.
Symmetry's Minimum Wage Finder is built for precisely this problem. It provides a single, continuously updated source of truth for wage rates and thresholds across federal, state, and local jurisdictions—including the indexed exempt salary calculations that states like Washington and California tie directly to the minimum wage. Because it's built on location-accurate data down to the place of performance, it surfaces the right rate (and the right threshold) for each jurisdiction, without requiring teams to track every legislative calendar manually.
For payroll and HR platforms, that means compliance logic that's always current can be embedded directly into the product. For internal payroll teams, it means one reliable place to check before each pay period—rather than a patchwork of government PDFs and manual lookups that go stale the moment a new effective date passes.
Why This Matters Beyond HR
When exempt salary misclassification surfaces—through an audit, a complaint, or a class action—the liability doesn't start today. It goes back. Under the FLSA, the standard lookback is two years, extended to three for willful violations. States with their own wage laws can reach further still.
For organizations with large salaried workforces in high-threshold states, the salary level test isn't a footnote. It's a recurring compliance checkpoint tied directly to a regulatory calendar that never stops moving. Staying ahead of it means treating threshold research as infrastructure — something built into how wage changes are tracked and applied, not something discovered after the fact.
Ready to go deeper? This article is drawn from Symmetry's comprehensive guide, Master Minimum Wage Accuracy. The full guide gives payroll teams and the platforms that power them the compliance intelligence to navigate every layer of wage law—accurately, confidently, and ahead of the curve.