Back to Blog

Why Business Units Won't Fill In Their BIA (and What to Do I

Why Business Units Won't Fill In Their BIA (and What to Do I

Every BCM practitioner knows the feeling: a BIA cycle launches, a 47-row spreadsheet goes out to 30 business unit contacts, and three weeks later eleven have responded, six of those partially, and two have submitted the template from the previous year with the date changed. The data is stale, inconsistent, and barely defensible to an auditor.

This is not a people problem. It is a design problem. When you understand why participation fails, the fixes become obvious.

TL;DR

  • Business units skip BIAs because forms are too long, the purpose is unclear, and there are no consequences.
  • Shorter, role-specific questionnaires and structured interviews fix most participation failures.
  • Executive sponsorship with named accountability is the single highest-leverage intervention.
  • Automation handles reminders and tracking; practitioners should spend their time on data quality, not inbox management.

What is a business impact analysis?

A business impact analysis (BIA) is the structured process of identifying which business activities are critical, what dependencies they rely on, and how much disruption the organization can tolerate before material harm occurs. It produces the RTO and RPO targets, dependency maps, and minimum viable staffing levels that underpin every recovery plan. Under ISO 22301:2019 Clause 8.2, the BIA is a mandatory input to the business continuity planning process.

The five reasons business units stall

Down below are some of the most common reasons why business units plans stall.

1. The form is built for the BCM team, not the respondent

Most BIA templates are designed around what auditors want to see, not around what a Finance manager or a Warehouse supervisor actually knows how to answer. Questions like "State your MTPD and RTO in hours" mean nothing to someone who has never encountered those terms. The respondent opens the spreadsheet, decides it is not their job, and closes it.

In most organizations we've seen, the longest BIA template runs to between 40 and 70 rows per function. Completion time exceeds 90 minutes for a thorough respondent. That is not a form; it is a project.

2. No one has explained why it matters

Business units operate under constant pressure. Without a credible explanation of why their BIA data protects them, the request competes with every other demand on their time and loses.

The CrowdStrike Falcon Channel File 291 outage in July 2024 brought this into focus sharply. Organizations whose BCM teams had already mapped dependencies between IT systems and revenue-generating functions recovered faster than those who had not. That mapping came from BIAs. When business units understand that their answers determine how quickly their own function gets resources after an incident, participation tends to improve.

3. Accountability sits with the wrong person

Typically the BCM team owns the BIA process, chases submissions, and absorbs the blame when data is missing. But BCM teams rarely have authority over the Finance director or the Head of Operations. Without named accountability at the business unit level, enforced by someone those leaders report to, the BIA is optional in practice regardless of what the policy says.

4. The annual cycle creates artificial urgency at the worst time

Most programs run a BIA once a year, often in Q4 when budgets are being set and teams are already overstretched. The result is a scramble to close submissions before year-end, which produces quantity over quality. Data submitted under deadline pressure is frequently copy-pasted from previous cycles without review.

5. There is no visible consequence for non-compliance

If a business unit submits nothing and nothing happens, the signal is clear. Rational people deprioritize work with no consequences. This is not cynicism; it is how organizations function. BCM programs that tie BIA completion to board reporting, operational resilience attestations, or regulatory submissions change that calculation immediately.

What actually works: a practitioner playbook

Shorten the questionnaire and make it role-specific

A BCM manager once told us she cut her completion time with 40% by reducing her BIA questionnaire by 60%, then creating three variants: one for operational functions, one for IT-dependent services, and one for support functions. The data she got back was more consistent, not less, because respondents answered questions they actually understood.

Start with the five questions every business unit can answer without BCM training:

  1. What does your team produce or deliver each week?
  2. What would stop if your team could not work for 24 hours? 72 hours?
  3. What systems, suppliers, or other teams do you depend on?
  4. What is the busiest period in your calendar?
  5. Who else knows how to do your team's work if you are unavailable?

From those answers, a practitioner can derive RTOs, critical dependencies, and minimum staffing levels. Additional technical questions can follow in a targeted second pass.

Use structured interviews for complex or high-risk functions

Self-service forms work for straightforward functions. For revenue-critical processes, regulated activities, or functions with deep technology dependencies, a 45-minute structured interview produces better data faster than waiting three weeks for an incomplete spreadsheet. Using a consistent set of business impact analysis interview questions keeps outputs comparable across functions.

