What happens right at a daylight saving transition?

The calculator flags it explicitly in the result, stating that a transition occurred, rather than silently reporting a wall-clock-only duration that would be off by an hour.

Why does this need a time zone at all instead of just two clock times?

Because whether a daylight saving transition falls inside the shift, and exactly when, depends on the specific zone the shift happened in, not on the clock times alone.

Paid vs Elapsed Time Calculator

Give a dated start and end in a specific time zone, plus any breaks. This resolves the real elapsed time (accounting for a possible daylight-saving transition) separately from the paid time after unpaid breaks.

No time zone or DST concern? The simpler Hours Calculator covers plain-clock shifts.

Want to learn more?

How Daylight Saving Transitions Distort Elapsed-Time Math

Worked example

A shift from 09:00 to 17:00 on an ordinary day, with no daylight saving transition involved, elapses exactly 8 real hours, and with a 30-minute unpaid break subtracted the paid total comes to 7 hours 30 minutes, matching what a plain wall-clock subtraction would also give. The real value of this calculator shows up on a day when the clocks in the shift's own time zone actually change. A shift spanning a spring-forward transition, where clocks skip an hour forward at a fixed local moment, elapses one real hour less than the wall-clock reading suggests, since that missing hour was never actually lived through. A shift spanning a fall-back transition elapses one real hour more than the wall-clock reading suggests instead, since that hour of local time genuinely repeats. Either case, this calculator resolves through the shift's real IANA time zone rather than subtracting clock readings directly.

Common mistakes

Assuming elapsed time always equals the plain wall-clock difference between the start and end times. Across a daylight saving transition, the real elapsed time and the wall-clock difference disagree by a full hour.
Entering a time zone that does not match where the shift actually took place, which can silently apply the wrong transition dates to the calculation.

Limitations

This resolves one shift in one stated time zone. It does not coordinate a shift or a meeting across multiple zones at once. See the time zones category for tools built specifically for that kind of cross-zone coordination.

Frequently asked questions

What happens right at a daylight saving transition?: The calculator flags it explicitly in the result, stating that a transition occurred, rather than silently reporting a wall-clock-only duration that would be off by an hour.
Why does this need a time zone at all instead of just two clock times?: Because whether a daylight saving transition falls inside the shift, and exactly when, depends on the specific zone the shift happened in, not on the clock times alone.