ISO 22301
International Standard for Business Continuity Management Systems
ISO 22301 is the international standard for business continuity management systems (BCMS). It helps organisations prepare for disruption and maintain priority products and services at an acceptable level. As a result, teams have a clearer approach to recovery.
Power failures, cyber incidents, supplier outages, extreme weather and the loss of key people can interrupt operations. To prepare for these events, ISO 22301 connects leadership, business impact analysis, risk assessment, continuity strategies, response plans and testing. Together, these activities form a repeatable approach to managing disruption.
The current published edition is ISO 22301:2019, supplemented by Amendment 1:2024 on climate-related considerations. Meanwhile, ISO is developing a new edition, but its draft does not replace the published requirements.
What is ISO 22301 and why does it matter?
Business continuity means keeping the services that matter most running when an incident disrupts normal operations. ISO 22301 sets requirements for a business continuity management system (BCMS). This brings policies, responsibilities, analyses, strategies, plans and reviews together, rather than relying on a single emergency document.
However, its purpose is not to prevent every incident. Instead, organisations identify essential activities and decide how long each can withstand disruption. In addition, they assess resource needs and arrange an effective response. As a result, decisions reflect the business consequences of downtime, rather than treating continuity as an IT backup project.
For example, a logistics company might need to continue accepting urgent orders while its central warehouse platform is unavailable. To do this, it might need a manual intake procedure and current inventory data. Alternative communications, trained staff and a rehearsed return to normal operations would also help. In practice, ISO 22301 helps turn those assumptions into explicit, testable arrangements.
Continuity starts with critical services and realistic recovery priorities.
A business impact analysis identifies what must continue, the consequences of downtime and the resources needed. Plans and technical recovery arrangements should follow those priorities, not the other way around.
Organisations can integrate a BCMS with their existing risk, quality or information security arrangements. For practical guidance, ISO 22313:2020 explains how to use ISO 22301. In addition, ISO/TS 22317:2021 supports a structured business impact analysis (BIA) process.
ISO 22301 is a voluntary standard. Organisations may use the standard without certification. Alternatively, they may seek an independent audit when customers, contracts or internal governance objectives justify formal assurance. However, organisations should check which edition ISO has published before pursuing certification. A revision is currently in development.
Who should consider ISO 22301?
ISO 22301 is relevant across many sectors, including public services, manufacturing, healthcare, technology and supply chains. For example, smaller firms with a few critical operations can also benefit. The requirements apply to organisations of different sizes and sectors. Even so, each organisation should set its BCMS scope and complexity according to its context, obligations and potential disruption impacts.
There is no blanket legal requirement to hold an ISO 22301 certificate. However, sector regulations, customer contracts and procurement conditions may require specific continuity arrangements, evidence or certification. In the EU, NIS2 Article 21(2)(c) addresses continuity for entities in scope. In particular, it covers backups, disaster recovery and crisis management. It does not, however, make ISO 22301 certification compulsory.
Identify the services that cannot be interrupted
Start with the outcomes your organisation must maintain for customers, citizens or partners. Also consider safety, contractual obligations, financial exposure, legal duties and trust for each service. For example, a hospital, an online retailer and a manufacturing plant have very different continuity priorities.
Map dependencies beyond IT
Identify the people, facilities, suppliers, information, systems, equipment and transport needed to deliver priority services. In addition, a complete continuity assessment includes third parties and physical operations, not just data centres and software.
Consider legal and customer expectations
Review applicable rules, contracts, tender terms and sector guidance separately from the voluntary standard. For each relevant entity and jurisdiction, assess requirements under NIS2, national implementing laws or industry-specific regulation.
Choose a sensible BCMS scope
Define covered products and services, sites, processes and dependencies. For instance, a multi-site business may begin with essential customer-facing services. However, it must still understand interfaces with shared resources and external providers.
Decide whether certification adds value
A certified BCMS can provide independent assurance, but it cannot guarantee uninterrupted operations. In practice, certification involves an external audit of the selected scope. Organisations can also use ISO 22301 internally without seeking a certificate.
ISO 22301 requirements: Clauses 4–10
How the management system is structured
ISO 22301:2019 follows a familiar management-system structure. Clauses 4–10 cover context, leadership, planning, support, operation, performance evaluation and improvement. In practice, these requirements are interdependent. First, leadership determines the scope and priorities. Next, operational analysis and strategies shape response arrangements. Over time, exercises, audits and reviews show which arrangements need to change.
Clause 8 addresses operational planning and control, business impact analysis and disruption risk assessment. In addition, it covers continuity strategies and solutions, response arrangements, exercise programmes and the evaluation of continuity documentation and capabilities. This guide paraphrases the standard rather than reproducing its copyrighted requirements.
Context, interested parties and BCMS scope
Understand the organisation, the operating environment and the requirements of interested parties. Then define the products, services, locations and activities covered by the BCMS, together with their boundaries and interfaces.
The 2024 climate-action amendment asks organisations to assess whether climate change is relevant to their BCMS. It also notes that interested parties may have climate-related requirements. Each organisation must assess relevance. However, the amendment does not assume that all organisations face identical climate risks.
Leadership, continuity policy and accountability
Top management must lead and support the BCMS and establish its business continuity policy. In addition, it must assign responsibilities and authorities. Continuity should be part of operational decision-making and resource allocation, not delegated entirely to an IT team.
For example, service owners may approve minimum acceptable operating levels, while crisis leads coordinate escalation, supplier communications and recovery decisions. Therefore, the organisation needs clear decision rights before an incident occurs.
Planning risks, opportunities and objectives
Plan how to address risks and opportunities affecting the BCMS and define measurable business continuity objectives. These management-system planning activities link to the operational disruption risk assessment under Clause 8. However, the two processes serve different purposes.
For example, objectives might include validated alternate processing arrangements, staff preparedness or timely completion of continuity exercises. In practice, owners, resources and evaluation methods make objectives actionable.
People, resources, communication and records
Provide sufficient resources and competent people, develop awareness, establish internal and external communication arrangements and control documented information. Above all, plans must be understandable and available to the teams expected to use them.
In particular, contact lists, escalation criteria, responsibilities and alternative channels need careful maintenance. A plan stored only on an unavailable system cannot guide the response. In addition, teams should update records as processes and dependencies change.
BIA, risks, strategies, plans and exercises
Operational requirements begin with understanding disruption impacts through BIA and assessing potential risks. Organisations then choose continuity strategies and solutions and establish response structures and plans. Finally, organisations exercise and evaluate these arrangements to identify weaknesses.
For instance, order processing might need to resume within four hours. The strategy could combine standby access, manual order capture and supplier coordination. Therefore, recovery time objectives, resource requirements and fallback procedures should reflect the business impact findings and remain practical.
Monitoring, internal audit and management review
Evaluate BCMS performance and effectiveness using suitable measures, audits and management review. In particular, management should check whether priority activities, recovery arrangements, resources and exercise outcomes still meet business needs.
For example, evidence can include exercise reports, observed recovery times and completed corrective actions. Updates to BIA assumptions and independent internal audit findings can also help. Ultimately, the purpose is to identify gaps, not merely count completed documents.
Corrective action and continual improvement
Address nonconformities, understand their causes, determine corrective actions and check that those actions work. Changes in critical services, suppliers, technologies or business conditions may also require a review of continuity analyses and plans.
After a supplier outage, for example, an organisation may revise communication routes, update alternative sourcing and rerun a scenario exercise. Therefore, improvement needs owners and evidence that the intended resilience has actually increased.
How to implement a business continuity management system
A practical implementation sequence connects business priorities with operational resilience. The nine activities below offer a planning approach; they do not replace the standard’s clauses or guarantee certification.
Assign a sponsor and determine the BCMS scope
Agree which products, services, locations and business units are in scope. Name a senior sponsor and continuity owners. Then record relevant stakeholder expectations, contracts and legal obligations so decisions reflect business consequences.
Map critical activities and dependencies
Identify activities that deliver in-scope products and services, then document their staff, suppliers, facilities, data, applications, equipment and other dependencies. In particular, highlight single points of failure and interdependencies across teams.
Conduct business impact analysis
Examine how disruption impacts increase over time. Determine priorities, maximum tolerable periods of disruption, minimum acceptable service levels, resource needs and recovery time objectives (RTOs). Where data recovery matters, define recovery point objectives (RPOs) separately.
Assess disruption scenarios and vulnerabilities
Evaluate plausible disruptive events and existing controls, including cyberattacks, utility loss, supplier failure, key-person absence and site inaccessibility. Then use BIA results to focus risk assessment on the services whose interruption would have the greatest consequences.
Select proportionate continuity strategies
Compare options such as alternate locations, supplier redundancy, manual workarounds, cross-training and resilient ICT recovery. In addition, consider cost, feasibility, capacity, contractual dependencies and whether each option can meet agreed service levels and recovery objectives.
Document response and recovery arrangements
Prepare escalation criteria, a command structure, contacts, communications, action checklists and practical workarounds. Specify who can activate each plan and how teams will restore priority services. Finally, the plans should explain how teams return from temporary arrangements to normal operations.
Train teams and coordinate with partners
Ensure employees and designated responders understand responsibilities and alternate procedures. Include suppliers and outsourced service providers where their participation is critical; agree on evidence, contact routes and realistic hand-offs.
Test capabilities and capture evidence
Run tabletop scenarios, technical recovery tests and operational exercises appropriate to the risk. Measure whether the business can deliver the required outcomes. Then record any obstacles and assign corrective actions. However, completing an exercise alone does not prove that the arrangements work.
Review results and update the BCMS
Use exercises, actual incidents, internal audits and management reviews to refresh the BIA, plans and strategies. In addition, consider changes to services, suppliers and operating conditions. Verify closure of corrective actions and keep the system usable between certification audits.
Illustrative BIA example: An online order fulfilment activity might have a four-hour recovery time objective. Its order data might need a one-hour recovery point objective. Meanwhile, staff could aim to process urgent orders manually during the interruption. These figures are hypothetical: an actual BIA must justify targets against business impacts, tolerable disruption, dependencies and technical feasibility. See the BIA overview and ISO/TS 22317:2021 for further guidance.
How Blue Octopus supports business continuity
Blue Octopus can support the information and analysis work that makes a BCMS usable. For example, its published modules cover an asset registry, dependency views, process management, business impact analysis and risk assessment. In addition, they include continuity-related RTO/RPO fields, alternative procedures and linked documents. Together, these capabilities help teams organise evidence and ownership. Even so, the platform does not replace continuity strategies, exercises, management judgement, audits or independent ISO 22301 certification.
Critical services and dependencies
Business impact analysis
Disruption risk assessment
Continuity workarounds
Responsibilities and evidence
Monitoring and follow-up
For practical continuity work, first agree the BIA and risk-analysis methodology. Then use structured process and asset records to maintain dependencies and recovery requirements. Nevertheless, the organisation still needs to exercise its plans and demonstrate that the chosen arrangements work. See the published module descriptions for supported features.
Frequently asked questions
Answers about certification, BIA, recovery objectives and cybersecurity obligations.
A business continuity plan guides responses and the restoration of essential activities. By contrast, ISO 22301 covers the wider management system. These requirements cover scope, leadership, business impact analysis, risk assessment, strategies and plans. They also cover exercises, performance evaluation and improvement. Therefore, a plan alone cannot demonstrate compliance with every BCMS requirement.
No. ISO 22301 is a voluntary standard, although some tenders and customer contracts require certification. Regulated entities may also have separate continuity duties. An independent certification body carries out the audit, not ISO. Therefore, check the applicable contract or legal text.
Yes. ISO lists ISO 22301:2019 as published, with Amendment 1:2024 addressing climate-related considerations. ISO is developing a revision. However, a committee draft does not replace the published edition. Check ISO and your certification body for future transition arrangements. Do not assume a deadline.
A business impact analysis (BIA) identifies disruption consequences, priorities and recovery requirements. The recovery time objective (RTO) sets a target for restoring an activity or capability. The recovery point objective (RPO) sets the tolerable amount of data loss for a system, measured in time. In practice, organisations must justify and test these targets.
ISO 22301 focuses on continuity of priority products and services. ISO/IEC 27001 focuses on an information security management system. In practice, organisations can coordinate the two standards. NIS2 Article 21(2)(c) includes continuity, backup management, disaster recovery and crisis management measures for in-scope entities. Implementing ISO 22301 does not automatically prove compliance with NIS2 or other legislation.
ISO 22301 requires an exercise programme and evaluation of continuity capabilities. However, one testing interval will not suit every scenario. Exercise frequency and depth should reflect risk, changing requirements and earlier findings. Therefore, teams should practise critical workarounds and recovery arrangements often enough to demonstrate their effectiveness.
Official sources and further guidance
Next steps
Begin with the services your organisation must protect, identify their dependencies and carry out a documented BIA. Next, agree realistic recovery objectives and choose strategies that can achieve them. Then exercise those arrangements with the people who will use them. Finally, review the evidence, address weaknesses and keep the plans current.
Explore Blue Octopus modules to see how you can organise process, asset, risk and BIA information alongside your continuity programme. However, formal conformity assessment and certification decisions remain the responsibility of your organisation and, where applicable, an independent certification body.