Skip to content
The Published Rota

All notes  /  Running it

The Numbers Worth Watching

Six measures that describe whether a scheduling arrangement is working, and the ones that mostly describe the workforce.

Running it · Reference

Scheduling generates a great deal of countable material. Six numbers say whether the arrangement is working.

The six

Notice actually achieved: days between publication and the first shift, averaged by site.

Changes per published shift, split by employer-initiated and worker-initiated.

Predictability pay, by site, where it applies.

Schedule variability per person: how much someone's pattern differs week to week.

Hours received against hours wanted, per person.

Distribution of undesirable slots, per person.

All six describe the schedule. That is deliberate.

What each says when it moves

Notice falling: the build is happening late, which is usually a manager workload problem.

Employer changes rising: scheduling to forecast without a buffer.

Predictability pay concentrated at one site: that site's planning, not its trade.

Variability rising: the optimiser has no stability objective, or nobody is reviewing its output.

Hours gap persistent for the same people: an allocation problem with a possible fairness edge.

Slot distribution skewed: the default allocation is running unchecked.

What not to measure

Individual acceptance rates for short-notice shifts, which measures whose life has the least slack.

Availability breadth as a performance indicator, which penalises people with caring responsibilities.

Swap requests as a reliability signal, which they are not — they are a signal about the rota.

Anything that ranks people using data generated by the schedule itself.

Who sees what

The owner of the process: all six, monthly.

Site managers: their own site's notice, changes and predictability pay.

The workforce: the notice figure and the slot distribution, published.

That last one is unusual and it is the point. Publishing the distribution is what makes the fairness claim checkable rather than asserted.

Annual review

Did notice improve?

Did employer-initiated changes fall?

Did variability fall?

Did the hours gap close?

What did turnover do, by site, against the above?

That last comparison is the one that justifies the whole approach, and it is available from records you already keep.

Publish two of them

The notice figure and the slot distribution.

To the workforce, not only upward.

Because a fairness claim nobody can check is an assertion, and a notice commitment nobody can verify is a promise.

Publishing both makes them testable, which is uncomfortable at first and is what makes the improvement believed.

Check the difficult case

Use employee productivity reports 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.

Independent reference

For a thematic point of reference, see the U.S. Bureau of Labor Statistics. Use this established source as an outside check before turning the principle into a workplace rule.