For daylight saving day pay, credit all hours actually worked; a shift crossing the clock change may differ from its scheduled total.
Key takeaways
- Find overnight shifts that cross the clock change.
- Count elapsed hours from actual punches, accounting for the skipped or repeated hour.
- Check whether scheduled totals already account for the change.
- Explain differences and review the records before payroll closes.
Why a clock change matters on night shifts
A day shift that starts at nine in the morning and ends at five in the afternoon sits safely on one side of the change, and the schedule matches the clock on the wall. A night shift is different. A shift that starts in the late evening and ends early the next morning runs straight through the moment the clock jumps, so the number of hours a person actually works can differ from the number printed on the schedule.
That gap is where timesheets go wrong. A manager fills in the scheduled number, the payroll system accepts it, and nobody checks whether the shift really lasted that long. For a small staffing team handling many overnight placements, one wrong line at each clock change adds up quickly.
This post is for hiring managers and small staffing teams who review timesheets for night shifts. The goal is simple: make sure the recorded hours are the hours worked. The principle comes from the U.S. Department of Labor, which works through this exact situation in its elaws - FLSA Hours Worked Advisor. The rest of this post follows that guidance and turns it into a practical check you can run on any timesheet.
What the advisor says about the spring change
The advisor starts with the change to Daylight Saving Time, when clocks move forward. Its example describes employees on a graveyard shift when that change happens, and it says they "work one hour less because the clocks are set ahead one hour."
The advisor explains the mechanics in a second sentence: "On the Sunday that Daylight Savings Time starts at 2:00 a.m., you do not work the hour from 2:00 a.m. to 3:00 a.m. because at 2:00 a.m. all of the clocks are turned forward to 3:00 a.m." In plain terms, the clock jumps from 2:00 straight to 3:00. The hour between those two times never appears on the clock, so a worker on a shift that runs through the jump does not spend that hour on the job.
The advisor then gives the total for a shift like this: "Thus, on this day you only worked seven hours, even though the schedule was for eight hours."
The advisor is also careful about the assumption behind that result. It adds: "This assumes, of course, that you actually worked the scheduled shift as in our example." The seven-hour figure is not a discount or a rounding convention. It is the count of hours a worker actually put in when the clock skipped ahead, and it only holds if the worker was on the job for the full scheduled shift apart from the missing hour.
For a manager, the practical lesson is that the spring night is the one where the schedule overstates the hours worked in this example. If the timesheet simply copies the eight scheduled hours, it records time that nobody spent working.
What the advisor says about the fall change
The fall change runs the other way. When Daylight Saving Time ends and clocks move back, the advisor says that "Those employees working the graveyard shift when Daylight Savings Time ends work an extra hour because the clocks are set back one hour at 2:00 a.m."
Again the advisor shows the mechanics: "On the Sunday that Daylight Savings Time ends at 2:00 a.m., you work the hour from 1:00 a.m. to 2:00 a.m. twice because at 2:00 a.m. all of the clocks are turned back to 1:00 a.m." The clock runs through the hour from 1:00 to 2:00, reaches 2:00, and then jumps back to 1:00. The worker lives through that hour twice.
The total follows: "Thus, on this day you worked nine hours, even though the schedule only reflected eight hours."
The seven-hour and nine-hour days
The table below summarizes the example for a scheduled eight-hour overnight shift that crosses the change:
| Clock change | Scheduled shift | Hours worked in the advisor's example |
|---|---|---|
| Clocks move forward (spring) | eight hours | seven hours |
| Clocks move back (fall) | eight hours | nine hours |
Notice that the advisor says "similar to" the example, not "identical to" it. Your shifts may start at different times, so check the applicable local clock-change time before counting elapsed hours. The principle still applies: find the hours that were actually worked, and let the timesheet reflect them.
Why the schedule is not the pay record
The most important sentence in the advisor's guidance is a general one: "The Fair Labor Standards Act requires that employees must be credited with all of the hours actually worked." That sentence is the reason the schedule cannot be the pay record.
A schedule is a plan. It says when a person is expected to work. The timesheet is supposed to be a record of what happened. On a clock-change night those two can disagree by an hour, and when they do, the timesheet has to follow what happened.
Recording eight hours worked when seven were worked is inaccurate. Crediting only eight hours when nine were worked leaves an hour uncredited.
Managers sometimes feel that the schedule is the safe default because it is familiar. Verify scheduled hours against actual hours worked. On clock-change nights, check whether the scheduled total already accounts for the change.
How to check a timesheet on a clock-change night
You do not need special software to run this check. You need the punch or sign-in record for each overnight shift and a calendar of when your local clocks change. The steps below work for a small team with a simple process.
-
Find the shifts that cross the change. Look at any overnight shift that was in progress when the clocks moved. A shift that ends before the change or starts after it does not need the adjustment.
-
Use the recorded start and end times. Take the times from the punch record, not from the schedule. If a worker clocked in late in the evening and out early the next morning, those are the times to work from.
-
Count the elapsed time. Compare the clock times with the change. For a spring shift crossing the jump, subtract one hour from the unadjusted difference between recorded local start and end times. For a fall shift crossing the repeated hour, add one hour to that unadjusted difference.
-
Compare with the schedule. Compare elapsed hours with scheduled length only after checking whether the worker followed the schedule and whether its total already accounts for the change.
-
Check for anything that breaks the pattern. The advisor's example assumes the worker actually worked the scheduled shift. If someone left early, arrived late, or took unscheduled time, the count will differ, and that difference should be explained in the record.
-
Write down the reason for any change. A short note such as "clocks moved back, shift ran nine hours" helps the next reviewer and protects both the business and the worker when questions come up later.
Check discrepancies while the original punch records are still easy to review.
Illustrative example: checking a fall shift
The recorded local start and end times suggest eight hours before accounting for the clock change. The worker stays on the job throughout the repeated hour, with no other time away. Adding that repeated hour gives nine hours worked. Record nine hours, explain the clock change, and check whether the schedule already shows that total before changing anything.
Setting up your timekeeping for the change
The clock change exposes weaknesses in some timekeeping setups. Before the next change, it is worth checking a few things.
First, make sure the system records actual clock times with enough detail to tell the two passes through the repeated hour apart. On the fall night, a punch taken during the repeated hour could be the first pass through it or the second. A system that records only the hour, or a paper log with a single column for each hour, may not be able to tell them apart. If that is your setup, add a note or a sequence marker for punches in that hour.
Second, review any rounding that applies to overnight shifts. If your system rounds punches, applying a rounding rule to a scheduled time rather than the actual punch can hide the one-hour difference the advisor describes. Check how the rules interact on clock-change nights.
Third, decide in advance who reviews the change-night timesheets and when. The best time is before payroll closes, not after a worker raises a question. A named reviewer and a fixed checkpoint keep the process from depending on memory.
Fourth, if your system stores times in a single format, confirm that the export to payroll shows the actual elapsed hours, not only the scheduled block. Errors can creep in during the handoff between the timekeeping tool and payroll, where the schedule can quietly replace the punch. Use the time clock setup checks when reviewing that handoff.
Talking to night workers about the adjustment
Workers notice when their hours look different from the schedule. A night worker who sees seven hours on the spring timesheet may assume they were shorted, and a worker who sees nine hours on the fall timesheet may wonder whether the entry is a mistake. Tell them before the change, not after.
A short message to night staff is enough. Explain that the clocks will change on a specific night, that a shift crossing the change may show one hour less or one hour more than the schedule, and that the timesheet will reflect the hours actually worked. Share the advisor's example, which is short and easy to read, so the explanation comes from an official source and not from a manager's opinion.
Invite questions and make it easy to raise them. If a worker believes the recorded hours are wrong, they should be able to point to their own punch times and have the record reviewed. A worker who can check the count themselves is less likely to feel that the process is unfair.
For staffing teams placing workers at client sites, add a line to the client communication as well. A client who schedules an eight-hour overnight block may see a different total on the timesheet during the change week. Explain in advance that the total follows the hours worked, and check your contract for how hours are measured and reported. The contract language, not this post, decides what a client agreement requires.
When the punch record is missing or unclear
Sometimes the record is incomplete. A worker forgets to punch out, a terminal fails, or a paper sheet is left blank. The clock change makes these gaps more painful, because the count depends on knowing the exact times.
The advisor's principle still applies: the question is the hours actually worked. A missing punch does not justify copying the schedule by default, because the schedule may not match what happened. Instead, gather whatever evidence exists. A supervisor's note, a badge log, a call record, or a message showing when the work ended can help reconstruct the shift.
Document every decision you make. Record what was missing, what evidence you used, who approved the figure, and why. A clear note turns a gap into a documented correction and makes it easier to defend if the figure is ever questioned.
If no reliable evidence exists, the decision should be made openly and recorded, not hidden inside a default. Whatever you choose, the timesheet should say how the hours were determined.
Common mistakes to avoid
Several errors come up again and again on clock-change nights. Knowing them in advance makes them easier to catch.
Paying the schedule by default. This is an easy error to make. Copying scheduled hours into the hours-worked record is accurate only when they match actual hours worked.
Assuming the change happens at midnight. The advisor's examples place the change at 2:00 a.m. A worker whose shift starts late in the evening and ends early the next morning is on the job across that time. Do not assume the change falls at the start or end of the shift, or at the middle of the night, without checking the actual change time for your location.
Forgetting the repeated hour in the fall. A reviewer who sees a fall shift of nine hours may assume the number is a mistake and reduce it to eight. That undoes the correction. The advisor is clear that the extra hour is real time worked.
Checking only the first and last punch. The first and last punch show the start and end of the shift, which is what the count needs. But if a worker took an unscheduled break or left and returned, the middle of the shift matters too. Look at the whole record, not only the endpoints. For a separate break review, see the meal break rules for shift handoffs.
Treating every difference as an error. A nine-hour fall shift or a seven-hour spring shift may be exactly right. The mistake is in forcing the timesheet back to the schedule, not in the difference itself.
Missing overnight shifts that cross the change. The clock change applies to every shift that crosses it, not only the one a manager happens to notice. Build the check into the review of every overnight timesheet for that week.
Keeping the records
Good records make the clock-change check easy to repeat and easy to defend. Keep the punch records, the schedules, and any notes about changed hours together for each overnight shift. A single file or folder for each change night works well for a small team.
Each entry should show the scheduled hours, the recorded start and end times, the hours counted, and the reason for any difference. If the count matches the pattern in the advisor's example, a short note is enough. If it does not, the note should explain the difference in plain words.
Keep the records for as long as your own policies and any contract or legal obligation require. Those requirements depend on your business and location, so check them with the people responsible for payroll and compliance. The point of keeping records here is practical: when a question comes up about a night shift, the record should answer it without anyone having to reconstruct the night from memory.
Store the records somewhere the reviewer can reach them easily. A record that exists but cannot be found during a dispute is of little use.
Putting it into practice
Today, pick a reviewer and have them check whether your timekeeping records distinguish punches in the repeated hour. Before the next change, confirm that your timekeeping records actual punch times, check how rounding applies on overnight shifts, and tell your night workers what to expect. Then run the check on every overnight shift that crosses the change. The time spent on this check helps catch a wrong total before payroll closes.
Questions about clock-change timesheets
Should you automatically change scheduled hours?
No; check actual elapsed work time and whether the schedule already accounts for the clock change.
What if a punch falls in the repeated hour?
Identify which pass through the hour it records. Use the sequence of punches and any supporting notes before counting elapsed time.