A Business Impact Analysis (BIA) is the foundation of business continuity planning. It answers three questions: which processes are critical, how long can we be down, and how much data can we afford to lose? Without a BIA, a continuity plan is guesswork with a cover page.
This guide walks through the full BIA process: how to scope it, how to run the interviews, how to set RTO and RPO defensibly, how to map dependencies across multiple analyses so you can see shared points of failure, and how to keep the whole thing alive once it is written.
What Is a BIA in BCP?
In business continuity planning, the BIA is the evidence-gathering stage that comes before you design any recovery strategy. BCP is the plan; the BIA is the analysis that tells you what the plan has to achieve.
The sequence matters and is frequently inverted:
- BIA — determine what is critical, how quickly it must come back, and what it depends on.
- Strategy — decide how to achieve those recovery targets, and what it costs.
- Plan (BCP) — write the runbooks, roles and communications.
- Test — prove the plan meets the BIA's targets.
- Maintain — revisit as the business changes.
Organisations that skip step one end up protecting whatever the IT team happened to think was important, then discover during an incident that the process the business actually could not live without was never in scope.
What a BIA Delivers
- Critical processes ranked by importance to the organisation — revenue, safety, regulatory obligation, contractual commitment, reputation.
- Recovery Time Objective (RTO): the maximum acceptable downtime before impact becomes unacceptable.
- Recovery Point Objective (RPO): the maximum acceptable data loss, expressed as time.
- Maximum Tolerable Period of Disruption (MTPD): the point beyond which the damage is irreversible. RTO must sit comfortably inside it.
- Dependencies: people, systems, data, facilities and third parties each process relies on.
- Recovery order: the sequence you will restore in, agreed in advance rather than argued about during an incident.
- Identify critical processes & owners
- Define RTO (recovery time) & RPO (data loss)
- Map dependencies (people, systems, vendors)
- Prioritize recovery order
- Document in BIA report & link to recovery plans
The BIA Process, Step by Step
1. Scope and Prepare
Decide what the analysis covers: which entities, sites, and functions. Agree the impact categories you will score against — typically financial, regulatory, customer, safety and reputational — and the scale for each. Do this before you speak to anyone, or every interview will produce impacts measured in a different currency.
Define the time horizons you will ask about: impact after 1 hour, 4 hours, 24 hours, 3 days, a week. Impact is rarely linear, and the shape of the curve is what determines RTO.
2. Identify Processes and Owners
List the business processes rather than the systems: order-to-cash, payroll, claims handling, customer support, production. Systems come later, as dependencies.
Every process needs a named owner who can speak for its criticality. Where nobody will own a process, that is itself a finding worth recording.
3. Assess Impact Over Time
For each process, work through the horizons with the owner: if this stopped now, what breaks at four hours, at a day, at a week? Score against your agreed categories.
Two disciplines keep this honest:
- Ask for the mechanism, not the adjective. "Severe reputational damage" means little; "we breach the regulatory reporting deadline on day two and it is publicly disclosed" is assessable.
- Separate impact from likelihood. A BIA deliberately assumes the disruption has happened. How probable it is belongs in the risk register, not here.
4. Set RTO and RPO
For each critical process:
- RTO: "We must resume within X." This drives the recovery strategy — failover, standby capacity, or a manual workaround.
- RPO: "We can lose at most X of data." This drives backup frequency, replication and journaling.
Be realistic. Aggressive targets cost real money, and an RTO of one hour that the business will not fund is worse than an honest four-hour target, because the plan then documents a capability that does not exist.
A useful challenge for any RTO of under an hour: what is the manual workaround, and have we tried it? Frequently there is one, and it moves the target out by hours at no capital cost.
RPO is the more commonly wrong of the two. If backups run nightly, the RPO is 24 hours regardless of what the plan claims. Compare stated RPO against actual backup and replication configuration for every critical process — the gap is a standing finding in most first-time BIAs.
How to Map Dependencies Across Multiple Business Impact Analyses
Individually, each BIA gives you a dependency list for one process. The value appears when you look across them, because that is where shared points of failure hide. A dependency that looks tolerable in one analysis may be carrying eleven critical processes once you aggregate.
Four practical steps:
1. Use one shared inventory, not per-BIA lists. Every BIA must reference the same named entries for systems, vendors, facilities and roles. If one analysis says "the CRM", another "Salesforce" and a third "customer database", no aggregation is possible. A shared inventory with stable identifiers is the single prerequisite.
2. Record the dependency direction and type. For each process capture people (skills, locations, succession), systems (applications, infrastructure, data stores), facilities, and third parties. Note whether the dependency is hard (the process stops) or soft (the process degrades).
3. Invert the map. For each dependency, list every process that relies on it and the tightest RTO among them. This inversion is the whole point: it tells you that the shared authentication service inherits a one-hour RTO because one of the eleven processes behind it needs one, even though it was never assessed that way.
4. Rank by aggregate criticality. Sort dependencies by how many critical processes they carry and by the tightest inherited RTO. That ranked list — not the individual BIAs — is what should drive resilience investment.
Two patterns fall out of this consistently and are worth looking for explicitly:
- Concentration. One vendor, one data centre or one person appearing across many processes.
- Inherited RTO mismatch. A shared component with a recovery capability far weaker than the tightest RTO depending on it. This is the most common cause of a plan that fails its first real test.
Doing this in spreadsheets is possible for a handful of processes and becomes unmanageable past about twenty, because the inversion has to be redone by hand every time anything changes. When the analyses share a single platform and inventory, the inverted view is a query rather than a project.
5. Agree the Recovery Order
Use RTO and criticality to decide what is restored first, and get it agreed while everyone is calm. Document it in the BIA and in the recovery runbooks. During an incident you follow the agreed order — no debate in the moment, when debate is most expensive and least rational.
6. Report, Approve, Maintain
A BIA that is not approved has no authority. Take the results to the accountable executive or committee: the ranked processes, the RTO/RPO targets, the gaps between target and current capability, and what closing each gap would cost. Those gaps are risk-acceptance decisions and belong to the business, not to the continuity team.
Then keep it current. A BIA reflects the business on the day it was written. Trigger a review when you add a critical system, materially change a process, onboard a critical vendor, or open or close a site — and run a full refresh annually regardless.
Common BIA Mistakes
- Analysing systems instead of processes. You end up with an IT recovery plan and no view of the business.
- Letting each owner use their own impact scale. Nothing can be compared or ranked.
- Confusing impact with likelihood. The BIA assumes the event; probability lives in the risk register.
- Accepting RTOs nobody has costed. Targets the business will not fund are fiction.
- Stating an RPO the backup schedule cannot deliver. Check the configuration, not the intent.
- Never aggregating across analyses. Shared points of failure stay invisible until they fail.
- Treating it as an annual document exercise. A stale BIA is worse than none, because it is trusted.
Frequently Asked Questions
What is BIA in BCP?
In business continuity planning, a Business Impact Analysis is the stage that determines which processes are critical, how quickly each must be restored, and what each depends on. It precedes the plan itself: the BIA establishes the recovery targets, and the BCP is the plan built to meet them.
What is the difference between RTO and RPO?
RTO, the Recovery Time Objective, is the maximum acceptable time a process can be down before impact becomes unacceptable. RPO, the Recovery Point Objective, is the maximum acceptable amount of data loss, measured as time. RTO drives recovery strategy such as failover or workarounds; RPO drives backup and replication frequency.
How often should a BIA be updated?
At least annually, and additionally whenever something material changes — a new critical system, a significant process redesign, a new critical vendor, or a site opening or closing. A BIA describes the business as it was on the day it was written, so its accuracy decays with every change that is not captured.
Who should be involved in a Business Impact Analysis?
Process owners provide the impact assessment and validate criticality; IT and operations supply dependency and recovery-capability detail; risk and continuity teams facilitate and ensure consistent scoring; and an accountable executive or committee approves the results, since the gaps between target and capability are risk-acceptance decisions.
How do you map dependencies across multiple BIAs?
Use one shared inventory of systems, vendors, facilities and roles so every analysis references the same named entries, then invert the map: for each dependency, list every process relying on it and the tightest RTO among them. Ranking dependencies by how many critical processes they carry reveals concentration and inherited-RTO mismatches that individual analyses cannot show.
What is the difference between a BIA and a risk assessment?
A BIA assumes disruption has already occurred and measures the consequences over time, producing recovery priorities and targets. A risk assessment evaluates how likely a disruption is and how severe, producing treatment decisions. They are complementary: the BIA tells you what to protect and how fast to recover it, the risk assessment tells you what is most likely to force you to.
Keeping the BIA Connected
The reason BIAs go stale is structural. The analysis lives in one document, the recovery plans in another, the vendor list in a third, and the risk register somewhere else entirely — so a change in one never propagates.
When the BIA, recovery plans, dependency inventory and incident management share one platform, the dependency map stays current as a by-product of ordinary work, and the aggregate view across every analysis is available on demand rather than rebuilt each year.
For more on continuity and resilience, see our Business Continuity and Risk OS pages, or read our guides to building a dynamic BCP and key risk indicators.