The Critical Role of Business Continuity Planning in IT

Most IT teams think they have business continuity covered because they have a disaster recovery plan. They don’t. Disaster recovery brings systems back. Business continuity keeps the business running while those systems are down, and for days or weeks after. Business continuity planning in IT means IT owning its part of both, and making sure they connect.

That gap is where most technology disruptions turn into business crises. On Managing Uncertainty, Episode 327, I described the pattern: the CEO calls the CIO, asks when it will be fixed, hangs up, and waits. But the CIO controls only a fraction of the problem. Customers, transactions, regulators, and employees are the rest of it, and none of that gets solved by restoring the servers.

Here is what business continuity planning in IT actually involves, where it differs from disaster recovery, and what IT leaders should do about it.

Old View New View
Business continuity belongs to the business; IT owns DR One program, two teams, with documented shared ownership
IT sets recovery times by technical tier The business impact analysis sets recovery times; IT builds to them
The cloud provider handles resilience The cloud is infrastructure; resilience is a capability you build
A successful DR test means we’re covered A successful test proves the business can operate, not just that the system restored

Business Continuity Planning vs. Disaster Recovery Planning

Business continuity planning (BCP) keeps critical business processes running through a disruption: people, workplaces, technology, and third parties. IT disaster recovery planning (DRP) restores the technology those processes depend on. They are different disciplines with different owners, and they only work when they’re joined.

Business continuity planning IT disaster recovery planning
Keeps critical business processes running during and after a disruption Restores applications, infrastructure, and data after a technology disruption
Owned by business leaders, coordinated by the BC program Owned by IT
Covers people, facilities, technology, and third parties Covers systems, data, networks, and technology providers
Uses workarounds, alternate sites, and manual processes while systems are down Uses backups, failover, alternate data centers, and cloud regions
Runs through the whole disruption and the recovery that follows Focuses on getting technology back within the required time
Standard: ISO 22301 Standards: ISO/IEC 27031, NIST SP 800-34

The bridge between them is the recovery time objective (RTO): the length of time a business process can be disrupted before the disruption becomes unacceptable to the organization. The business sets it. IT has to meet it. The RTO and RPO section of our Ultimate Guide to IT Disaster Recovery explains both in detail.

What Business Continuity Planning in IT Involves

IT has a role in every step of the business continuity lifecycle, not only the recovery step.

  1. Risk assessment. IT brings the technology threats: ransomware, cloud and SaaS outages, single points of failure, aging platforms, and AI tools that quietly became dependencies.
  2. Business impact analysis (BIA). The BIA tells IT which applications support the most critical processes and how fast each must come back. For many IT teams, it is the first real data they’ve seen on what the business expects.
  3. Recovery strategy. IT designs and funds the recovery capability that meets those RTOs: backups, replication, alternate regions, and a recovery sequence that brings dependencies back in the right order.
  4. Plans. IT writes application, infrastructure, and service recovery plans. Business units write their own continuity plans, including the manual workarounds they’ll use while IT recovers.
  5. Training and awareness. Technical teams need to know their part in the continuity plan. Business teams need to know what to expect from IT, and when.
  6. Testing. IT and the business test together, so a successful restore is measured against whether the business process can actually run.

The Gap Between What the Business Expects and What IT Can Deliver

The most common finding when we put a BIA next to IT’s actual recovery capability is a gap. For example, the business says payroll can be down for four hours. IT’s realistic recovery time for the payroll platform, with its dependencies, is three days.

Neither side is wrong. They have just never compared notes. Business continuity planning in IT is how you make that gap visible, put a price on closing it, and let executives decide which parts to close. Not everything gets a one-hour recovery. That’s a business decision, not an IT one.

