The average cost of a data breach reached $4.44 million globally in 2025, and $10.22 million in the United States, according to IBM. Yet the number a business continuity assessment should produce is a different one: how many of your critical processes would actually survive a serious disruption, and what evidence do you have for that? Most organisations can produce a plan. Far fewer can produce a defensible answer.
Closing that gap is what an assessment is for. A business continuity assessment is the structured process of measuring how well a continuity programme is designed, how well it is embedded, and how well it would perform when it is tested. Where a business impact analysis tells you what matters and a risk assessment tells you what threatens it, an assessment tells you whether the programme built on top of them is actually working, and where it is not.
This guide explains what a business continuity assessment is, why most programmes avoid doing one honestly, the maturity model and evidence to use, and how to move from a once-a-year audit to a measurement you trust.
TL;DR
- A business continuity assessment evaluates the whole programme, not just whether plan documents exist.
- Score against defined maturity levels and require evidence behind every score.
- Most programmes stall because assessment evidence is scattered across systems, which turns the result into opinion.
- The output should be a prioritised action list, not a number on a slide.
- Move from an annual scramble to a cadence supported by data that updates between reviews.
What is a business continuity assessment?
A business continuity assessment is a structured evaluation of the maturity and effectiveness of a continuity programme. It examines whether the programme has the right elements in place, such as governance, a business impact analysis, plans, exercises, and maintenance, and whether those elements are working in practice rather than merely existing on paper. The output is a score you can defend and a prioritised view of where to invest next.
It is worth separating the assessment from the artefacts it sits alongside. A business impact analysis identifies critical activities and sets recovery objectives. A risk assessment identifies threats, their likelihood, and their impact. A gap analysis compares your current state against a target standard. A business continuity assessment is broader than a gap analysis and more evaluative than either: it scores the programme against a maturity model, gathers evidence for each score, and turns the result into an ordered improvement plan.
| Activity | What it answers | Primary output | Typical cadence |
|---|---|---|---|
| Business impact analysis | Which activities are critical, and how long they can be down | RTOs, RPOs, dependency maps | Annual or event-triggered |
| Risk assessment | What could cause disruption, and how likely and severe it is | Risk register with ratings | Annual |
| Gap analysis | Where do we sit against a target framework or standard | List of gaps and actions | Before certification or major change |
| Business continuity assessment | How mature and effective is the programme as a whole | Maturity score, evidence, improvement roadmap | Annual, moving to continuous |
The standard reference points are ISO 22301:2019, which sets out the requirements for a business continuity management system, and the DRI International Professional Practices, which describe the practice areas a programme should cover. Neither prescribes a maturity model, which is why most organisations build or borrow one. What they do provide is the checklist of things an assessment should be verifying.
The lifecycle matters here. A continuity programme moves through analysis, planning, testing, and maintenance, then back through the cycle again. An assessment is the review step that keeps the rest of the cycle honest. Run it once and it is a photograph. Run it on a cadence and it becomes a control.
Ownership is part of the definition. The BCM team usually runs the assessment, but the evidence comes from across the organisation, and the decisions it produces belong to the executive sponsor. An assessment that stays inside the BCM function tends to confirm what the function already believes. One that pulls in business unit owners, plan owners, and exercise participants produces a score that can withstand challenge.
Why assessing continuity maturity is harder than most think
Most teams do not lack the will to assess their programme. They lack a method that produces anything more useful than a spreadsheet of ticks. Three structural problems get in the way.
Plans measure intention, not capability
A completed plan template tells you that someone wrote down what should happen. It does not tell you whether the named recovery lead still works at the organisation, whether the documented workaround has ever been tried, or whether the stated recovery time objective is achievable with the infrastructure the business actually has. Those are capability questions, and they are exactly the ones a maturity score is meant to answer.
The gap between intention and capability is where most programmes quietly fail. The documentation satisfies the audit. The assumptions behind it have never been validated. An assessment that only checks for the existence of documents will score a fragile programme as mature, which is worse than no assessment at all, because it manufactures false confidence.
The evidence lives in six different systems
To score a programme honestly you need evidence from several places at once: exercise records, incident logs, plan review dates, BIA refresh dates, training completion, and the closure rate of corrective actions. In most organisations those live in different tools, or in shared drives, or in the memory of the person who ran the last exercise.
When evidence is scattered, the assessment collapses into opinion. The person closest to the programme scores it highest. The person who inherited it scores it lowest. Neither score is grounded, so the resulting action plan reflects personality rather than risk. This is the single most common reason assessments are abandoned: the effort of gathering evidence outweighs the value of the result.
Assessment is treated as a one-off event, not a control
For many organisations the assessment happens once, shortly before certification or a regulatory review, and then not again until the next renewal. That cadence is a year out of step with how quickly the business changes. Between assessments, processes are reorganised, vendors are swapped, and key people leave, none of which shows up until the next review.
A programme that is assessed annually is being measured against a business that no longer exists by the time the report is written. The fix is not a longer, more detailed assessment. It is a shorter and more frequent one, supported by data that updates between reviews. The BCI's Horizon Scan Report 2025 continues to show disruption arriving steadily across the year, which is precisely the gap an annual review leaves open.
What to look for in a business continuity assessment
Whether you build your own assessment or adopt one, five elements determine whether it produces a useful score or a cosmetic one.
A maturity model with defined levels
The most useful assessments score against a maturity model with clearly defined levels, each described in behavioural terms rather than adjectives. A five-level scale is common and works well, provided each level says what it looks like in practice rather than how mature it feels.
Defined levels matter because they make the score comparable over time and between business units. Saying a programme is fairly mature is not a measurement. Saying it is at level three for exercises and level two for supplier continuity is. The second statement can be tracked, challenged, and improved.
| Level | Name | What it looks like in practice |
|---|---|---|
| 1 | Ad hoc | Continuity is informal. Plans exist in scattered documents, if at all, with no consistent methodology. |
| 2 | Documented | Core artefacts exist, including a BIA, plans, and contact lists, but they are produced by one or two people and rarely updated. |
| 3 | Tested | Plans are exercised on a schedule. Findings are recorded and most are actioned. Roles are assigned and understood. |
| 4 | Managed | Data stays current. Exercises drive plan updates. Metrics are reported to management, and suppliers are in scope. |
| 5 | Optimised | Continuity data updates continuously. The programme is embedded in change management and judged on measured capability, not documents. |
Evidence-based scoring, not self-report
A score is only as good as the evidence underneath it. For each criterion the assessment should require an artefact: a dated exercise record, a plan review log, a BIA refresh date, a closed corrective action, or a training record. Self-reported maturity, where a manager simply marks their own area as strong, consistently overstates capability.
Evidence brings a second benefit. It is the same material a regulator or auditor will ask for. An assessment built on artefacts produces a report you can reuse for ISO 22301, DORA, or an internal audit, rather than a separate exercise repeated for each audience.
A useful discipline is to list, for each criterion, the single artefact that would prove it. If no artefact can prove a criterion, the criterion is probably subjective and should be reworded or dropped. An assessment full of unprovable criteria will always drift back toward opinion, no matter how carefully the scale is written.
Coverage of the whole lifecycle, not just plans
A plan-only assessment misses the parts of a programme most likely to fail under pressure: whether BIAs are current, whether exercises test realistic scenarios, whether corrective actions close, and whether the programme survives staff turnover. The assessment should touch analysis, planning, testing, maintenance, governance, and culture.
Supplier and third-party continuity belong here too. Most programmes test their own response but have never tested what happens when a critical vendor fails, even though third-party failure is one of the most common real triggers for disruption. An assessment that ignores supplier continuity is measuring half the exposure.
A scoring method that leads to decisions
An assessment that ends in a score without a prioritised action list changes nothing. The output should sort findings by risk and effort so the team knows what to fix first, and it should be simple enough to explain to a board on a single page.
It also helps to separate findings the team can fix inside the programme, such as a missing exercise, from findings that need executive action, such as a business unit that will not nominate an owner. The second category is where assessments earn their keep, because they give the BCM manager evidence to escalate rather than an opinion to argue.
A cadence you can sustain
The right cadence is the one the team can actually keep. For most lean teams that is an annual full assessment supported by lighter quarterly checks on a rotating subset of criteria. The mistake is designing a perfect assessment that runs once and is then abandoned because it took three weeks and produced a document nobody read.
Continuous data collection makes a tighter cadence possible. When plan reviews, BIA refresh dates, and exercise completion update automatically, the quarterly check becomes a review of a dashboard rather than a manual audit. That shift is what turns an assessment from a project into a control.
A useful test for any cadence is whether the programme could answer an unexpected question from the board at short notice: how many critical plans are overdue for review, how many exercise findings remain open, and which business units have not confirmed their data this year. If the answer requires a two-week data-gathering exercise, the cadence is too slow. If the answer is a dashboard, the cadence is working.
Running your first assessment: a 30-day outline
If you have never run a formal assessment, the fastest way to a usable result is to bound it. Thirty days is enough for a first pass in a mid-size organisation, and a fast assessment that ships beats a perfect one that never does.
- Week 1: agree the model. Pick or adapt a five-level maturity model and write, on one page, what each level looks like for your organisation. Get the executive sponsor to sign off on the model before you score anything, so the later conversation is about the score rather than the scale.
- Week 2: gather evidence. Collect what already exists: plan review dates, exercise records, BIA refresh dates, open corrective actions, and training completion. Where evidence is missing, record it as missing rather than filling the gap with an assumption.
- Week 3: score against evidence. Score each criterion using only the artefacts you collected. This is the discipline that separates an assessment from an opinion survey. Expect the score to come in lower than the team's gut feel, which is the point.
- Week 4: produce the action list. Rank findings by risk and effort, separate in-programme fixes from decisions the executive sponsor must make, and present a one-page summary. Book the next assessment before you close this one, so the cadence starts immediately.
Common mistakes that produce a misleading score
Assessments go wrong in a small number of predictable ways. Each one inflates the score and hides the risk it was supposed to surface.
- Scoring self-reported capability. If a manager can mark their own area as strong without an artefact, the score measures confidence, not readiness.
- Assessing documents instead of outcomes. A plan that exists, has been approved, and has never been tested is evidence of intent, not capability.
- Leaving suppliers out of scope. Third-party failure is one of the most common real triggers for disruption, and one of the most commonly unassessed areas.
- Running the assessment once, before certification, then filing it. A one-off assessment measures a business that has already changed.
- Ending on a number. A score without a prioritised action list changes nothing in the following quarter.
- Ignoring the cultural dimension. Whether staff know their role in a disruption, and whether leadership reinforces it, is part of maturity and never shows up in a document review.
What a good assessment report contains
The score is only the top line. What makes an assessment useful is the structure of the report around it, and a report that is too long to read is a report that will not be acted on. Five elements are worth insisting on.
- A one-page summary a board can read in five minutes: overall maturity, movement since the last assessment, and the top three risks.
- A score per dimension rather than a single blended number, so weak areas stay visible instead of being averaged away by strong ones.
- The evidence behind each score, linked to the artefact so a reviewer can check it rather than take it on trust.
- A prioritised action list, divided into in-programme fixes and decisions that require executive sponsorship.
- A named owner and a due date against every action, because an action without an owner is a wish.
How Fortiv handles it
- Assessment evidence comes from the programme itself, not a separate audit. Plan reviews, BIA refresh dates, exercise completion, and action closure are tracked in the platform, so much of the evidence behind a maturity score already exists when you need it.
- A live view of coverage by business unit. You can see which areas have current BIAs, which plans are overdue for review, and which exercise findings are still open, without chasing anyone for a status update.
- Dependency mapping exposes gaps a document review cannot. Cross-process dependencies across people, technology, vendors, and facilities are visualised, so single points of failure surface before an incident finds them.
- AI plan review reads your plans against the scope you define, whether that is ISO 22301, NIST, or DORA, and flags gaps for a human to approve. The AI does the first pass; the practitioner keeps the judgement.
- Exercises and simulations run in the same platform. Micro-simulations, what-if scenarios built on your own data, and AI-generated tabletop exercises produce the tested-capability evidence a maturity score depends on.
- Reporting built for the board. Programme status, outstanding actions, and movement in maturity can be exported and shared without a manual consolidation exercise.
- Migration takes weeks, not months. Existing BIA data and plans are imported and used as the baseline, so adopting a platform does not mean restarting the programme.
From a one-off audit to continuous assessment
The fear that keeps teams on annual, manual assessments is that changing the approach means starting over. It does not. A typical move to continuous assessment follows a short path. In week one, import existing BIA data, plans, and exercise records. In week two, map processes, dependencies, and owners. In weeks three and four, run a baseline assessment against the maturity model and let the platform fill in the evidence it already tracks.
From there the cadence changes rather than the method. The annual assessment still happens, but it becomes a validation of data that is already current, not a three-week scramble to gather it. Quarterly checks confirm the programme is holding. Event-driven triggers, such as a new vendor, a restructure, or a failed exercise, prompt a targeted review of the affected area straight away.
The practical effect is that the programme stops being measured against last year's business. The maturity score reflects what the organisation looks like now, which is the only version of it that matters when a disruption arrives.
Frequently asked questions
Next step
If the last time your programme was assessed was before your last reorganisation, the score you are reporting is already out of date. The first honest assessment is usually the most uncomfortable, because it is the one that turns assumptions into findings. It is also the one that gives you something concrete to improve against.
Book a demo with Fortiv to see how the platform tracks assessment evidence as the programme runs, and what a current maturity view looks like for your organisation.
Sources
IBM Cost of a Data Breach Report, 2025 (global and US average breach cost).
BCI Horizon Scan Report 2025, Business Continuity Institute.
ISO 22301:2019, Security and resilience, business continuity management systems.
DRI International Professional Practices for Business Continuity Management.
DORA (EU Regulation 2022/2554), ICT business continuity requirements.




