Opens in a new tab
How mature is your risk management?
Take the Free AssessmentTake Assessment

Risk Management

Business Continuity Plan: How to Write One That Works, With an Example

A business continuity plan is a documented set of arrangements that keeps an organisation’s critical activities running, or restores them within agreed timescales, when a disruption hits. This guide shows how to write one that works: run a business impact analysis first, set recovery objectives in the context of each activity, follow seven steps to a tested plan, and keep it current, with a worked example to follow.

Keith Ricketts-Clew-GRC

Keith Ricketts

November 18, 2026
Time to read: 12 minutes

Summarize this article with:

ClaudeChatGPTGoogle GeminiPerplexityGrok
7
steps from business impact analysis to a tested, current plan
2
recovery objectives per system: time to return, and data that can be lost
3
systems behind one critical activity in the worked example
Didn't have time to read - TL;DR
3 key takeaways
1

Start with what matters, not with what could go wrong. A business impact analysis identifies the critical activities and the systems behind them before any plan is written.

2

Set recovery objectives in context. The same system can need to be back within an hour for one activity, and within three days for another.

3

A plan is only as good as its last test. Record tested results against targets, and close the gaps before an incident finds them.

The storm took out the power at 2am. By 2.20 the duty manager had found the business continuity plan: a Word document last updated three years ago. It named a standby site the company had since sold, a recovery target nobody had ever tested, and a contact list with three people who had left.

Nothing in the plan was wrong when it was written. It had simply been written once. The organisation moved on, the plan did not, and the night it was needed was the first time anyone had opened it in a year.

A business continuity plan should be the calm reference an organisation reaches for in the first minutes of a disruption. This guide covers what a business continuity plan is, how it differs from disaster recovery, how to run a business impact analysis, how to set recovery objectives, what to include, seven steps to write one, a worked example, how to test it, and how to keep it alive.

What Is a Business Continuity Plan?

A business continuity plan is a documented set of arrangements that keeps an organisation’s critical activities running, or restores them within agreed timescales, when a disruption hits. It sets out which activities matter most, what they depend on, how quickly each must be recovered, who does what, and how the plan is tested and kept current.

The plan sits within business continuity management: the wider cycle of analysis, planning, testing and review that keeps plans current. ISO 22301 is the international standard for business continuity management systems.

Business Continuity Plan vs Disaster Recovery Plan

The two are often confused, because they share a vocabulary.

Business continuity planDisaster recovery plan
FocusKeeping critical activities runningRestoring technology: systems, data and infrastructure
ScopePeople, premises, suppliers, processes and technologyIT systems and data
Usually owned byThe owners of critical activities, with the risk or resilience leadIT
The question it answersWhich activities must continue, and how quickly?How quickly does each system return, and with how much data?

The two work together. The disaster recovery plan restores the systems. The business continuity plan decides which systems matter, how fast, and what people do while they wait.

Start with a business impact analysis. A business impact analysis identifies the activities an organisation depends on and what happens if they stop. It comes first because recovery targets set before you know what is critical are guesses.

  • List the critical activities: the services and processes whose loss would cause serious harm to people, customers, operations or reputation.
  • Map what each activity relies on: systems, people, premises and suppliers.
  • Assess how the impact grows over time, in the first hour, the first day and the first week.
  • Record the longest disruption each activity can tolerate before the damage becomes unacceptable, often called the maximum tolerable period of disruption.
  • Give each activity an owner and a review date.

Australia’s official emergency management template uses the term “business impact assessment” for something different: a damage assessment after an emergency. Both are useful, but the analysis comes first, because it shapes the plan.

RTO vs RPO: Setting Recovery Objectives in Context

Every system behind a critical activity needs two recovery objectives.

Recovery time objective (RTO)Recovery point objective (RPO)
The questionHow quickly must the system be back?How much data can be lost?
Measured asTime from the disruption to recoveryTime between the last good copy of the data and the disruption
ExampleBack within 8 hoursNo more than 1 hour of data lost
What drives itHow fast the harm grows when the activity stopsHow hard it is to recreate or re-enter lost data

Most plans set RTO and RPO once for each system. That is the most common mistake. The right target depends on the activity the system supports. A customer contact platform may need to be back within an hour when it handles calls during a supply interruption, while billing can wait three days. Set each objective in the context of each critical activity, and the plan puts its effort where it matters.

Key distinction

RTO is about time: how fast the system must return. RPO is about data: how much of it you can afford to lose.

