Reviewed & updated by WordNExcel Team — Updated November 10, 2026
A business continuity plan checklist helps you prepare your organisation to keep working, or recover quickly, when something goes wrong, from a power cut or IT outage to a fire, flood, supplier failure or widespread illness. On this page you can download five free business continuity plan checklist templates in Word: a business continuity plan checklist, a business impact analysis worksheet and an emergency contact list with a call tree, plus a disaster recovery runbook and a crisis communications plan.
Each file is a real, editable .docx document created for this page. The checklist uses tick boxes grouped into five clear stages, and the worksheet and contact list use ruled tables you can fill in on screen or by hand. The templates open in Word, Google Docs and LibreOffice Writer and print on one page each.
Free download: 5 templates (.docx). Works in Word and Google Docs. No sign-up needed.
What Is Business Continuity Planning?
Business continuity planning is the process of working out which activities your organisation cannot do without, what could stop them, and how you would keep them going or restore them within an acceptable time. The result is a business continuity plan: a short, practical document that tells people what to do, who to call and where to work when normal operations are disrupted.
Continuity planning is not only for large companies. Small businesses are often more vulnerable to disruption, because they depend on a few key people, one location or a single supplier. A simple plan, built with a checklist like the one on this page, can make the difference between a few days of disruption and losing customers for good.
Business Continuity vs. Disaster Recovery
The two terms are related but not the same. Disaster recovery usually refers to restoring IT systems and data after an outage or incident. Business continuity is broader: it covers people, premises, suppliers, communication and customers as well as technology. A complete plan includes both, which is why the checklist has a recovery section covering backups and systems alongside sections for staff, suppliers and communication.
Download the Free Business Continuity Plan Templates
The five Word files below take you from planning to analysis to the contact list you will need on the day.
Business Continuity Plan Checklist
The checklist is organised into five stages: scope and team, risk and impact, recovery, communication, and test and review. Each stage has tick boxes for the key steps, such as naming a plan owner, completing a risk assessment, testing backups, updating the staff call tree and holding a yearly exercise. A header records the organisation, owner and review date.

Business Impact Analysis Worksheet
The business impact analysis (BIA) worksheet helps each department list its critical activities and record the impact if each one stopped, the maximum tolerable downtime, the recovery time objective (RTO), the key people and the key systems or suppliers. The completed worksheet tells you what to protect first and how quickly it must come back.

Emergency Contact List and Call Tree
When an incident happens, you need phone numbers immediately. This sheet lists the continuity team by role, with name, mobile, an alternative contact and who each person calls next, followed by a table of external contacts such as emergency services, insurance, IT support, the landlord, the bank and key suppliers.

Disaster Recovery Runbook

A short, practical script for bringing a named system or service back after an outage or data loss. It states when to use the runbook, the first actions (page the owner, assess, decide whether to fail over), a three-step recovery procedure with owners, and where backups and vendor contacts live — without storing passwords in the file. A closing section captures the timeline and one improvement after the event. Keep the recovery time and recovery point objectives in the header so the person on call can see them at a glance.
Crisis Communications Plan

