Plain-language guides to emergency management

Search

Planning for Essential Operations During a Disruption

business continuity plan

If a fire, outage or storm stopped your normal work tomorrow, you would want answers already written down. A business continuity plan is a set of documented instructions for keeping essential operations running through a disruption.

This guide is one part of our wider look at emergency preparedness, and it focuses on keeping essential work going.

Item Value
Essential elements of a viable continuity program (FEMA course) 10 essential elements
Traditional use of business impact analysis Determine availability requirements for business continuity
Mission-essential functions, in NIST’s phrase What must go right
NIST IR 8286D publication date February 2025
Effect of a cyber disruption on continuity elements Any or all elements may be impacted

These figures come from NIST IR 8286D and a FEMA continuity course page. They can change, so check the source before you rely on them.

What a business continuity plan actually is

The NIST glossary describes a business continuity plan (BCP) as documented, predetermined instructions for sustaining an organization’s mission and business processes during and after a significant disruption. The key word is “predetermined”: decisions are made while things are calm.

In plain terms, the plan answers one question before trouble arrives: what must keep running, and how? It is not a full emergency response manual, and it does not replace the guidance of local officials during an event.

A usable plan tends to share a few traits:

  • It is written down and stored where you can reach it if your main systems or building are unavailable.
  • It names people and roles, not just departments.
  • It is short enough to follow under stress.

Start with a business impact analysis

According to NIST IR 8286D, published in February 2025, business impact analysis (BIA) has historically been used to determine availability requirements for business continuity. The same publication says the process can be extended to show the potential impacts of any type of loss on the enterprise mission.

NIST ties this to mission-essential functions, which it frames as “what must go right,” set against the scenarios that might go wrong. Your analysis is the step that turns a vague worry into a ranked list of what matters most.

A simple way to run the analysis is to work through these steps:

  1. List the functions your organization cannot do without.
  2. Note which people, assets and systems each function depends on.
  3. Have leadership state how much risk it will tolerate, since NIST describes leaders providing risk appetite and tolerance as input to the analysis.
  4. Assign owners to rate the impact of losing each asset and to set protection requirements.

Once you know what matters, a hazard vulnerability assessment helps you judge which threats are most likely to interrupt it.

The elements a continuity program should cover

A FEMA continuity course page lists 10 essential elements of a viable continuity of operations program. Government programs use this vocabulary, but a business or nonprofit can borrow it as a checklist.

  • Continuity communications: how you reach staff and partners.
  • Continuity facilities: where work can happen if the usual site is lost.
  • Delegations of authority: who may make decisions, and when.
  • Devolution: passing responsibilities to another team or location.
  • Essential functions: the work that cannot stop.
  • Human capital: the people who carry out that work.
  • Orders of succession: who steps in if a leader is unavailable.
  • Reconstitution: returning to normal operations afterward.
  • Test, training, and exercise (TT&E): proving the plan works.
  • Vital records management: protecting the information you need.

You do not need to write a chapter for each on day one. Start with essential functions, communications and vital records, then widen the plan as it matures.

business continuity plan Joined hands
Several people stack their hands together.

How a cyber incident changes the picture

The same FEMA page says its later lesson focuses on the continuity elements most likely to be impacted by a cyber incident. It also reminds readers that, depending on the disruption, all continuity elements may be affected.

That matters for planning, because a ransomware event or a failed cloud service can take out communications, records and staff access at once. Write a version of your plan that works without email, shared drives or the office network.

Keep a printed or offline copy of contact lists and priority procedures. Decide in advance how you will reach people if your usual channels are down.

Keep the plan alive with practice

A plan nobody has tried is a guess. The test, training and exercise element exists to find gaps while the stakes are low, and emergency management exercises are one way to do that.

After each practice, record what failed and who will fix it. Update contact lists, roles and procedures whenever people, suppliers or systems change.

Frequently asked questions

Is a business continuity plan the same as a disaster recovery plan?

Show answer

Not quite. Continuity focuses on keeping essential work going, while recovery usually concerns restoring systems or facilities afterward. Many organizations write the two to fit together.

Who should help write the plan?

Show answer

Involve the people who run each essential function, plus leadership who can set risk tolerance. They know the dependencies that a single author would miss.

Does a small organization need one?

Show answer

Any organization with work it cannot afford to lose for long can benefit. A small plan covering key functions, contacts and records is better than none.

Where should I keep the plan?

Show answer

Store copies in more than one place, including an offline or printed version. If the plan lives only on the systems that fail, it cannot help you.