What Is ISO 22301? Business Continuity Management System Requirements

The ISO 22301 clause structure, the standard-specific requirements of clause 8, a clause–output mapping table, integration with ISO 27001 and certification steps in one guide.
Technical summary
Technology
ISO 22301:2019, ISO 22313, ISO/TS 22317, ISO 27001:2022
Topic
Business continuity management system requirements
Level
Beginner–intermediate
Prerequisites
  • General familiarity with management system concepts
In this article7 sections

Companies with backup software, a second data center and a signed contingency plan often get stuck in the same place in an ISO 22301 audit: they can’t show which business impact analysis the plan is based on, who approved the targets and when the plan was last exercised. ISO 22301 defines the requirements of a business continuity management system (BCMS); it ties the organization’s preparation for disruption, keeping its prioritized activities going during disruption and returning to normal into a management cycle. Below we explain the clause structure, the standard-specific requirements, the output each clause produces and the certification steps, in a simple order for information security and quality managers and the compliance teams of ISO 27001-certified companies.

The purpose and structure of ISO 22301

The current version of the standard is ISO 22301:2019 (“Security and resilience — Business continuity management systems — Requirements”); the first edition was published in 2012. An amendment published in 2024 (Amd 1:2024) added, as in many management system standards, an assessment of whether climate change is a relevant issue to the context of the organization clauses. Certification audits are carried out together with this amendment.

ISO 22301 uses ISO’s common high-level structure for management systems. Anyone who has worked with ISO 9001 or ISO 27001 will recognize the clause order immediately:

  • Clause 4 – Context of the organization: internal and external issues, interested parties, legal and regulatory requirements, BCMS scope.
  • Clause 5 – Leadership: top management commitment, business continuity policy, roles and authorities.
  • Clause 6 – Planning: risks and opportunities, business continuity objectives, planning changes to the BCMS.
  • Clause 7 – Support: resources, competence, awareness, communication, documented information.
  • Clause 8 – Operation: the standard’s business continuity-specific core.
  • Clause 9 – Performance evaluation: monitoring and measurement, internal audit, management review.
  • Clause 10 – Improvement: nonconformity, corrective action and continual improvement.

Implementation guidance is in ISO 22313, business impact analysis guidance in ISO/TS 22317, and supply chain continuity guidance in ISO/TS 22318. These documents contain no requirements; the criterion in the audit is ISO 22301 itself. A guidance document helps. It isn’t the criterion.

Clauses specific to business continuity

Clauses 4–7 and 9–10 are largely shared with other management systems. The content that sets ISO 22301 apart is in clause 8, and that’s where the auditor spends most of their time:

  • 8.2 Business impact analysis and risk assessment: Impact criteria, prioritized activities, time frames (MTPD and RTO are mentioned in this clause’s notes), resources and dependencies; plus assessing risks that could disrupt prioritized activities. For the method, see the business impact analysis guide.
  • 8.3 Strategies and solutions: Identifying and selecting options before, during and after disruption, based on the BIA and risk assessment; meeting resource requirements such as people, information and data, buildings and infrastructure, facilities and equipment, IT systems, transport and logistics, finance and partners.
  • 8.4 Plans and procedures: Response structure (teams, authorities), warning and communication, business continuity plans and recovery (return to normal). The BCP content guide gives details on the content of the plan document.
  • 8.5 Exercise program: Exercising plans and solutions at planned intervals and when significant changes occur, reporting the results and carrying out improvements.
  • 8.6 Evaluation of documentation and capabilities: Reviewing the suitability, adequacy and effectiveness of plans, the BIA and strategies through exercises, post-incident reviews and performance evaluations.

Some requirements outside clause 8 also take on a continuity angle. Clause 7.4 on communication covers routine internal and external communication about the BCMS; warning and communication during a disruption is covered separately in 8.4.3: communication with interested parties, the media where necessary and the relevant authorities, communication channels remaining usable during disruption and these arrangements being exercised. In practice, this means something simple: if crisis communication depends on corporate email and email is also affected by the outage, 8.4.3 isn’t met.

Clause–output mapping table

What wastes the most time in certification preparation is not knowing which concrete output meets which clause. A team that starts searching folders when the auditor asks “What can you show for 8.5?” is already too late. The table below shows typical outputs. There may be a difference between items the standard explicitly requires as “documented information” and records kept as good practice; the final list is built according to the organization’s scope.

