Explainer Safety, Emergency, Crisis & Business Continuity · Business Continuity · Issue 2026-W46
The backup name can fail too: examine shared dependencies before a continuity crisis
Guidance from the Chartered Institute of Personnel and Development (CIPD), dated 3 November 2026, examines organisational dependence on roles, skills and leadership. The practical question is whether a substitute can work under the same constraint. We propose a bounded tabletop discussion exposing shared dependencies, clearly separated from live tests and emergency procedures.
Guidance from the Chartered Institute of Personnel and Development (CIPD), dated 3 November 2026, examines organisational dependence on roles, skills and leadership. The practical question is whether a substitute can work under the same constraint. We propose a bounded tabletop discussion exposing shared dependencies, clearly separated from live tests and emergency procedures.
What does the guidance add?
The guidance asks organisations to examine critical roles, knowledge, decision authority and workforce availability, including single points of failure concentrated in a few people. It suggests considering 72 hours without power, connectivity or transport. These are professional recommendations and an assessment scenario, not experimental evidence that organisations will maintain operations for that period. [1]
The current version connects this review to the UK's Be Ready campaign, launched on 22 October 2026 according to the government's parliamentary statement. The development examined here is that specific context for checking dependencies, not the discovery of business continuity. November 3 is the guide's displayed version date, not its unresolved first-publication date. The campaign is British; neither its message nor the 72 hour scenario is presented as a Saudi requirement. [1] [3]
We approach the development as a joint question for the continuity lead, operations manager and people professional: which task stops when its owner is unavailable, and what would a substitute need to perform it? A backup may be named while decision permission, knowledge or access remains unresolved. That possibility needs checking inside the organisation. We claim no prevalence rate for it and do not suggest that changing a roster alone resolves it.
Independence is a condition of a substitute
We propose distinguishing a substitute person from a substitute capability. Record the critical function, its required decision, who can authorise that decision, how necessary knowledge reaches that person and which resources support it. Then ask whether one resource could disable both the primary arrangement and the substitute. The aim is not to eliminate every dependency. It is to make remaining common dependencies visible so that a duplicated name is not mistaken for demonstrated independence.
Begin with one low-risk administrative process that can be discussed without changing systems or services. The process owner and continuity lead should agree the purpose and boundaries, involving appropriate authority, safety and privacy specialists where needed. Use fictional or desensitised information and have the facilitator state that this is a training discussion. Do not execute operating instructions or subject real people to unagreed pressure.
The proposed output is a simple record for each dependency: known and supported within scope; an assumption requiring examination; or a gap preventing a conclusion. Assign each gap an owner and follow-up decision. Attendance is not a measure of capability. The team needs to know where its argument for continued performance stops. If answering a question requires technical or field testing, record a request for specialists to design it safely under approved procedures and permissions.
A hypothetical example: a second channel relies on the first
Imagine a team with named substitutes and a second communication route, where accessing both routes requires a shared sign-in service that is unavailable in the scenario. This is not an account of a real organisation, and we do not propose bypassing access controls. Discussion alone can reveal that naming a second channel does not demonstrate its independence. Record the dependency and ask the authorised owner to review alternatives within organisational policy, instead of improvising a technical workaround during the session.
A different gap might emerge: the substitute can access information but does not know the limits of their authority or where to escalate a decision. Adding communication channels does not resolve that problem. Clarify which decisions they may take, which need escalation and how that is documented. The example separates a knowledge or authority gap from a technology gap while retaining specialists' responsibilities. This article grants nobody a new authority.
The example also prevents the opposite overstatement. Discovering a common dependency does not establish that the whole organisation would collapse. Describe the affected service, the scenario boundary and what remains untested. Where approved alternatives already exist, review their evidence rather than reinventing them. One discussion, or a persuasive description of a response on paper, cannot stand for organisational resilience as a whole.
A discussion is not an operating test
The UK Resilience Academy guidance distinguishes tabletop exercising as structured discussion in a controlled, non-operational environment from live exercises. This is an earlier reference published in 2024 and updated in February 2025. We use it to clarify the activity type, not as new news or a binding rule in Saudi Arabia. [2]
Do not disconnect power, communications or transport, issue alarms or messages that could be mistaken for a real incident, relocate staff or stop services to implement this article. Any live test requires specialist design, risk assessment, authority, coordination with affected parties and approved stopping and restoration conditions. If a real incident emerges during the discussion, stop the exercise and follow organisational and relevant authority arrangements, rather than the training scenario.
Before convening, agree how participants can raise a concern and how sensitive findings will be recorded. A useful dependency discussion should not become a public map of vulnerabilities. Limit circulation to people with a justified need, using the organisation's existing information-handling rules. If the required participants or authority are unavailable, reduce the scope or defer the relevant question instead of recording an unsupported answer as resolved.
What should the decision-maker take away?
The responsible manager should leave with specific gaps, not a declaration of comprehensive readiness. For each gap, identify its potential effect within the scenario, who owns its treatment and what evidence would close it. Assess the next round by whether evidence about previously identified dependencies has improved, rather than by how many names were added. If safe knowledge access or decision authority remains unresolved, continuity of that function remains unsubstantiated within scope even when the form is complete.
Start with this question: can our substitute perform the task if the resource supporting the primary arrangement is lost? An honest answer may be that we do not yet know. Turning that uncertainty into a clear, safe investigation assignment is the review's value. Announcing capability before examining its conditions leaves the plan's central assumption without an owner.
Follow peers and make professional contacts through ARPS communities; ordinary membership is free. Share a category of dependency worth examining without revealing security arrangements or sensitive information.
References
- Business continuity and organisational resilience: Preparing your workforce for operational disruption
- Exercising Best Practice Guidance
- Strengthening community resilience across the UK: Be Ready launch
References open in a new tab.
Discuss this with practitioners
Create a free account to save articles and join the Specialists community discussion.
Discussion 0 published comments
No published comments yet. Be the first to share your experience.