Blog

Daylight saving and the nine-hour night shift

· payroll, overtime, time & attendance

A night audit shift scheduled 22:00 to 06:00 is eight hours long on 363 nights of the year. On the night the clocks go back it is nine, and on the night they go forward it is seven, because those two nights do not contain twenty-four hours. In 2026 the fall change lands at 2:00 a.m. on Sunday 1 November, which puts the long shift on the Saturday night before it. Whether your timesheet says eight or nine for that shift depends on a decision somebody made inside your time system years ago, and you cannot tell which from the outside.

Daylight saving: the night that has twenty-five hours

At 2:00 a.m. local time the clocks go back to 1:00 a.m., so the hour between 1:00 and 1:59 happens twice. Walk the night auditor’s shift forward and the gap opens up in the middle of it:

Wall clock at the hotelElapsed since clock-in
22:00 — clocks in0:00
00:002:00
01:593:59
01:00 — clocks go back4:00
02:005:00
06:00 — clocks out9:00

Nobody worked a minute they did not work. The shift is nine hours of elapsed time wearing an eight-hour label, and the local day is twenty-five hours long. In March it runs the other way: 2:00 a.m. becomes 3:00 a.m., the day is twenty-three hours, and the same shift contains seven.

The schedule behind this is federal and has been stable since 2007 — daylight saving runs from the second Sunday in March to the first Sunday in November, set by the Energy Policy Act of 2005, which amended the Uniform Time Act (Congressional Research Service, Daylight Saving Time (DST)). States may exempt themselves, and some do: Arizona apart from the Navajo Nation, Hawaii, and the US territories stay on standard time all year. If your property is in one of those, the rest of this post does not apply to you, and that is genuinely the end of it.

Eight or nine: two defensible ways to measure one shift

A time system can compute the length of that shift in two ways, and both look correct on the day they are written.

From the two moments. Take the instant the punch opened and the instant it closed, and subtract. Because those are absolute moments, the duplicated hour is inside the interval and gets counted. The answer is nine.

From the labels. Take 06:00 minus 22:00, add a day because the end reads smaller than the start, and return eight. This is the arithmetic everyone does by hand, and it is right on every night except two.

The two methods agree 363 nights a year, which is exactly why the disagreement survives. There is no error message, no exception, nothing to reconcile. One night a year the timesheet is an hour short and nothing on it looks wrong.

The schedule is the other half of this, and the schedule is always eight — including ours. A schedule is a plan written in clock labels, so any forecast of hours built from one will say eight for that Saturday night. That is less a defect than the nature of the document: a plan cannot know how long an hour will turn out to be. The consequence is what matters. On the two changeover nights, the schedule and the time record are supposed to disagree, and the time record is the one that happened.

What the ninth hour actually does

Take an invented 48-room motel with one night auditor working five nights, Wednesday through Sunday, each shift scheduled 22:00 to 06:00. The week the clocks go back:

ShiftScheduledActual elapsed
Wed–Thu8:008:00
Thu–Fri8:008:00
Fri–Sat8:008:00
Sat–Sun8:009:00
Sun–Mon8:008:00
Week40:0041:00

Forty hours scheduled, forty-one hours worked. Against a 40-hour weekly threshold — the one most properties in this segment are working to — the first premium hour of that week was produced by the calendar rather than by anything anybody decided. One hour at a premium rate is not a crisis. What makes it worth five minutes is that it is invisible: not on the schedule, not in the forecast, not in the roster, and visible only if the system measured the moments rather than the labels.

There are two other seams where it lands harder. If you operate in a state with a daily overtime threshold, a nine-hour night can cross a daily rule that an eight-hour night sits under, which moves the question from one premium hour to a different calculation entirely — the states with daily rules, and how they differ is worth a read before March if that is you. And in spring the error reverses: the week is thirty-nine hours, and a system measuring labels pays forty for thirty-nine worked. One night a year the arithmetic favours the employee and one night a year it favours the hotel. Whichever one you are running, the record disagrees with the night.

If you would rather read the night that happened than reconstruct it, start a free trial — hours come from the clock-in and clock-out moments and every date is resolved on the property’s own clock, which is the method that has a chance of getting these two nights right.

Which calendar day the hours land on is a separate problem

The neighbouring failure is worth naming so you do not go hunting for it here. An overnight shift also has to be filed under a day, and systems disagree about which — the day it started, or split at midnight into two part-days. That is independent of how long the shift was, it goes wrong on far more than two nights a year, and it has its own mechanism and its own ten-minute check. A changeover night can expose both at once, which is why the week after a time change is a good week to audit.

Two properties that share a clock for eight months

If you run more than one property, the changeover is also the day a portfolio stops lining up. Arizona stays on Mountain Standard Time all year. For the months daylight saving is in force, that puts a Phoenix property on the same clock as one in Los Angeles and an hour behind one in Denver; once the clocks go back it is the other way round — level with Denver, an hour ahead of Los Angeles. Nothing about either hotel changed. Any report that resolves “yesterday” centrally rather than at each property will quietly re-cut one of them on the first Sunday in November and again in March.

What you owe for that hour is a different question

Whether the ninth hour is compensable, at what rate, and what happens if the auditor is salaried rather than hourly, are wage-and-hour questions. They turn on how the employee is classified, on your state’s rules, and on any agreement you are party to. This is not legal advice and a blog post cannot settle it — take it to counsel licensed where you operate, or to your state labor department, and make your payroll match the answer.

What is not in dispute is the record. Nine hours of elapsed time happened at that hotel, and the timesheet is the document that is supposed to say so.

The check, and it takes about five minutes

The Monday after a changeover, before the pay period closes:

  1. Open the shift that spanned 2:00 a.m. on the changeover Sunday, for one employee.
  2. Read the hours total your system computed for it.
  3. Compare it against the scheduled hours for the same shift.

If both read exactly eight, your system is measuring labels. If the record reads nine against a scheduled eight, it measured the moments. Write down which answer you got, because the same test runs in reverse in March — a system that said eight in November will say eight again when the truth is seven, and that is the half that costs the hotel rather than the employee.

Start seeing what labor actually costs

Set up your property, put staff on the clock, and read tomorrow morning’s labor number.

14-day free trial · No credit card · Cancel anytime