ISO 22301
Business Impact Analysis Guide: How to Run a BIA for ISO 22301
3 July 2026 · Updated 3 July 2026
A business impact analysis is the ISO 22301 process for working out which activities matter most and how quickly they must recover. An organisation identifies its activities, judges how the impact of losing each grows over time, and then sets recovery objectives. Those outputs drive every continuity strategy and plan that follows.
Where the business impact analysis is wrong, everything downstream inherits the error. An organisation either pours money into recovering activities that could have waited, or leaves the ones that matter under protected. It is the decision the rest of the system is built on, so it repays the effort of getting it right.
What is a business impact analysis in ISO 22301?
A business impact analysis (BIA) is the process of identifying an organisation’s activities and working out how badly, and how fast, a disruption to each would hurt. In ISO 22301 it lives inside clause 8, operation, alongside risk assessment, and it is the analysis the rest of the business continuity management system depends on.
The BIA answers a specific question for each activity: if this stopped, how quickly would the impact become unacceptable? That impact might be financial, reputational, regulatory, contractual or safety related. By plotting how the harm grows over time, an organisation can rank activities by urgency and set defensible recovery targets rather than arbitrary ones. It is deliberately cause neutral: the question is not what might go wrong here, but what it costs to be without this activity, while the threats are handled separately in the risk assessment. For the wider standard, see our ISO 22301 guide.
What is the difference between a business impact analysis and a risk assessment?
A business impact analysis measures consequence, a risk assessment measures cause and likelihood. The BIA asks how much damage results from losing an activity, without caring what caused the loss. The risk assessment asks which threats could realistically disrupt the organisation, how likely they are, and what reduces them.
ISO 22301 requires both, and they inform each other. The BIA tells an organisation which activities are worth protecting and how quickly they must recover, while the risk assessment then focuses attention on the threats most likely to breach those recovery targets, such as a data centre failure, a key supplier collapse or a cyber incident. The BIA runs first, because it defines what is worth analysing risk against. A risk assessment without a BIA protects everything equally, which means it protects nothing well. This mirrors information security practice, covered in our ISO 27001 risk assessment guide. For how the two standards relate, see ISO 22301 vs ISO 27001.
What are the steps in a business impact analysis?
A business impact analysis runs in a repeatable sequence, from listing activities to signing off recovery objectives. The table below sets out the core steps and what each produces.
| Step | What you do | Output |
|---|---|---|
| 1. Identify activities | List the activities behind each product and service | Activity inventory |
| 2. Assess impact over time | Judge how harm from losing each activity grows | Impact profiles |
| 3. Set MAO | Fix the maximum acceptable outage per activity | Time tolerances |
| 4. Set RTO and RPO | Derive recovery time and recovery point targets | Recovery objectives |
| 5. Map dependencies | Record the people, systems, suppliers and sites each needs | Dependency map |
| 6. Prioritise | Rank activities by urgency and dependency | Prioritised recovery order |
The method has to stay consistent across the organisation, otherwise one department’s “critical” is another’s “important” and the priorities do not compare, so the same impact scale and the same time bands apply everywhere. The output of this sequence feeds directly into continuity strategies and plans, which are set out in ISO 22301 clauses explained.
How are RTO, RPO and MAO set?
These targets come from the impact profiles the business impact analysis produces, working from the outage limit inward. Maximum Acceptable Outage (MAO) comes first: it is the point at which the harm from losing an activity becomes unacceptable. Recovery Time Objective (RTO) is the target the organisation commits to for restoring the activity, and it must be shorter than the MAO so recovery happens with margin to spare.
Recovery Point Objective (RPO) is a different axis. It measures acceptable data loss, expressed as how far back in time an organisation must be able to recover. An RPO of one hour means losing at most an hour of data, while a near zero RPO demands continuous replication and costs accordingly, so the number has to reflect real tolerance rather than aspiration. The discipline is to justify each figure against the impact profile, because a four hour RTO that cannot be funded is not a recovery objective, it is a wish. The targets have to be ones the organisation can actually meet, with the gap closed where they cannot.
What are the common mistakes in a business impact analysis?
The most common mistake is letting every owner declare their activity critical. When impact is self assessed without a consistent scale and a challenge process, everything becomes urgent and the analysis loses its value, because a BIA that ranks nothing has failed at its one job.
The other frequent errors follow a pattern: assessing impact at a single point in time instead of across a timeline, which misses how a tolerable two hour outage becomes intolerable at day three; ignoring dependencies, so an activity with a two hour RTO relies on a system with an eight hour one; and treating the BIA as a one off document rather than a live input. Recovery objectives that are never revisited drift out of line with the business. A BIA is only useful if it is current, consistent and challenged, and left unmaintained it quietly stops describing the organisation it is meant to protect. For an organisation building toward ISO 22301 certification, Cybernion’s ISO 27001 and management systems service covers both the continuity and information security pathways.
Frequently asked questions
What is a business impact analysis?
A business impact analysis is the process of identifying an organisation’s activities, assessing how the impact of disrupting each one grows over time, and using that to set recovery priorities and objectives. In ISO 22301 it is the analysis that turns broad continuity intent into concrete recovery time and recovery point targets.
What is the difference between a business impact analysis and a risk assessment?
A business impact analysis looks at the consequence of losing an activity, regardless of cause, and works out how quickly it must recover. A risk assessment looks at the threats that could cause disruption and how likely they are. ISO 22301 requires both, and they feed each other, but they answer different questions.
What are the outputs of a business impact analysis?
The main outputs are a prioritised list of activities, the maximum acceptable outage for each, recovery time and recovery point objectives, and the resources each activity depends on, such as people, systems, suppliers and premises. These outputs drive the continuity strategies and plans that follow.
Who should be involved in a business impact analysis?
The people who run each activity, because they know how it works and what breaks when it stops. Process and department owners provide the impact judgement, IT and facilities confirm the dependencies, and a continuity lead or coordinator runs the method and keeps the analysis consistent across the organisation.
How often should a business impact analysis be updated?
At least annually, and whenever something material changes, such as a new product, a restructure, a major system migration or a new critical supplier. ISO 22301 treats continuity as a live management system, so a business impact analysis that is two years out of date no longer reflects the organisation it is meant to protect.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- ISO 22301:2019 Security and resilience, Business continuity management systems, Requirements, ISO, published October 2019
- ISO 22313:2020 Security and resilience, Business continuity management systems, Guidance on the use of ISO 22301, ISO, 2020
- ISO 31000:2018 Risk management, Guidelines, ISO, 2018
Last updated: 3 July, 2026
