Closing Then Opening

Working a closing shift and then the opening shift the next morning is called clopening, and it is scheduled far more often than anyone defends.

Why it happens

It looks efficient: the person knows the close-down and the open-up, so handover is minimal.

Small teams have few alternatives.

And the rota builder is optimising coverage without a constraint that forbids it.

Nobody decides to do it. It falls out of a solver or a spreadsheet with no rest rule in it.

Why it is worse than it looks

The gap is frequently under eight hours, and that is door to door: travel, sleep, travel.

Actual sleep is five hours or less, repeatedly.

Which affects safety in food handling, in driving and in anything involving equipment, and affects service quality in everything else.

And it produces the absence on the following shift that then gets recorded as unreliability.

The legal position

General orientation, not legal advice.

Fair workweek ordinances in the US commonly include a right to rest between shifts, typically nine to eleven hours, with premium pay owed if the employee works the second shift anyway.

In the EU and UK, daily rest requirements of eleven hours apply more broadly, with limited exceptions.

Which means in a growing number of places, clopening is either prohibited, priced, or requires consent — and the consent has to be genuine.

Designing it out

Put a minimum rest constraint in the rota before anything else. Eleven hours is a reasonable default even where nothing requires it.

Make it a hard constraint, not a warning, because warnings get clicked through at eight in the evening.

Where a small team genuinely cannot avoid it, rotate who does it, pay for it, and treat it as a staffing finding rather than a permanent arrangement.

The check

Count clopenings per published rota, by site.

Most operations have never counted and are surprised.

Include the near misses — gaps under twelve hours — because the pattern is the same and the constraint is arbitrary at the margin.

The measure that follows

Absence on the morning after a short turnaround, compared against absence generally.

The difference is usually visible, and it converts an abstract argument about rest into a number about staffing cost.

Make it a hard constraint

Not a warning.

A warning at eight in the evening gets clicked through, and the rest breach is published.

Eleven hours is a reasonable default even where nothing requires it.

Applied to swaps as well, because a swap can create a turnaround the original rota avoided — which is where most breaches actually occur.

Turn the principle into a test

For a concrete product reference, this resource-planning case can help turn the principle above into a test. Verify the current behaviour in a trial and judge the record it creates, not the wording on the page.