Imagine you are told that a storm will close your building for a week. Which services would you restore first? Which customers would you call? Which team could work from home without any trouble, and which could not work at all? If you can answer these questions calmly, you are already thinking like a business continuity planner. If the questions make you uneasy, a business impact analysis is exactly what you need.
A business impact analysis, often called a BIA, is the foundation of every good continuity plan. It is a simple idea: before you decide how to protect your organisation, you need to know what matters most, how quickly harm grows when things stop and what each activity relies on. This guide explains the process in plain words, so beginners can run a first analysis with confidence.
What Is a Business Impact Analysis?
A business impact analysis is a structured way of studying how a disruption would affect each important activity in your organisation over time, and what each activity depends on.
Think of it as a map of consequences. It does not tell you what will cause a disruption. It tells you what would happen if a key activity stopped, whatever the cause. That focus on effects makes it useful for every kind of event, from a power cut to a supplier failure to a sudden loss of staff.
Why It Matters
Without a BIA, continuity plans often rest on guesses. Teams protect what is noisy or familiar, and overlook what is quietly vital. A BIA brings several benefits.
Clear priorities. You learn which activities must be restored first, and which can wait.
Sensible spending. Money and effort go to the areas where harm would be greatest.
Hidden dependencies revealed. You discover which people, systems, suppliers and places each activity relies on, including single points of failure.
Agreed expectations. Leaders and teams agree on how long an activity can be down before harm becomes unacceptable.
Better plans. Recovery plans are built around real needs, not assumptions.
Evidence for others. Auditors, regulators and customers often expect to see that you have analysed what matters.
*Key Terms in Plain Words
*
A few phrases appear in almost every BIA, so it helps to meet them early.
Critical activity. Something the organisation must continue, or restore quickly, to avoid unacceptable harm.
Impact. The effect of an activity stopping, such as lost income, unhappy customers, broken promises, safety risks, legal trouble or damage to reputation.
Maximum tolerable period of disruption. The longest time an activity can be stopped before the damage becomes unacceptable. You may also see it called maximum acceptable outage.
Recovery time objective. The target time within which you aim to restore an activity after a disruption. It should be shorter than the maximum tolerable period.
Recovery point objective. For activities that rely on data, how much recent data you can afford to lose, measured as how far back in time you can go.
Dependency. Anything an activity needs to work, such as people, systems, data, suppliers, equipment, buildings or utilities.
Minimum level of service. The reduced standard at which an activity can run temporarily, which is often enough to keep customers safe and satisfied.
Types of Impact to Consider
When you think about harm, look at several kinds, not only money.
Financial. Lost sales, extra costs, penalties and delayed payments.
Customer. Complaints, lost customers, broken service promises.
People and safety. Risks to employees, customers or the public.
Legal and regulatory. Missed deadlines, breached rules or contract terms.
Reputation. Loss of trust, bad publicity or damage to the brand.
Operational. Backlogs, knock on delays for other teams, loss of data or knowledge.
A useful habit is to ask how each kind of impact grows over time: after an hour, a day, three days, a week and a month. Often, harm is small at first and then jumps sharply at a certain point. That point helps set your recovery targets.
Step by Step: R*unning Your First BIA*
You do not need special software or training to begin. A friendly set of conversations and a simple form are enough.
Step 1: Agree the scope
Decide which parts of the organisation to cover. If you are new to this, start with one department or a handful of key services. A narrow, finished analysis is far more valuable than a broad, abandoned one.
Step 2: Choose who to talk to
Identify the people who really understand each activity, usually team m****anagers and experienced staff. Explain the purpose, and make it clear that you are trying to understand the work, not to judge it.
Step 3: List the activities
For each team, list the main activities they carry out. Use plain descriptions, such as "process customer claims", "run payroll" or "answer support calls."
Step 4: Ask about impact over time
For each activity, ask what would happen if it stopped for an hour, a day, three days, a week and a month. Record the effects in each category above, and rate their seriousness using a simple scale, such as low, medium, high and severe.
Step 5: Set the time limits
Based on the answers, agree on how long each activity can be stopped before harm becomes unacceptable. Then set a recovery target that is shorter than that limit. Note whether a reduced level of service would be acceptable in the meantime.
Step 6: Map the dependencies
For each important activity, list what it relies on, including people with special skills, systems and data, suppliers, equipment, premises, utilities and other internal teams. Ask how many people know how to do the work, and what the backup options are today.
Step 7: Look for peaks
Some activities are more critical at certain times, such as month end for finance, tax season for accountants or holiday periods for retailers. Note these peaks, because the impact of disruption can be far higher then.
Step 8: Rank the activities
Group activities into tiers, such as must restore within hours, within a day, within a week or later. This ranking becomes your guide for planning and investment.
Step 9: Review and agree
Share the draft with managers and a senior sponsor. Check that the results feel right, and resolve any disagreements. Senior agreement matters, because recovery targets often involve money and trade offs.
Step 10: Record and keep it current
Store the analysis in one place. Review it at least once a year, and after major changes in the business.
A Simple Way to Present Results
A one page summary works well for leaders. It might list each critical activity, the impact after one day and one week, the maximum tolerable period, the recovery target, the main dependencies and any single points of failure. A short sentence on what you recommend, such as "cross train a second person for claims handling" turns the analysis into action.
A Small Example
A small training company runs courses, handles bookings and supports clients online. In a BIA, the operations manager asks the team what would happen if each activity stopped.
Booking and payment processing look critical. After one day, the company would lose sales and frustrate customers. After a week, it would lose repeat business. The team agrees that bookings must be restored within four hours, using a simple manual process in the meantime. Course delivery depends on two key trainers and a rented venue. Marketing emails matter less in the short term and could be paused for several days without serious harm.
The dependency map reveals surprises. Booking relies on a single cloud service and one staff member who knows how to fix problems. Payments depend on a third party provider that has no backup. The company decides to cross train a second person, prepare a manual booking sheet and ask the payment provider about its recovery plans.
The analysis took a few conversations and a simple form. It changed what the company protected first.
Common Beginner Mistakes
The first is trying to analyse everything at once. Start with the most important areas.
The second is asking only managers. People who do the work often know hidden dependencies.
The third is thinking only about money. Safety, legal duties and trust matter too.
The fourth is setting every activity as urgent. If everything is a top priority, nothing is.
The fifth is forgetting suppliers and people. Technology is only part of the story.
The sixth is writing the analysis once and filing it away. Businesses change, and so should the BIA.
The seventh is skipping senior agreement. Without it, plans may not receive the resources they need.
The eighth is confusing the analysis with the plan. The BIA tells you what matters. Plans explain what to do. Our guide on how to identify and prioritise risks in business continuity management shows how the two connect.
How Technology Can Help
A set of forms and a shared spreadsheet can serve a small organisation well. As the number of activities, teams and dependencies grows, collecting information, keeping it consistent and spotting connections becomes harder.
IBM OpenPages Business Continuity Management supports this with a central location for business continuity data, so that managers can use current information to carry out business impact analyses and prepare plans. Users can visualise data relationships, identify dependencies and reach information quickly. Views and workflows allow tasks for business impact analyses to be assigned to the right people, with automatic population of fields and guidance to help them complete the work. Role based permissions make sure people see the records they need, and out of the box views and workflows can be modified by administrators to suit different business units. Scheduled testing and issue management then help improve analyses and plans over time.
These capabilities reduce the effort of gathering and updating information. Still, a BIA depends on honest conversations with the people who know the work.
A Quick Start for This Month
- Choose one team or service as your pilot.
- List its five most important activities.
- For each one, write what would happen after one hour, one day and one week of disruption.
- Agree on how long each could be stopped, and what reduced service would be acceptable.
- List the people, systems, suppliers and places each depends on.
- Circle the biggest single point of failure, and agree on one action to reduce it.
Final Thoughts
A business impact analysis is not about predicting disaster. It is about understanding your own organisation well enough to protect what matters most. A few honest conversations, a simple form and a willingness to look at dependencies can reveal more than months of guessing. Start small, ask good questions and let the answers guide your continuity plans.
If you would like help building a clearer and more connected approach, the team at iTechGRC supports organisations with business continuity management using IBM OpenPages. You can reach them at itechgrc18@gmail.com or call +1 800 960 0149.
Top comments (0)