Before the Sick Call: Testing Team Cover in Twenty Minutes
Photo: printed staff rota on desk with pen in UK office, via m.media-amazon.com
Most rotas are built for a week that never quite happens. The spreadsheet shows full cover on paper, but annual leave, sickness and unexpected absence arrive together. For many UK managers, the result is a familiar scramble: calls to colleagues on rest days, delayed approvals and a supervisor filling gaps they cannot really fill.
A full business continuity exercise is rarely the right response for a small team. It is heavy, slow and often produces a document nobody uses. A 20-minute rota stress test is a lighter alternative. It does not predict the future. It exposes where cover depends on one person and helps managers decide whether cross-training, an escalation route or temporary cover is worth the effort.
What the test is — and is not
This is a structured conversation with the rota, a pen and a single sheet of paper. It is not a risk register, a workforce plan or a guarantee of cover. It works best when the manager and a supervisor or team leader complete it together, because knowledge of who can actually do what often sits with both.
Step 1: Define minimum viable cover (5 minutes)
List the activities that must happen for the team to function. Keep the list short — five to eight items is usually enough. For each, state the minimum number of people needed and the skill or authority required. Separate 'must happen every day' from 'must happen this week'.
Typical examples include opening a site, answering customer calls, approving payments, completing a safety check or dispatching orders. Be specific about authority: two people may know the process, but only one may be able to sign off the result.
Step 2: Mark single-person dependencies (5 minutes)
For each activity, write the names of people who can cover it independently. Use a simple traffic light:
- Red: one named person only.
- Amber: two people, but one is part-time, newly trained or often unavailable.
- Green: three or more people, including at least one who can act without supervision.
Count system access and sign-off limits, not just familiarity. A person who can complete the task but cannot approve it is not full cover.
Step 3: Model a normal absence week (5 minutes)
Choose a real week in the next quarter. Apply three ordinary events: one period of planned annual leave, one short-notice sickness absence of one or two days, and one unexpected absence such as dependant care or a transport disruption. Do not model a major incident; model a difficult Tuesday.
Use a simple grid:
| Activity | Minimum cover | Available after absences | Red/Amber/Green | Action |
|---|---|---|---|---|
| Daily payment approval | 1 approver | 0 | Red | Train second approver by 15 Jan 2027 |
| Customer phone cover | 2 advisers | 1 | Amber | Agree escalation to duty manager |
The point is not to create a perfect simulation. It is to see which red items lose cover when ordinary life happens.
Step 4: Decide the response (5 minutes)
For each red item, choose one response and give it an owner and a date. The options are usually:
- Cross-train a named second person, with a practical assessment rather than a shadowing session.
- Create a temporary escalation route: who decides, what delay is acceptable and how the decision is recorded.
- Use temporary or agency cover where the task is infrequent but critical.
- Accept the risk for a defined period, with a review date.
Avoid the default answer that everyone should learn everything. That sounds fair but rarely survives contact with workload. Prioritise activities that are frequent, high-impact and trainable. For rare specialist work, an escalation route is often more realistic than cross-training.
Where cross-training earns its place
Cross-training works best for routine tasks with clear steps and regular practice. It is less effective for work that depends on scarce qualifications or complex judgement. In UK teams with part-time hours, compressed weeks and hybrid patterns, informal cover is less reliable than it once was. A named second person with access and practice is worth more than a general expectation that someone will step in.
Common mistakes
- Testing only planned annual leave and ignoring short-notice sickness.
- Assuming the rota system holds skills data that it does not.
- Confusing headcount with cover: three people on shift may still leave one critical task uncovered.
- Forgetting approval limits, system permissions and safety certifications.
- Running the test once and filing it away.
Keep a one-page record
Record the week tested, the red items, the chosen response, the owner and the review date. Store it with the rota or in the team's operations folder. Repeat the test each quarter or whenever the team structure changes. If a red item affects a statutory duty — health and safety, safeguarding or financial control — raise it through the appropriate compliance route rather than treating it as a local scheduling issue.
Twenty minutes will not remove every absence problem. It will show managers where the rota is honest and where it is hopeful. That is usually enough to decide the next practical step.
