Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A business impact analysis establishes which activities an organisation cannot do without, how quickly each must return, and what the loss looks like over time. Everything in continuity planning depends on it.

What Is a Business Impact Analysis?
A business impact analysis, usually shortened to BIA, answers one question in measurable terms: if this activity stopped, how bad would it get, and how fast? It identifies the organisation’s prioritised activities, the resources they depend on, the point at which disruption becomes unacceptable, and the order in which things must come back.
Without that analysis, continuity planning becomes guesswork dressed as policy. Recovery targets get set by whoever shouts loudest, backup budgets go to the systems with the most vocal owners, and the first real outage reveals that a dependency nobody mapped is holding up the recovery of everything else.
Four terms carry the analysis, and mixing them up is the most common cause of unusable output.
| Term | Meaning | Example |
|---|---|---|
| MTPD | Maximum tolerable period of disruption, after which the damage becomes unacceptable | Order dispatch: 5 days |
| RTO | Recovery time objective, the target for restoring the activity, set inside the MTPD | Order dispatch: 48 hours |
| RPO | Recovery point objective, the maximum acceptable data loss measured in time | Order dispatch: 15 minutes |
| MBCO | Minimum business continuity objective, the reduced level of service that is acceptable while recovering | Manual dispatch of priority orders only |
RPO drives technical architecture more than people expect. A fifteen-minute RPO means replication or frequent log shipping; a 24-hour RPO means nightly backup is enough. Agreeing an RPO of zero across the business, which happens in workshops where nobody mentions cost, produces a plan nobody will fund.
The work is structured interviewing, not a survey. A workable sequence:
Repeat the analysis annually and after significant change: a migration, an acquisition, or a new critical supplier.
Clause 8.2.2 of ISO 22301 requires a documented business impact analysis as the basis of the business continuity management system, and clause 8.2.3 pairs it with a risk assessment. The two are complementary: the BIA tells you what the consequences of loss are, while the risk assessment tells you what might cause that loss and how likely it is. Running one without the other leaves you either defending against threats to unimportant systems or protecting important systems from the wrong threats.
Outputs feed straight into the disaster recovery plan, backup design, and the priorities an incident response team uses when it has to choose what to restore first.
UK financial firms work to a related but distinct concept. PRA and FCA operational resilience rules ask firms to identify important business services, set impact tolerances expressed as the maximum tolerable disruption, map the resources supporting each service, and test their ability to stay within tolerance. Firms had to be able to remain within those tolerances by 31 March 2025. The vocabulary differs from ISO 22301, but the underlying work is a BIA with a consumer-harm lens.
Elsewhere, the NIS Regulations expect operators of essential services to manage continuity for the services in scope, and UK GDPR Article 32 explicitly requires the ability to restore availability and access to personal data in a timely manner after an incident, which is an RTO commitment in all but name.
Three patterns recur. Every activity is rated critical, because owners answer honestly about their own work and nobody arbitrates. Targets are collected but never reconciled with what the technology can deliver, so the plan promises a four-hour recovery for a platform that takes three days to rebuild. And the document is written once for an audit and never revisited, so it describes a system estate that has since moved to the cloud.
The fix for all three is validation by test. Restore something, time it, and compare with the paper. If you want help running that analysis or proving the recovery targets hold, our emergency action plan services cover both sides.
A business impact analysis measures the consequences of losing an activity and how quickly it must return, regardless of cause. A risk assessment examines what could cause that loss and how likely each scenario is. ISO 22301 requires both, because recovery targets without threat analysis leave gaps, and threat analysis without impact data cannot set priorities.
Activity owners from each business function provide the impact data, since only they know what happens when their process stops. IT and operations validate what recovery is technically achievable. An executive sponsor arbitrates when every function claims to be critical, and signs off the final targets. A facilitator runs the interviews consistently so results can be compared across functions.
At least annually, and after any material change: a system migration, an acquisition, a new critical supplier, a site move, or a significant shift in the service portfolio. Many organisations schedule it alongside the annual risk review. If a plan references systems that were decommissioned eighteen months ago, the analysis has stopped being useful.
Technically yes, with synchronous replication, but the cost rises sharply and it introduces its own failure modes, including the replication of corrupted or encrypted data during a ransomware event. Most organisations set a short RPO for transactional systems and a longer one elsewhere, and keep at least one immutable or offline copy that an attacker cannot reach.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.