Here’s a free business continuity plan (BCP) template you can copy and fill in 60–90 minutes: capture your critical functions, RTO/RPO, roles and alternates, key dependencies, activation triggers, communication steps, and recovery procedures, then test with a short tabletop. This business continuity plan bcp template keeps the focus on the decisions that reduce downtime, not paperwork.
For a 25–100 person company, expect 6–12 total hours to finalize with the team; most organizations can do this at no cost using Word or Google Docs/Sheets unless you choose paid tooling. Start with the one-page skeleton below, gather owners for a quick working session, and schedule a 90-minute tabletop to validate the plan this week.

Business continuity plan BCP template (free) and quick start
Copy this one-page template into Word or Google Docs. Fill the first three sections (Critical Functions, RTO/RPO, and Roles) before anything else. That alone gives you a working BCP draft.
Title: Business Continuity Plan (BCP) — Version, Date, Owner Scope: Business unit(s) covered, sites, systems 1) Critical functions (Top 5–10) - Function name: - Why critical (impact if unavailable): - RTO (maximum acceptable downtime): - RPO (maximum acceptable data loss): - Dependencies (people, apps, sites, vendors): - Manual workaround available? Summary: 2) Roles and contacts - Continuity lead (primary/alternate): Name, mobile, email - Incident manager (primary/alternate): - Function owners (primary/alternate): - IT lead / Facilities lead / HR lead: - 24/7 contact list: name, role, phone, email 3) Activation triggers and escalation - Triggers (e.g., facility loss > 4 hours, critical app outage > RTO): - Who declares BCP activation: - Escalation path (level 1..3): 4) Communications plan - Internal channels (email, Slack, SMS): - External (customers, partners, regulators): - Pre-approved scripts: internal, customer-facing - Spokesperson and backup: 5) Recovery procedures - First 60 minutes checklist: - First 24 hours checklist: - Manual workarounds (how-to and limits): - DR/backup reference links: 6) Logistics and resources - Alternate workspace / remote options: - Equipment and access needs: - Vendor/SLA notes (contacts, escalation): 7) Testing, training, and maintenance - Tabletop cadence: - Technical test cadence (restore/access): - Change log (owner, date, summary):
Quick start order that works: 1) list top functions, 2) set RTO/RPO for each, 3) name owners and alternates, 4) write one activation trigger and one customer message, 5) outline the first-24-hours actions.
Time and cost estimate by size:
- Micro (≤25 staff): 3–6 hours total, zero software spend. One facilitator plus 2–3 owners.
- SMB (25–250): 6–12 hours total; optional spend on notification tools if needed.
- Mid-market (250–1000): 15–30 hours across teams; consider a notification app and document control.
If you prefer a longer checklist format, see our internal resource Your business continuity planning checklist: a practical playbook and a team-friendly primer Business continuity planning for busy managers and small teams.
What is a BCP and how it protects your business
A business continuity plan explains how your organization keeps critical work going during disruptions such as facility loss, key system outages, cyber incidents, severe weather, or supplier failures. The goal is continuity of operations, not perfection. A good BCP shrinks decision time, limits downtime, and provides clear communications.
Common disruption scenarios include: cloud or network outages, payment gateway failure, warehouse unavailability, loss of a key vendor, or a region-wide event that keeps staff from the office. With a BCP, leaders can quickly decide whether to activate the plan, shift to manual workarounds, notify customers, and prioritize recovery steps by impact and RTO.
Outcomes of a solid BCP include: fewer ad hoc decisions, shorter outages, consistent messaging to customers, simpler handoffs between teams, and easier audits. If your company is pursuing certifications or vendor approvals, a BCP also demonstrates basic operational discipline. For broader operational discipline beyond continuity, see Build a business operating system: playbooks, tools, and habits.
Core elements your BCP must include
These components are the backbone of a practical plan. They mirror what auditors and customers expect and, more importantly, what teams need during an actual event.
- Risk assessment and business impact analysis (BIA): Identify top risks (facility, technology, people, vendor) and quantify impacts by dollars, customers, and legal exposure. BIA outputs your list of critical functions with business impacts.
- Recovery objectives per function: Define the Recovery Time Objective (RTO) and Recovery Point Objective (RPO) for each critical function. RTO is how long you can operate without the function before significant impact; RPO is how much data you can afford to lose.
- Roles and responsibilities: Name a continuity lead, incident manager, function owners, and alternates. Keep a 24/7 contact list. If a role is single-threaded, add an alternate.
- Activation criteria and escalation: Write specific triggers (e.g., core ordering app down longer than RTO) and an escalation ladder. Clarify who has authority to activate and de-activate the plan.
- Communication plan: Internal channels, customer notices, supplier coordination, and media handling. Include pre-approved scripts to avoid drafting under stress.
- Recovery procedures and manual workarounds: First-60-minutes actions, system recovery steps, and how to run the process manually while systems are down. Link to your DR guides where relevant.
- Testing, training, maintenance: A realistic cadence to keep the plan alive: tabletop exercises, restore-from-backup tests, and documented updates with version control.
Searchers often ask: What are the four R’s of business continuity? A practical framing is Resilience (reduce single points of failure), Response (activate and communicate), Recovery (restore services to RTO/RPO), and Review (capture lessons and update). Another common question: What are the five components of a BCP? Many list BIA, strategies, plan development, testing, and maintenance. The template above covers these without jargon.
Step-by-step: fill the template in 60 minutes
Block one hour with the people who own work that customers notice and care about. Use these prompts to move fast and get a working draft.
- List top 5–10 critical functions: Examples: order processing, customer support, payroll, billing, shipping, and core IT services. For each, note why it’s critical and the top dependency (apps, sites, people, vendors).
- Set RTO/RPO per function: Use practical ranges. For online orders, RTO might be 4 hours and RPO 1 hour; for payroll, RTO 24–48 hours and RPO 24 hours may be acceptable. Don’t overpromise.
- Assign owners and alternates: Name a primary and backup for each critical function and for incident management. Add mobile numbers and personal emails for off-hours.
- Write activation triggers and first-24-hours actions: Write one trigger like “Ordering app unavailable beyond 4 hours” and one immediate action list (see example below). Define who activates and who informs customers.
- Add comms checklist and contact details: Include a short internal update template and a customer note. List the channels (email, SMS, status page) and who pushes messages.
- Store and share: Save the BCP in your shared drive with controlled access. Keep a PDF export; print one copy in each site’s go-binder if you still use physical binders.
To see how this aligns with broader risk work, check our guide Overcome challenges with risk mitigation strategies.
Testing, training, and maintenance that actually work
A plan that never gets exercised won’t help during a disruption. Keep testing lightweight and focused on decision-making, not theatrics.
90-minute tabletop agenda (this week):
- Introductions and roles (5 minutes)
- Scenario brief (5): Cloud ordering app down for 6 hours across all regions
- Activation decision (10): Who declares, why, and what threshold
- First 60 minutes actions (20): Assign tasks, start workarounds, start communications
- Customer communication (15): Draft and read the internal and customer messages
- Recovery path (15): How to restore, what to check, when to roll back workarounds
- Dependencies and vendor coordination (10): What to escalate to which vendor
- Debrief and gaps (10): What slowed you down, what to fix in the plan
Pass/fail criteria: Did the team reach an activation decision within 10 minutes? Were roles and alternates clear? Could you deliver a customer update in 20 minutes or less? Did someone own the first-60-minutes checklist? Were RTO/RPO referenced in decisions? If two or more answers are no, the plan needs revisions and a retest.
Cadence by risk profile: Most teams benefit from a quarterly tabletop (60–90 minutes) and an annual technical test. If you depend on backups, perform at least one partial restore to a test environment annually. If you rely on VPN or alternate workspace, confirm remote access and MFA for alternates and plan a test login quarterly.
Maintenance you’ll actually do: Assign one owner per section; update contacts after major staffing changes; revisit RTO/RPO annually; version the document and log changes. Keep the plan under version control with a simple change log at the end of the document.
BCP vs DRP vs Incident Response vs Crisis Comms
Different documents handle different kinds of bad days. This table shows how they fit together and when to use each.
| Document | Purpose | Primary owner | Typical triggers | Time horizon | Key artifacts/sections | Success metrics | When to use |
|---|---|---|---|---|---|---|---|
| BCP | Keep critical business functions going during disruptions | Operations/Business owners | Facility outage, key vendor failure, major app outage beyond RTO | Hours to days | BIA, RTO/RPO, roles, activation, communications, workarounds | Downtime vs RTO, customer SLAs met, clear decisions | Any event that interrupts normal operations across teams |
| DRP | Restore IT systems and data after a disruption | IT/Infrastructure | Data loss, infrastructure failure, site failover | Minutes to hours | Backup/restore procedures, failover runbooks, test logs | Restore within RTO/RPO, integrity checks passed | When systems/data need restoration or failover |
| Incident Response | Contain and resolve security or operational incidents | Security/Incident manager | Cyber incident, P1 outage, safety event | Minutes to hours | Detection, triage, containment, eradication, lessons learned | MTTD/MTTR, impact minimized, root cause addressed | When an incident requires coordinated response and containment |
| Crisis Comms | Coordinate internal and external messaging | Communications/PR | High-visibility issues affecting stakeholders | Minutes to days | Stakeholder map, channels, templates, approval workflow | Timely, consistent messaging, stakeholder feedback | When public or customer communications are essential |
Filled-out sample: 50‑person company
Use this example as a model to finish your draft quickly. It describes a US-based e-commerce firm with a small warehouse and a remote-first team.
Critical functions and objectives
- Online order processing: RTO 4 hours, RPO 1 hour; dependencies: e-commerce platform, payment gateway, order management system, Internet; manual workaround: accept phone orders, queue fulfillment in spreadsheet.
- Customer support: RTO 8 hours, RPO N/A; dependencies: helpdesk, VoIP, CRM; manual: forward phones to cell, track tickets in shared spreadsheet.
- Shipping/fulfillment: RTO 12 hours; dependencies: WMS, label printer, carrier portal; manual: pick from printed picklists; create handwritten labels; batch upload later.
- Payroll: RTO 48 hours; dependencies: payroll SaaS, bank access; manual: issue off-cycle paper checks if platform is unavailable for more than 2 days.
Roles and contacts
- Continuity lead: Operations manager (alternate: HR lead)
- Incident manager: Head of IT (alternate: senior systems admin)
- Function owners: Support lead, Fulfillment lead, Finance manager
- 24/7 contact list: Google Sheet link with mobile and personal email entries; printed in warehouse go-binder
Activation triggers and escalation
- BCP activate if: e-commerce platform outage exceeds 4 hours; or warehouse inaccessible; or carrier portal unavailable beyond 12 hours at end of day.
- Authority to activate: Incident manager; if unavailable, continuity lead.
- Escalation ladder: Level 1 departmental, Level 2 cross-functional, Level 3 executive notification.
First 24 hours actions
- 0–15 minutes: Acknowledge incident; check RTO for affected function; assign scribe.
- 15–30 minutes: Decide activation; notify internal stakeholders; begin manual order intake via phone and form.
- 30–60 minutes: Publish customer status note; route support lines to alternates; print picklists for orders already in queue.
- 1–4 hours: Coordinate with platform vendor; track backlogs; prepare reconciliation plan.
- 4–24 hours: Monitor progress; send customer update cadence every 4–6 hours while impact remains.
Communications scripts
Internal (Slack/SMS): “BCP activated for order processing due to platform outage exceeding RTO. Manual order intake live via phone form. Next update in 60 minutes. Owner: Ops. Scribe: Finance.”
Customer (email/status page): “We’re experiencing a delay processing online orders due to a platform issue. Orders placed since [time] are queued and will be processed as soon as service is restored. If you need immediate assistance, call [number]. We’ll provide another update by [time].”
Manual workarounds
- Online order intake form (Google Form) routes to a shared sheet; CS agents confirm payment via phone and note transaction IDs.
- Fulfillment prints picklists from last successful export; labels handwritten; carrier portal used later for batch label creation and tracking uploads.
Recovery and reconciliation
- When platform restores, reconcile queued manual orders against payment records; import via CSV; update shipment statuses.
- Review any duplicate orders or payments; contact customers where needed; document lessons learned.
BCP quick-start checklist
- Identify top critical functions
- Define RTO/RPO for each
- List dependencies (people, apps, locations, vendors)
- Document manual workarounds
- Assign owners and alternates with contacts
- Set activation triggers and escalation
- Prepare internal/external comms scripts
- Outline first-24-hours actions
- Verify backups/access and alternate workspace
- Schedule tabletop test
- Set review cadence and version control
Templates and variants by company size/industry
Micro (≤25 staff) — Minimal viable BCP fields you can’t skip: top 5 functions, RTO/RPO, owners and alternates, one trigger and one customer message, first-24-hours actions, and a contact list. Keep it to one page and rehearse once per quarter.
SMB (25–250) — Add dependency mapping for key vendors and SLAs, a simple status page process, and a shared contacts sheet with alternates. Consider a lightweight notification tool for off-hours SMS if email or chat may be down.
Regulated or IT-heavy — Add compliance notes (e.g., ISO 22301 alignment), evidence of tests (tabletop and restore), and documented approval workflows for communications. Ensure documented RTO/RPO tie back to your BIA and DR tests, and that vendor contracts reflect expected support windows.
Minimal viable timeline — Day 1: finish the one-page draft. Day 2–3: 30-minute owner reviews per function. Day 5: run the 90-minute tabletop. Week 2: apply lessons, update version, and share. The plan is now live.
As you mature, fold continuity into your operating cadence. For broader operational practices and process thinking, see Business Process Optimization: A Practical Playbook for Managers.
FAQs: common questions answered briefly
How do I write a business continuity plan? Start with the template above: list critical functions, define RTO/RPO, assign roles, set activation triggers, write comms, and outline recovery steps. Validate with a tabletop and keep it updated.
What is the difference between a BCP and a disaster recovery plan? A BCP focuses on keeping business operations running, including manual workarounds and communications. A DRP is the technical plan to restore IT systems and data. They interlock; a BCP references DR runbooks and backup procedures.
How often should a BCP be tested? Quarterly tabletop exercises work for many teams; high-risk environments may do monthly scenario reviews. Do at least one annual technical test (restore, failover, or alternate access) and one communications test.
What if my RTO/RPO are unrealistic? Adjust based on actual tests. If the platform can only restore to a 4-hour RPO, set that expectation and mitigate with workarounds. RTO/RPO are business targets, but they must be anchored to what your systems and vendors can actually deliver.
Do I need software? Not to start. Word/Docs and Sheets handle most small and midsize needs. As you grow, consider notification tools, status pages, and document control for audit trails. The plan above is designed to work without paid tools.
Use the free template, adapt it to your context, and keep it short enough that your team will actually read it. A simple, current plan beats a thick binder that nobody remembers during a bad day.