PunchCrews That Cross State Lines: Which State's Overtime Law Applies in 2026
Crews That Cross State Lines: Which State's Overtime Law Applies in 2026
The short answer: Overtime follows the work, not your office address and not the employee's home address. A crew that spends Tuesday on a job across the state line is covered that day by the rules of the state where their boots were. Two states can therefore govern one paycheck, and the deciding evidence is a per person, per day record of where each shift happened and how long it ran. Punch makes that record a byproduct of punching in.
The Rule: The Work Location Governs
Employers generally must apply overtime rules based on where the employee physically performs the work, not where the business is headquartered and not where the worker lives. When federal and state law both apply, the standard that is more generous to the employee wins. The FLSA is a floor, never a ceiling.
California made the point unmistakably. In Sullivan v. Oracle Corporation, the California Supreme Court held that nonresident employees are entitled to California overtime for full days worked in California for a California-based employer. The plaintiffs lived in Colorado and Arizona and worked somewhere between 15 and 33 days a year in California. Residency did not save the employer. The days on the ground did the deciding.
For a field crew, that translates into a simple operating rule. If your people ever load up and drive to a job in a neighboring state, you do not have one overtime policy. You have as many as you have states.
The Daily Overtime States Are Where This Bites
Most states track the federal 40-hour week and nothing more. A handful add a daily trigger, and a 10-hour day that costs nothing at home can cost time and a half one exit ramp away.
California. Time and a half for hours 9 through 12 in a workday, and double time beyond 12 hours in a single day. California also has the seventh-consecutive-day rules on top of that.
Alaska. Time and a half after 8 hours in a day and after 40 in a week, for employers with four or more employees. Employers with fewer than four employees in the regular course of business are exempt under AS 23.10.055(a)(13).
Nevada. Time and a half after 8 hours in a day, but only for employees whose regular rate is less than one and a half times the state minimum wage. Nevada's 2026 minimum wage is a flat $12.00 per hour with no tip credit, which puts the line at $18.00. Below that rate, the daily rule applies. At or above it, only the 40-hour week does.
Colorado. Under the COMPS Order, overtime is owed for hours over 40 in a workweek, over 12 in a workday, or over 12 consecutive hours, whichever produces the most pay. The consecutive-hours version is the one that surprises people, because it can run across midnight and across two calendar days.
Notice the shape of every one of these. They are answered by the length of a single day, not by a weekly total. A payroll process that only sums the week cannot see them.
The Workweek Does Not Reset at the Border
Here is the mistake that produces the biggest checks.
The FLSA workweek is one fixed and regularly recurring period of 168 hours. It belongs to the employee, not to the job site. Working 30 hours in one state and 22 in another is a 52-hour workweek with 12 hours of overtime, not two clean part-time weeks that each stay under 40.
Splitting hours across two state columns and paying each column straight time is the classic multi-state error. Weekly overtime is computed once, on the employee's total hours for the week. Daily overtime, where a state has it, is computed separately for the days spent in that state. Then you pay whatever combination the law requires without double-counting the same hour.
Two other pieces ride along with the same records. If the employee earned different rates on different jobs during the week, the overtime premium is based on the weighted average regular rate for that week, not the rate on whichever job happened to run long. And travel between job sites during the workday is generally hours worked, which means the drive across the state line usually belongs in the total.
Minimum Wage and Local Ordinances Travel Too
The same "where the work happened" logic governs the wage floor, and the floor is no longer just a state number. Roughly 40 California cities and counties sit above the state minimum wage, and at least 49 cities and counties nationwide raised local rates during 2026. The UC Berkeley Labor Center keeps a running inventory because the list moves every January and July.
For a crew that works two counties, this is not academic. The applicable minimum wage can change between Monday and Tuesday. Same crew, same truck, different floor. You need to know which site produced which hours to price them correctly.
The Tax Side Runs on the Same Day Count
Wage and hour is only half of it. Nonresident income tax withholding is triggered by the same fact pattern and often by a literal count of days.
As of January 1, 2026, 22 states have no meaningful nonresident filing threshold, meaning a single day of work in the state can create an obligation. Nineteen states have thresholds that relieve nonresidents from filing when the work is limited. Among the day-based thresholds, Illinois, Indiana, Louisiana, and Montana use 30 days with no mutuality requirement.
Congress has been asked to standardize this at 30 days in some form in every session since 2006, most recently as the Mobile Workforce State Income Tax Simplification Act of 2025 (S.1443, 119th Congress). It has not become law. Until it does, the burden of counting days sits with the employer.
Whatever your accountant needs, it comes down to a number of days per employee per state. That number should come out of your timekeeping, not out of somebody's memory of the spring.
What Your Records Actually Have To Show
Strip away the statutes and the requirement is small and specific:
- Which person worked
- Which day, with real start and stop times to the minute
- Which job site those hours belong to
- Whether the unpaid meal was taken, and when
- The rate that applied
- All of it retained long enough to answer a question raised years later
A weekly total typed into a spreadsheet on Friday answers none of this. It cannot prove a 9-hour Tuesday in California, it cannot count 30 days in Illinois, and it cannot separate hours at the county rate from hours at the city rate.
How Punch Handles It
Punch is built so that record exists without anyone assembling it.
Every punch in and punch out is timestamped to the minute and attached to a job site, so a day's hours are already sorted by where the work happened. Lunch is its own tracked event, so the unpaid meal never gets folded into the paid block, and a split shift stays two clean segments on one day instead of one long invented one.
Punches work offline. A rural site, a basement, or a stretch of highway with no signal still records a real punch that syncs when service returns, which matters most for exactly the crews who cross state lines.
Overtime is applied automatically against your fixed workweek using Punch's overtime presets covering more than 50 countries, including state daily overtime rules where they apply. The workweek stays the employee's single 168-hour period, so hours across multiple sites roll into one correct weekly total instead of two convenient ones.
Owners and managers review the week in one place and approve or reject in bulk rather than one shift at a time, and the decision is recorded against the shift. Pay periods run weekly or bi-weekly. When the week is approved, Reports export to Excel or a QuickBooks CSV, or push straight into QuickBooks Online, so what you pay matches what was punched and the job-site detail survives the trip to payroll.
For crews without company phones, a shared iPad in the shop or the trailer becomes a punch station with a PIN. Verification stays private throughout: Punch confirms an on-site punch-in with a job-site geofence on iOS, never facial recognition and never a photo at the punch. Proving someone was at the Reno site should not require a camera in their face. Trust beats surveillance.
Why Punch Beats the Per-Seat Alternatives
Multi-state work is what happens when a business grows, and growth is exactly when per-seat billing turns hostile. ClockShark, Connecteam, Buddy Punch, QuickBooks Time, and Homebase all charge by the user, so every hire that widens your footprint also widens the invoice, and the reporting that would prove which hours happened where tends to live one tier up or behind an add-on.
Punch charges a flat price per organization. Every plan includes every feature, from geofenced punch-in to kiosk mode to bulk approvals to QuickBooks Online export, and owners are always free. Add the crew you need for the out-of-state job and your software bill does not move.
The Bottom Line
Overtime, minimum wage, and withholding all follow the work across the state line, while the 40-hour workweek stays whole and belongs to the employee. California, Alaska, Nevada, and Colorado each add a daily trigger that a weekly summary will never surface. Every one of those questions resolves to the same thing: which person, which day, which site, which minutes. Capture that once, at the moment of the punch, and the rest is arithmetic.
Start with Punch and let every shift record where it happened.
This article is general information, not legal advice. Wage, hour, and tax rules vary by state, city, and industry, and they change. Confirm your obligations with the enforcing agency in each state where your crew works, or with a qualified professional.