Sets out who speaks, through which channel, when something disrupts the organisation. A table assigns a spokesperson for staff, customers and the media, then lists first-hour actions: confirm facts, send an internal holding message, and prepare a short external statement if customers are affected. Message points cover what is known, what you are doing, what customers should do, and when the next update will come. After the event, file what was sent and note changes to the plan. Only named people speak to the press.
How to Build a Business Continuity Plan
- Name an owner. One person should be responsible for the plan, with a deputy.
- List critical activities. Use the BIA worksheet to record what each department must keep doing.
- Assess risks. Consider the events most likely to disrupt you, such as IT failure, loss of premises, loss of key staff and supplier problems.
- Set recovery targets. For each critical activity, decide how long you can manage without it.
- Plan workarounds. Decide where people will work, how data will be restored, which suppliers can step in and what manual processes can be used.
- Prepare communication. Build the call tree and draft short messages for staff, customers and suppliers.
- Write it down. Keep the plan short and practical, and store copies both online and offline.
- Test and update. Run a tabletop exercise at least once a year and update the plan after every test or real incident.
Understanding the Business Impact Analysis
The BIA is the heart of continuity planning. For each activity, ask what would happen if it stopped for an hour, a day or a week. Consider lost income, unhappy customers, legal or contractual penalties, safety issues and damage to your reputation. The maximum tolerable downtime is the longest the activity can be unavailable before the damage becomes unacceptable. The recovery time objective is the target time to restore it, which should be shorter than the maximum tolerable downtime.
Activities with the shortest recovery targets get the most attention in your plan. For example, a shop might decide that taking payments must be restored within hours, while updating the website can wait several days.
Common Risks to Plan For
- IT and power outages: loss of internet, servers, cloud services or electricity.
- Cyber incidents: ransomware, data breaches or account takeovers.
- Loss of premises: fire, flood, storm damage or being unable to access the building.
- Loss of key people: illness, resignation or several staff absent at once.
- Supplier failure: a key supplier unable to deliver goods or services.
- Transport disruption: staff or deliveries unable to reach the site.
You don’t need a separate plan for every risk. Most plans focus on the impact, such as “we cannot use the office” or “we have lost our IT systems”, because the response is similar whatever the cause.
Using the Call Tree
A call tree spreads the work of contacting people. The plan owner calls two or three people, each of them calls two or three more, and so on, until everyone has been reached. Record who calls whom in the “calls next” column. Keep personal mobile numbers as well as work numbers, because work phones and email may be unavailable during an incident. Check the list every three months, because phone numbers and staff change.
Testing Your Plan
A plan that has never been tested often fails when it is needed. The simplest test is a tabletop exercise: gather the continuity team for an hour, describe a scenario such as “the office is closed for a week after a flood” and walk through the plan step by step. Note what worked, what was missing and what was unclear, then update the plan. Test backups by actually restoring a file, and test the call tree by sending a message and checking how long it takes to reach everyone.
Keeping the Plan Current
Review the plan at least once a year and whenever something important changes, such as moving office, changing IT systems, adding a new product or losing a key supplier. Record the review date on the checklist header so everyone knows the plan is current. Store a printed copy away from the main office and a digital copy that can be reached from a phone.
Roles in the Continuity Team
Even a small organisation benefits from naming a few clear roles. The plan owner decides when to activate the plan and leads the response. The deputy takes over if the owner is unavailable. An IT lead restores systems and data, a facilities lead deals with the building, utilities and alternative premises, an HR lead looks after staff welfare and contact, and a communications lead handles messages to customers, suppliers and, if needed, the media. In a small business one person may hold two roles, but writing the roles down avoids confusion on the day.
Related Templates
You can also check these important templates like the family emergency plan templates for preparing households for emergencies, and the project schedule templates for planning the work of building and testing your continuity plan.
You may also like the checklist templates for creating other step-by-step checklists for your team.
Frequently Asked Questions
What is a business continuity plan checklist?
It is a list of the steps needed to build and maintain a business continuity plan, from naming an owner and assessing risks to testing and reviewing the plan.
What is the difference between RTO and maximum tolerable downtime?
Maximum tolerable downtime is the longest an activity can be unavailable before the damage is unacceptable. The recovery time objective is the target time to restore it, which should be shorter.
How often should a business continuity plan be tested?
At least once a year, and after any major change to the business or a real incident.
Do small businesses need a continuity plan?
Yes. Small businesses often depend on a few people, one location or one supplier, so even a short plan can greatly reduce the impact of a disruption.
Can I edit the templates in Google Docs?
Yes. Upload the .docx files to Google Drive and open them with Google Docs. The tables and tick boxes stay in place.
What is a call tree?
A call tree is a list showing who contacts whom during an incident, so messages reach everyone quickly without one person making every call.
