Most rota software will let you schedule someone off at midnight and back in at 6am without blinking. That's legal in exactly nowhere in the EU, and it's the kind of thing that looks fine on a spreadsheet and terrible in an inspection — or worse, in a tribunal.
The rule, plainly
Under the EU Working Time Directive (and its UK-retained equivalent), workers are entitled to a minimum of 11 consecutive hours of rest in every 24-hour period. Italy, Germany, Spain and France all implement this directly, with only narrow, specific exceptions — hospitality isn't one of them by default, though some national collective agreements carve out limited derogations for genuinely unavoidable cases. The safe assumption for a rota: 11 hours, no exceptions, unless you've specifically checked your local CCNL or sector agreement.
Where it actually bites
The 11-hour rule doesn't get broken by bad intentions — it gets broken by Sunday-night rota Tetris. Your night auditor finishes at 07:00. Somebody swaps the Monday breakfast shift and the only person free starts at 06:00 the next day. That's 23 hours of rest short of the line, and nobody notices until it's already published — or until someone's too exhausted to notice they've made a mistake at the front desk.
What "compliant" actually looks like in practice
- Measure rest between the end of one shift and the start of the next, not calendar days — an 11pm–7am night shift followed by a 9am start is fine; followed by a 7am start is not.
- Treat rest as a hard constraint the scheduler enforces, not a rule your manager is expected to remember while also handling a walk-in at the desk.
- Flag violations before you publish the rota, not after a shift's already been worked.
- Log overrides. If an emergency genuinely requires a short-rest shift, that should be a deliberate, recorded decision — not a silent gap nobody notices.
Why this is worth automating, not memorizing
A property with 15 staff across three shift patterns has thousands of possible shift-to-shift transitions in a single week. No manager is checking all of them by hand, every week, forever. This is exactly the kind of rule that belongs in the scheduling engine itself: smartHOD's rota builder treats the minimum rest gap as a hard constraint — any late-to-early pattern under the threshold is flagged red on the schedule before you publish, not discovered after the fact.
The rule isn't complicated. Enforcing it by hand, every week, forever, is where things quietly go wrong.