How Long the Rota Takes to Build

Most scheduling problems trace back to one thing: the person building the rota does not have time to build it.

What the build actually involves

Reading the forecast.

Checking availability, which is out of date.

Working around approved leave, requests and training.

Satisfying rest rules, minor limits, capability requirements and contracted minimums.

Balancing hours against what people want.

Distributing the awkward slots.

And doing it while running a shift, because in most retail and hospitality operations the rota builder is also on the floor.

The time it takes

Measure it. Almost nobody has.

In a fifty-person site it is commonly several hours, weekly, in fragments.

Fragmented time produces worse rotas than the same total in one block, because the constraints have to be reloaded each time.

And the fragments get displaced by anything urgent, which is why the rota goes out late.

What follows from it being squeezed

Late publication.

Last week copied forward, which perpetuates whatever unfairness was already there.

Constraints checked by memory rather than systematically.

Changes after publication, because the build was rushed.

Every one of these appears elsewhere in this collection as a problem in its own right, and this is where several of them originate.

Reducing it

Protected time: a stated block, covered on the floor, weekly.

Availability kept current, which removes the largest source of rework.

Constraints enforced by the tool rather than checked by a person.

A pattern underneath — fixed or rotating — so most of the rota is decided before the build starts.

That last one is the largest reduction available and is the argument for patterns beyond their effect on staff.

What not to do

Do not push the build down to someone with less context to save a manager's time; they will copy last week.

Do not add approval layers, which add delay without improving the rota.

Do not treat generated rotas as removing the work, because the review is the part that matters and it still takes time.

The measure

Hours spent building, per site, per period.

Against notice achieved.

The relationship is usually direct, and it converts an argument about discipline into a resourcing decision.

Measure the build time

Almost nobody has.

Hours spent building, per site, per period, including the fragments.

Against notice achieved.

The relationship is usually direct, and it converts an argument about discipline into a resourcing decision.

Fragmented time produces worse rotas than the same total in one block, because the constraints have to be reloaded each time.

Connect policy to configuration

The choices in this note can be compared with the consulting workflow. 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 CIPD resources. Consult the source directly because technical and legal details can change.