Twenty free business continuity plan templates in Microsoft Word. A continuity plan answers one question: when something stops working, what keeps the business running and for how long can it cope? Two numbers do most of that work, and most plans never state them.
- Templates20 layouts
- FormatMicrosoft Word
- Opens inWord, Google Docs, LibreOffice
- CostFree, no signup
Continuity, recovery, or incident response?
Three documents that overlap and are not the same. Larger organisations keep all three; smaller ones often fold them into one, which is fine as long as each job is covered.
| Document | Answers |
|---|---|
| Business continuity plan this page |
How does the business keep operating while something is broken? Covers people, premises, suppliers and processes, not only technology. |
| Disaster recovery plan | How do we get the IT systems and data back? A technical subset of continuity. |
| Incident or crisis response | What happens in the first hour? Who is called, who decides, who speaks to customers and press. |
The templates
Twenty layouts, from short plans suitable for a small business through to fuller documents with impact analysis tables, recovery procedures and contact appendices.
Start with a business impact analysis
This is the foundation, and it is routinely misunderstood as market or stakeholder analysis. It is neither. A business impact analysis asks, process by process: if this stopped, what would happen, and how quickly would it hurt?
Work through what your business actually does — taking orders, delivering, invoicing, paying staff, supporting customers — and for each one record:
- What it depends on. Which systems, which people, which suppliers, which premises.
- What happens if it stops — lost revenue, missed contractual obligations, regulatory consequences, reputational damage.
- How long before it hurts. Some processes can pause for a week unnoticed. Others cause damage within hours. This difference is the whole point of the exercise.
- What the workaround is, if any. Manual processing, a second supplier, another site.
The output is a ranked list of what genuinely matters. Without it, a continuity plan treats everything as equally urgent, which in an actual incident means nothing is prioritised.
RTO and RPO: the two numbers
These come straight out of the impact analysis, and a plan that does not state them is not really a plan.
- Recovery time objective (RTO) — how quickly a process must be working again. “Order processing must be back within four hours.” It drives what you invest in: a four-hour RTO and a two-week RTO call for completely different arrangements.
- Recovery point objective (RPO) — how much data you can afford to lose, measured in time. This one catches people out. If you back up once a night, your RPO is 24 hours — an incident at four in the afternoon loses everything since the previous evening. If losing a day’s orders is unacceptable, nightly backups are not sufficient, regardless of how reliable they are.
Set both per process rather than for the business as a whole. Payroll and the customer-facing website rarely deserve the same numbers.
Find the single points of failure
Most real disruptions are mundane rather than dramatic. The useful question is what has no backup.
- One person. Who knows the thing nobody else knows? Who holds passwords, supplier relationships, or the undocumented process? Key-person dependency is the most common and most ignored continuity risk.
- One supplier. Particularly for something hard to replace quickly, and especially where your supplier themselves has a single point of failure.
- One site. If the building is inaccessible — fire, flood, a road closure — can anyone work?
- One system, one account. A platform that holds your customer data, a domain registered to one personal email, a payment account only one person can access.
The plan has to be reachable when everything is down
The single most common failure in continuity planning: the plan is stored on the file server, in the system, or on the network that the incident has just taken out. Nobody can open the document that tells them what to do.
Keep copies where they survive the thing you are planning for:
- Printed, with the key people, at home as well as at work.
- Offline on a phone — a downloaded PDF, not a link to a cloud folder that needs a login you cannot reach.
- In a separate cloud account from your main systems, where that is practical.
The same applies to your contact list. A call tree stored only in a system you cannot log into is not a call tree. Keep names, roles, mobile numbers and an alternative contact for each person, printed and current — and include suppliers, your insurer, your bank and your IT support, not only staff.
Test it, or it is fiction
-
Run a tabletop exercise
Gather the people named in the plan for an hour, describe a scenario — the office is inaccessible on Monday morning, or the main system is down for two days — and work through it from the document. No systems touched, no cost beyond the hour.
-
Write down what did not work
Every first run surfaces the same things: out-of-date phone numbers, a procedure that assumes someone who has left, a password nobody has, a step that depends on something also broken.
-
Actually test the restore
Backups are the classic case of something assumed to work. Restore something real, to somewhere real, and time it. Discovering during an incident that the backup is incomplete or the restore takes two days is the expensive version of this lesson.
-
Review at least annually
And after any significant change — new premises, new system, people joining or leaving. A plan written three years ago and never revisited is usually wrong in the details that matter most.
General information, not professional advice. Continuity requirements differ by sector, and regulated industries often have specific obligations. ISO 22301 is the international standard for business continuity management if you need a formal framework. For regulated or high-risk operations, take specialist advice rather than relying on a template.
Common questions
How long should a continuity plan be?
Short enough to be used under pressure. For a small business, ten to twenty pages with the contact list and immediate actions at the front. Detail belongs in appendices, not in the part someone reads at seven in the morning.
Does a small business really need one?
A short one, yes — small businesses have less resilience, not more. Even a few pages covering key contacts, critical processes and where the backups are puts you ahead of most.
Who should own it?
One named person, with a named deputy, since the owner may be unavailable during the incident. Everyone named in the plan should have read it before it is needed.
What is the difference between RTO and RPO?
RTO is how fast you must be running again. RPO is how much data you can afford to lose. A four-hour RTO with a 24-hour RPO means you are back quickly but have lost a day’s work.
Do I need Microsoft Word?
No. Upload the file to Google Docs or open it in LibreOffice. Keep an offline copy regardless — a plan that needs an internet connection to read is a plan with a built-in flaw.
Can I use these commercially?
Yes, including for client work. You may not resell or redistribute the template files themselves. See our Terms of Use.































Pingback: Training Budget Templates for Courses, Cohorts and Compliance
Pingback: Checklist Templates and How to Make One That Works
Comments are closed.