Framework · Business continuity · Certifiable

ISO 22301 business continuity: requirements, BIA and certification

ISO 22301 is the international standard for a business continuity management system (BCMS). The 2019 edition, with Amendment 1:2024 on climate change, sets requirements in clauses 4 to 10, including a business impact analysis, continuity strategies, plans and exercises. Accredited certification bodies audit it in two stages.

Key takeaways

What you need to know about ISO 22301

BIA firstThe business impact analysis sets priorities and recovery time objectives.
Exercised plansPlans only count if you exercise them and learn from the results.
Not only ITIt covers people, sites, suppliers and processes, not just systems.
CertifiableAccredited bodies certify it with two-stage audits.
OverlapPairs well with ISO 27001 A.5.29 and A.5.30 and with DORA and RBI expectations.

Who needs ISO 22301?

No law requires the certificate, but these situations usually make it valuable.

Financial servicesRegulators expect operational resilience and tested recovery.
Outsourcing and IT providersClients want proof you can keep delivering during disruption.
Critical infrastructureEnergy, telecom, health and transport need continuity.
Manufacturers with key customersSupply chains ask for continuity assurance.
Public-sector suppliersTenders often score business continuity certification.

QULDEX helps here first: the readiness check shows where you stand before you commit budget.

Clauses 4–10

What does ISO 22301 require?

ISO 22301 requires a business continuity management system: understand what matters most, analyse impacts, choose strategies, write and exercise plans, and keep improving. Clause 8 holds the continuity-specific work.

Clause 4 Plan

Context

Issues, interested parties, legal requirements and scope.

In QULDEX: Scope and legal register set once
Clause 5 Plan

Leadership

Commitment, BC policy and roles.

In QULDEX: Policy approvals with sign-off history
Clause 6 Plan

Planning

Risks to the BCMS and BC objectives.

In QULDEX: Objectives tracked on the dashboard
Clause 7 Plan

Support

Resources, competence, awareness, communication.

In QULDEX: Training and exercise records
Clause 8 Do

Operation

BIA, risk assessment, strategies, plans, exercises.

In QULDEX: BIA and plans linked to activities
Clause 9 Check

Evaluation

Monitoring, internal audit, management review.

In QULDEX: Audit workspace and review packs
Clause 10 Act

Improvement

Nonconformity, corrective action, continual improvement.

In QULDEX: Exercise findings flow into CAPA
Clause explorer · 26 sub-clauses

What are the ISO 22301 clauses?

ISO 22301 has seven requirement clauses with 26 sub-clauses. Clause 8 is where business continuity work happens: BIA, strategies, plans and exercises. Select any sub-clause to see what it asks for and typical evidence.

7requirement clauses
26sub-clauses
8.2business impact analysis
Amd 1:2024climate change added

Showing up to 6 per group. Search, filter, or open a group to see all 26.

Clause 4 · Context 4

  1. 4.1Understanding the organisation and its context

    Determine issues that affect the BCMS, including, since Amendment 1:2024, whether climate change is relevant.

    In QULDEXQULDEX gives this clause an owner, a review cycle and an evidence request, shared with ISO 27001 where the clause is common.

    Typical evidence
    Context analysis
    Maps to
    ISO 27001 4.1

  2. 4.2Needs and expectations of interested parties

    Identify interested parties, their requirements, and applicable legal and regulatory requirements.

    In QULDEXQULDEX gives this clause an owner, a review cycle and an evidence request, shared with ISO 27001 where the clause is common.

    Typical evidence
    Interested parties and legal register

  3. 4.3Scope of the BCMS

    Set the scope: which products, services and locations the BCMS covers.

    In QULDEXScope is set once per programme and drives the BIA.

    Typical evidence
    Scope statement

  4. 4.4Business continuity management system

    Establish, run and improve the BCMS.

    In QULDEXQULDEX gives this clause an owner, a review cycle and an evidence request, shared with ISO 27001 where the clause is common.

Clause 5 · Leadership 3

  1. 5.1Leadership and commitment

    Top management leads the BCMS and integrates it into business processes.

    In QULDEXQULDEX gives this clause an owner, a review cycle and an evidence request, shared with ISO 27001 where the clause is common.

  2. 5.2Business continuity policy

    Set a business continuity policy.

    In QULDEXPolicy approvals with named owners and sign-off history.

    Typical evidence
    Approved BC policy

  3. 5.3Roles, responsibilities and authorities

    Assign BC roles, including incident response teams.

    In QULDEXQULDEX gives this clause an owner, a review cycle and an evidence request, shared with ISO 27001 where the clause is common.

    Typical evidence
    BC team structure

