Inherited Numbers
Why every number in a rota should carry a date, how to run a numbers audit in an afternoon, and what to do with the ones that turn out to have no source.
Six numbers in daily use at one depot, traced to a source
One of the six had a current document behind it. Two were costing money every week and two were costing nothing at all, which is why the exercise is worth running on every number rather than on the ones people complain about. This is one employer's own trace, not a statement of what any rule requires.
Every rota runs on numbers: how many on each shift, how many consecutive days, how long the cycle, how much notice, how many in training at once. Each of them was set by somebody, once.
The constraint in “Inherited Numbers” becomes useful only when its source, cost and effect on coverage are visible. A team considering see this Monitask scheduling resource for employee monitoring data security can add timely work and attendance context, with transparent settings, limited access and a clear correction route.
Almost none of them carries a date or a source, which means none of them can be checked, which means all of them persist until something breaks.
Additional context for “Inherited Numbers” is available from OSHA worker-fatigue guidance. Use external guidance to prompt a specific validation check rather than replace local review.
The audit
List every number currently in use. For each, write where it came from and when. Mark the ones with a current document, the ones with an out-of-date document, and the ones with nothing.
An afternoon for a department. The output is usually one or two numbers worth money, two or three worth nothing, and a handful confirmed.
Why numbers drift from their reasons
Because the reason is a sentence and the number is a number, and only the number gets carried forward. Four drivers for four routes becomes four drivers; the routes change and the four does not.
The sentence is what makes a number checkable. Without it, the number is simply a fact about the rota.
The numbers worth auditing first
Staffing levels per shift, because they cost the most. Notice periods, because they constrain everything else. Cycle length, because it determines fairness. And maximum consecutive shifts, because it affects individuals directly.
- Staffing levels per shift, because they cost the most.
- Notice periods, because they constrain everything else.
- Cycle length, because it determines whether fairness is possible.
- Maximum consecutive shifts, because it lands on individuals.
Four categories, usually eight or ten numbers in total for a department.
Notice periods, which are frequently wrong in both directions
A published-rota notice period is usually either a contractual or agreed figure, or a custom. Teams regularly operate a longer notice than anything requires, which removes flexibility nobody intended to give up, and occasionally a shorter one than they have agreed.
Both are worth knowing. The second is a compliance question; the first is free capacity.
Cycle length
The length of a repeating pattern is almost always inherited and almost always matters more than anybody expects, because it determines whether unsocial shifts can be shared evenly.
A cycle length that does not fit the team size produces permanent unfairness that no amount of goodwill corrects, and changing it is usually possible without touching anybody's contracted hours.
What to do with a number that has no source
Treat it as a live question: is this the number we want? Somebody has to answer, and the answer should be recorded with their name against it.
In practice most unsourced numbers are kept, and that is a good outcome: the organisation now owns a number it was previously obeying.
The number that is about to be wrong
Some numbers are correct today and will not be after a known event: a service change, a contract starting, a cohort of trainees qualifying.
Those should carry the date of the event rather than a review date, so the register prompts at the right moment instead of annually. It is a small refinement and it catches the cases where a review would arrive six months late.
Telling people the numbers
Most teams do not know why there are four on the early, and the absence of an explanation gets filled with a worse one, usually about cost.
Publishing the numbers with their reasons is a short note that forestalls a lot of speculation, and it also invites correction from the people most likely to know the number is out of date.
What the audit does not do
It does not decide anything. A number that turns out to have no source is not thereby wrong, and an audit presented as a list of errors will be fought rather than used.
The output is a register with sources and dates. What changes, and when, is a separate conversation with the people who will be affected by it.
The two numbers that interact
Staffing level and cycle length are usually audited separately and determine the outcome together: a level that needs seven people and a cycle built for six produces a permanent gap that looks like absence.
Checking them as a pair takes five minutes with a calculator and explains a surprising share of the shifts that nobody can ever fill.
The rule that prevents all of this
Any number entering a rota carries a date and a one-line reason, written at the time it is set. That is thirty seconds of work at the only moment when the reason is actually known.
Everything else in this section is archaeology required because that thirty seconds was not spent.