A business continuity plan helps a small business keep essential work moving when an office, system, supplier, employee, or communication channel becomes unavailable. This practical business continuity plan template shows what to record, how to assign recovery priorities, and how to test the plan before an operational disruption occurs.
Overview
Small business continuity planning is not about predicting every emergency. It is about deciding in advance which activities matter most, who owns them, what resources they depend on, and what the business will do if normal operations are interrupted.
A useful operational continuity plan should be short enough to use under pressure and detailed enough to guide a person who is not normally responsible for the work. Keep the main plan in an accessible format, store it somewhere separate from the primary workplace or system, and make sure relevant people know where to find it.
Use the following sections as an editable business continuity worksheet:
- Plan ownership: Record the person responsible for maintaining the plan, approving changes, and coordinating reviews.
- Critical-process inventory: List the activities that must continue or resume first, such as customer support, order fulfilment, payroll preparation, invoicing, production, or access to essential records.
- Risk and impact assessment: Note what could interrupt each process, the likely consequences, and the longest acceptable period of downtime.
- Recovery priorities: Assign an order for restoring systems, people, facilities, suppliers, and customer-facing services.
- Emergency contacts: Include internal decision-makers, staff contacts, key customers, suppliers, technology providers, building contacts, and professional advisers where appropriate.
- Communication plan: Define how the team will communicate if email, phones, messaging tools, or the normal workplace are unavailable.
- Workaround instructions: Describe temporary methods for completing essential tasks, including manual records, alternate locations, remote access, or substitute suppliers.
- Review and testing log: Record the date of each test, what was checked, what failed, and who owns each follow-up action.
For processes that are difficult to explain in a continuity plan, link to a current business process mapping template or the relevant SOP. A continuity plan should point people toward dependable instructions rather than reproduce every routine procedure.
Checklist by scenario
1. Loss of premises or physical access
- Identify which activities require the usual site and which can be performed remotely or from another location.
- List the equipment, files, keys, stock, and records that are essential to restart operations.
- Define who can authorise temporary premises, equipment purchases, or changes to working arrangements.
- Confirm that staff know how to work securely away from the usual workplace.
- Record how customers, delivery partners, and suppliers will be told about temporary changes.
2. Technology outage or cybersecurity incident
- List core systems, account owners, administrators, vendors, and recovery contacts.
- Record where backups are stored, how often they are created, and who can restore them.
- Separate backup access from ordinary user access where practical, so a compromised account does not expose every recovery option.
- Define an approved fallback for order records, customer enquiries, payments, scheduling, and internal communication.
- State who decides whether systems should remain offline while an issue is investigated.
- Keep a paper or offline copy of essential contacts and first-response steps.
The plan should not include exposed passwords or unnecessary sensitive information. Instead, explain how an authorised person can retrieve credentials or contact the responsible technology provider.
3. Loss of a key person
- Identify roles where only one person understands a critical process, system, customer relationship, or approval step.
- Name a backup owner for each role and provide enough documentation for a handover.
- Record approval limits, recurring deadlines, important contacts, and current work in progress.
- Use a RACI matrix template to distinguish who is responsible, accountable, consulted, and informed.
- Review access rights when responsibilities change, particularly after staff departures or extended absences.
4. Supplier or service-provider failure
- List vendors that support critical products, systems, payments, delivery, communications, or compliance work.
- Record the service or item provided, expected lead time, contact route, and available alternative.
- Identify dependencies that may not be obvious, such as a payment processor, cloud platform, courier, or specialist subcontractor.
- Define the point at which the business will activate a substitute supplier or customer workaround.
- Review important vendors using a vendor evaluation scorecard so risk information remains current.
5. Cash-flow interruption
- Identify the payments that must continue, including payroll, essential suppliers, tax-related obligations, rent, and critical software.
- List expected customer receipts and the person responsible for monitoring them.
- Define a short-term approval process for deferring, prioritising, or renegotiating non-essential spending.
- Use a cash flow forecast template to understand upcoming commitments and available runway.
- Keep customer and invoice records accessible if the main accounting system is unavailable.
What to double-check
Before approving the plan, test whether another competent team member could use it without relying on informal knowledge. Check each critical process against these questions:
- What must happen first? Write the first action in plain language, not simply “follow the procedure.”
- Who can make the decision? Name a primary owner and a backup rather than assigning the task to a department.
- What is the acceptable delay? Record when a process becomes materially harmful to the business if it has not resumed.
- What does the owner need? Include systems, documents, equipment, permissions, supplier details, and customer information.
- What is the fallback? Describe a workable temporary method, even if it is slower or less convenient.
- How will people know the plan is active? Establish a clear internal message and a channel for updates.
- How will the business return to normal? Include a handback step for reconciling manual records, checking transactions, and closing temporary arrangements.
Backups also need to be checked, not merely listed. Confirm that files can be located, restored, opened, and used by an authorised person. A backup that exists but cannot be recovered within the required timeframe does not complete the recovery plan.
Check remote-work procedures for practical details: device availability, secure access, communication channels, document sharing, customer privacy, and a method for recording decisions. If work is transferred between people, connect the plan to a project handoff template or another documented handover process.
Common mistakes
- Making the plan too broad: A long list of every imaginable risk can obscure the few processes that require immediate attention. Start with critical services and expand gradually.
- Assigning ownership to a group: “Operations” cannot make a decision unless a specific person is accountable. Name a lead and a deputy.
- Ignoring third-party dependencies: A business may have a strong internal procedure but still depend on one payment, hosting, logistics, or communications provider.
- Keeping the plan in one location: If the only copy is on an inaccessible computer or in a locked office, it may not be available when needed.
- Documenting recovery without prevention: Record basic safeguards too, such as access reviews, backup routines, supplier alternatives, and cross-training.
- Failing to test the contact list: People change roles, phone numbers change, and vendor contacts move. An untested list quickly becomes unreliable.
- Forgetting reconciliation: Manual workarounds can create duplicate orders, missed invoices, or inconsistent customer records. Add a clear return-to-normal process.
When to revisit
Review the business continuity plan at least before major seasonal planning cycles and whenever workflows or tools change. A quarterly review is a practical rhythm for many small businesses, but the right interval depends on how quickly the business, its systems, and its dependencies change.
Update the plan immediately after a disruption, near miss, failed test, or significant change to systems, locations, staff, suppliers, products, or recovery priorities. Also revisit it when onboarding a critical vendor, changing payment or accounting tools, introducing remote work, moving premises, or assigning a new process owner.
Use this action sequence:
- Choose one critical process and one disruption scenario to test.
- Contact the listed owners and confirm their responsibilities and current contact details.
- Walk through the first hour of the response, including communication and decision-making.
- Test one backup, alternate system, supplier route, or manual workaround.
- Record gaps, assign owners, and set due dates for corrections.
- Update the document, label the new version, and tell affected staff what changed.
A continuity plan becomes useful through small, repeated checks. Keep the document linked to current SOPs, process maps, financial planning, and team workflows, then return to it whenever the underlying business inputs change.