Keeping Continuity Plans Usable

Keeping a continuity plan usable means keeping it accurate, short enough to follow under pressure, and findable when normal systems are unavailable. A plan that was accurate when written, but that now names departed staff, retired systems, changed suppliers or obsolete workarounds, can mislead responders at the worst moment. Under DORA in the EU, which applies from 17 January 2025, and under the separate UK regime in FCA PS21/3 and PRA PS6/21, maintenance expectations should be labelled by regime. In practice, usability is maintained through ownership, change triggers, plain language, and a feedback loop from every test and incident.

Length is a usability problem. Long plans that mix background, policy, governance and action steps force responders to search for the next action while customers wait. A more usable structure puts the action sequence first: service, decision maker, activation signal, recovery order, contacts, data sources, workarounds and communication steps. Background, reasoning and detailed appendices can follow, clearly separated, so that they support the action sequence without burying it. Short action cards or summaries, drawn from the full plan and kept consistent with it, can help responders who need a quick reference, provided they are maintained with the same discipline as the full plan. An action card that diverges from the plan creates a new risk.

Contacts are a frequent point of failure. People change roles, suppliers change escalation routes, and out-of-hours contacts change without a formal announcement. A usable plan therefore separates stable content, such as recovery order and decision principles, from volatile content, such as names, numbers and access routes, and checks the volatile content more often. That check should be a real contact test, not a visual review of a list, because a number that looks correct can still reach the wrong person, a mailbox that is no longer monitored, or a supplier route that only works during normal business hours. Findings from contact checks should update the plan promptly, with a record of what changed.

Consider an illustrative retail banking service with several customer channels. Its plan may be updated after a channel change, a supplier change, or a new vulnerability in a customer journey, but updates that only amend one section can leave other sections inconsistent. A change to the recovery order, for example, may also affect communication wording, workaround limits and supplier escalation. The service owner should therefore review the whole service picture when a material change occurs, rather than patching a single paragraph. Version discipline helps: the current version should be clearly marked, previous versions should be accessible for review but not mistaken for the current plan, and responders should know where the authoritative copy lives when normal document systems are unavailable.

Plain language is another usability test. A plan written in dense internal jargon, with unexplained abbreviations and cross-references to other documents that responders may not have, slows action and increases error. Each step should state what to do, who does it, and what success looks like, in terms that a deputy or a colleague from another team can understand. If a step requires specialist knowledge, the plan should name the specialist and the alternative if that person is unavailable, rather than assuming that knowledge will be present. Reviewers who were not involved in writing the plan are well placed to test readability, because they approach the document as a responder would.

Feedback closes the loop. Every test, near miss and real activation should produce a short list of plan changes, with owners and follow-up dates, and those changes should be checked at the next test. Plans should also be reviewed after quiet periods, because a plan that has not been used or tested for a long time may have drifted from the service it describes. A useful maintenance routine therefore combines event-driven updates, after changes and incidents, with periodic reviews that check contacts, access, suppliers and workarounds even when nothing obvious has changed. That routine, owned by the service owner, is what keeps a plan a working tool rather than a historical document.