On Sunday, November 1, 2026, at 2:00 a.m., the clocks in most of the United States will do something your payroll system may not be ready for: they will jump backward to 1:00 a.m. Your graveyard shift will live through the 1:00-to-2:00 a.m. hour twice — and under federal law, you owe them for both times through it.
This is not a rounding question or a goodwill gesture. The Fair Labor Standards Act requires employers to credit employees with every hour they actually work. A scheduled eight-hour overnight shift that spans the fall time change is, legally, a nine-hour shift. Miss that extra hour and you have underpaid wages, a corrupted overtime calculation, and a paper trail that proves it.
Here is the part that catches even careful employers: the spring time change does not work in reverse. When clocks jumped forward on March 8, 2026, your overnight crew worked seven hours — and you were only required to pay for seven. The two transitions follow asymmetric rules, and getting them confused is exactly how small businesses end up in wage disputes every November. This guide walks through what you owe on November 1, why March works differently, where the overtime traps hide, and the payroll checklist to get it right.
What Actually Happens on November 1, 2026
Daylight saving time ends at 2:00 a.m. local time on the first Sunday in November — in 2026, the earliest possible date, November 1. At that moment, clocks turn back one hour to 1:00 a.m. and the country returns to standard time.
Take the textbook example straight from the Department of Labor's own guidance: an employee works 11:00 p.m. to 7:30 a.m. with a 30-minute unpaid meal break. On a normal night, that is eight paid hours. On the night daylight saving time ends, the employee works the 1:00-to-2:00 a.m. hour twice — once on daylight time, once on standard time — and the shift becomes nine paid hours.
Three details worth pinning down now:
- It is local time, not Eastern. The change happens at 2:00 a.m. in each time zone, so multi-state employers have overnight shifts crossing the line at different absolute moments.
- Two states mostly sit this out. Most of Arizona and all of Hawaii do not observe daylight saving time, so shifts there are unaffected. If you run locations across state lines, only some of your overnight crews get the extra hour.
- The trigger is being on duty at 2:00 a.m. Only shifts that span the changeover are affected. A shift that ends at 1:30 a.m. or starts at 3:00 a.m. is a normal shift.
Fall Back: You Owe the Ninth Hour, Plus Its Overtime Consequences
The core rule is simple: pay for nine hours. But that ninth hour ripples into three other calculations employers routinely get wrong.
1. It counts toward the 40-hour weekly threshold. The extra hour is hours worked, so it goes into the week's total. An employee at 32 regular hours who picks up the fall-back overnight shift lands at 41, and the 41st hour is overtime at time-and-a-half. Audit any employee hovering near 40 hours in the week containing November 1.
2. It can trigger daily overtime. Federal law only requires overtime past 40 in a week, but several states require it past 8 in a day — California, Alaska, and Nevada being the prominent ones, with Colorado requiring it past 12. In those states, the fall-back shift is a nine-hour day on its face, and the ninth hour is owed at the overtime rate even if the employee works 30 hours that week. In California the analysis runs through your defined workday: overtime is owed when hours worked in a single workday exceed eight, so check how your workday boundary interacts with a shift that straddles midnight.
3. It enters the regular-rate math. Overtime is calculated from the regular rate of pay, and the ninth hour's earnings are part of the week's straight-time compensation. Fold it in before computing the overtime premium — do not treat it as a flat add-on outside the rate calculation.
One legitimate way to avoid the overtime entirely: adjust the schedule. Employers commonly stagger the overnight crew that night — for example, one group works 11:00 p.m. to 6:30 a.m. and another covers the remaining hours — so nobody individually works more than eight. That is perfectly legal as long as everyone is paid for every hour actually worked. What you cannot do is keep the nine-hour shift and pay eight.
Spring Forward Is Not the Mirror Image
When daylight saving time began on March 8, 2026, clocks jumped from 2:00 a.m. to 3:00 a.m., and the overnight crew simply never worked the 2:00-to-3:00 hour. The same DOL rule — credit all hours actually worked — produces the opposite result: a scheduled eight-hour shift was a seven-hour shift, and you were only required to pay for seven.
Many employers pay the full eight anyway, out of fairness or simplicity. That is allowed, but the FLSA attaches two strict conditions to the generosity, and both surprise people:
- The phantom hour is excluded from the regular rate. Because the extra hour's pay is not compensation for work performed, it is excluded from the regular rate of pay under Section 7(e)(2) of the FLSA. Do not add it to the numerator when computing the overtime rate.
- The phantom hour cannot offset real overtime. If the employee worked 40.5 genuine hours that week, you cannot point to the gifted hour and call the overtime covered. The statute prohibits crediting non-work pay toward overtime owed.
Keep this asymmetry straight with a one-line rule: in November you pay for time worked that the schedule hides; in March you may pay for schedule time that was never worked — but that payment is legally invisible to overtime math. File this section away until next March; the November rules below are the urgent ones.
The Payroll and Timekeeping Checklist for November 1
Most DST payroll errors are systems errors, not policy decisions. Work through this list before the weekend of October 31:
Audit your time clocks. Many electronic systems record elapsed time correctly through the changeover; many do not, and some record the shift as eight hours because that is what the schedule says. Verify with your vendor how your specific system handles the repeated 1:00–2:00 a.m. hour. If it cannot distinguish the two passes through the hour, plan a manual adjustment and document it.
Brief the managers who approve timesheets. The most common failure mode is a supervisor "correcting" a nine-hour entry down to the scheduled eight because it looks like an error. Tell every approver in advance: on November 1, nine hours on the overnight shift is correct. Put it in writing — an email the week before is enough.
Check collective bargaining agreements and state laws first. A union contract, company policy, or state wage law may promise more than the FLSA floor — for example, a guaranteed eight hours' pay for a seven-hour spring shift, or premium pay for overnight hours generally. The FLSA sets the minimum; your own agreements can raise it. If a contract guarantees shift pay regardless of hours worked, honor the contract.
Decide on schedule staggering deliberately. If you will split shifts to avoid the ninth hour, publish the adjusted schedule in advance so employees know when to arrive and leave. A last-minute verbal change that shortens someone's shift can create show-up-pay obligations under several state laws — trading a federal overtime problem for a state reporting-time problem.
Watch the pay-period boundary. The extra hour belongs to the pay period in which the work was performed. For most Sunday-to-Saturday or Monday-to-Sunday cycles this is automatic, but if your week ends at midnight Sunday, confirm the 1:00–2:00 a.m. repeat lands in the intended week before finalizing overtime totals.
Keep the record. Note the DST adjustment on the timesheet or in payroll memos. If a wage claim arrives in February, a contemporaneous note saying "11/1 overnight shift: 9 hrs incl. DST fall-back hour per FLSA" ends the dispute before it starts.
Book It Right: The Bookkeeping Side of the Extra Hour
Payroll accuracy is the compliance half; clean books are the management half. The fall-back hour creates small distortions that confuse month-end review if nobody labels them:
- Code the hour to the right cost center. The ninth hour is direct labor in the department where it was worked, not a miscellaneous payroll variance. If the overnight shift already earns a shift differential, apply the differential to all nine hours — the premium follows the hours.
- Explain the overtime variance. If your October-to-November labor reports show an overtime blip concentrated in overnight roles, annotate it. Six months later, an unexplained 12% overtime spike in one week looks like a staffing problem; labeled correctly, it is a calendar event that reverses nothing and predicts next November.
- Reconcile gross-to-net on the affected checks. The employee whose pay stub shows nine hours when the schedule said eight will call payroll — and the one whose stub shows eight will call a lawyer. A one-line stub memo or break-room notice ("Overnight shifts 10/31–11/1 include the DST hour") prevents both calls.
Accurate books do more than satisfy auditors here. Overnight labor is often your most expensive hourly labor once differentials and overtime stack. Knowing its true cost — all nine hours of it — is what lets you price night-shift work, bids, and contracts correctly the other 51 weeks of the year.
Simplify Your Financial Management
Getting one strange payroll week right is good hygiene; keeping every week's labor costs, differentials, and overtime visible in one trustworthy ledger is what prevents the next surprise. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