Clause Topic Typical output
4.1–4.2 Context, interested parties, legal requirements Context analysis, list of interested parties and obligations
4.3 Scope Scope document and justifications for exclusions
5.2–5.3 Policy, roles Business continuity policy, role and authority definitions
6.1–6.2 Risks and opportunities, objectives BCMS risk/opportunity register, measurable objectives and action plan
7.2–7.3 Competence, awareness Training records, evidence of team members’ competence
8.2 BIA and risk assessment Approved BIA, continuity risk assessment
8.3 Strategies and solutions Strategy decisions, resource requirements
8.4 Plans and procedures Response structure, communication procedure, BCPs, recovery procedures
8.5 Exercise program Annual exercise plan, exercise reports
8.6 Assessment Plan review records, post-incident review
9.1–9.3 Monitoring, internal audit, management review Indicator reports, internal audit report, management review minutes
10.1 Nonconformity and corrective action Corrective action records

What ISO 27001 shares, and how they differ

An ISO 27001-certified organization doesn’t start ISO 22301 from scratch. Thanks to the shared structure, document control, internal audit, management review and corrective action processes can be run under a single management system. How to build the integrated structure is covered separately in the article integrated management system for ISO 27001, ISO 9001 and ISO 22301.

There’s an overlap at control level too. The ISO 27001:2022 Annex A controls 5.29 (information security during disruption), 5.30 (ICT readiness for business continuity), 8.13 (information backup) and 8.14 (redundancy of information processing facilities) relate directly to the IT dimension of ISO 22301. In particular, 5.30 expects ICT readiness to be planned according to business continuity objectives. Without targets derived from a BIA, this control can’t be fully met; the sentence “we take backups every night” doesn’t say which RPO it meets.

Topic ISO 27001 ISO 22301
Focus Confidentiality, integrity and availability of information Keeping products and services going during disruption
Core analysis Information security risk assessment BIA and continuity risk assessment
Control set Annex A and the Statement of Applicability No annex control list; strategy and plans
Testing obligation Per control (e.g. backup tests) Mandatory exercise program
Unit of scope Information assets and processes Products, services and prioritized activities

The certification process

Certification is carried out by an accredited certification body through a two-stage audit. Preparation typically follows this order:

  1. Current state analysis: Existing contingency plans, backup and DR arrangements and any ISO 27001 or ISO 9001 processes are assessed against the standard. The most common finding here is that the DR arrangement isn’t tied to any business target.
  2. Scope and policy: Which products, services and locations will be within the BCMS scope is decided with management.
  3. BIA and risk assessment: Prioritized activities and targets are approved.
  4. Strategies and plans: The response structure, communication procedure and business continuity and recovery plans are prepared.
  5. Exercise: Having held and reported at least one exercise before certification is the strongest evidence in the audit that the plans work.
  6. Internal audit and management review: It’s shown that a full cycle of the system has run.
  7. Stage 1 and Stage 2 audits: Stage 1 assesses documentation and readiness, Stage 2 the effectiveness of implementation. The process logic is similar to ISO 27001; for details, see the article the Stage 1 and Stage 2 audit process.

The certificate is valid within a three-year cycle; during this period, annual surveillance audits are held, with a recertification audit at the end of the cycle. Check whether the certification body is accredited for ISO 22301; an unaccredited certificate gets questioned in customer audits.

Scaling the implementation for small and medium-sized companies

The standard doesn’t impose a number of documents based on the organization’s size. In a medium-sized company, a single business continuity plan with attached task cards and an IT recovery plan is often enough. Writing a separate plan for each department increases the maintenance burden; a year later, half the plans are circulating with old phone numbers. These principles help when scaling:

  • Limit the scope to critical products and services first; it’s possible to widen the scope in the first certification cycle.
  • Run the BIA at activity level, but with a simple form.
  • In small companies, combine the crisis team and the business continuity team under the same structure; but write their authorities separately.
  • Keep the exercise program realistic: one tabletop exercise and one technical restore test a year are worth more than an ambitious program that stays on paper.
  • If you have ISO 27001, run document control, internal audit and management review jointly.

How implementation and certification preparation against the standard are run is explained on the ISO 22301 business continuity management consulting page; the structure for managing several standards together is explained on the integrated compliance program page. For the standard’s official reference, see the ISO 22301:2019 page.

Frequently asked questions

Is ISO 27001 certification needed to get ISO 22301 certification?

No. ISO 22301 can be certified on its own. ISO 27001-certified organizations can shorten preparation by reusing their document control, internal audit and management review processes thanks to the shared structure.

What’s the difference between ISO 22301 and ISO 22313?

ISO 22301 is the requirements standard, and certification audits are carried out against it. ISO 22313 gives guidance on how the same requirements can be implemented; you don’t get certified against it.

Is an exercise mandatory before the certification audit?

The standard expects an exercise program to be implemented and the results to be evaluated. It’s hard to show this requirement is met in a system where no exercise has ever been held; that’s why, in practice, at least one exercise needs to have been reported before certification.

Does the BCMS scope have to cover the whole company?

No. The scope can be limited to specific products, services or locations. The scope boundaries and exclusions must be documented with justification, and the external dependencies of in-scope services must also be managed.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles