The 11-Hour Rest Rule: Why the Most Common ATW Violation Is the One Planners Never Think About

The shift pair that violates the law every weekend

Picture a roster you've probably seen a hundred times. An employee works a closing shift on Friday, finishing at 22:00. They're back for the opening shift on Saturday, starting at 06:00. Eight hours between punching out and punching back in.

That roster is illegal. It violates the Arbeidstijdenwet by three full hours. And it's happening across retail and hospitality rosters in the Netherlands every single week.

The employee probably asked for it. Maybe they wanted the Saturday hours for the extra income, or it just worked for their weekend plans. The planner saw a gap in the Saturday morning schedule, checked the employee wasn't already over their weekly hours, and filled it. Everything looked fine.

The fact that the employee agreed changes nothing. That's the first thing to understand about ATW Article 5:3, and it's the detail that makes this violation so persistent.

What ATW Article 5:3 actually says

The rule is simple. Every employee is entitled to at least 11 consecutive hours of rest between two shifts within any 24-hour period. This is a public law standard, not a contractual term. It cannot be waived by the employee. It cannot be traded away in a side agreement. It cannot be overridden by a verbal "she was fine with it."

There is one narrow exception. Under specific sector CAO provisions, rest can be reduced to a minimum of 8 hours, but only once per seven-day period, and only where the nature of the work genuinely requires it. That reduction must be explicitly permitted by your sector CAO. An informal arrangement between planner and employee carries no legal weight.

This matters because planners often conflate two separate obligations: maximum working hours and minimum rest periods. Both must be satisfied simultaneously. An employee who works 36 hours in a week, well within the ATW limits, can still have accumulated multiple rest-period violations. The hour total tells you nothing about the gaps.

The practical implication: you can build a roster that passes every weekly and daily hour check and still be systematically non-compliant on rest.

Why planners miss it: the cognitive bias toward hours, not gaps

Scheduling intuition is built around totals. How many hours is this person working? Are they over 12 hours in a day? Over 60 in a week? These are the numbers planners see, calculate, and worry about.

The gap between shifts is not a number that most tools surface. A spreadsheet shows shifts. It shows start times, end times, durations. It does not, by default, calculate the interval between the end of one shift and the start of the next and flag it with a colour.

The violation is invisible because the data that would reveal it is never computed.

Overtime violations, by contrast, get caught quickly. Extra hours create immediate cost pressure. They show up on payroll reports. Someone in finance asks a question. The feedback loop is fast. Rest-period violations have no such feedback loop. The employee doesn't complain because they wanted the hours. The payroll looks normal. Nothing triggers a review.

This is not a knowledge problem. Most planners, if asked directly, can tell you that 11 hours rest is required between shifts. The problem is that the question never gets asked during the scheduling process. The shift gets filled, the week template gets saved, and the pattern repeats every weekend for months.

When it surfaces, and why the timing is the worst possible

Months pass. The employee works their close/open rotations every other weekend. Then something changes. They go on extended sick leave. A WIA arbeidsongeschiktheid claim gets filed. Or an FNV inspector requests roster documentation as part of a sector audit. Or the Nederlandse Arbeidsinspectie arrives with a standard inspection request covering 12 months of roster and time-registration records.

At that point, every rest-period violation in those records becomes a documented finding.

The NLA's boetenormbedragen for ATW violations run from around 1,500 euros per minor finding to upward of 10,000 euros for systemic failures, meaning patterns that repeat across employees and time periods. A retail organisation that's been running close/open pairs on three or four employees every weekend for a year isn't looking at one fine. It's looking at a systemic finding that multiplies.

There's a harder problem than the fine. Companies found in violation are listed on the NLA's public register. For healthcare providers and regulated hospitality businesses, that listing creates disproportionate reputational damage relative to the actual fine amount.

And then there's the sick-leave dimension. An employee claiming WIA is represented by a lawyer or FNV delegate reviewing the employment record. A pattern of documented ATW rest violations strengthens their position in the arbeidsongeschiktheid assessment, particularly if they're arguing that fatigue contributed to their condition. The employee who "wanted the hours" is now the claimant. The informal agreement that seemed harmless at the time is now absent from the record, while the violation is present in it.

NLA inspectors request roster exports alongside time-registration data. A spreadsheet that doesn't calculate gaps is not a defence. It is evidence of a planning process that didn't check for what it was legally required to check for.

The sector CAO layer makes it more complicated

ATW Article 5:3 sets the floor. Your sector CAO may raise or lower it, and getting that wrong adds a second layer of exposure.

We covered the structural logic of this two-layer compliance problem in the CAO roster compliance overview, but the rest-period rule has some particularly sharp sector-specific edges worth naming here.

