Skip to content
The Published Rota

All notes  /  Running it

Scheduling and Turnover

The cost that scheduling decisions produce and labour percentage never contains. How to attribute it, and what it is worth.

Running it · Analysis

Turnover in retail and hospitality is high, expensive, and substantially driven by the rota. Almost nobody connects the two.

What leaving costs

Recruitment, induction, training, and the period of reduced productivity.

Plus the load on whoever covers the gap, which is where the second resignation comes from.

Sector estimates vary enormously and none of them is yours. Work out your own from recruitment spend and training hours, because the figure is the whole argument.

What the schedule contributes

Late publication, which makes the job incompatible with anything else in a person's life.

Insufficient hours, which means the job does not pay enough regardless of the rate.

Unpredictable patterns, which prevent a second job, a course or childcare.

Clopenings and short turnarounds.

Perceived unfairness in slot allocation, which is a leaving reason people rarely give in an exit conversation and give readily in an anonymous one.

Attributing it

Compare turnover by site against the six measures.

The correlation with notice period and with hours gap is usually visible without any statistical sophistication.

Ask leavers about the schedule specifically, because a general "why are you leaving" produces "another opportunity".

Ask anonymously, because people leaving on good terms do not criticise the rota to a manager.

The comparison that decides it

Take the cost of a one-person buffer on the uncertain shifts, for a year.

Against the cost of the turnover attributable to schedule instability, for a year.

In operations that have run this honestly, the buffer is cheaper, and it also removes the predictability pay, the scramble and the overtime.

The reason it is rarely run is that the two numbers live in different reports owned by different people.

The signal worth watching

Turnover among people with the most variable schedules, compared against those with the most stable.

If it differs, the schedule is a retention lever and can be treated as one.

If it does not, something else is driving it and the scheduling project should not claim credit it has not earned.

The honest framing

Schedule stability is not a welfare gesture.

It is a retention intervention with a measurable cost and a measurable return, and framing it that way is what gets it funded.

Ask leavers about the rota specifically

A general question produces a general answer.

"Why are you leaving" gets "another opportunity".

"Did the schedule work for you" gets the actual answer.

Ask anonymously, because people leaving on good terms do not criticise the rota to the person who built it.

And ask about notice and hours separately, since they are different problems with different fixes.

A practical implementation prompt

During configuration, use this operational use case to prompt questions about fields, ownership and output. Keep the written scheduling purpose in control and document every assumption.

Independent reference

For a thematic point of reference, see the CIPD website. Its current material provides useful context beyond product documentation.