Business impact analysis (BIA) in ISO 22301: how it works and what auditors check

Published on November 17, 2026

6afcbf10c7a15_iso-22301-business-impact-analysis

Every business continuity management system is built on one piece of analysis. Before an organization can decide how it will recover from a disruption, it needs to know what matters most, how quickly it needs to be back, and what it depends on to get there. In ISO 22301, that analysis is the business impact analysis (BIA).

The BIA is also where many business continuity programmes go wrong. Some organizations produce a spreadsheet with every process marked "critical" and every recovery time set to "4 hours". Others copy recovery objectives from the IT department and call it a BIA. Neither gives management the information it needs to make decisions.

This article explains what ISO 22301:2019 requires in clause 8.2.2, the key concepts you need to understand, and what an auditor will look for.

Where the BIA sits in ISO 22301

Clause 8.2 is titled Business impact analysis and risk assessment. Clause 8.2.1 requires the organization to implement and maintain systematic processes for analysing business impact and assessing the risks of disruption, and to review both at planned intervals and when there are significant changes inside the organization or in its context.

The two analyses answer different questions:

  • the BIA asks: if this activity stops, what happens, and how fast does it become unacceptable?
  • the risk assessment (clause 8.2.3) asks: what could cause it to stop, and how likely is that?

The BIA comes first in logic, because it tells you which activities the risk assessment should focus on. Together, they feed the business continuity strategies and solutions in clause 8.3.

What clause 8.2.2 requires

ISO 22301 requires the organization to use a process for analysing business impacts to determine its business continuity priorities and requirements. That process must:

  1. define the impact types and criteria relevant to the organization's context;
  2. identify the activities that support the provision of products and services;
  3. use the impact types and criteria to assess the impacts over time resulting from the disruption of these activities;
  4. identify the time frame within which the impacts of not resuming activities would become unacceptable to the organization;
  5. set prioritized time frames, within that time frame, for resuming disrupted activities at a specified minimum acceptable capacity;
  6. use the analysis to identify prioritized activities;
  7. determine which resources are needed to support prioritized activities;
  8. determine the dependencies, including partners and suppliers, and the interdependencies of prioritized activities.

Each step builds on the previous one. Let us look at the ones that cause the most confusion.

Impact types and criteria

Impact types are the categories of harm the organization cares about: financial loss, harm to people, legal and regulatory consequences, contractual penalties, reputational damage, environmental damage, loss of service to vulnerable customers. Criteria define what "minor", "significant" or "severe" means for each type — for example, a financial loss above a given amount, or a regulatory breach that must be reported.

Without defined criteria, the BIA becomes a list of opinions. With them, different departments can be compared on the same scale, and management can see why one activity is prioritized over another.

Impacts over time

This is the heart of the BIA, and the step most often skipped. Disruptions do not cause a fixed level of harm; the harm grows with time. A payroll system that is down for two hours may be an inconvenience. Down on the day before salaries are paid, for three days, it becomes a serious problem with employees, regulators and possibly unions.

A good BIA assesses each activity at several points — for example after 4 hours, 1 day, 3 days, 1 week and 1 month — and records when each impact type crosses the threshold of being unacceptable.

MTPD and RTO

Two of the requirements above have well-known names, which ISO 22301 mentions in notes:

  • the time frame within which the impacts of not resuming an activity would become unacceptable is often called the maximum tolerable period of disruption (MTPD);
  • the prioritized time frame for resuming the activity at a specified minimum acceptable capacity is often called the recovery time objective (RTO).

The RTO must be shorter than the MTPD. The gap between them is the safety margin: if recovery takes a little longer than planned, the organization should still be within what it can tolerate.

Note the phrase "minimum acceptable capacity". Recovery does not mean returning to 100% immediately. A call centre may need to answer 40% of calls within one day and full volume within a week. The BIA should define what level of service is acceptable at each stage, sometimes called the minimum business continuity objective.

Resources and dependencies

Once prioritized activities are identified, the organization must determine what they need: people and skills, information and data, buildings and equipment, IT systems, consumables, and funding. It must also identify dependencies on partners and suppliers, and interdependencies between activities.

This is where a BIA often reveals surprises — a single specialist who knows how to run a critical process, a supplier with no alternative, or an "internal" service that actually runs in a third party's cloud. These findings are exactly what the business continuity strategies in clause 8.3 must then address.

What auditors look for

When auditing clause 8.2.2, an auditor will typically check:

  • A defined method. Is there a documented approach with impact types and criteria, or does each department use its own logic? ISO/TS 22317 provides detailed guidance on BIA methods, and many organizations base their approach on it.
  • Coverage. Does the BIA cover the activities that support the products and services within the scope of the BCMS — including support functions such as IT, HR and procurement?
  • Impacts over time. Is there evidence that impacts were assessed at different time points, or were RTOs simply assigned?
  • Consistency. Are RTOs shorter than MTPDs? Do the RTOs of supporting activities and IT systems support the RTOs of the activities that depend on them? An application with a 72-hour recovery time supporting an activity with a 4-hour RTO is a classic finding.
  • Management approval. Business continuity priorities are a business decision. Has top management reviewed and accepted the results?
  • Currency. When was the BIA last reviewed? Has it been updated after organizational changes, new products, new suppliers or a real incident?
  • Link to strategies and plans. Can the auditor trace a prioritized activity from the BIA through to a business continuity solution, a plan and an exercise?

Common mistakes

  • Everything is critical. If all activities have the same priority, the BIA has not done its job.
  • Confusing the BIA with an IT recovery plan. IT disaster recovery is important, but the BIA starts from the business activities and products, not from the servers.
  • RTOs chosen by wishful thinking. An RTO is only meaningful if the strategies and resources to achieve it exist. If they do not, either the solution must be improved or the gap must be accepted by management.
  • A one-time exercise. A BIA performed for the initial certification audit and never reviewed again is a common nonconformity against clause 8.2.1.

Frequently asked questions

Is the BIA a documented information requirement?
ISO 22301 requires documented information to the extent the organization needs for an effective BCMS (clause 7.5). In practice, the results of the BIA must be recorded: they drive the strategies, plans and exercises, and no auditor will accept a BIA that exists only in someone's head.

Who should carry out the BIA?
It is usually coordinated by the business continuity function but performed with the owners of the activities, who understand the impacts. Interviews and workshops are common methods.

What is the difference between RTO and RPO?
The recovery point objective (RPO) relates to data: the point to which information must be restored, which determines how much data loss is acceptable. ISO 22301 does not use the term in clause 8.2.2, but it is widely used when defining requirements for information and IT resources.

Want to go deeper? Read about the role of a business continuity professional. And if you want to prove your knowledge, the ISO 22301 BCMS practitioner and ISO 22301 BCMS auditor certifications are smart options.