In healthcare, the CAO VVT imposes additional constraints on shift length alongside its 28-day roster notification requirement. Some zorg CAOs restrict shifts to nine hours, which narrows the safe scheduling window further. For a nurse finishing a nine-hour shift at 23:00, the next shift cannot start before 10:00. That's later than most planners instinctively assume.

Consignatiediensten (standby arrangements) in homecare create a separate complication. Following the CJEU Matzak ruling and its application in Dutch employment tribunals, standby hours where an employee must respond within a very short window, typically 15 minutes or less, count as working time under ATW. A homecare worker on consignatie from midnight to 06:00 is not resting. They are working. Their rest period begins when the consignatie ends, not when it starts. Several homecare providers restructured their entire on-call roster model after tribunal decisions applied this reasoning to their specific arrangements.

In hospitality, the CAO Horeca's four-day notification window creates a layered problem. If a roster has already been published, a change within that window triggers toeslag rights. If that change also creates a sub-11-hour gap, you now have both a rest-period violation and an unrecorded toeslag obligation. The gap violation and the notification violation are separate findings, but they almost always occur together in late roster changes.

Checking ATW alone tells you nothing about your actual compliance position. The sector CAO overlay determines your real exposure.

Three things you can check in your current roster today

This doesn't require new software. It requires 30 minutes and a spreadsheet export.

The gap test. Export your roster for the past four weeks. For each employee, list every consecutive shift pair: the end time of one shift and the start time of the next. Calculate the interval in hours. Flag every pair below 11 hours. If you have any flags, you have documented violations. The calculation is straightforward: `=((next_start - prev_end) * 24)` in decimal hours if your times are stored as Excel date values.

The close/open pattern scan. Look at your recurring week templates. Search for any combination of an evening shift ending after 21:00 followed by a morning shift starting before 07:00. These are the structural patterns that generate rest violations by default, every time they repeat. A 22:00 finish followed by a 06:00 start is an eight-hour gap. A 21:30 finish followed by a 06:30 start is a nine-hour gap. Both are violations. Both are probably sitting in a template that's been in use for years.

The consent trail check. Think about informal shift swaps from the past month. Any agreement made via WhatsApp, verbally in the break room, or by text message. If any of those swaps placed two shifts closer than 11 hours apart, the informal consent provides no legal protection. The violation exists in the roster data. The consent doesn't.

The cost of running this audit is negligible. The cost of not running it is an NLA inspection that finds what you would have found yourself, months before, for free.

Building the gap check into your planning process

The audit tells you where you stand today. The harder work is making sure the pattern doesn't regenerate.

The core change is treating the 11-hour gap as a hard constraint at roster-build time, not a post-publication review. Every planner already treats a max-hours breach as a hard stop. The 8-hour rest gap between that Friday close and Saturday open should generate the same response: this shift cannot be assigned here.

If you use scheduling software, check how it handles rest-period violations. Not all tools treat them equally. Some surface rest gaps as high-priority alerts that block publication. Others bury them as low-severity warnings underneath hour-cap notifications, where they get ignored. Some don't calculate them at all. This is worth verifying explicitly, because "we have scheduling software" is not the same as "our scheduling software checked for rest-period gaps." When Soon's auto-scheduler handles shift constraints, minimum time between shifts is a first-class constraint that the solver respects before assigning anyone. Not all tools are built that way, and it's worth confirming which category yours falls into.

For organisations using multiple shift templates across departments, the gap violation most often occurs at the boundary between templates. Team A's last shift ends at 22:30. Team B's first shift starts at 06:00. No one owns the transition between those two templates, so no one checks it. Assign someone to review cross-template shift pairs specifically. This is where the structural blind spot lives.

Document any legitimate exceptions explicitly. If your sector CAO contains an afwijkingsbepaling that allows reduced rest in specific circumstances, the documentation linking that CAO clause to the specific shift is the evidence that protects you if inspected. "The CAO allows it" is not a defence. "Here is the clause, here is the shift, here is the record" is.

One more structural protection: if your organisation has a Works Council, understand that under WOR Article 27, they have formal instemmingsrecht over scheduling systems that monitor or register working time. Any system change that introduces automated gap checking requires their formal consent to use the resulting data in employment disputes. This doesn't mean you shouldn't build the check. It means the OR process needs to run alongside the implementation, not after it.

The 11-hour rest rule isn't an obscure technical provision buried in the ATW. It's a daily obligation that shapes every roster involving shift transitions. The reason it generates more violations than the maximum-hours rules isn't because it's harder to satisfy. It's because it's harder to see. Once you build the gap check into your standard process, most of the exposure disappears.

The Friday close followed by the Saturday open is still there in the schedule template. You just need someone to calculate the number in between.