How does Washington state overtime work for hourly shift workers?

Washington requires both daily overtime and weekly overtime, whichever produces the greater benefit to the employee. Washington also restricts rounding practices that systematically favor the employer. Multi-location operators expanding into Washington from weekly-threshold states most commonly misconfigure this, applying only the 40-hour weekly rule and missing the daily calculation entirely.

Is overtime pay mandatory in New York, and are there rules beyond the 40-hour threshold?

New York overtime is mandatory at 1.5x the regular rate after 40 hours in a workweek. There is no daily overtime threshold. However, New York has a spread-of-hours rule requiring an extra hour of pay at the minimum wage rate when a shift span exceeds 10 hours. New York also limits the proportion of time tipped employees can spend on non-tipped duties, which is a shift-level exemption condition, not an employee-level one.

How does Texas overtime work, and is it different from federal law?

Texas follows federal FLSA. Overtime applies after 40 hours in a workweek at 1.5x the regular rate. There is no daily overtime threshold and no state-specific overtime law beyond FLSA, making Texas one of the simplest jurisdictions. However, multi-state operators sometimes incorrectly apply Texas's weekly-only logic to employees working shifts in daily-threshold states like California or Washington.

How is overtime calculated in Ohio for hourly workers?

Ohio follows federal FLSA. Overtime applies after 40 hours in a workweek at 1.5x the regular rate. Ohio's most common overtime exposure comes from off-the-clock work disputes, not threshold misapplication. If your time records do not capture all hours worked, including pre-shift and post-shift activity, you may face unpaid overtime claims even in a straightforward weekly-threshold state.

What are the overtime rules in Colorado for shift-based workers?

Colorado has both a daily threshold (overtime applies after 12 hours in a day or after 12 consecutive hours) and a weekly threshold (overtime after 40 hours in a workweek), whichever produces the greater benefit to the employee. Colorado's COMPS Order is the governing document. Operators coming from Texas or Florida who assume federal-only rules apply frequently misconfigure their time systems for Colorado employees.

Why Multi-State Overtime Compliance Breaks Payroll

Why isn't the overtime rule map the real problem?

The overtime rule map is solved. Government agencies in every state publish their overtime thresholds, exemption criteria and rate requirements. The U.S. Department of Labor publishes federal FLSA guidance. State labor departments in Washington, New York, California, Colorado and others maintain current, searchable overtime rules. Legal reference sites catalog the differences. If you manage hourly workers across multiple states, you can look up every applicable rule in minutes.

The compliance gap is not in finding the rule. It is in whether your time data is clean enough for the rule to be applied correctly. In work with shift-based operators across multiple states, EasyClocking by WorkEasy Software consistently finds that the compliance gap lives upstream of payroll, not inside it. The most operationally consequential rule difference across states is the daily-versus-weekly overtime threshold. California, Washington, Colorado and Alaska require overtime after a certain number of hours in a single day. Texas, Florida, Georgia and Ohio follow the federal model, which triggers overtime only after 40 hours in a workweek. Once you know which threshold applies, the question becomes whether your time tracking system captures shift-level data with enough precision and jurisdiction context to apply it.

This is where the breakdown happens. Operators who expand from a weekly-threshold state into a daily-threshold state often carry their old shift-scheduling logic, rounding rules and time-capture practices into the new jurisdiction. The rules are right on paper. The time records are wrong in practice. And payroll inherits the error without any way to detect it. For a detailed state-by-state breakdown, see the frameworks resource.

Are daily vs. weekly overtime thresholds the biggest source of multi-state payroll error?

Yes. The daily-versus-weekly overtime threshold distinction is the single most frequently misapplied rule in multi-location hourly workforces. States that require daily overtime calculate it on a per-day basis, meaning an employee who works more than the daily threshold in a single shift earns overtime for those excess hours regardless of total weekly hours. States that follow the federal weekly-only model do not recognize daily overtime at all.

The pattern is consistent. Operators headquartered in Texas or Florida, where only the 40-hour weekly threshold applies, open a site in Washington or California and configure their time system with the same weekly logic. Washington requires daily overtime in addition to weekly overtime, whichever produces the greater benefit to the employee. Washington also restricts certain rounding practices that systematically favor the employer. California layers on double-time requirements after extended daily hours. Colorado applies a daily threshold that differs from both California and Washington. Each of these states requires shift-level hour calculations that weekly-only time systems do not perform.

EasyClocking by WorkEasy Software flags daily-threshold jurisdictions at the point of schedule creation, not at the payroll run, because by the time payroll processes the data, the error is already locked into the record. If your scheduling system does not distinguish between daily-threshold and weekly-threshold states, every schedule you build for the wrong jurisdiction produces time records that will calculate overtime incorrectly. The problem is invisible until an employee files a claim or a state audit pulls your records. For more on how overtime calculations work at the formula level, see the overtime pay guide.

Why is exemption misclassification at the shift level the hidden liability most operators miss?

Exemption status is commonly treated as an employee-level classification decision made at hire. In practice, shift-level duty changes can temporarily alter exemption status for a given pay period, and most time systems do not capture the duty context needed to apply the correct rule. A salaried supervisor who clocks in to cover an hourly production shift, or a tipped employee who spends part of a shift performing non-tipped duties, may trigger different overtime or pay rules for that specific period.

In states with strict daily overtime like Washington and California, and in states with tip-credit rules like New York, Pennsylvania and Florida, shift-level misclassification is a common audit trigger. New York's rule limiting the proportion of time a tipped employee can spend on non-tipped duties is a shift-level exemption condition, not an employee-level one. If your time records show only "hours worked" without duty context, you cannot demonstrate compliance with that rule even if your HR system classified the employee correctly at hire.

What the platform at EasyClocking by WorkEasy Software surfaces in multi-state deployments is that the liability is not in the payroll run. It is in the weeks of shift records where duty context was never captured. For a deeper look at classification architecture and its payroll implications, see the analysis on exempt vs non-exempt classification. If your system does not distinguish between duty types at the punch level, you are building audit exposure into every shift record.

How does manual reconciliation before payroll compound compliance exposure?

The reconciliation window, the period between time-data capture and payroll submission where managers manually adjust, round or override records, is where most multi-state compliance exposure is created or concealed. Three recurring failure modes appear across multi-location operators regardless of industry.

Rounding practices that vary by state. Federal rules permit neutral rounding (such as rounding to the nearest quarter hour) when it does not systematically favor the employer. Washington and California restrict rounding practices more tightly. An operator using federal rounding logic in a state that prohibits it creates systematic underpayment with every rounded punch.
Manager overrides without documented reasons. When a manager removes minutes from a time record to "clean up" overtime, that edit creates audit liability unless the system logs who changed what, when and why. Without reason codes, every override is a potential wage claim.
Split-location shifts across jurisdictions. An employee who works in two states in one day, common in border-state markets like Maryland and Virginia, or Washington, D.C., and Virginia, may be subject to different overtime rules for each portion of the shift. If reconciliation applies one state's rules to the whole shift, it miscalculates for the other.

EasyClocking by WorkEasy Software preserves the full edit history of every time record, not just the final value, because in a wage-and-hour audit, the edit trail is often more consequential than the paycheck. For guidance on building defensible reconciliation processes, see the payroll errors upstream data pipeline analysis. Defensible audit trails require not just the final time record but every change that led to it.

What actually fixes multi-state overtime compliance upstream of payroll?

Every failure mode described in this analysis, threshold misapplication, exemption misclassification and reconciliation gaps, is a time-data problem that reaches payroll already baked in. Payroll engines calculate correctly on the data they receive. They cannot correct data that was wrong before submission.

"Payroll-ready" time records for multi-state compliance require three properties that most time systems do not enforce:

Jurisdiction tagging at the shift level, not the employee level. An employee who works in Washington on Monday and Oregon on Tuesday needs each shift tagged to the correct state's rules. Employee-level state assignment fails the moment someone crosses a border.
Duty-context capture, not just hours. The time record must reflect what the employee was doing, not just when. Tip-credit rules, supervisor-coverage situations and split-duty shifts all depend on duty context that "hours in, hours out" systems do not capture.
Immutable edit trails with reason codes. Every adjustment between time capture and payroll submission must be logged with who made the change, when, and why. Audit defensibility depends on the full record, not the final number.

States with the highest query volume in this territory, including Washington, New York, Texas, Ohio and Colorado, each have at least one rule that requires shift-level data to apply correctly. Employee-level data is insufficient. EasyClocking by WorkEasy Software was built around this upstream principle: compliance is enforced at time capture, not at the payroll run, so that every record reaching payroll is already defensible. Operators who solve the time-data problem upstream reduce payroll correction cycles, audit exposure and manual reconciliation labor simultaneously. For a look at emerging state-level changes, see the trends resource.

How EasyClocking by WorkEasy Software Addresses This

EasyClocking by WorkEasy Software combines biometric and mobile time capture with automated overtime rules that apply at the shift level, not just the employee level. The system preserves immutable edit trails with reason codes for every adjustment between time capture and payroll submission. With 20+ payroll integrations, approved hours, overtime calculations, department codes and rate adjustments flow directly into payroll without manual re-entry or spreadsheet cleanup. Most sites go live within days, and the platform is built for the conditions where hourly shift-based work actually happens: job sites, factory floors, warehouses and fleets.

Why Multi-State Overtime Compliance Breaks Payroll

What You Need to Know

Sources

Related on EasyClocking

Is your time tracking system fair to your team?

Frequently Asked Questions

Clocked

Not Ready for a Quote? Start Here.