What to Include in a Business Continuity Plan

A complete plan has ten sections.

SectionWhat it covers
1. Scope and objectivesWhat the plan covers, and what it is for
2. Roles and contactsWho leads, who decides and how to reach them, including deputies
3. Critical activitiesThe activities in scope, their owners and the longest disruption each can tolerate
4. Systems and dependenciesThe systems, people, premises and suppliers behind each activity, with their RTO and RPO
5. ActivationWhat triggers the plan, and who invokes it
6. Immediate actionsWhat happens in the first minutes and hours, by role
7. Strategic recoveryHow each activity is restored over the following days and weeks
8. CommunicationsStaff, customers, suppliers, regulators and the public
9. TestingHow and when the plan is exercised, and the last tested results
10. Review and approvalWho approves the plan, who owns it, and when it is next reviewed

Keep immediate actions separate from strategic recovery. In the first ten minutes, people need a short card that tells them what to do, not a forty-page document.

How to Write a Business Continuity Plan in Seven Steps

1. Run a business impact analysis

Identify the critical activities, what they depend on and how fast the harm grows, as set out above. Everything else in the plan follows from it.

2. Set recovery objectives for each system, per activity

Give every system behind every critical activity an RTO and an RPO, set in the context of that activity rather than once for the system.

3. Connect the plan to your risks and controls

Each critical activity faces risks already in the risk register, and depends on controls already assessed. Link them, so the plan answers the risks the organisation has accepted, and a change to a risk or control shows up in the plan. How the register should be structured is covered in how to build a risk register.

4. Write immediate and strategic actions, with owners

Write the first actions as short, role-specific cards, and the longer recovery as a sequence with an owner for each step. Name deputies for every role.

5. Approve and activate the plan

Take the plan through formal approval, so it carries authority. Then make sure the right people can reach it, including when systems are down: keep copies that work offline.

6. Test it and record the results

Exercise the plan, time each recovery, and record the result against the target. A gap found in a test is a finding. A gap found in an incident is a failure.

7. Keep it current

Review the plan on a fixed cycle, and whenever systems, suppliers, people or risks change. After any real incident, update the plan with what was learned, using the same discipline as an incident report.

A gap found in a test is a finding. A gap found in an incident is a failure.

Who Owns a Business Continuity Plan?

Continuity is not owned by one team, and plans fail when everyone assumes someone else has it.

  • The board or executive sets the organisation’s tolerance for disruption, and approves the plan.
  • An executive sponsor is accountable for continuity across the organisation, and chairs the response when the plan is activated.
  • Each critical activity has an owner, who keeps its part of the analysis and the plan current.
  • The risk or resilience lead runs the method, the testing programme and the reporting.
  • IT owns the recovery of systems, against the objectives the business has set.
  • Internal audit gives independent assurance that the plans exist, are tested and are kept up to date.

Business Continuity Plan Example

Here is the method applied to one critical activity at a UK water utility: keeping drinking water flowing to customers.

SystemRTORPOLast tested resultStatus
Telemetry and control system1 hour5 minutesRecovered in 3 hours in the March exerciseGap: 2 hours over target
Laboratory information system24 hours4 hoursRecovered in 18 hours, with 2 hours of data lostMeets target
Maintenance scheduling system48 hours1 dayRecovered in 30 hours, with no data lostMeets target

The plan shows one gap before any storm does: the control system took three times its target to recover in the last exercise. The fix goes in as an action with an owner and a date: a standby control server at a second site, and a repeat test within the quarter. Until the repeat test passes, the plan states the gap plainly.

The immediate action card for the treatment works operator is three lines long: switch the affected works to manual operation, call the duty incident manager, and alert the water quality team. Everything else belongs in strategic recovery.

How to Test a Business Continuity Plan

Testing turns a plan from a document into a capability. There are three common levels.

  • A walkthrough is a desk check, where the plan’s owners read it together and check the contacts, roles and steps.
  • A tabletop exercise talks decision-makers through a realistic scenario, to test judgement and communication.
  • A live recovery test actually restores a system or relocates a team, and times the result against the RTO and RPO.

Record the result of every test against its target, not just the fact that a test happened. A test that recovered a system in three hours against a one-hour target is the most valuable finding the plan will ever produce.

Testing is also a duty for some organisations. In the UK, the government’s exercise guidance under the Civil Contingencies Act 2004 sets out that local authorities and other Category 1 responders must maintain business continuity arrangements, exercise them and train their staff. In Australia, the government’s emergency management guidance advises businesses to rehearse their plans with their staff.

