Who Holds the Pager? A Pre-Holiday Cover Audit for UK Critical Platforms
Photo: NASA Goddard Space Flight Center / Denny Henry, Public domain, via Wikimedia Commons
As of 14 November 2026, many UK organisations are moving into the final planning stretch before the holiday period. Change freezes are being drafted, leave is being approved and the on-call rota is approaching the point at which it becomes difficult to alter. That makes the next few weeks the right time to examine whether the rota is merely a staffing timetable or a genuine operational control.
The distinction matters. A rota can show that someone is listed as available without proving that the right person can access the right system, make the right decision and evidence the right handover at the moment a critical platform fails. For teams responsible for data platforms, integration layers, ERP estates, reporting warehouses and customer-facing systems, the test is not who appears on a spreadsheet. It is who can act when a batch misses its deadline, an interface stalls or a regulatory report cannot be produced.
Begin with the service catalogue, not the staff list
A cover audit should start from the services that matter, not from the people who happen to be available. For each critical service, record the business process it supports, the peak operational windows, the dependencies it relies on and the supplier support arrangements that apply outside normal hours. A financial close process, a nightly data load, a payment reconciliation feed and a contact centre routing platform will have different failure modes and different tolerable recovery times.
The output should be a short list of critical services with named operational owners. That list then becomes the basis for testing cover. Starting from names tends to reproduce existing assumptions; starting from services exposes where those assumptions are thin.
Primary and secondary are roles with evidence
For every critical service and every shift in the holiday period, there should be a named primary responder and a named secondary responder. The secondary should be capable of acting, not merely willing to be contacted. A common weakness is a rota that lists a secondary name who has never run the recovery procedure, does not hold the required access or cannot approve the necessary workaround.
The audit should check for rota intersections. Is one person secondary for six services across the same week? Are two critical services relying on the same individual? Does a bank holiday create a gap between shifts? A rota that names a team rather than an individual is not a control. It is a hope that someone will notice.
Test the escalation path quietly
Escalation paths should be tested before the holiday period, not discovered during it. A tabletop exercise can confirm the sequence from monitoring alert to primary responder, secondary responder, service owner and supplier escalation. Where appropriate, a silent paging test can confirm that contact details, out-of-hours numbers and acknowledgement times are correct.
The test should also cover the less obvious routes. Does the service catalogue hold the same contact data as the rota? Are supplier support portals accessible to the people who will need them? Can the secondary responder authenticate to the relevant systems from outside the office? These details are unglamorous, but they are precisely where holiday cover tends to fail.
Handover is an artefact, not a conversation
A handover before leave should produce evidence. That evidence should include open incidents, known errors, workarounds, batch status, changes that fall inside the freeze, supplier tickets awaiting response and any access or approval that expires during the holiday. It should be written down, owned and dated. If it exists only in a conversation at the end of a Friday, it is not a handover.
The audit should sample handover notes from the previous holiday period and ask whether a competent colleague could have acted from them alone. Where the answer is no, the gap should be fixed before the 2026 rota locks.
Find the single points of knowledge
The most important coverage question is not how many people are on the rota. It is how many people can make a decision without calling someone else. Map the services where one individual holds the runbook knowledge, the supplier relationship or the informal history of past failures. Then arrange shadowing, pair cover or written decision rights before that person goes on leave.
This is not only a technical exercise. It is also an operational one. A platform can have two responders and still have only one person who knows when to invoke a workaround, when to accept a data delay or when to escalate to a business owner. Cover without decision authority is partial cover.
Produce a pre-holiday action list
Before the rota is locked, the audit should produce a short, owned action list. Typical actions include updating the critical service list, naming deputies for every service, correcting contact data, running an escalation test, completing written handovers, scheduling shadow shifts, confirming supplier support hours and publishing a single cover map for the holiday period. Each action should have a named owner, a completion date and an evidence artefact.
The list should be reviewed by the digital operations lead and, where appropriate, the business service owner. Exceptions should be recorded and accepted rather than left implicit. That record is what turns the rota from an administrative schedule into an auditable control.
The real test may arrive at 03:00 on a bank holiday, when a batch has failed and the usual expert is unavailable. The organisation that has tested its cover, documented its handovers and named its deputies will not necessarily find that moment easy. It will, however, be able to prove that someone could act, with access and authority, and that the evidence existed before the holiday began.
