Is a schedule a time record? Not once the hours move
· payroll, recordkeeping, time & attendance
A posted schedule is a plan. A time record is what happened. Federal recordkeeping rules do allow a narrow shortcut — for an employee on a genuinely fixed schedule, an employer may keep the normal daily and weekly hours and mark that those hours were in fact worked, instead of logging actual hours every day. But the same provision ends the shortcut immediately: for any week in which the employee works more or less than the scheduled hours, the exact hours for each day and each week have to be recorded (29 CFR 516.2(c)).
That is the whole answer, and it is worse news for a small hotel than it sounds. The shortcut belongs to a property whose week holds still, and a 50-room motel’s week does not. The honest reading is not “a schedule is never a record” — it is “a schedule is a record only for the weeks nothing moved, and you still have to know which weeks those were.”
What a time record has to contain
The federal baseline for a non-exempt employee is a short, specific list, and the two items that matter here are the hours. The Department of Labor’s own summary asks for hours worked each day and total hours worked each workweek, alongside the employee’s name and Social Security number, address, birth date if under 19, sex and occupation, the time and day of week the workweek begins, and the pay and wage items (DOL Fact Sheet #21).
Two things that list does not say are worth knowing, because operators assume both. No particular form is required — no mandated layout, no required software, no requirement that you own a time clock. Paper is legal; the information has to be complete and accurate. And clock times are not the federal minimum: the rule asks for hours worked each workday, not the moment work began and ended. Recording actual start and finish times is allowed, better evidence, and often required by a state — but it is a stronger record than the floor, not the floor.
So the gap between a schedule and a record is not a formatting problem. One of them is a forecast and the other is an observation, and only the observation survives a question about a specific Tuesday.
Count the exception weeks on your own floor
The fixed-schedule shortcut is easy to argue for in the abstract and easy to test in practice. Take an invented property: a 52-room exterior-corridor motel in western Nebraska, eleven non-exempt staff — four front desk, four room attendants, a houseperson who also runs laundry, one maintenance tech, one night auditor. Everybody is on a published five-shift rota. That is 55 scheduled shifts a week, and on paper the shortcut covers all of them.
Now walk one ordinary week:
| What happened | Shifts affected |
|---|---|
| 19-departure Sunday; two attendants ran about 35 minutes past | 2 |
| One of those two sent home early on a 9-departure Wednesday | 1 |
| 3-to-11 agent held 40 minutes for a late arrival | 1 |
| Morning agent’s car dead; night auditor covered the first two hours | 2 |
| Maintenance called in at 10 PM for a water heater | 1 |
| Houseperson moved their own Thursday to Friday | 2 |
Nine shifts out of 55 — about 16% — and nothing on that list is unusual. But the count that decides the question is not shifts, it is people: those nine shifts belong to seven of the eleven employees, and the rule attaches to the week, not to the day. For any week an employee works more or less than scheduled, you need exact hours for each day and each week of that employee’s week — not just the day that moved.
So the shortcut covered four people. Next week it covers a different four, and you will not know which four until the week is over — so its correctness depends on reconstructing afterwards which of eleven people had an ordinary week. That is more work than recording eleven ordinary weeks. The shortcut is real, and at this size it costs more than it saves.
If you want to see what a week looks like when the record is captured rather than reconstructed, start a free trial and run one real week through it alongside your rota.
What a schedule structurally cannot show
Three kinds of movement account for almost all of the gap, and a schedule is blind to all three by construction:
- Held over. The shift that should have ended at 15:00 ended at 15:34 because a check-in arrived with a problem. The schedule says 15:00 and always will.
- Sent home. A light departure morning ends at 12:40. This is the direction operators forget, and it cuts the other way: a schedule used as a record overpays here, and systematic overpayment is still a finding that your records are not records.
- Moved. Somebody worked Friday instead of Thursday and told the supervisor verbally. The schedule is now wrong about which day, not just how long — and a day is the unit the rule is written in.
The same blindness is why an assumed break is not a record. A 30-minute deduction applied because the schedule has a break in it is an assumption dressed as data. And real work before the scheduled start is the case most people misread as theft rather than as a recordkeeping failure.
When the record is thin, somebody else’s number fills the gap
This is the part that changes how much the question is worth. Under Anderson v. Mt. Clemens Pottery Co., 328 U.S. 680 (1946) — whose burden-shifting framework courts still apply, whatever later happened to the rest of that decision — an employee can carry their initial burden, where the employer has not kept the required records, by producing evidence sufficient to support a reasonable inference of the hours worked. It then falls to the employer to produce evidence of the precise amount, or to undercut the reasonableness of that inference. An employer who did not keep the records cannot complain that the resulting figure lacks precision.
Read that as an evidence rule, not a threat: in a dispute, the party holding the better record sets the starting number. If your record is the schedule, your best evidence says 7:00 to 15:00, every day, for everyone — the one thing both sides already agree is not what happened.
None of this is legal advice, and it is the federal floor only. States add their own requirements on top — more detail on the record, longer retention, itemised wage statements, sometimes per-shift start and finish times outright — and a city ordinance or a collective bargaining agreement can add more still. The federal retention baseline is covered in what to check before buying hotel time clock software; your own state’s rule is on your state labor department’s site, and it changes. Check it, and talk to your own counsel about your own property.
The summary of the regulations and the case above is based on secondary sources and should be checked against the primary text.
Keep the schedule. Just stop asking it to testify
The practical version is four things, and only the first is about software:
- A start and finish time for every shift, captured when it happens. Reconstructed time is an estimate with a timestamp on it.
- A trace on every change. Hours get corrected — a missed clock-out, a kiosk nobody could reach. The question is whether the correction leaves the original visible; an edit that overwrites it leaves you one number and no evidence about the other. ProfitClock keeps punch edits as history instead of overwriting them, and the approval accepting a change is a recorded decision rather than a formality.
- The right day. A record of hours is only as good as its idea of which day they fell on, which at a hotel means the property’s own calendar day rather than a server’s. Overtime computed on the wrong day is the same class of fault as a schedule used as a record: the totals look fine and the grouping is wrong.
- The schedule, kept as a schedule. This is worth saying plainly, because the argument above is not that the rota is useless. The variance between what you planned and what you paid is one of the most useful numbers on the property, and you only get it if you keep both. What you cannot do is keep one and call it the other.
Where this is genuinely hard: a property with a stable rota, no overtime, no call-outs and no swaps really can use the shortcut, and for a small steady operation a timekeeping system may not pay for itself on recordkeeping alone. The argument at a 50-room motel is not paperwork — it is that your week moved nine times, and nine moved shifts is the payroll difference between a good month and a bad one. The record is where you find out which one you had.
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