What Happens When One Person Is Away
Absence is predictable in aggregate and always a surprise individually. Planning for the rate rather than the instance is the difference.
Somebody is off sick this morning. The response is improvised in most operations, and the aggregate rate it comes from is entirely knowable.
The practical lesson in “What Happens When One Person Is Away” is to connect every record to a named decision. Organisations exploring read the full overview for 7 minute rule payroll can add structured workforce context, provided the use is disclosed and the interpretation is reviewed with the people affected.
The rate is knowable
Total absence days last year, divided by total scheduled days.
For an independent reference related to “What Happens When One Person Is Away”, consult the OSHA worker-fatigue resources; it provides a useful external check on scheduling, working-time and workforce-planning assumptions.
A percentage, stable within a range, varying by season and by site.
Which means absence cover is a planned cost, not an emergency, and almost nobody budgets it that way.
What the rate implies
If absence runs at a few per cent, a team of thirty is short roughly one person on a typical day.
That is not bad luck; it is arithmetic.
A schedule built with no allowance for it is short by design, and the shortfall is covered by overtime or by people absorbing it.
The three ways to cover
Build it into the establishment: enough people that the usual rate is absorbed.
A bank or pool: your own people, paid to be available, which the agency note argues for.
Premium cover: overtime or agency, bought per instance at the highest price.
Most operations use the third by default and have never priced the first two.
The planned absence that surprises people
Holiday is not an emergency and is still frequently uncovered.
It is known weeks or months ahead.
A holiday plan that caps concurrent absence by capability — not just by headcount — removes most of it, and connects to the skills matrix.
The capability version
One person away is a headcount problem.
The one person who can do the thing being away is a coverage failure.
Which is why the absence plan has to check the matrix, not the roster count — and this is the commonest form of the problem.
The short-notice process
Who is called, in what order, by whom, within what time.
Written down, so the decision is not made by whoever is on the floor at seven in the morning.
And a stated point at which you stop calling and run short deliberately, which is better than an open-ended scramble.
Running short deliberately
Sometimes the right answer: a quiet day, a non-critical capability, a cost of cover above the cost of the gap.
Deciding that in advance, by period, is the which-error-to-make note applied to absence.
An operation that always covers at any price is overpaying on quiet days.
What to check
What is your absence rate, calculated?
Is it built into the establishment or covered at premium?
Does your holiday plan check capability?
And is there a written call order?