Help center/Time and pay
Why a night shift can be 13 hours
What we count, and why it is not what a clock face says.
Read the transcript
A night shift from seven in the evening to seven in the morning is twelve hours, except on the two nights a year when the clocks change. In this video you'll see why MedAligna counts real elapsed time, what that looks like on the schedule on both nights, how the payroll export shows it, and which time zone decides. Here's Luis's week of nights at the end of October. On Saturday the thirty-first, the clocks go back an hour at two in the morning. His shift still says seven to seven, but the chip shows thirteen hours real, twelve on the clock. He was there for thirteen real hours, so that's what we count. That's daylight saving time. In the US, the clocks go forward an hour on the second Sunday of March and back an hour on the first Sunday of November, both at two a. m. Any shift that runs across two a. m. that night is an hour longer or shorter than its clock times suggest. A system that subtracts one clock face from the other gets twelve every time, and shorts that nurse an hour of pay every autumn. Every duration in the product is computed the same way, from the two real moments a shift started and ended: the hours on the time clock, rest gaps, overtime, the weekly total, the payroll export and the CMS PBJ file. Here, Luis's week is thirteen plus twelve plus twelve: thirty-seven hours, which is over his thirty-six-hour contract, and the overtime warning says so. Now the spring change. Saturday the seventh of March, seven p. m. , to Sunday morning at seven. At two a. m. the clock jumps to three, so the hour from two to three never happens. Luis worked eleven hours, and the chip says so. His week is eleven plus twelve plus twelve: thirty-five, not thirty-six. A seven-to-seven day shift on either Sunday is unaffected, because the change happens at two a. m. , hours before it starts. Here's Maya's day shift on Sunday the first of November: twelve hours. And an unpaid break is subtracted after the real time is measured, so a thirteen-hour night with a thirty-minute break exports as twelve point five. Open Exports, pick the dates around the change, and press Show hours. Because a thirteen-hour night looks like a typo to whoever approves the timesheet, the screen says so up front: the clocks changed during this shift, twelve hours on the clock, thirteen actually worked, and we export the real figure. In the summary, Luis has thirty-seven hours. The Source column says whether a figure came from the time clock, Clocked, or from the rostered times, Scheduled. These nights haven't been worked yet, so they're scheduled hours. Here's that night in the all-hours CSV. Date, the thirty-first. Start, seven p. m. End, seven a. m. Hours, thirteen. The start and end are what he saw on the clock; the hours are what he worked; and the two are not inconsistent. The local date is the day the shift started, so a night is filed under the evening it began. The note explains the clock change, and hours are summed unrounded and rounded to two decimals once, at export. Which time zone decides? The place the work happens: the site's time zone, or the hospital's, when the shift is call carried at a service you don't operate. Not the server's, and not yours. Each shift remembers the time zone it was worked in, and you can see the site's zone here, in Settings. Correcting a site's time zone once shifts exist means confirming the wall times were the truth: seven a. m. stays seven a. m. , and the shifts move with the clock. Once anyone has clocked in at that site, it's refused, because a clock-in is a real moment that can't honestly be moved; add a new location instead. And two edge cases are always decided the same way: a start time that doesn't exist on the spring night moves forward past the gap, and one that happens twice on the autumn night takes the first. Finally, what this is not. It's an hours figure, not a pay calculation. The export carries no rate, no differential and no dollar figure, and we never compute gross or net pay, withhold tax or move money. Your payroll provider prices the thirteen hours; our job is to make sure it's thirteen. To recap: every hour is measured between two real moments, so the autumn night is thirteen hours and the spring night is eleven. The export carries the real figure, with a note that explains it. And the clock that decides is the one at the site where the work happens.
Filmed in the product on October 23, 2026. All video tutorials
Real elapsed time, always
A 19:00–07:00 night is twelve hours on most days. On the night the clocks go back it is thirteen real hours, and on the night they go forward it is eleven. We count the hours that actually passed, so the night somebody worked thirteen hours reaches payroll as thirteen.
That is daylight saving time: in the US the clocks go forward an hour on the second Sunday of March and back an hour on the first Sunday of November, both at 2 a.m., so any shift that runs across 2 a.m. that night is an hour longer or shorter than its clock times suggest. A system that subtracts one clock face from the other gets twelve every time, and shorts that nurse an hour of pay every autumn.
Every duration in the product (the hours on the time clock, rest gaps, overtime, the weekly total, the payroll export and the CMS PBJ file) is computed the same way, from the two real moments a shift started and ended, never from the wall-clock times. The number on a nurse's phone and the number in the export are the same number.
A worked example: the two nights in 2026
Take a nurse on three 19:00–07:00 nights a week at a site on US Eastern time. In 2026 the clocks go forward on Sunday 8 March and back on Sunday 1 November.
Saturday 7 March, 19:00 → Sunday 8 March, 07:00. At 02:00 the clock jumps to 03:00, so the hour from 02:00 to 03:00 never happens. She worked 11 hours. Her week is 11 + 12 + 12 = 35, not 36.
Saturday 31 October, 19:00 → Sunday 1 November, 07:00. At 02:00 the clock goes back to 01:00, so the hour from 01:00 to 02:00 happens twice. She worked 13 hours. Her week is 13 + 12 + 12 = 37.
A 07:00–19:00 day shift on either Sunday is unaffected: the change happens at 02:00, hours before it starts. An unpaid break is subtracted after the real time is measured, so a 13-hour night with a declared 30-minute break exports as 12.50.
How the export shows it
In the all-hours CSV the row for that night reads Date 2026-10-31, Start 19:00, End 07:00, Hours 13.00. The start and end are what she saw on the clock; the hours are what she worked, and the two are not inconsistent. The Hours Source column says whether the figure came from her clock-in and clock-out (Clocked) or from the rostered times (Scheduled), and the local date is the day the shift started, so a night is filed under the evening it began.
Because a 13-hour night looks like a typo to whoever approves the timesheet, the row carries a note: 'Clocks changed during this shift: 12.00 on the clock face, 13.00 actually worked (gained an hour). The hours figure is the real one.' The per-person summary counts the rows that crossed a clock change, so a payroll clerk can see why one week a year does not add up to the roster. Hours are summed unrounded and rounded to two decimals once, at export.
Which clock
The authority is the place the work happens: the site's timezone, or the hospital's timezone when the shift is call carried at a service you do not operate. Not the server's, and not yours. A Denver group covering Chicago call sees 07:00 in Chicago, and its hours are counted there.
Each shift remembers the timezone it was worked in. Correcting a site's timezone once shifts exist means confirming that the wall times were the truth (07:00 stays 07:00 and the shifts move with the clock), and it is refused entirely once anybody has clocked in at that site, because a clock-in is a real moment that cannot honestly be moved; Settings offers a new location instead. Two edge cases are decided the same way every time: a start time that does not exist on the spring night (02:30) is moved forward past the gap, and one that happens twice on the autumn night (01:30) takes the first.
What this is not
It is an hours figure, not a pay calculation. The export carries no rate, no differential and no dollar figure, and we never compute gross or net pay, withhold tax or move money. Your payroll provider prices the 13 hours; our job is to make sure it is 13.
More on time and pay
Not what you needed? Email helen@medicalstaffscheduling.com.
Already a customer? Sign in. Not yet? Open the live demo or start a free trial.