What is a business continuity plan?
A business continuity plan (often shortened to BCP) is a written document that sets out how your business keeps its essential operations running during and after a disruption. It answers a simple question in advance: if something important breaks tomorrow, what do we do, in what order, and who does it?
Business continuity is broader than disaster recovery. Disaster recovery is the IT-focused part, restoring servers, systems and data. Business continuity planning covers the whole business: people, communications, suppliers, premises and the practical steps that keep you trading. You need both, but the continuity plan is the bigger picture the rest hangs from.
Why small businesses need business continuity planning
There is a persistent myth that continuity planning is only for large corporations with compliance teams. The opposite is true. A big company has redundancy: layers of staff, documented processes and someone to cover every role. A small business often runs on a handful of people, and sometimes on one person who holds the passwords, the supplier relationships and the knowledge in their head. That is a single point of failure, and it is exactly what a business continuity plan is designed to remove.
The cost of not planning is rarely just the downtime itself. It is the scramble: the hours lost working out who to call, the customer trust spent while you are dark, the domain that lapses because the renewal went to an inbox nobody reads. A short, honest plan turns a crisis into a checklist.
What a business continuity plan should include
A good BCP does not need to be long, but it should cover these core components:
- Critical functions: the handful of things your business absolutely must keep doing.
- Business impact analysis: what breaks if each function stops, and how quickly it hurts.
- Risks and threats: the disruptions most likely to affect you (outage, cyber attack, supplier failure, illness, loss of premises).
- Roles and responsibilities: who does what when the plan is triggered, with named people and deputies.
- Communication plan: how you reach staff, customers and suppliers, and who speaks for the business.
- IT and data recovery: backups, how to restore them, and the systems you cannot operate without.
- Access and key-person continuity: how trusted people get into critical systems and accounts if the person who normally holds them is unavailable.
- Suppliers and dependencies: your critical third parties and the fallback if one fails.
- Testing and review: when you will rehearse the plan and keep it current.
How to write your business continuity plan, step by step
- List your critical functions. Ignore everything that can wait a week; focus on what must keep running in the first 24 to 72 hours.
- Assess the impact. For each function, note what stops, who is affected, and how fast it becomes serious. This is your business impact analysis.
- Set recovery objectives. Decide how quickly each function must be back (your recovery time), and how much data you could afford to lose (your recovery point).
- Assign roles. Name a person and a deputy for each responsibility, so nothing depends on one individual being reachable.
- Document the procedures. Write the actual steps in plain language, the way you would explain them to someone covering at short notice.
- Plan communications. Decide in advance how you will contact people and what you will say, so you are not drafting it mid-crisis.
- Secure access to systems and credentials. Make sure the right people can get into the accounts, domains and servers that run the business, even if the usual keyholder is not around.
- Test and review. Walk through the plan at least once a year, and after any big change. Fix what does not work.
The gap most plans miss: key-person and access risk
Most continuity templates cover fire, flood and IT failure but skip the quiet risk that sinks small businesses: what happens to the passwords, domains, servers and accounts if the one person who holds them is suddenly unavailable? A plan is only as good as the ability to actually get in. If the recovery step is "log in and restore the backups" but nobody else has the login, the plan fails at the first line.
This is key-person risk, and it is exactly the problem VigilVault was built to solve. It keeps your critical credentials in an encrypted vault, monitors the domains and certificates that quietly expire, and provides a legacy handover: you nominate trusted people who can be granted controlled, time-limited access if you become unreachable, entirely on your terms. You can even generate a one-page handover document to attach to the plan below, so the access step is covered without writing a single password into your BCP.
A free business continuity plan template
Use this as the skeleton of your plan. Copy it, print it, and fill in each section. Keep it short and real; a two-page plan people actually follow beats a fifty-page one nobody reads.
Business Continuity Plan, [company name]
Owner: [name] · Last reviewed: [date] · Next review: [date]
1. Critical functions
The functions we must keep running, and how quickly each must recover.
2. Business impact analysis
For each function: what stops, who is affected, how fast it hurts.
3. Key risks
The disruptions most likely to affect us, and how we reduce each.
4. Roles and responsibilities
Who leads the response, plus a named deputy for each role.
5. Communication plan
How we contact staff, customers and suppliers, and who speaks for us.
6. IT and data recovery
Critical systems, where the backups are, and how to restore them.
7. Access and key-person continuity
How trusted people get into critical accounts, domains and servers if a keyholder is unavailable. (See the attached VigilVault handover document.)
8. Suppliers and dependencies
Critical third parties and our fallback if one fails.
9. Testing and review
When we rehearse this plan and how we keep it current.
Keeping your plan current
A business continuity plan is not a document you write once and file away. Review it at least once a year, and again whenever something material changes: new systems, new staff, a new supplier, a move. Rehearse it so the gaps show up in a drill, not in a real incident. An out-of-date plan is dangerous precisely because people trust it.
Frequently asked questions
What is a business continuity plan?
A business continuity plan (BCP) is a written document that sets out how a business keeps its essential operations running during and after a disruption, such as an outage, a cyber incident, the loss of a supplier, or a key person becoming unavailable.
What should a small business continuity plan include?
At a minimum: your critical functions and their recovery priorities, the main risks you face, who is responsible for what, how you will communicate, how you recover IT and data, how trusted people can access critical systems and credentials if a key person is unavailable, and a schedule for testing and review.
What is the difference between business continuity and disaster recovery?
Business continuity is the wider plan for keeping the whole business running. Disaster recovery is a subset focused specifically on restoring IT systems and data. You need both, but continuity is the bigger picture.
How often should you review a business continuity plan?
Review it at least once a year, and again whenever something material changes, such as new systems, staff, suppliers, or premises. A plan that is out of date can be worse than no plan, because people trust it.
VigilVault covers the part of continuity planning most tools ignore: making sure the right people can reach your critical systems and credentials when it matters. Start free, see everything it does, or read our trust centre.