A business impact analysis is meant to do more than document whether a process is important. It should identify the operational and financial consequences of disruption, the critical resources and dependencies involved, and the information needed to develop recovery priorities and recovery strategies.
That is the short answer, and it is a useful place to start.
A good BIA interview should produce usable recovery data, not just a record of what someone thinks is important. That means the interview has to do more than collect broad descriptions of a process. It has to surface enough detail to support real decisions later.
In short
A strong BIA interview gives you recovery data you can use later, not just general opinions about what matters.
For a practitioner, this matters because weak interviews create problems that show up much later. Recovery targets become shaky, dependencies are missed, workarounds are overstated, and leadership loses confidence in the results.
In practice, a useful BIA interview should help you uncover five kinds of information.
It should tell you what the process actually does, what happens if it stops, how the impact changes over time, what resources it depends on, and what the organization would need to keep the process running at some minimum acceptable level.
This is where many interviews go wrong. They stay at the level of “this process is critical” or “we need it back quickly,” which feels useful in the meeting but does not give you much to work with afterward.
A better interview forces the conversation into specifics:
That is the difference between descriptive data and decision-quality data.
You do not need a huge interview script. You need the right structure.
Start with process definition:
Then move to impact questions:
Then ask recovery and continuity questions:
Then ask dependency questions:
Finally, ask confidence questions:
That last step matters more than people think. It separates a strong first pass from a false sense of precision.
The interviewee should be someone with detailed knowledge of how the process actually operates, not just someone senior enough to approve the result.
If you are also tightening recovery-target decisions downstream from the BIA, see RTO and RPO.
A BIA interview should not depend entirely on memory.
The interviewee may know the process well, but even strong process owners often estimate volumes, timing, and resource needs from habit rather than from records. That is why it helps to ask for supporting evidence where the answer will later drive a decision.
Useful evidence often includes:
Not every answer will have a perfect record behind it, but the answers that drive recovery priorities, impact scales, or recovery targets should be supported where possible by something more durable than recollection alone.
For teams struggling with pre-work, consistency, and follow-up across many interviews, a more structured workflow can help reduce manual friction and make the output easier to review later. If that is part of your challenge, BIA On-Demand is relevant because it supports a more organized interview process and cleaner capture of the output. The interview quality still comes first.
A few patterns usually tell you the interview is not producing usable data.
Everything is described as critical.
If every process is equally urgent, the interview is not helping you prioritize anything.
The interviewee cannot distinguish between inconvenience and unacceptable impact.
If nobody can explain when the impact becomes serious, the recovery data will usually be too vague to use later.
Manual workarounds sound unlimited.
If the workaround depends on a few people working off spreadsheets for three days straight, that is not really a stable continuity option.
Dependencies stay generic.
“We need IT” or “we need the system” is not enough. You need to know which system, which data, which site, which handoff, and what happens if that dependency is only partially available.
No one can tell whether the answer is based on evidence or judgment.
Judgment is fine. Hidden judgment is not.
If your team is also working on how to score criticality and impact more consistently, related BCMMetrics reading may help: BIA Criticality: Definitions and Time Bands and BIA Scoring Models: Impact Scales, Time Bands, Confidence Ratings, and Examples.
The strongest improvement is usually not rewriting the whole questionnaire. It is tightening the workflow around it.
Send focused pre-work first. That lets you reserve live interview time for clarification, challenge, and validation instead of spending half the session collecting basic facts.
Use a consistent structure across interviews. That makes the data easier to compare later.
Push for timing and evidence. If the interview does not pin down when impacts escalate or what supports the answer, the results will usually be harder to defend.
Capture open questions explicitly. Do not let uncertain answers harden into final data just because the meeting ended.
That is usually where the process improves most, not from asking more questions, but from getting more disciplined about the ones that matter.
BIA interviews produce useful data when they move beyond broad process descriptions and force clarity on impact, timing, dependencies, minimum operating levels, and evidence.
That is the real standard.
If the interview only tells you that a process matters, you are still missing the information needed to prioritize recovery, defend targets, and explain the result to leadership. The better interviews are the ones that surface specifics, expose weak assumptions early, and leave you with data that can support real recovery decisions later.
If your BIA interviews are generating inconsistent answers, weak evidence, or recovery data that nobody fully trusts, MHA can help you tighten the interview process and improve the quality of the output.