Clause 6 · Planning 3

  1. 6.1Actions to address risks and opportunities

    Plan actions for risks and opportunities to the BCMS itself.

    In QULDEXQULDEX gives this clause an owner, a review cycle and an evidence request, shared with ISO 27001 where the clause is common.

  2. 6.2Business continuity objectives

    Set measurable BC objectives and plan to achieve them.

    In QULDEXQULDEX gives this clause an owner, a review cycle and an evidence request, shared with ISO 27001 where the clause is common.

  3. 6.3Planning changes to the BCMS

    Make changes to the BCMS in a planned way.

    In QULDEXQULDEX gives this clause an owner, a review cycle and an evidence request, shared with ISO 27001 where the clause is common.

Clause 7 · Support 5

  1. 7.1Resources

    Provide the resources the BCMS needs.

    In QULDEXQULDEX gives this clause an owner, a review cycle and an evidence request, shared with ISO 27001 where the clause is common.

  2. 7.2Competence

    Make sure people with BC roles are competent.

    In QULDEXTraining and exercise participation kept in the evidence vault.

    Typical evidence
    Training records

  3. 7.3Awareness

    Make people aware of the policy and their role during disruption.

    In QULDEXQULDEX gives this clause an owner, a review cycle and an evidence request, shared with ISO 27001 where the clause is common.

  4. 7.4Communication

    Plan internal and external communication about the BCMS.

    In QULDEXQULDEX gives this clause an owner, a review cycle and an evidence request, shared with ISO 27001 where the clause is common.

    Typical evidence
    Communication plan

  5. 7.5Documented information

    Create and control the documented information the BCMS needs.

    In QULDEXDocument control with versions, approvals and retention.

Clause 8 · Operation 6

  1. 8.1Operational planning and control

    Plan, run and control the processes needed for business continuity.

    In QULDEXQULDEX gives this clause an owner, a review cycle and an evidence request, shared with ISO 27001 where the clause is common.

  2. 8.2Business impact analysis and risk assessment

    Run a BIA to set priorities, recovery time objectives (RTO) and resources, and assess risks of disruption.

    In QULDEXBIA results and RTO/RPO sit beside each activity and its dependencies.

    Typical evidence
    BIA, risk assessment
    Maps to
    ISO 27001 A.5.30SOC 2 CC9.1

  3. 8.3Business continuity strategies and solutions

    Choose strategies and solutions that meet the RTOs from the BIA.

    In QULDEXQULDEX gives this clause an owner, a review cycle and an evidence request, shared with ISO 27001 where the clause is common.

    Typical evidence
    Strategy decisions
    Maps to
    ISO 27001 A.5.29

  4. 8.4Business continuity plans and procedures

    Set up response structure, warning and communication, and plans to respond and recover.

    In QULDEXPlans are versioned and linked to the activities they protect.

    Typical evidence
    BC and recovery plans
    Maps to
    ISO 27001 A.5.29NIST RC.RP-01

  5. 8.5Exercise programme

    Exercise and test plans regularly and learn from the results.

    In QULDEXExercises are scheduled tasks with results and actions captured.

    Typical evidence
    Exercise reports
    Maps to
    ISO 27001 A.5.30SOC 2 A1.3

  6. 8.6Evaluation of BC documentation and capabilities

    Evaluate whether BC documentation and capabilities are suitable and effective.

    In QULDEXQULDEX gives this clause an owner, a review cycle and an evidence request, shared with ISO 27001 where the clause is common.

Clause 9 · Evaluation 3

  1. 9.1Monitoring, measurement, analysis and evaluation

    Decide what to monitor and evaluate BCMS performance.

    In QULDEXReadiness dashboards per activity and objective.

  2. 9.2Internal audit

    Audit the BCMS at planned intervals.

    In QULDEXInternal audit workspace with sampling and findings.

    Typical evidence
    Audit programme and reports

  3. 9.3Management review

    Top management reviews the BCMS.

    In QULDEXManagement review packs generated from live data.

    Typical evidence
    Review minutes

Clause 10 · Improvement 2

  1. 10.1Nonconformity and corrective action

    React to nonconformities, fix causes and record corrective actions.

    In QULDEXFindings from audits and exercises flow into CAPA.

    Typical evidence
    CAPA records

  2. 10.2Continual improvement

    Continually improve the BCMS.

    In QULDEXQULDEX gives this clause an owner, a review cycle and an evidence request, shared with ISO 27001 where the clause is common.

Sub-clause numbers and titles follow ISO 22301:2019. Summaries are QULDEX paraphrases; the standard's text is the authority.

Certification path

How do you get ISO 22301 certified?

Run the BIA, choose strategies, write and exercise plans, then an accredited certification body audits you in two stages. Most organisations take 6 to 12 months.

  1. Define scope and context

    Decide which products, services and sites are in scope, and list legal and regulatory requirements.

  2. Business impact analysis and risk assessment

    Identify prioritised activities, impacts over time, recovery time objectives and dependencies, then assess disruption risks.

  3. Choose strategies and solutions

    Pick strategies for people, sites, technology, information and suppliers that meet the RTOs.

  4. Write plans and run exercises

    Write response and recovery plans, then exercise them, from tabletop to full tests.

  5. Internal audit and management review

    Clause 9 must operate at least once before certification.

  6. Stage 1 and Stage 2 audits

    The certification body checks design and documents, then samples evidence such as BIA results and exercise reports.

    Audit days set by headcountMulti-auditor workspace →
  7. Keep it running for three years

    Year 1Surveillance audit
    Year 2Surveillance audit
    Year 3Recertification audit

Durations are typical planning ranges from QULDEX audit delivery, not requirements of the standard.

Documented information

Which documents does ISO 22301 require?

Auditors ask for these in Stage 1. The BIA and exercise reports carry the most weight.

Document or recordClauseWhere it lives in QULDEX
BCMS scope and exclusions4.3Program setup
Legal and regulatory requirements4.2Evidence vault
Business continuity policy5.2Evidence vault · policy library
BC objectives6.2Program dashboard
Evidence of competence7.2Evidence vault
Business impact analysis and risk assessment8.2Risk register
Business continuity strategies8.3Evidence vault
Business continuity plans and procedures8.4Evidence vault
Exercise reports and actions8.5Evidence vault · CAPA automation
Internal audit and management review9.2 · 9.3Audit workspace
Nonconformities and corrective actions10.1CAPA automation

Clause references follow ISO 22301:2019.

Time and cost

How long does ISO 22301 take and what drives the cost?

First certification usually takes 6 to 12 months. The number of sites and prioritised activities, and how many exercises you need, drive the effort.

Where the time goes

Scope and context2–4 wk
BIA and risk4–8 wk
Strategies3–6 wk
Plans and exercises2–4 mo
Audit, review, certification1–2 mo

Bars show the upper end of each range on one scale (8 months = full width).

What changes the effort

  • Sites: each site needs its own BIA inputs and plans
  • Prioritised activities: more activities mean more strategies and plans
  • Supplier dependencies: critical suppliers need continuity checks
  • Exercise depth: full tests take more than tabletop exercises
  • Existing ISO 27001: shared clauses and A.5.29/A.5.30 evidence cut effort
Readiness check · 2 minutes

Are you ready for an ISO 22301 Stage 1 audit?

Stage 1 auditors look for these eight things first. Nothing you enter leaves this page.

4.3Is your BCMS scope written down and approved?
5.2Is there an approved business continuity policy?
8.2Have you completed a business impact analysis with RTOs?
8.2Have you assessed risks of disruption?
8.3Have you chosen strategies for each prioritised activity?
8.4Are response and recovery plans written and approved?
8.5Have you exercised plans in the last year?
9.2Have you completed an internal audit of the BCMS?
Crosswalk

How ISO 22301 maps to ISO 27001, SOC 2 and NIST CSF 2.0

Business continuity overlaps with information security on backup, redundancy, incident response and recovery. One exercised plan can serve ISO 22301, ISO 27001 A.5.29–A.5.30 and SOC 2 availability.

Business continuity vs disaster recovery

Business continuity (ISO 22301)Disaster recovery
ScopeThe whole organisation: people, sites, suppliers, processes and ITIT systems and data
GoalKeep prioritised activities running at an acceptable levelRestore systems and data after an outage
Key measuresRTO, MBCO, maximum tolerable period of disruptionRTO and RPO
OwnerBusiness leadership with a BC managerIT operations
StandardISO 22301Part of a BCMS; ISO/IEC 27031 for ICT readiness
In QULDEXQULDEX links IT recovery plans to the business activities they protect, so both views stay in sync.

Continuity crosswalk

ISO 22301ISO 27001:2022SOC 2NIST CSF 2.0Shared evidence
8.2 BIAA.5.30CC9.1GV.OC-04BIA results
8.2 Risk assessment6.1.2CC3.2ID.RA-05Risk register
8.3 StrategiesA.5.29 · A.5.30CC9.1PR.IR-03Strategy decisions
8.4 PlansA.5.29A1.2RC.RP-01BC and recovery plans
8.4 Warning and communicationA.5.26CC2.3RC.CO-03Communication plan
8.5 ExercisesA.5.30A1.3ID.IM-02Exercise reports
BackupA.8.13A1.2PR.DS-11Backup tests
RedundancyA.8.14A1.1PR.IR-03Resilience tests

Indicative mapping for planning. The full crosswalk is in the QULDEX control library.

Where QULDEX fits

How QULDEX runs ISO 22301 from BIA to certificate

QULDEX is ISO 22301 business continuity and audit management software built from EGV Group's audit delivery, used by the organisation getting certified and by the auditors who test it. Pick your role to see who does what.

For organisations building or renewing a BCMS.

  1. ScopeSet scope and contextScope and legal register set once
  2. BIAAnalyse impactsBIA per activity with RTOs and dependencies
  3. StrategiesChoose solutionsStrategies linked to the RTOs they meet
  4. Plans and exercisesWrite and test plansExercise schedule with results and actions
  5. CertificationHost the auditorControlled, logged evidence sharing
  6. SurveillanceKeep it runningLive readiness per activity
Without one systemWith QULDEX
BIA in spreadsheets that age quicklyBIA linked to activities and dependencies
Plans nobody has testedExercise schedule with results and actions
Separate work for ISO 22301 and ISO 27001Shared clauses and evidence
Exercise findings forgottenFindings tracked to closure in CAPA
10+years of audit delivery500+audits deliveredBoth sidesof the audit on one platformRBACand a full audit trail on every action
FAQ

ISO 22301 questions people ask

Does ISO 22301 have Annex L controls?

No. ISO 22301:2019 has no annex of controls; its requirements are in clauses 4 to 10. Annex L, now called Annex SL, is the ISO rule that gives management system standards the same clause structure, which is why ISO 22301 is laid out like ISO 27001 and ISO 9001.

What is ISO 22301?

ISO 22301 is the international standard for a business continuity management system. It helps organisations prepare for, respond to and recover from disruption, and it can be certified.

What is a business impact analysis?

A BIA identifies your prioritised activities, the impact of disrupting them over time, and the recovery time objectives and resources each one needs. It is required by clause 8.2.

What changed in ISO 22301 Amendment 1:2024?

It adds climate change to clause 4: you decide whether climate change is a relevant issue for the BCMS and for interested parties.

What is the difference between business continuity and disaster recovery?

Business continuity covers the whole organisation and keeps prioritised activities running. Disaster recovery is the IT part: restoring systems and data.

How long is an ISO 22301 certificate valid?

Three years, with surveillance audits in years one and two and recertification in year three.

What is the difference between RTO and RPO?

RTO is how quickly an activity or system must be back. RPO is how much data loss, measured in time, is acceptable.

Can QULDEX run ISO 22301 alongside ISO 27001?

Yes. Shared clauses and continuity controls are mapped once, and each standard keeps its own report.

Sources

References

  1. ISO 22301:2019, Security and resilience: Business continuity management systems: Requirements. iso.org
  2. ISO 22301:2019/Amd 1:2024, Climate action changes. iso.org
  3. ISO 22313:2020, Guidance on the use of ISO 22301. iso.org
  4. ISO/TS 22317:2021, Guidelines for business impact analysis. iso.org
  5. ISO/IEC 27001:2022. iso.org

Reviewed by

Ankit Tiwari

Framework reviewer · QULDEX

Reviewed this page against ISO 22301:2019 and Amendment 1:2024: clauses, BIA requirements, certification path and crosswalk.

Page history
  • : Rebuilt with clause explorer, BIA-led certification path, BC vs DR table and readiness check
  • : Page first published

Find your ISO 22301 gaps in 15 minutes

Answer a short readiness check and get a gap summary by clause. No sales call needed to see the result.

Schedule
Book a Demo