Two shifts, both perfectly reasonable on their own. Someone closes on Friday, finishing at 00:30 once the till is done. They open on Saturday at 08:00.

That is seven and a half hours between finishing and starting. Across most of Europe the minimum daily rest is eleven consecutive hours, and this pattern - the close-then-open - is the single most common way a rota breaches it without anyone noticing.

Nobody notices because nothing on the schedule looks wrong. Friday's shift is fine. Saturday's shift is fine. The problem lives in the gap between two rows, and gaps are exactly what a weekly grid is bad at showing you.

Why it keeps happening

It is almost never deliberate. It is usually one of four things.

  • The closer is the opener because they are the keyholder. Small teams end up with two people who can lock up and open, and both ends of the day land on the same person.
  • The shift got longer than planned. A 23:00 close that actually finishes at 00:30 turns a compliant eleven-hour gap into a nine-hour one after the rota was published and approved.
  • A swap did it. Two people trade shifts, each trade looks fine in isolation, and the combination produces a gap neither of them would have accepted if asked directly.
  • It crosses a week boundary, so it is on two different printouts and nobody sees both at once.

The third one is worth dwelling on, because swap approvals are usually the least scrutinised change anyone makes to a published rota, and they are the change most likely to create this.

Spotting it without a system that checks for you

Sort by person, not by day. That is the whole trick. A rota laid out as a grid of days hides the gap; the same shifts listed per person in time order make it obvious, because you read the finish time and the next start time on consecutive lines.

Then look for three specific things:

  1. Any finish after 23:00 followed by a start before 10:00 the next day. That is the classic, and eleven hours is the line to test against.
  2. Any pair where the actual finish ran late. Compare against what was worked, not what was scheduled. This is where a compliant rota becomes a non-compliant week.
  3. Fridays and Saturdays specifically. Late closes and early opens cluster at weekends, and so do the breaches.

What to do instead

The fix is nearly always structural rather than a matter of asking people to be careful.

  • Separate keyholding from the person. If only two people can open, the close-then-open is arithmetic, not scheduling. Widening keyholding by one person usually removes the pattern entirely.
  • Make the opener the second shift of the day for the closer's counterpart. In practice: whoever closes gets a mid shift the next day, not the open. It costs nothing and it solves it.
  • Put the gap in front of whoever approves swaps. Most swap requests are approved on whether the two people are qualified and available. The gap either side is the thing worth checking, and it is the thing nobody has in view at the moment of approval.
  • Treat a late close as a change to tomorrow. If Friday ran ninety minutes over, Saturday's 08:00 start is now a different decision than it was when you published.

The bit worth being honest about

You cannot fix this with a policy that says "please leave eleven hours". Everyone agrees with the policy. The breach happens because the information is spread across two rows, two weeks or two people, and no one is looking at the join.

So the useful question is not whether your team knows the rule. It is: when someone approves a swap or extends a close, does anything put the resulting gap in front of them? If the answer is no, the rule is being enforced by memory, and memory is why this is the most common breach on the continent.

Daily rest is eleven consecutive hours under the EU Working Time Directive, and national rules vary around that floor - check yours, because a few countries and plenty of collective agreements are stricter. But the pattern is the same everywhere, and so is the fix.