Business Continuity Plan: What It Is, 6 Steps and a Template
Author: Kevin Baur BSc
Published on
Contents
In many companies the plan for a bad day exists only in someone's head: whoever has been there longest knows whom to call when the server is down or the warehouse floods. That works until that person is the one who is missing. This guide explains what a business continuity plan contains, how the business impact analysis works and how to write a plan in six steps, with a template to copy and a check for the part most plans skip: key people.
What is a business continuity plan?
A common definition of business continuity is the capability of an organization to continue the delivery of products or services at predefined acceptable levels following a disruptive incident. A business continuity plan is the document that makes this concrete. It is written ahead of time and says which activities must continue, how quickly, by whom and with which resources. According to Wikipedia it is usually created with the input of key staff and stakeholders, and US government bodies call the same process continuity of operations planning (COOP).
The plan does not have to cover everything a company does. Under ISO 22301:2019, the international standard for business continuity management systems, organizations define their continuity objectives, the minimum acceptable level of their products and services and the maximum tolerable period of disruption. Everything else can wait.
Three terms are often mixed up:
| Plan | Question it answers | Scope |
|---|---|---|
| Business continuity plan | How do we keep the critical activities running and restore them? | People, processes, premises, suppliers, IT, communication |
| Disaster recovery plan | How do we restore systems and data? | IT systems, data, servers, software |
| Crisis management | Who decides and who talks to staff, customers and media in the first hours? | Emergency response and crisis communication |
| Succession planning | Who takes over a key role permanently? | Individual roles over months and years |
Business Wales, the Welsh government's business support service, puts the difference simply: a disaster recovery plan focuses on restoring IT systems, data, servers and software, while a business continuity plan covers wider organisational resilience, including people, processes, facilities and communications. Both should be aligned. If you are planning who will permanently fill a key role, that is succession planning, a related but separate task.
What a business continuity plan contains
There is no single mandatory format. The template that Business Wales recommends for small businesses is a good starting point because it fits on a few pages:
- Business details: main contact, date completed and next review date.
- Essential activities: what must continue during a disruption for the business to operate.
- Key people and responsibilities: who decides, who talks to customers, who coordinates recovery, each with a backup contact.
- Communication arrangements: primary and backup channels if the usual systems fail, plus a holding message for customers.
- Essential resources and workarounds: premises, equipment, IT systems, stock, vehicles and key documents.
- Suppliers and alternatives: critical suppliers, including cloud services, and backup options.
- Financial continuity: banking, payroll, invoicing and cash flow.
- Immediate response for the first hour: ensure staff safety, notify emergency services, assess impact, start communication and recovery.
The business impact analysis: RTO, RPO and MTD
The business impact analysis (BIA) is the core of every plan. It asks for each critical activity: how long can we live without it, and what does it need to run? Business Wales lists critical activities, maximum tolerable downtime, recovery time objectives and the resources required for recovery as its outputs. Three abbreviations come up again and again. INCIBE, Spain's national cybersecurity institute, explains them with a payroll example:
| Term | Meaning | Payroll example |
|---|---|---|
| RTO, recovery time objective | Time within which the activity must run again at an acceptable minimum level | 24 hours |
| MTD, maximum tolerable downtime | Time after which an outage causes serious damage to the company | 48 hours |
| RPO, recovery point objective | Maximum amount of data that may be lost without unacceptable consequences | 24 hours of data |
INCIBE also recommends gathering this information in meetings with department heads, coordinators and technical staff. That is where you find out which activities depend on which people, suppliers and systems. For the IT side, NIST, the US standards agency, publishes a business impact analysis template together with its contingency planning guide SP 800-34.
How to create a business continuity plan in 6 steps
The steps follow the planning process that Ready.gov, the US government's preparedness site, uses in its business continuity training.
1. Prepare
Name one person who owns the plan, get backing from management and decide the scope: the whole company or one site first. In a small company the owner and two or three people who know the daily business are enough.
2. Define objectives
Write down what the plan must achieve, for example: orders can be taken within one day after any disruption, and payroll is never late. These objectives decide later what counts as critical.
3. Identify and prioritize risks and impacts
List what could happen (fire, flood, IT outage, cyberattack, loss of a key supplier, absence of key staff) and run the business impact analysis for your critical activities. Sort them by recovery time: what has to work again within hours comes first.
4. Develop strategies
For each critical activity, decide how it continues: a second supplier, working from home, a backup site, cloud backups, a deputy who can do the task. Some activities need more than one strategy.
5. Define teams and tasks
Assign who does what in an incident, with a deputy for every role. A RACI matrix helps make clear who is responsible, who decides and who must be informed.
6. Test
A plan nobody has tried is a hypothesis. Start with a tabletop exercise: a small group walks through one scenario on paper and notes where the plan breaks. Wikipedia describes a biannual or annual maintenance cycle that includes checking contact data and specific training for critical individuals. Update the plan whenever people, suppliers or systems change.
Business continuity plan template
Copy the table and add one column per critical activity. The example is invented and shows the level of detail that helps in an emergency.
| Field | What to fill in | Example (invented, 20 person wholesaler) |
|---|---|---|
| Critical activity | What must keep running | Taking and shipping customer orders |
| RTO and MTD | Back within, damage after | 1 day, 3 days |
| Dependencies | Systems, suppliers, premises | Online shop, inventory software, carrier, warehouse |
| Key people and deputy | Who does it today, who steps in | Head of logistics, deputy warehouse lead |
| Knowledge only one person has | What is not written down anywhere | Special agreements with the carrier, workaround when the shop interface hangs |
| Workaround | How it continues during the disruption | Orders by phone and email, manual shipping list |
| First steps | What happens in the first hour | Inform customers, call the carrier, start the manual list |
| Owner and last review | Who keeps the row up to date | Operations manager, reviewed every six months |
The gap in most plans: key people
Business continuity plans are good at the visible things: backups, a second site, emergency numbers. Staff usually appear in two forms: as people to evacuate and as a contact list with backup contacts. What rarely appears is the knowledge that makes an activity work. A backup contact for the head of logistics helps little if nobody else knows the special agreements with the carrier.
In small teams one person often handles a function alone, and the risk does not only arise in disasters. A resignation, a long illness or retirement has the same effect on that activity, only without an alarm. Three questions belong in every business impact analysis:
- Who can do this besides the person doing it today? A skills matrix shows where the answer is "nobody".
- Where is it written down? Recurring tasks need process documentation that a deputy can follow.
- What is in this person's head only? Exceptions, contacts and experience are often tacit knowledge and need to be asked for actively.
For planned departures, an employee handover document closes the gap. The knowledge loss calculator gives a rough idea of what a departure without a handover could cost.
Common mistakes
- Too long to use: nobody reads 80 pages in an emergency. Keep the first hour on one page.
- Stored only on the server: if the server is down, so is the plan. Keep a copy offline and in a second location.
- Never tested: the first test should not be the real incident.
- Only IT: a disaster recovery plan alone does not tell anyone how orders, payroll or customer service continue.
Conclusion
A business continuity plan does not need to be thick. For every critical activity it answers: how long can we do without it, who steps in, what is the workaround and what happens in the first hour. Write it with the people who do the work, test it on paper and keep it current. And check whether the knowledge each activity needs lives in a document or only in one person's head.
Frequently asked questions
- What is a business continuity plan?
- A business continuity plan (BCP) is a document written in advance that describes how a company keeps its critical activities running during a disruption and restores them afterwards. It covers people, processes, premises, suppliers, IT and communication.
- What is the difference between a business continuity plan and a disaster recovery plan?
- A disaster recovery plan focuses on restoring IT systems, data, servers and software. A business continuity plan is broader and covers how the whole business keeps operating, including people, processes, facilities and communication. The disaster recovery plan is usually one part of it.
- What are the steps of business continuity planning?
- Ready.gov uses six steps: prepare, define the objectives, identify and prioritize risks and impacts, develop continuity strategies, define teams and tasks, and test the plan.
- What are RTO, RPO and MTD?
- The recovery time objective (RTO) is how quickly an activity must run again. The maximum tolerable downtime (MTD) is the point after which an outage causes serious damage. The recovery point objective (RPO) is how much data may be lost without unacceptable consequences.
- How often should a business continuity plan be tested?
- There is no single rule. A biannual or annual cycle is common, plus an update whenever key people, suppliers or systems change. A tabletop exercise on paper is a simple way to start.
Sources
- Business continuity planning (Ready.gov, US Department of Homeland Security)
- Business continuity and crisis management (Business Wales)
- Business continuity planning (Wikipedia)
- Steps for a business impact analysis with RTO, MTD and RPO (INCIBE, in Spanish)
- NIST SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems