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.
What you need to know about ISO 22301
Who needs ISO 22301?
No law requires the certificate, but these situations usually make it valuable.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
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.
Context
Issues, interested parties, legal requirements and scope.
In QULDEX: Scope and legal register set onceLeadership
Commitment, BC policy and roles.
In QULDEX: Policy approvals with sign-off historyPlanning
Risks to the BCMS and BC objectives.
In QULDEX: Objectives tracked on the dashboardSupport
Resources, competence, awareness, communication.
In QULDEX: Training and exercise recordsOperation
BIA, risk assessment, strategies, plans, exercises.
In QULDEX: BIA and plans linked to activitiesEvaluation
Monitoring, internal audit, management review.
In QULDEX: Audit workspace and review packsImprovement
Nonconformity, corrective action, continual improvement.
In QULDEX: Exercise findings flow into CAPAWhat 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.
Showing up to 6 per group. Search, filter, or open a group to see all 26.
Clause 4 · Context 4
4.1Understanding the organisation and its contextDetermine 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
4.2Needs and expectations of interested partiesIdentify 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
4.3Scope of the BCMSSet 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.4Business continuity management systemEstablish, 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
5.1Leadership and commitmentTop 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.
5.2Business continuity policySet a business continuity policy.
In QULDEXPolicy approvals with named owners and sign-off history.
- Typical evidence
- Approved BC policy
5.3Roles, responsibilities and authoritiesAssign 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
6.1Actions to address risks and opportunitiesPlan 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.
6.2Business continuity objectivesSet 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.
6.3Planning changes to the BCMSMake 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
7.1ResourcesProvide 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.
7.2CompetenceMake sure people with BC roles are competent.
In QULDEXTraining and exercise participation kept in the evidence vault.
- Typical evidence
- Training records
7.3AwarenessMake 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.
7.4CommunicationPlan 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
7.5Documented informationCreate and control the documented information the BCMS needs.
In QULDEXDocument control with versions, approvals and retention.
Clause 8 · Operation 6
8.1Operational planning and controlPlan, 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.
8.2Business impact analysis and risk assessmentRun 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
8.3Business continuity strategies and solutionsChoose 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
8.4Business continuity plans and proceduresSet 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
8.5Exercise programmeExercise 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
8.6Evaluation of BC documentation and capabilitiesEvaluate 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
9.1Monitoring, measurement, analysis and evaluationDecide what to monitor and evaluate BCMS performance.
In QULDEXReadiness dashboards per activity and objective.
9.2Internal auditAudit the BCMS at planned intervals.
In QULDEXInternal audit workspace with sampling and findings.
- Typical evidence
- Audit programme and reports
9.3Management reviewTop management reviews the BCMS.
In QULDEXManagement review packs generated from live data.
- Typical evidence
- Review minutes
Clause 10 · Improvement 2
10.1Nonconformity and corrective actionReact to nonconformities, fix causes and record corrective actions.
In QULDEXFindings from audits and exercises flow into CAPA.
- Typical evidence
- CAPA records
10.2Continual improvementContinually 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.
Nothing matches that search.
Sub-clause numbers and titles follow ISO 22301:2019. Summaries are QULDEX paraphrases; the standard's text is the authority.
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.
Define scope and context
Decide which products, services and sites are in scope, and list legal and regulatory requirements.
Business impact analysis and risk assessment
Identify prioritised activities, impacts over time, recovery time objectives and dependencies, then assess disruption risks.
Choose strategies and solutions
Pick strategies for people, sites, technology, information and suppliers that meet the RTOs.
Write plans and run exercises
Write response and recovery plans, then exercise them, from tabletop to full tests.
Internal audit and management review
Clause 9 must operate at least once before certification.
Stage 1 and Stage 2 audits
The certification body checks design and documents, then samples evidence such as BIA results and exercise reports.
Keep it running for three years
Year 1Surveillance auditYear 2Surveillance auditYear 3Recertification audit
Durations are typical planning ranges from QULDEX audit delivery, not requirements of the standard.
Which documents does ISO 22301 require?
Auditors ask for these in Stage 1. The BIA and exercise reports carry the most weight.
| Document or record | Clause | Where it lives in QULDEX |
|---|---|---|
| BCMS scope and exclusions | 4.3 | Program setup |
| Legal and regulatory requirements | 4.2 | Evidence vault |
| Business continuity policy | 5.2 | Evidence vault · policy library |
| BC objectives | 6.2 | Program dashboard |
| Evidence of competence | 7.2 | Evidence vault |
| Business impact analysis and risk assessment | 8.2 | Risk register |
| Business continuity strategies | 8.3 | Evidence vault |
| Business continuity plans and procedures | 8.4 | Evidence vault |
| Exercise reports and actions | 8.5 | Evidence vault · CAPA automation |
| Internal audit and management review | 9.2 · 9.3 | Audit workspace |
| Nonconformities and corrective actions | 10.1 | CAPA automation |
Clause references follow ISO 22301:2019.
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
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
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.
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 | |
|---|---|---|
| Scope | The whole organisation: people, sites, suppliers, processes and IT | IT systems and data |
| Goal | Keep prioritised activities running at an acceptable level | Restore systems and data after an outage |
| Key measures | RTO, MBCO, maximum tolerable period of disruption | RTO and RPO |
| Owner | Business leadership with a BC manager | IT operations |
| Standard | ISO 22301 | Part of a BCMS; ISO/IEC 27031 for ICT readiness |
| In QULDEX | QULDEX links IT recovery plans to the business activities they protect, so both views stay in sync. | |
Continuity crosswalk
| ISO 22301 | ISO 27001:2022 | SOC 2 | NIST CSF 2.0 | Shared evidence |
|---|---|---|---|---|
| 8.2 BIA | A.5.30 | CC9.1 | GV.OC-04 | BIA results |
| 8.2 Risk assessment | 6.1.2 | CC3.2 | ID.RA-05 | Risk register |
| 8.3 Strategies | A.5.29 · A.5.30 | CC9.1 | PR.IR-03 | Strategy decisions |
| 8.4 Plans | A.5.29 | A1.2 | RC.RP-01 | BC and recovery plans |
| 8.4 Warning and communication | A.5.26 | CC2.3 | RC.CO-03 | Communication plan |
| 8.5 Exercises | A.5.30 | A1.3 | ID.IM-02 | Exercise reports |
| Backup | A.8.13 | A1.2 | PR.DS-11 | Backup tests |
| Redundancy | A.8.14 | A1.1 | PR.IR-03 | Resilience tests |
Indicative mapping for planning. The full crosswalk is in the QULDEX control library.
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.
- ScopeSet scope and contextScope and legal register set once
- BIAAnalyse impactsBIA per activity with RTOs and dependencies
- StrategiesChoose solutionsStrategies linked to the RTOs they meet
- Plans and exercisesWrite and test plansExercise schedule with results and actions
- CertificationHost the auditorControlled, logged evidence sharing
- SurveillanceKeep it runningLive readiness per activity
For continuity consultants and internal audit.
- ScopeRun the gap assessmentA reusable ISO 22301 gap template
- BIAFacilitate BIAsBIA templates per client
- StrategiesAdvise on strategiesStrategy options linked to RTOs
- Plans and exercisesRun exercisesExercise reports and findings
- CertificationPrepare the clientAn audit-ready pack
- SurveillanceStay on retainerOne dashboard across clients
For accredited bodies auditing business continuity.
- PlanningPlan audit daysScope and BIA in a standard format
- Stage 1Review documentsDocument review with comments tied to clauses
- Stage 2Sample evidenceView-only evidence access with download control and an access log
- FindingsGrade nonconformitiesMajor and minor findings per clause
- DecisionCertifyA traceable audit record
- SurveillanceReturn each yearHistory across the 3-year cycle
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →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.
Go deeper on ISO 22301
References
- ISO 22301:2019, Security and resilience: Business continuity management systems: Requirements. iso.org
- ISO 22301:2019/Amd 1:2024, Climate action changes. iso.org
- ISO 22313:2020, Guidance on the use of ISO 22301. iso.org
- ISO/TS 22317:2021, Guidelines for business impact analysis. iso.org
- ISO/IEC 27001:2022. iso.org
Reviewed by
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.