The gap has grown in three places:

  • Ransomware. Modern attacks steal data and target backups. Restoring one database and declaring the strategy sound no longer proves anything. A ransomware event is a whole-business crisis: technical recovery is only part of it, and the rest is legal, communications, regulatory, and operations. Our post on building your ransomware playbook covers the full response.
  • Cloud. Moving to the cloud shifts risk; it doesn’t eliminate it. Multi-region architecture and a strong contract are not a recovery plan. As I put it on Episode 327, “The cloud is infrastructure. Resilience is a capability.”
  • Third parties. Your own IT can be fine while a provider’s isn’t.

That last point is the clearest recent lesson. When the February 2024 ransomware attack on Change Healthcare took down claims processing, eligibility checks, and pharmacy transactions across the US, the American Hospital Association told HHS that providers could not process a substantial portion of their claims. The outage was at a vendor, not inside those providers. Their own disaster recovery plans couldn’t bring a vendor’s service back. Their business continuity plans, and their manual workarounds, were what mattered.

Why IT Teams Struggle With Business Continuity Planning

These are the hurdles we see most often:

  • A technical lens. IT experts are trained on systems, networks, and security. Business continuity asks about people, processes, facilities, and vendors, which sit outside the usual IT scope.
  • Limited view of the business. It’s hard to prioritize recovery without knowing how business processes depend on each other.
  • A translation gap. Business leaders need recovery risk in terms of revenue, customers, and regulators, not server tiers.
  • Competing priorities. Continuity work loses to projects with a visible return until an incident makes the case.
  • Comfort with DR. Recovering technology feels concrete. Planning for how the business runs without it feels like someone else’s job.

How to Connect Business Continuity and IT Disaster Recovery

1. Make it one program with shared ownership

Before founding Bryghtpath, I worked at Target, where business continuity reported to the general counsel and technology disaster recovery reported to the CIO. When I inherited the program, it had a single sponsor and no link on paper to IT recovery. It took years, and a change in IT leadership, to get to a single programmatic approach co-sponsored by the general counsel and the CIO. The working rule became: “this is your box. Continuity is our box. Program management is our box.” Write that shared ownership into your policy and governance, not just the org chart.

2. Let the BIA drive IT recovery requirements

Feed RTOs and recovery point objectives (RPOs) from the BIA straight into application tiering. When an application’s tier doesn’t match the processes it supports, raise it with the steering committee and get a decision.

3. Map the dependencies

Know what’s tied to what: which processes rely on which applications, which applications rely on which infrastructure, identity services, and vendors. Without that map, nobody can sequence a recovery.

4. Test the business, not just the restore

Stop running exercises where the technical team restores a system and everyone claps. Run recovery exercises where IT disaster recovery and business recovery happen together, and the measure of success is whether the business process works on the recovered system.

5. Report in business terms

Tell executives where recovery risk sits, what it costs to buy it down, and what the last investment returned. That is the language that gets IT recovery funded.

This is the work we do in IT disaster recovery engagements. For a leading Midwest health insurer whose IT disaster recovery program had never been fully invested in, we ran an ISO/IEC 27031 maturity evaluation, defined roles and recovery requirements for on-premise and cloud-native applications, built a DR testing strategy, and updated the Master Disaster Recovery Plan with ransomware scenario planning. The result, as the case study puts it, was better alignment between business needs and IT capabilities.

Our Ultimate Guide to IT Disaster Recovery covers governance, dependency mapping, recovery sequencing, and testing step by step.

Standards Worth Knowing

  • ISO 22301 sets the requirements for a business continuity management system.
  • ISO/IEC 27031 covers information and communication technology readiness for business continuity, the bridge between the two disciplines.
  • NIST SP 800-34 Rev. 1, the Contingency Planning Guide for Federal Information Systems, is written for federal systems but remains a practical reference for IT contingency planning in any organization.

Restoring the servers is IT’s job. Keeping the business running while you do it is everyone’s, and IT has to be at that table.

Keep Going

A few ways to go deeper if this was useful.

Jamie Anderson Avatar

About the author

Let’s build your Resilience Roadmap

Our team has spent two decades helping the world’s leading organizations prepare for and navigate disruption. We’ll bring that experience to yours.