Ask most organizations whether they are prepared for a serious disruption and the answer will usually point to documents: a business continuity plan, a disaster recovery runbook, a crisis communications playbook, an incident response policy. Those documents matter. They capture decisions, assign roles, and set out procedures. But a plan describes what an organization intends to do. It does not show what the organization can actually do under pressure.
The distance between those two things is the readiness gap. It is where well-written plans meet stale contact lists, untested recovery steps, suppliers that cannot meet their contractual commitments, and leaders who have never made decisions together under time pressure. Closing that gap, and being able to demonstrate that you have closed it, is what separates documented resilience from proven readiness.
This article sets out a practical way for executives and boards to move from plans to evidence, and from activity reporting to outcome measurement.
Why This Matters
Expectations are moving from "show me the plan" to "show me it works." In the United Kingdom, operational resilience rules for in-scope financial firms require mapping and scenario testing to assess whether important business services can remain within impact tolerances under severe but plausible disruption. In the United States, the FFIEC Business Continuity Management booklet expects banks to run exercise and test programs that validate their ability to restore critical functions, and to report test results, identified issues, and remediation to the board. Similar themes run through ISO 22301, which requires organizations to exercise and test their continuity procedures and evaluate performance.
Beyond regulation, the people who depend on an organization ask the same question in their own way. Large customers ask suppliers for evidence of continuity capability. Insurers ask what controls have been tested. Investors and lenders want to understand how management would handle a material disruption. In each case, a plan is the starting point of the conversation, not the end of it.
For boards, the stakes are personal as well as institutional. Directors are expected to exercise oversight of significant risks. Being told that plans exist, without any view of whether they work, makes that oversight difficult to demonstrate.
The Business Challenge
Moving from plans to proof is difficult even for organizations that are committed and well resourced.
Plans age quietly. People change roles, systems are replaced, suppliers are switched, and processes are redesigned. Unless plans are tied to change management, they drift out of date without anyone noticing.
Tests are designed to pass. Exercises are often scheduled around convenience and scoped to what is known to work. A recovery test that restores one application in a planned window, with the right people on standby, proves something, but not much about a surprise event at the worst possible time.
Metrics count activity. Many resilience reports measure inputs: plans reviewed, exercises held, training completed, percentage of systems with documented recovery procedures. These numbers can rise steadily while actual capability stays flat.
Evidence is scattered. Test results sit in one team's files, audit findings in another's, incident post-mortems in a third. Nobody assembles them into a coherent view of whether critical services can withstand disruption.
Remediation stalls. Exercises surface issues, but actions are vague, owners are unclear, and nobody checks whether fixes worked. The same weaknesses reappear year after year.
Key Concept: The Readiness Evidence Ladder
A practical way to think about proof is as a ladder. Each rung represents a stronger form of evidence that a critical service can withstand disruption. The aim is not to reach the top rung for everything, but to know which rung each critical service is on and to climb deliberately where the stakes are highest.
- Documented. A plan exists, with roles, procedures, and recovery strategies written down. This is necessary but provides the weakest assurance.
- Reviewed. The plan has been checked against current reality: people, systems, suppliers, and locations are accurate, and it aligns with the service's impact tolerance.
- Walked through. The people responsible have discussed the plan together against a scenario, confirming they understand their roles and identifying obvious gaps.
- Exercised. The plan has been tested in conditions that apply pressure: realistic timing, incomplete information, unexpected developments, and dependencies on other teams and suppliers.
- Demonstrated. Recovery or continuity has been shown to work in practice, for example by actually failing over a system, operating from an alternate site, or switching to a manual workaround at realistic volume, and the service stayed within tolerance.
- Sustained. The demonstration has been repeated over time, after significant changes, and findings from each round have been closed and verified.
The ladder gives executives a common language. Instead of asking, "Do we have a plan for this?", a board can ask, "Which rung is this service on, and when will it move up?" It also makes honest reporting easier. A service at rung two is not failing; it simply has not yet been proven, and everyone can see what the next step is.
Outcome metrics that matter
To accompany the ladder, shift reporting from activity to outcomes. Useful outcome measures include:
- The proportion of critical services that have been tested against a severe but plausible scenario within the last cycle.
- For each critical service, whether testing showed it could remain within its impact tolerance, and by what margin.
- The number and age of open remediation actions from exercises, audits, and real incidents, especially those rated high impact.
- The proportion of remediation actions verified as effective through retesting, not just marked complete.
- Time to detect, escalate, and decide in exercises and real incidents, compared with targets.
- Dependencies, including third parties, whose recovery capability has been independently evidenced rather than self-reported.
These measures are harder to make look good, which is exactly why they are more useful.
What makes evidence credible
Not all evidence carries the same weight, even on the same rung. Four qualities make the difference between evidence a board can rely on and evidence that merely fills a file.
Realism. Was the test run under conditions that resemble a real event, including surprise, time pressure, and the absence of key people, or was it staged for success? A demonstration at two in the afternoon with every expert in the room tells you less than one that starts without warning.
Scope. Did the test cover the whole service, including upstream data, downstream customers, and third parties, or just one component? A successful system failover is valuable, but it does not prove that the people, processes, and suppliers around that system can keep the service running.
Independence. Was the outcome assessed by someone other than the team responsible for the capability? Self-assessment has a place, but independent observation, from a second-line function, internal audit, or an outside facilitator, adds weight and catches blind spots.
Currency. Is the evidence recent, and has anything material changed since? A test from two years ago, before a platform migration and a supplier change, says little about today. Evidence should carry a date and a note of the conditions under which it remains valid.
A simple discipline helps: whenever a test result is reported upward, record the rung it supports, the scenario used, what was in and out of scope, who observed it, and what has changed since. That small amount of structure turns a collection of reports into a body of evidence leaders can defend to regulators, auditors, customers, and themselves.
What Organizations Should Do
Anchor everything to critical services and tolerances
Proof needs a yardstick. If you have not already identified critical services and agreed impact tolerances, that comes first. Every test, metric, and report should connect back to whether a specific service can stay within its tolerance.
Assess where each critical service sits on the ladder
Run an honest baseline. For each critical service, gather the existing evidence: plans, test reports, incident reviews, audit findings, and supplier assurances. Place each service on the ladder. Expect some uncomfortable results; the baseline is valuable precisely because it is candid.
Build a multi-year testing program that climbs
Plan exercises so that each cycle increases realism for the most important services. Move from walkthroughs to scenario exercises with injects, then to technical demonstrations and integrated tests involving suppliers. Vary scenarios so that teams do not rehearse the same story every year.
Make remediation rigorous
Treat exercise findings as seriously as audit findings. Each action should have a single owner, a deadline, a description of what "fixed" means, and a plan to verify the fix through retesting. Track aging and escalate stalled actions.
Consolidate the evidence
Bring test results, incident lessons, audit findings, and third-party assurance into one view per critical service. Whether this sits in a GRC platform or a well-governed register, the point is that leadership can see the whole picture without commissioning a special report.
Report to the board in outcome terms
Give directors a concise view: which services are critical, where each sits on the ladder, whether testing shows each can stay within tolerance, which material gaps remain, and what is being done about them. Pair this with a short narrative on the most significant lessons from the period.
Leadership Considerations
Reward candor. The fastest way to stall progress is to treat a failed test as a failure of the team that ran it. Exercises that expose weaknesses are doing their job. Leaders should say so publicly and fund the fixes.
Participate personally. Executive and board participation in exercises signals priority and tests the decision-making layer, which is often the least rehearsed part of any response.
Challenge the green dashboard. If every resilience indicator is green, ask what would turn one red, and whether the testing was demanding enough to find out.
Accept uneven progress. Not every service needs to reach the top of the ladder. Focus investment where the potential harm is greatest, and be explicit about where the organization is accepting lower assurance.
Use the evidence externally. Proven readiness has value beyond internal governance. When a major customer, insurer, or regulator asks about continuity capability, a clear account of what has been tested, what it showed, and what was fixed is far more persuasive than a copy of the plan. Prepare that account once and keep it current.
Link readiness to strategy. Major decisions, such as entering a market, adopting a new platform, or consolidating suppliers, change the resilience picture. Ask how each one affects the evidence for critical services before it is approved.
How OpResONE Can Help
OpResONE helps organizations close the gap between documented plans and demonstrated readiness. We work with your teams to baseline critical services against an evidence ladder, design multi-year testing programs that increase realism over time, build remediation processes that verify fixes, and develop board reporting focused on outcomes rather than activity.
Our approach starts with what you already have. Existing continuity, disaster recovery, cyber, and third-party programs become inputs to a connected view of readiness, not work to be repeated. Where you need technology to consolidate evidence, we can help you assess options matched to your size and maturity.
Related Resources
- Operational Resilience advisory
- Why Testing Matters
- From Compliance to Confidence
- Turning Lessons into Readiness
Move from Plans to Proof
If your board sees plans but not proof, a focused conversation can clarify where to start. Schedule a Strategy Call to discuss your critical services, the evidence you have today, and a practical path to demonstrated readiness.
Sources
- FFIEC IT Examination Handbook, Business Continuity Management booklet, "VII Exercises and Tests"
- FFIEC IT Examination Handbook, Business Continuity Management booklet, "IX Board Reporting"
- Financial Conduct Authority, "Operational resilience"
- ISO, "ISO 22301:2019 Security and resilience — Business continuity management systems — Requirements"

