
A business continuity plan typically includes eight things: a stated scope and owner, the results of a business impact analysis with recovery targets, recovery strategies and the resources behind them, roles and the rules for invoking the plan, communications, links to the IT disaster recovery plan, arrangements for critical suppliers, and a record of testing and maintenance. Having all eight headings proves very little. A plan can have every one and still fail on the day.
The checklist below is for a plan that already exists. It has 35 checks in seven groups, each paired with what good looks like, so a review produces evidence instead of a feeling. If you are still writing the plan, use our business continuity plan template first; this list assumes the sections are there and asks whether they would hold up.
How to run the review
Book two to three hours with the plan owner, the IT lead and one person from each priority function. Ask everyone to bring evidence: the last exercise report, the impact analysis, the contact list, key supplier contracts.
Score each line Yes, Partly or No. A Yes needs something you can put on the table, such as a dated approval, a test record or a contract clause. A Yes without evidence is a Partly.
Do not fix things in the room. Log each gap with an owner and a date, and keep moving. One more habit is worth the time: pick a page of the plan at random and ask the newest person present to act on it. Their questions will tell you more than the next hour of discussion.
1. Scope and governance
| Check | What good looks like |
|---|---|
| Scope names what is covered and what is not | Sites, entities and services listed; each exclusion has a reason and points to whatever covers it |
| A senior owner approved the current version | Sign-off dated within the last 12 months, and the sponsor can name the top three priorities without looking |
| There is one controlled version | Version number and change log; superseded copies withdrawn; nobody works from last year's PDF |
| Copies can be reached without your network | Printed and offline copies with named holders, and someone has actually retrieved one at short notice |
| The work has time allotted | Continuity tasks appear in the plan owner's objectives instead of being squeezed into December |
2. Business impact analysis and recovery targets
| Check | What good looks like |
|---|---|
| Each priority activity has a maximum tolerable period of disruption | Taken from an impact analysis or workshop less than two years old, approved by leadership |
| Each has a minimum acceptable service level | Stated in operational terms, such as "top 60 accounts only," not "reduced service" |
| Activity RTOs are shorter than the tolerance | The margin covers detection, decision and catch-up; no RTO simply equals the tolerance |
| Data loss limits come from the business | The RPO for each data set reflects what it would take to reconstruct the gap, and IT has agreed to it |
| Peak periods are reflected | Month-end, payroll dates, seasonal peaks and regulatory deadlines noted against each activity |
3. Strategies and resources
| Check | What good looks like |
|---|---|
| A strategy exists for each kind of loss | Losing the building, people, technology or a supplier each has a named response, not only the fire scenario |
| Resources are listed by time band | People, seats, devices and systems needed at 4 hours, 24 hours, 72 hours and one week |
| Manual workarounds are written down | Each has an owner, the forms or lists it needs, and a stated limit on how long it can run |
| Outside arrangements are confirmed | Alternate space, rentals and mutual-aid agreements in writing, with contact names checked this year |
| Spending authority is clear | Who can commit money during an incident, up to what amount, and how costs are coded for the insurance claim |
4. People and communications
For who hears what, through which channel and from whom, see our guide to a business continuity communication plan.
| Check | What good looks like |
|---|---|
| Every critical role has trained alternates | Two alternates per role, and at least one has taken part in an exercise |
| Invocation rules are usable | Plain triggers and the names of who can declare; a manager reading them at 6 a.m. would know whether to act |
| Staff can be accounted for wherever they are | The method covers office, home, travel and field staff, and the last test reached everyone within its target time |
| Key-person dependencies are known | Activities only one person can perform are listed, each with a backup in training or a written procedure |
| Messages and channels are ready | Audiences, spokespeople, approval path, holding statements, and one channel that works without company email |
5. IT recovery
This group is where the business plan and the technology plan have to agree. If the boundary between them is fuzzy in your organization, our piece on business continuity plan vs disaster recovery plan sets out who owns what. If the IT side has no plan at all, start with the disaster recovery plan template.
| Check | What good looks like |
|---|---|
| Systems are mapped to activities | Each priority activity lists the systems it needs, including SaaS and the sign-in service |
| IT targets fit business targets | System RTOs and RPOs in the DR plan sit inside the activity targets here; mismatches are listed with owners |
| Achieved recovery times are known | A restore or failover test in the last 12 months produced actual times, recorded next to the targets |
| An offline or immutable copy exists | At least one copy of critical data that a compromised administrator account cannot alter or delete |
| The DR plan is current and owned | A named owner, a review within the year, and a version number this plan refers to |
6. Suppliers and outsourced services
ISO 22301:2019 asks organizations to evaluate the continuity capabilities of their partners and suppliers as well as their own (clause 8.6), so certification auditors will look for evidence here.
| Check | What good looks like |
|---|---|
| Critical suppliers are identified by activity | Each priority activity names the suppliers and service providers it cannot run without |
| Their continuity has been assessed | Questionnaire answers, evidence of their own testing, or recovery commitments in the contract, on file |
| Each critical supplier has a plan B | A second source, a stock buffer or a workaround, with realistic lead times |
| Contract terms are understood | Recovery commitments, notice duties, force majeure wording and exit terms read by someone in the room |
| Shared dependencies are visible | Where two "independent" suppliers rely on the same cloud provider, carrier or site, the plan says so |
7. Testing and maintenance
The test types, from walkthrough to full interruption, are covered in business continuity plan testing.
| Check | What good looks like |
|---|---|
| The plan was exercised in the last 12 months | The exercise covered the top priority activities, with business staff taking part as well as IT |
| Findings are tracked to closure | Each finding has an owner and a date, and overdue items go to the sponsor |
| Changes trigger updates | New systems, suppliers, office moves and reorganizations prompt a plan check through existing change processes |
| Training is recorded | People with roles were briefed within the year, and new joiners within their first month |
| Leadership reviews the results | A dated review of exercises, incidents, open gaps and resources, which ISO 22301 calls management review (clause 9.3) |
Scoring the result and deciding what to fix
Count the Yes, Partly and No answers in each group. Then fix in a deliberate order rather than the order the gaps were found.
Start with groups 2 and 4. If the recovery targets are wrong, every strategy and IT design built on them is wrong too. If nobody can invoke the plan or reach staff, no strategy runs at all. Groups 5 and 6 usually come next, because technology and supplier gaps tend to be the most expensive to close and need the longest lead time.
For each No, write two numbers: a rough cost to fix it and the exposure it leaves while open. The downtime cost calculator in our planning toolkit gives a defensible first figure for the exposure side. Take the list to the sponsor, who has three legitimate answers for each line: fund it, schedule it, or accept the risk in writing. Leaving it undecided is the only wrong answer.
Frequently asked questions
What are the components of a business continuity plan?
Scope and governance, business impact analysis results with recovery targets, recovery strategies and resources, roles and invocation rules, communications, IT recovery links, supplier arrangements, and testing and maintenance records. The names vary between organizations and standards, but a plan missing any of these will show the gap during an incident.
How often should a business continuity plan be reviewed?
Run a full review like this one at least once a year, and after any real incident or major exercise. Update the plan between reviews whenever something it depends on changes: a new system, a key supplier, an office move or a reorganization.
Who should review a business continuity plan?
The plan owner leads, with the IT lead and one person from each priority function. An outside reviewer, such as internal audit or a peer from another site, catches assumptions the authors no longer see. The sponsor should receive the results and decide on the gaps.
What is the difference between a business continuity plan checklist and a template?
A template helps you write a plan by giving you the sections and prompts. A checklist tests a plan that already exists, asking whether each section would work and what evidence proves it. Use the template first, then this checklist once the plan has been in place for a while.



