Skills and Coverage

A rota with the right number of people can still fail because none of them can open the safe.

What a shift actually needs

A headcount, by hour or by part-day.

And a set of capabilities: keyholder, first aider, fire warden, alcohol licence holder, food safety supervisor, till authorisation, equipment certification.

Most rotas encode the first and carry the second in someone's head.

Writing it down

One line per shift type: minimum people, plus which capabilities must be present.

A matrix of who holds what, with expiry dates, because certifications lapse and nobody notices until an inspection.

Checked automatically before publication, not by a manager remembering.

This is an afternoon of work and it removes an entire category of Saturday-morning crisis.

The single point of failure

Count how many people hold each capability, per site.

Anywhere the answer is one, the site cannot run without that person, and their holiday, illness or resignation is a closure risk.

This list is the argument for training budget and it is far more persuasive than a general request.

Two people minimum for anything a shift cannot run without.

Cross-training

The highest-return investment in this subject and the one always deferred.

Start from the single-point list.

A few days of someone's time, once, and it permanently widens who can cover.

It also improves the rota's fairness, because the awkward shifts stop being the exclusive property of the two people who can do them.

What it does for swaps

A swap between two people with different capabilities can break a shift that looked fine.

Which is why swap confirmation checks capability rather than preference, and why the matrix has to be in the system rather than in a manager's memory.

The expiry problem

Licences, food safety certificates, first aid qualifications and equipment authorisations all expire.

A rota built on a lapsed certificate is a compliance failure that looks like a normal shift.

Track expiry dates with a lead time — sixty days is usual — and treat the renewal as scheduled work rather than as something people arrange in their own time.

The check

Publish nothing that fails the capability check.

Count single points of failure per site, quarterly.

And count near-expiries, because both are cheap to see and expensive to discover on the day.

Count the single points of failure

Per site, quarterly.

Any capability held by one person is a closure risk whenever they are ill, on leave or leaving.

The list is short and specific.

It is also the most persuasive training-budget argument available, because it names a risk rather than requesting development in general.

Connect policy to configuration

The choices in this note can be compared with this team example. Enable only the data required for the stated purpose and confirm who can see and change it.

Independent reference

For a thematic point of reference, see ILO resources. This widely used specialist site offers a useful second reference for the issue.