Business Continuity Management: The Cycle Around the Plan

A plan on its own goes stale. Business continuity management keeps it alive through a repeating cycle: analyse what matters, choose recovery strategies, write the plan, exercise it, and review it, then start again as the organisation changes. ISO 22301 builds its requirements around the same idea of continual improvement.

The cycle is also where continuity meets risk management. The analysis draws on the risks the organisation already manages, exercises test the controls it relies on, and the gaps feed back into the risk register as actions with owners and dates.

From a Document to a Living Plan

Most business continuity plans start life as a document, and that is where their problems begin. A document copies information that already lives elsewhere: the risks are in the register, the controls are in the assurance programme, the incidents are in the incident log and the contacts are in the HR system. The day any of them changes, the document is out of date, and nobody is told.

A living plan works the other way round. Instead of copying, it connects.

  • The business impact analysis becomes the plan, so critical activities, systems and recovery objectives are entered once.
  • The plan links to the risks it answers and the controls it depends on, so a change in the register shows up in the plan.
  • Every test result is recorded against its target, and any gap is flagged automatically.
  • An incident record opens the right plan, with the affected activities, recovery steps and contacts.
  • Role-specific action cards and a full plan can be exported, so the plan still works when systems are down.
  • Review reminders and a full audit trail keep the plan current, and a programme-level view shows which plans are due for review or carry open gaps.

That is how business continuity planning software such as Clew’s BCP module works. The plan lives in the same platform as the risks, controls and incidents it depends on, so the plan and the register never drift apart.

Common Business Continuity Planning Mistakes

  • The plan lives in a document nobody can find. If people cannot reach it in the first ten minutes, it does not exist.
  • Recovery targets are set once and never tested. An untested target is an assumption.
  • Objectives are set per system, not per activity. The same system can be urgent for one activity and patient for another.
  • The plan is disconnected from the risk register. It answers risks the organisation stopped worrying about, and misses the ones it accepted last month.
  • Nobody owns the critical activities. If nobody owns the activity, nobody owns the plan, and review becomes an annual document refresh.
  • The plan only works when the systems are up. Keep copies and action cards that work offline.

Knowing a risk exists is not the same as knowing what happens when it materialises. The continuity plan answers that second question, which is why it belongs on the traceable link from an organisation’s objectives through its risks, controls, actions and assurance to the indicators that show whether it is performing.

Frequently Asked Questions

A business continuity plan is a documented set of arrangements that keeps an organisation’s critical activities running, or restores them within agreed timescales, during a disruption. It covers critical activities, their dependencies, recovery objectives, roles, actions, testing and review.

Scope and objectives, roles and contacts, critical activities, the systems and dependencies behind them with recovery objectives, activation triggers, immediate actions, strategic recovery, communications, testing and the last tested results, and review and approval.

The recovery time objective (RTO) is how quickly a system must be back after a disruption. The recovery point objective (RPO) is how much data can be lost, measured as the time between the last good copy of the data and the disruption.

A business impact analysis identifies an organisation’s critical activities, what they depend on, how the impact of losing them grows over time, and how long each can be disrupted before the damage becomes unacceptable. It comes before the plan, because it decides what the plan must protect.

At least once a year, and whenever systems, suppliers, people or risks change significantly. Critical systems often justify more frequent recovery tests. Every test should record the result against its target.

Disaster recovery restores technology: systems, data and infrastructure. Business continuity keeps critical activities running, which depends on people, premises, suppliers and processes as well as technology. The disaster recovery plan is one part of business continuity.

Put your plan where your risks are. Clew is a risk and assurance platform built around the Golden Thread. Its BCP module holds business continuity plans in the same platform as your risks, controls and incidents, from the business impact analysis through to tested recovery results and role-specific action cards. It sits alongside the risk management software your team already uses. Risk and assurance teams in government, healthcare, construction, infrastructure and utilities, mining and resources, and transport use Clew to keep their risks, controls and indicators connected to the objectives they protect. See it working with your own plans: request a demo of Clew, or explore Clew’s business continuity planning software.

Related Resources

Keith Ricketts-Clew Risk Software

Meet the author

Keith Ricketts

VP Of Marketing

25 years with global software vendors in Cyber Security, Risk and ERP. Blends strategic marketing, agility and a proven record of results.
Connect on LinkedIn

In this article

How mature is your risk management?

Take the free assessment and get a personalised report in minutes.
Take the assessment