The interview also builds the relationship that makes future BIA cycles easier.

Secure a named executive sponsor per business unit

The BCM team should not be chasing submissions. An executive sponsor in each major business unit should own completion within their area. This is a governance question, not a process question. It belongs in the business continuity policy.

The BCM manager's role is to brief those sponsors, provide them with a simple status dashboard showing completion rates, and escalate to the CISO or COO when units fall below threshold. Executives respond to executive pressure in a way they simply do not respond to email reminders from a risk team.

Move away from the annual big-bang cycle

The change Healthcare ransomware attack in February 2024 knocked out prescription processing across the United States for weeks. Organizations with annual BIA cycles that had last run in mid-2023 were working from dependency data that pre-dated significant system migrations. Organizations with more frequent, lightweight BIA refresh processes had current data.

A rolling quarterly mini-BIA, targeting one quarter of business units each cycle, keeps data fresher without overloading the BCM team. Each mini-BIA covers only changes since the last submission: new dependencies, headcount changes, system migrations, supplier changes. Full reviews happen every two years or after a material operational change.

Automate reminders and track progress visibly

A BCM team that manually tracks 30 business units across email chains is spending time on administration that should go to data quality. Platforms designed for BIA collection automate submission reminders, escalation sequences, and completion dashboards. When program leaders can see at a glance which units are overdue and by how much, conversations with executive sponsors become factual rather than anecdotal.

Comparing approaches to BIA collection

ApproachCompletion rate (typical)Data qualityResource costBest for
Annual spreadsheet, self-service40–60%Low to mediumLow up front, high chasingSmall programs with mature respondents
Structured interviews only90–100%HighHigh per unitComplex functions, first BIA cycle
Short digital form + interview for gaps70–85%Medium to highMediumMost enterprise programs
Automated platform with role-specific flows80–95%HighLow ongoingPrograms with 20+ business units
Rolling quarterly mini-BIA85–95% (if governed)High, currentMedium ongoingRegulated industries, frequent change

The governance backbone that makes it stick

Process changes only get you so far. Without governance teeth, participation eventually erodes. Three structural elements keep BIA programs functional:

Board-level visibility. When BIA completion rates appear in a board risk report, business unit leaders treat them differently. The BCM maturity benchmark 2026 found that programs with board-level BCM reporting outperformed peers across almost every operational resilience metric.

Regulatory grounding. For financial services firms operating under the FCA's PS21/3 or under DORA Article 11, mapping critical business services requires current impact analysis data. That is not a BCM preference; it is a regulatory obligation. Naming that obligation to business unit contacts changes the conversation. For a fuller view of DORA obligations, see the DORA compliance guide.

Linking BIAs to recovery plans. A BIA that feeds directly into a recovery plan the business unit will actually use in a crisis is worth something to the people who fill it in. When BCM teams close the loop by showing business units their own recovery procedures, BIA participation in the next cycle almost always improves. That linkage between impact analysis and planning is detailed in what is a business continuity plan.

A word on data quality vs. completion

A common mistake practitioners make is celebrating high submission rates while ignoring what was submitted. Ninety percent completion with 40% of responses carrying copied RTOs from last year is not a healthy BIA program. It is a documentation exercise.

After each collection cycle, run a simple data quality check: flag any RTO that matches the previous year exactly, any dependency list that is suspiciously identical to a neighbouring unit's, and any critical function with no named recovery owner. Those flags go back to the business unit contact for clarification before the data enters planning records.

The BIA is a practitioner artefact. Its value is proportional to the quality of the conversation it represents, not the number of rows returned.

Sources

  • ISO 22301:2019, Clause 8.2 , Business impact analysis and risk assessment requirements
  • FCA Policy Statement PS21/3 , Building operational resilience (March 2022)
  • DORA (EU Regulation 2022/2554), Article 11 , ICT business continuity policy requirements
  • CrowdStrike Falcon Channel File 291 outage, July 19 2024 , Reuters coverage
  • Change Healthcare ransomware attack, February 2024 , Bloomberg coverage

Discover how Fortiv's BIA automation solutions help teams collect higher-quality impact data in less time →

Frequently asked questions

Related Resources