A business continuity assessment answers one question: would your program work on a bad day? Not whether the plans exist. Whether the people, plans, and recovery capabilities behind them would hold up when a critical process stops.
You don’t need a consultant to get a first answer. This self-assessment takes about 30 minutes. It covers the 11 elements of a business continuity program in 20 questions, gives you a score out of 40, tells you what the score means, and tells you what to do next.
It is a first read, not a substitute for a full assessment. More on that at the end.
How to Score Your Business Continuity Assessment
Score each question 0, 1, or 2:
- 0: No, or it doesn’t exist.
- 1: Partly. It exists, but it is out of date, incomplete, or untested.
- 2: Yes, and you can show the evidence: a date, a document, a signed approval, or an After-Action Report (AAR).
Two rules make the score honest. First, score a 2 only if you could hand the evidence to an auditor today. “I think we did that last year” is a 1. Second, don’t score it alone. Ask a business unit plan owner and your IT disaster recovery lead to score it with you. Where your answers differ, you have found something.
| Old View | New View |
| An assessment checks whether the plans exist | An assessment checks whether the plans would work |
| The total score is the answer | The weakest element is the answer |
| The program owner scores the program | The people who would run the response score it too |
| Assess once, before the audit | Assess every year and track the trend |
The 20 Questions, by Program Element
The elements come from our guide to starting a business continuity program, which explains each one. I walked through all 11 on Managing Uncertainty, Episode 234.
Governance (questions 1 to 3)
- Do you have a written business continuity policy, approved by an executive, that sets the program’s scope and objectives?
- Do you have a named executive sponsor who funds the program and shows up when asked?
- Does a steering committee, or an equivalent group, meet on a schedule and make decisions about the program?
Risk assessment (question 4)
- Have you assessed the threats that could disrupt your critical operations in the last 12 months, rated by likelihood and impact? It can live in enterprise risk management; it just has to exist and connect to your continuity work. Our business continuity risk assessment matrix shows one way to do it.
Business impact analysis (questions 5 to 7)
- Has every business unit in scope completed a Business Impact Analysis (BIA) in the last 12 to 24 months?
- Have your executives reviewed and validated the BIA results, including which processes are critical and how long each can be down?
- Does the BIA identify what each critical process depends on: applications, data, facilities, key people, and third parties?
Business continuity strategies (questions 8 and 9)
- Does each critical process have a documented way to keep going, such as a manual workaround, remote work, or an alternate site?
- Have those strategies been checked against today’s operations, not the way you worked before the last reorganization?
Plans (questions 10 and 11)
- Does every critical process have a plan with a named business owner, updated in the last 12 months?
- Could the person who has to act find and use the plan under pressure? A plan nobody can use in a disruption doesn’t count.
Training and awareness (question 12)
- Have plan owners and team members been trained on their roles in the last 12 months?
Exercises (questions 13 and 14)
- Have you exercised your critical plans in the last 12 months, with an AAR?
- Does every AAR action have an owner and a due date, and do you check in the next exercise that the fixes happened?
Program maintenance and review (questions 15 and 16)
- Do you review and update the program on a published calendar, and when the business changes?
- Do you report the program’s status and gaps to your executives, and at least once a year to the board or one of its committees?
Crisis communications (question 17)
- Is there one plan for communicating with employees, customers, suppliers, and regulators during a disruption, with clear roles, whoever owns it?
Coordination with external parties (question 18)
- Do you know how your critical suppliers would manage a disruption, how you would absorb its impact, and how you would communicate while it is happening?
Alignment with IT disaster recovery (questions 19 and 20)
- Do your recovery time and recovery point objectives come from the BIA, not from what the infrastructure team assumed?
- Has IT shown, through a test in the last 12 months, that it can recover critical applications within those objectives? If the business expects four hours and IT can deliver four days, score it 0.
What Your Score Means
Add up your points. The maximum is 40.
| Score | What it usually means | What to do next |
| 0 to 12 | Informal. The program lives in a few people’s heads and a few old documents. A disruption will be handled by whoever is in the room. | Start with governance: a sponsor, a short policy, and a first-year scope. Then run the BIA for the processes that drive revenue and customer commitments. |
| 13 to 24 | Developing. The pieces exist but they are uneven, out of date, or untested. This is where most programs are. | Get the lifecycle on a calendar. Validate the BIA with your executives, update the plans that matter most, and run one exercise this year. |
| 25 to 32 | Established. The lifecycle runs and the documents are current. The open question is whether it works, and whether IT can deliver what the business expects. | Test harder. Close the gap between the BIA and IT recovery capability, exercise the scenario you have been avoiding, and track AAR actions to closure. |
| 33 to 40 | Managed. The program is current, tested, and visible to executives. Your risk is complacency and complexity. | Get an outside view, benchmark against peers, and simplify. Cut what doesn’t add value before you add anything new. |
Then ignore the total for a minute and find your lowest element. A program that scores 2s on plans and 0s on exercises doesn’t have an average problem. It has an exercising problem, and that is where the next dollar goes.
These bands are a rough guide, not a formal business continuity maturity model. A maturity model scores each domain against a standard such as ISO 22301 on a five-point scale. On that scale, most programs we evaluate start between 1.5 and 2.5, and a well-run program reaches 2.5 to 3.5 within two years. If you land in the first two bands here, you are where most programs start. That is normal. Staying there is the problem.
What We See When We Assess Programs
After more than a decade of evaluating business continuity programs, the same gaps come up again and again. I covered them on Episode 289:
- The program isn’t aligned with business strategy. If it protects processes your executives don’t care about, it loses funding and credibility.
- Plans and BIAs are too complicated. When we ask organizations that had a disruption about their plans, some tell us they didn’t use them because they were too hard to use. “Then that’s not an effective business continuity program.”
- Crisis management is informal. No defined team, no clear way to convene executives.
- Exercises are rare or shallow. “At a minimum, you should do this once a year. But our best clients do this two to four times a year.”
- Crisis processes are fragmented. Safety, cyber, weather, and physical security each escalate differently, and executives are left asking why.
If your self-assessment points at any of these, you are in good company. The fix usually starts with subtraction. “Start simple. You can build complexity in later.”
What a Self-Assessment Can’t Tell You
A self-assessment is cheap, fast, and useful. It also has three limits.
It can’t interview your people. Documents show what the program says. Interviews show what it does, and they find the two crisis plans with overlapping teams and the recovery order that exists only in one person’s head.
It can’t carry outside credibility. Your executives will weigh an independent assessment differently than they weigh your own score.
It can’t prioritize for you. Twenty questions tell you where the gaps are. They don’t tell you which gaps matter most for your business, your regulators, and your budget.
When those limits matter, step up:
- A quick second read: the free ResiliencyPulse self-check takes about four minutes, and the paid version scores your program against the published standards with peer benchmarking.
- A detailed score of your own: our ISO 22301 maturity model lets you score the program clause by clause.
- An independent assessment: a Resiliency Diagnosis® scores your business continuity, crisis management, and recovery programs against ISO 22301 and the standards that apply to you, interviews your stakeholders, and ends with a prioritized roadmap and an executive briefing. It typically runs about 12 weeks.
Before you buy any outside assessment, read what a business continuity maturity assessment should tell you. It lists the seven things a good one must answer and the red flags in a proposal.
Make It a Habit
Run this business continuity assessment once a year, at the same time, with the same people, and keep the scores. The trend matters more than any single number. A program that moves from 14 to 22 in a year is in better shape than one that has sat at 26 for three.
Score it honestly, fix the weakest element first, and score it again next year.
Keep Going
A few ways to go deeper if this was useful.
- Read more. Resilience, crisis management, and continuity writing at Bryghtpath Insights, or the evaluating section of our Ultimate Guide to Business Continuity.
- Take the four-minute check. The ResiliencyPulse self-check gives you a quick maturity read to compare with your score here.
- Get a maturity score. Our Resiliency Diagnosis® is a standards-based review that produces a maturity score and a prioritized roadmap.
- Talk to us. Set up a call to talk through what your score means for your program.





