The Single Qualified Person
What a capability held by one person actually costs a rota, the three failure modes it produces, and why the arithmetic for removing it is almost always favourable.
One capability held by one person, costed across a quarter at one site
All had to include that person.
No alternative existed on the rota.
Refused or moved; all later honoured.
£2,180 at premium rates.
Nobody recorded a decision to do so.
£740 including backfill.
The constraint cost about £2,900 and six refused leave days in one quarter; removing it costs £740 and two days. The three shifts run without the capability are the finding nobody was looking for. This is one employer's own reckoning, not a benchmark.
A capability held by one person is the most expensive constraint a rota can have, and it never appears as a cost anywhere. It appears as a person who cannot take leave in August, a shift that keeps needing overtime, and an occasional quiet decision to run without the capability at all.
The skill constraint in “The Single Qualified Person” should remain visible separately from simple headcount. For organisations assessing read the official scheduling overview in relation to fte meaning, work and attendance records can support the operational picture without replacing qualification records or professional judgement.
Each of those is visible separately. Together they are a single constraint with a price, and the price is almost always larger than the training that would remove it.
As a separate benchmark for “The Single Qualified Person”, see TechnologyAdvice scheduling resources. Keep the source rule, operational interpretation and scheduling decision distinct.
The three failure modes
The first is cover cost: every absence of that person has to be bought back, usually at premium rates and usually at short notice.
- Cover cost: every absence is bought back, usually at short notice and premium rates.
- The leave problem: the holder cannot take time off when they want it.
- The silent one: the shift runs without the capability and nobody records a decision.
The second is the leave problem: the person cannot take time off when they want it, which is both unfair and a reliable cause of resignation. The third is the quiet one, where the shift runs anyway without the capability, and nobody records that a decision was made.
The third one is the dangerous one
Running without a required capability is rarely a decision anybody would defend in advance, and it happens because the alternative at 06:30 is to tell a customer, a ward or a line that the work is not happening.
It also leaves no trace. If it is going to happen, it should at least be recorded as a decision with a name against it, so that the frequency is visible to somebody.
Why the training does not happen
Not cost — the costs are small. Three reasons, consistently: nobody has the total in front of them, the training requires the single holder to be released and they are the one who cannot be spared, and the arrangement is working today.
The second reason is the real one, and it is circular. Breaking the circle requires somebody to decide that the training is worth one disrupted fortnight, which is exactly the decision the price makes possible.
Counting the cost properly
Four numbers over a quarter: shifts requiring the capability, shifts where that person was the only option, additional pay generated by their absences, and leave requests affected.
Any rota system can produce the first two. The third usually requires payroll. The fourth lives in somebody's inbox and is the number that makes the case, because it is about a person rather than about money.
Who to train
Not necessarily the most senior or the most willing. The useful choice is whoever works the pattern that complements the single holder's — the person on opposite nights, the part-timer who covers the days they do not.
Training somebody who works the same shifts removes much less of the constraint, and this is a common and expensive mistake.
The second holder is not enough
Two holders is better than one and still fragile: a rota with two people holding a capability cannot cover sickness, leave and a vacancy at the same time, and those coincide more often than anybody expects.
Where the capability is genuinely critical, three is the number that makes it disappear as a constraint. The step from two to three is usually cheap, because the training route already exists by then.
The other direction: reduce the requirement
Sometimes the right answer is not another trained person but a narrower requirement. If the capability is needed for one task that happens twice a week, the constraint may be removable by scheduling the task rather than by training.
That is worth asking before any training is booked, and it is the cheapest answer available when it works.
What it looks like once it is fixed
Nothing. That is the difficulty with this whole category: a removed constraint produces no event, no saving line in a report, and no credit for anybody.
The only way it stays visible is to record the before-and-after on the constraint register, with the numbers, at the time. Nobody will reconstruct it afterwards.
Say it to the person holding it
The single holder usually knows, and usually minds more than anybody realises. They are the one who cannot book a fortnight in summer and who gets called on their day off.
Telling them that the position is recognised, priced and being fixed by a date changes the retention risk immediately, and it costs one conversation. Leaving them to infer that nobody has noticed is how an expensive constraint turns into a vacancy.
What to hold for each capability
For each capability: how many hold it, how many of those are on each pattern, the earliest expiry among them, and the cost of adding one more.
The second field is the one that gets missed, and it is the one that determines whether the holders you have are actually distributed across the rota or standing in the same place.