Skip to content
The Published Rota

All notes  /  Running it

Who Owns the Schedule

The recurring work a scheduling arrangement generates, and what happens when it belongs to whoever has least to do that week.

Running it · Analysis

Building a rota is a weekly task. Owning the arrangement it sits inside is a different job, and in most operations nobody has it.

The recurring work

The build, weekly, per site.

Availability reviews, twice a year, plus after any signal.

Capability matrix and expiry tracking.

The six measures, monthly.

Predictability pay checking, where it applies.

Rule changes when a jurisdiction moves, which in this area is frequent.

And the annual look at slot distribution and the hours gap.

What goes wrong without an owner

Notice drifts later and nobody notices because nobody tracks it.

Availability goes stale, producing conflicts that get treated as unreliability.

Certifications expire.

The allocation rule is announced and never reviewed, so the distribution returns to where it was.

A new ordinance takes effect and nobody knows.

None of these announces itself. They surface as a grievance or a penalty.

Naming the owner

One person, named, with allocated time.

Not the busiest site manager by default.

With authority to change the pattern and the notice period, or every improvement becomes a request.

And a deputy, because rotas do not pause for annual leave.

The runbook

How the build works, and the constraint checks that precede publication.

How availability is reviewed.

How the six measures are produced.

Which jurisdictions apply and what each requires.

Written so the deputy can follow it, which is the test.

What to report

Monthly: notice achieved, employer changes, predictability pay, by site.

Quarterly: slot distribution, hours gap, schedule variability.

Annually: turnover against the above, and whether the arrangement would be built the same way again.

To the workforce as well, at least the notice figure and the slot distribution, because publishing them is what makes the commitments checkable rather than asserted.

The runbook test

One check that shows whether the runbook is real.

Can the deputy build and publish a rota from it, without asking the owner?

Try it once, deliberately, while the owner is available to watch rather than help.

Whatever they had to ask is a gap, and it takes minutes to fill while it is fresh.

Check the difficult case

Use the agency workflow to frame one representative case. The useful evidence is what happens when an employee questions an entry and a manager must correct and export it.