
ISO 22301: when the standard is worth more than a continuity plan
ISO 22301 is the international standard for business continuity, and it is often confused with the continuity plan itself. A plan says what you do when things go wrong; the standard asks for a system that makes sure that plan is right, exercised and kept current. This article is about that difference: when ISO 22301 pays off, what it requires and how it sits alongside ISO 27001.
ISO 22301 is not a plan template but a management system: it requires your plan to be justified, exercised, reviewed and kept up to date.
The standard pays off mainly when customers or tenders ask for it, when your outage becomes someone else’s incident, or when you run several sites.
If you already hold ISO 27001, you share the clauses, internal audit and management review. Certification is done by an accredited body; we certify no one.
ISO 22301 is a management system, not a plan
ISO 22301 sets out requirements for a business continuity management system, or BCMS. It is not a fill-in template. It does not tell you which system to restore first or whom to call at night; it requires that you have decided that, justified it, exercised it and kept it current, and that senior management steers it.
In practice the difference is large. A business continuity plan is a document with a date on it. A BCMS is the cycle around it: who owns the plan, how often it is exercised, what happens to the findings, and how you notice it is out of date because a system, a site or a supplier was added.
The standard has two well-known companions. ISO 22313 gives guidance on the requirements and ISO/TS 22317 covers the business impact analysis. Certification is only possible against ISO 22301 itself; in the UK it is published as BS EN ISO 22301.
When the standard is worth more than a plan
For many SMEs a good plan that is exercised every year is enough. ISO 22301 starts to pay off once you answer yes to one of these questions:
- Does a customer or a tender ask for it? Then a certificate is evidence that a self-declaration is not, and it saves telling the same story on every questionnaire.
- Does your outage become someone else’s incident? If you provide logistics, care, payments or a critical service to a larger organisation, you are judged on their continuity.
- Do you operate several sites or countries? Without a shared system each office has its own plan, in its own state of repair.
- Are you in scope of NIS2 or DORA? Both require business continuity and crisis management. The standard is not mandatory for that, but it is a recognisable way to demonstrate it.
The other way round: if the only goal is to be prepared, start with the plan and the impact analysis. You can choose the standard later, and whatever you have already exercised and recorded still counts.
What ISO 22301 requires, clause by clause
The standard uses the same clause structure as ISO 9001 and ISO 27001. The requirements sit in clauses 4 to 10:
- Context (4): which processes, services and sites are in scope, and what customers, regulators and legislation expect of you.
- Leadership (5): policy, roles and a board that is demonstrably involved, not only signing.
- Planning (6): objectives and the risks and opportunities of the management system itself.
- Support (7): people, resources, awareness, communication and documented information.
- Operation (8): the substance. Business impact analysis and risk assessment, continuity strategies and solutions, plans and procedures, an exercise programme, and evaluation of what you have.
- Performance evaluation (9): monitoring, internal audit and management review.
- Improvement (10): nonconformities, corrective action and continual improvement.
An organisation with a good continuity plan usually has part of clause 8. The rest is what the standard adds, and that is where the work is.
Exercising and review: the part a plan lacks
The biggest difference between a plan and a BCMS is that ISO 22301 requires an exercise programme: planned exercises with an objective, a report and follow-up. A plan that has never been exercised is an assumption.
- Tabletop walk-through. The crisis team works through a scenario with the plan in hand. Cheap, and it finds most of the gaps: outdated numbers, unclear decision-makers, assumptions about systems.
- Technical test. Actually restoring a backup, failing over to a second line or site, timing it and comparing it with the agreed recovery time.
- Full exercise. A scenario the participants do not know in advance, including external communication. Demanding, so not every month.
Every exercise produces findings. The standard wants to see that they get an owner and a resolution, and that management takes them into its review. An exercise without an action list is a demonstration.
Watch one trap: exercising only IT. A restore test proves the server comes back, not that invoicing runs or that customer service knows what to say.
ISO 22301 alongside ISO 27001 and NIS2
If you already hold ISO 27001, half the system is in place: the same clauses, the same internal audit and management review, the same document control. Annex A of ISO 27001:2022 also has two controls close to it: 5.29 (information security during disruption) and 5.30 (ICT readiness for business continuity). What you already have for those is in our ISO 27001 checklist.
The difference is the question. ISO 27001 asks whether information stays protected. ISO 22301 asks whether the business keeps running, even when nothing is wrong with information: a fire, a failed supplier, a flu wave, a blocked access road.
Combine them in one management system, with one audit cycle and one management review, rather than two binders side by side. NIS2 lists business continuity, backup management, disaster recovery and crisis management among the measures in Article 21; ISO 22301 is one recognisable way to cover that, not the only one.
From decision to certificate: the sequence
- Define the scope. Which services, sites and processes. Too wide and it is never finished, too narrow and it does not convince the customer who asked for it.
- Gap analysis. Hold what you have against the requirements and list what is missing, with an owner for each item.
- Impact analysis and risk assessment. Which processes may stop for how long, what they depend on, and what is most likely to go wrong.
- Strategies and plans. For each critical process the solution and the plan that goes with it, including IT and suppliers.
- Exercise. At least one full round before the audit, with a report and follow-up.
- Internal audit and management review. Without those two there is no management system to certify.
- Certification audit. In two stages by an accredited certification body (in the UK, accredited by UKAS): first the design and readiness, then the operation. After that come periodic surveillance audits and recertification.
What drives the timeline and the effort: the size of the scope, what you already have (an existing ISO 27001 system saves a lot), the number of sites and critical suppliers, and whether exercising already happens or starts from zero.
Where it goes wrong
- A system nobody owns. Documents written by a consultant that no process owner recognises. The auditor asks the people, not the binder.
- Continuity as an IT project. The standard is about the business. If only IT is at the table, the decisions that matter are missing: which process first, which customer first.
- Suppliers out of sight. Your critical suppliers belong in the analysis, with their own continuity arrangements. Ask for them and include them in an exercise.
- Plans that do not change. A new application, an office move or a change of supplier should trigger a review automatically, not at the next audit.
- The certificate as the goal. Then people exercise for the auditor instead of for the outage, and you only notice on the day it is needed.
Where our work stops
What we do. We deliver the IT side of business continuity: setting up recovery and failover, backups that can demonstrably be restored, running and recording restore tests, supplying the IT dependencies for your impact analysis, supporting technical exercises, and the evidence from our management that an auditor asks for. We work under ISO 9001, ISO/IEC 27001, ISO 14001 and Kiwa NEN 4400-1 ourselves.
What we do not do. We are not a certification body and not an auditor. We do not issue an ISO 22301 certificate, we do not tell you whether you comply with the standard, and we do not carry out an independent audit of your BCMS. Which processes are critical and how long they may stop is for your board to decide; we deliver the technical side of that decision.
Questions we get about this
The ones that come up most when ISO 22301 is on the table.
What is ISO 22301?
ISO 22301 is the international standard setting requirements for a business continuity management system (BCMS). It asks you to establish which processes are critical, how you keep them going during a disruption, and to exercise, review and maintain that. An organisation can be certified against it.
What is the difference between ISO 22301 and a business continuity plan?
A business continuity plan is a document saying what you do when things go wrong. ISO 22301 is the management system around it: who owns the plan, how often it is exercised, what happens to the findings and how it stays current. A plan is therefore part of what the standard requires, not the same thing.
Is ISO 22301 mandatory?
No, ISO 22301 is a voluntary standard. Customers and tenders sometimes ask for it, and legislation such as NIS2 and DORA requires business continuity and crisis management. The standard is a recognisable way to demonstrate that, but not the only one.
What is the difference between ISO 22301 and ISO 27001?
ISO 27001 is about protecting information; ISO 22301 is about keeping the business running through any disruption, even when nothing is wrong with information. They share the same clause structure, so you can combine them in one management system with one internal audit and one management review.
Can you get us ISO 22301 certified?
No. Only an accredited certification body issues a certificate, and we are not a certification body or an auditor. What we do is set up the IT side and make it demonstrable: recovery, failover, restore tests and the evidence for them from our management.
Further reading
The plan, the analysis beneath it and the technology behind it.
Shall we go through the IT side of your continuity?
Tell us which processes must not stop and what you have today for backup, failover and testing. We will tell you what is demonstrable and what is still an assumption; the certificate we leave to your certification body.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.