Rest, Breaks and Maximum Hours

General orientation, not legal advice; requirements differ substantially by jurisdiction.

Before any advance-notice rule applies, a rota has to satisfy basic working time constraints — and these are the ones most often violated by a solver with no rules in it.

What typically applies

Daily rest: a minimum period between shifts, commonly eleven hours in the EU and UK.

Weekly rest: an uninterrupted period, commonly twenty-four hours, sometimes averaged over a fortnight.

Rest breaks within a shift, triggered by shift length.

Maximum weekly hours, averaged over a reference period in many places.

Night work limits, where applicable.

Where rotas breach them

Short turnarounds, which is the clopening note and the commonest breach.

A run of days with no rest day, which happens when someone covers.

Breaks scheduled but not takeable, because the shift is single-staffed.

Second jobs, where combined hours matter in some jurisdictions and the employer cannot see them.

Overtime accumulating across a reference period without anyone tracking the average.

The single-staffing problem

A break that cannot be taken is not a break.

Someone working alone in a shop cannot leave the floor, so the scheduled break is a fiction and the deducted time is unpaid working time.

This is both a working-time breach and a pay problem, and it is extremely common in small-format retail.

Either staff the break or do not deduct it, which is the whole answer and costs what it costs.

Building the constraints in

Minimum rest between shifts: a hard constraint.

Weekly rest day: a hard constraint.

Maximum hours per week and averaged: checked before publication.

Break feasibility: checked against the staffing of that shift, which most tools do not do and which a person can spot.

What a solver will do without them

Produce a perfectly efficient rota that is unlawful, because nothing in the objective function mentions rest.

Repeatedly, and confidently.

Which is why the constraints go in before the optimisation rather than as a review step afterwards.

The check

Run every published rota against the four constraints automatically.

Count breaches by site.

And check break feasibility by hand for single-staffed periods, because no tool knows how many people are on the floor at the moment the break falls.

Check break feasibility by hand

The one check no tool can do.

A scheduled break during a single-staffed period cannot be taken.

No system knows how many people are on the floor at the moment the break falls.

Look at the single-staffed periods in each published rota and confirm the break is actually takeable — and where it is not, either staff it or stop deducting it.

Connect policy to configuration

The choices in this note can be compared with the scheduling example. Enable only the data required for the stated purpose and confirm who can see and change it.

Independent reference

For a thematic point of reference, see the Occupational Safety and Health Administration. Its current material provides useful context beyond product documentation.