Working Overnight When the Clocks Change: How Many Hours Did You Work?

Open the calculator

Dates, Clock Readings, and Elapsed Time

An overnight shift crosses midnight, so times alone are not enough. Write start date with start time and end date with end time. A note saying Saturday 22:00 to Sunday 06:00 cannot be verified later. A note saying 2026-03-07 22:00 to 2026-03-08 06:00, America/New_York, can be verified.

Keep local clock readings and elapsed time separate. Local clock readings are what the wall clock showed. Elapsed time is how much time passed while you were present. On ordinary nights they match. On clock-change nights they do not. Do not subtract the end reading from the start reading unless you have confirmed that no transition occurred between them in that zone on those dates. Keep original readings unchanged, then store elapsed time as a separate field.

Zone matters because transitions happen on different dates in different places. That is why every record needs the zone alongside both dates.

Repeated Times and Nonexistent Times

A fall transition creates repeated times. The clock moves back and runs through the same local hour twice. A reading such as 01:30 can therefore occur twice in one night: once before the change and once after it.

If your shift includes that hour, 01:30 alone is ambiguous. Record first occurrence or second occurrence next to any time inside the repeated hour. For an overnight shift, the safest method is to anchor both ends with full date, time, and zone, then add a note such as present through both occurrences of the repeated hour.

A spring transition creates nonexistent times. The clock moves forward and some local readings never happen. A schedule showing 02:30 may refer to a time that does not exist on that date in that zone. Do not invent a reading for the gap. Record continuous presence from dated start to dated end and note that clocks moved forward during the shift.

IANA Zones and Both Occurrences

Use an IANA zone name for the workplace, such as America/New_York or Australia/Lord_Howe. City names can be unclear near a boundary, and abbreviations can repeat across regions. The IANA name ties the record to the exact transition rules used on those dates.

Do not invent an offset for an unknown zone. Keep the IANA name with the original local dates and times. That preserves enough detail to calculate elapsed time later without adding unverified data.

Write fall records so both occurrences are explicit:

• Start: 2026-10-31 22:00, America/New_York
• End: 2026-11-01 06:00, America/New_York
• Breaks: none
• Note: present through both occurrences of the repeated hour

Write spring records so the gap is explicit:

• Start: 2026-03-07 22:00, America/New_York
• End: 2026-03-08 06:00, America/New_York
• Breaks: none
• Note: clocks moved forward during shift

Verified Overnight Examples Without Breaks

All examples below are without breaks and use local-clock 22:00 to next-day 06:00.

The spring row is shorter because one local hour is skipped. You arrive at 22:00 and leave at 06:00 by the wall clock, but only 7 hours pass. The fall row is longer because one local hour repeats. The same wall-clock span contains 9 hours of presence. These outcomes apply to those dates in that zone only.

Lord Howe needs its own table because its change is 30 minutes rather than one hour.

Here the fallback repeats 30 minutes, so the same 22:00 to 06:00 wall-clock span contains 8.5 elapsed hours. Do not apply this half-hour result to other zones.

Practical Checklist

1. Write start as date, time, and IANA zone: 2026-10-31 22:00, America/New_York.
2. Write end the same way: 2026-11-01 06:00, America/New_York.
3. Keep wall-clock readings unchanged.
4. Label times inside a repeated hour as first occurrence or second occurrence.
5. For spring, note clocks moved forward and avoid entering times that never existed.
6. Record breaks with dated start and end; subtract dated break duration from elapsed presence.
7. Store clock difference and elapsed presence as separate fields.
8. Do not add an offset from memory when it is unknown.
9. Keep the time record separate from the pay decision.

Mathematical Duration Versus Compensation

Mathematical duration tells how much time passed. Compensation applies the agreement and coverage rules for the worker. The public US Department of Labor Hours Worked Advisor discusses actual seven-hour and nine-hour worked examples when shifts cross daylight-saving transitions, within FLSA coverage. That guidance counts what was actually worked across the transition.

Use the same order in your records. First calculate elapsed presence from dated start, dated end, zone, breaks, and repeated-time notes. Then apply the relevant pay rules. Do not adjust the elapsed-time math to reach a pay result, and do not treat the 7, 9, 8, or 8.5 hour results above as pay decisions by themselves.

Sources and rule references

• US Department of Labor: daylight-saving hours worked
• 29 CFR 785.19: meal periods