Setting Rest-Hour and Consecutive-Shift Rules That Actually Hold
Rest and consecutive-shift rules fail most often not because managers don't know them, but because the schedule is built week by week with no check against what came before. Here's how to make the rules stick.
Most rest-hour violations aren't caused by managers ignoring the rules. They happen because a schedule gets built one week at a time, and nobody looks back at the shift that ended the night before. Someone closes at 11pm Tuesday and opens at 6am Wednesday, and it passes review because the two shifts sit in different weekly views, or different people built each one. The fix isn't more training — it's building the check into how you schedule, not into what you remember.
Why these rules get broken even by careful managers
Rest and consecutive-shift limits are simple in theory: a minimum gap between the end of one shift and the start of the next, and a cap on how many days in a row someone can work. In practice they break down for predictable reasons:
- The schedule is built in weekly chunks, so the last shift of one week and the first shift of the next are never compared side by side.
- Multiple people build the schedule (shift leads, department heads) and nobody owns the full picture for one employee across departments.
- A swap or a covered call-out changes someone's hours after the original schedule was approved, and the new combination never gets re-checked.
- Open shifts get claimed by whoever's fastest, not whoever has rest hours left.
- "Consecutive days" gets counted by calendar week instead of rolling days, so someone working Thu-Sun then Mon-Thu looks fine on paper but has worked eight days straight.
That last one catches more businesses than any other. If your count resets every Monday, you can build a fully "compliant" schedule that still runs someone ragged across the boundary.
Building rules that survive contact with a real schedule
A rule only holds if it's checked at the moment a shift is assigned, not after the week is published. A few practical habits:
- Write the rule as hours, not shifts. "11 hours between shifts" is enforceable. "One shift off between closes and opens" isn't — it doesn't say how long the gap actually is.
- Count consecutive days on a rolling basis, not by calendar week. Check the seven days ending on any given day, not just Monday-to-Sunday.
- Check across departments and locations, not just within one schedule. Someone who works stockroom Monday-Wednesday and front-of-house Thursday-Saturday is still one person with one set of rest hours.
- Re-check after every swap or open-shift claim. A shift that was fine when assigned can become a violation the moment it's traded.
- Put the limit in writing where schedulers see it, not in a policy document nobody reopens. A rule that lives in someone's head gets forgotten during a busy week.
Where automation actually helps
This is one area where manual scheduling genuinely struggles, because the check requires looking at every other shift that employee has — including ones outside the week you're currently editing. Tools that apply working-time rules per country while you're building the schedule, and flag it the moment an assignment or swap would put someone under the rest-hour minimum, catch problems before they're published rather than after someone complains or a labor inspector asks questions. helloswap checks these rules as shifts are built or swapped, which matters most exactly at the handoff points — end of week, change of department, after a swap — where manual review tends to miss them.
Whatever system you use, the test is the same: can you see, for one person, every shift they're on across the full week and across departments, checked against the actual rule, not the policy summary. If you can't answer that in under a minute for any employee, the rule isn't holding — it's just written down somewhere.