Sample business continuity plan template (with example)

A sample business continuity plan template to copy, section by section, with a filled-in activity sheet and how it maps to NIS2, DORA and ISO 22301.

8 min read
Sample business continuity plan template (with example)

Key takeaways

  • A business continuity plan template sets out the fixed sections of the plan: document control, purpose and scope, roles with deputies, contacts, activation conditions, order of recovery, critical activity sheets, resources, return to normal, testing and review.
  • Fill it in from a business impact analysis, a risk assessment and strategies already decided: the plan puts strategies into action, it does not choose them.
  • Sections 1 to 8 follow the plan contents of point 4.1.2 of the Annex to Implementing Regulation (EU) 2024/2690, binding for certain digital providers under NIS2 and a sound checklist for anyone else.
  • The core of the plan is one sheet per critical activity, written as numbered steps that someone who did not write them can follow.
  • DORA Article 11 asks financial entities for documented plans, tests at least yearly and readily accessible records of activities during disruptions.
  • In ISO 22301 plans and procedures sit in clause 8.4 and the exercise programme in clause 8.5.

A business continuity plan template gives you the fixed sections of the plan, ready to fill in: document control, purpose and scope, roles with deputies, activation and deactivation conditions, contacts and communication channels, order of recovery, one sheet per critical activity, resources, return to normal operations, and testing and review. Below is a sample template you can copy, with a filled-in example.

The template follows the plan contents listed for NIS2 in Commission Implementing Regulation (EU) 2024/2690 and adds the parts that make a plan usable under pressure. The placeholders in square brackets are what you replace. If you first need the background (what a BCP is, how it differs from disaster recovery, RTO and RPO), start with our guide to the business continuity plan.

Before you fill in the template

A template filled in without data produces a complete-looking document with invented priorities. Three inputs come first:

  • A business impact analysis (BIA). Which activities are critical, how long each can stop before the damage becomes unacceptable, and which people, systems, sites and suppliers each one depends on.
  • A risk assessment. Which disruptions are plausible for those activities.
  • The strategies already decided. Alternative site, remote work, stock, manual workarounds, backup suppliers, backups and replication. The plan does not choose strategies: it puts them into action.

ISO 22301 follows the same order. Business impact analysis and risk assessment sit in clause 8.2, strategies in clause 8.3, and only then, in clause 8.4, the plans and procedures.

The business continuity plan template (copy and adapt)

Sections 1 to 8 of the template below map to points (a) to (h) of point 4.1.2 of the Annex to Implementing Regulation (EU) 2024/2690. That annex is binding only for certain digital providers under NIS2 (among them cloud computing, data centre, managed service and managed security service providers), but the list works as a checklist for any organisation. Document control and section 9 are our additions.

Document control

  • Plan owner: [name, role]
  • Approved by: [management body or board member], on [date]
  • Version and date: [v1.0, date]
  • Next scheduled review: [date]
  • Distribution list: [who holds a copy, and where: printed, offline device, alternate site]
  • Record of changes: [date, section changed, what changed, approved by]

NIST Special Publication 800-34 Rev. 1, the US contingency planning guide for information systems, recommends keeping a record of changes and a record of who received copies of the plan, with a copy stored at the alternate site and with the backup media.

1. Purpose, scope and audience

  • Purpose: [keep delivering (products, services) at (agreed level) during a disruption and return to normal within the times set by the BIA]
  • In scope: [products, services, sites, systems]
  • Out of scope: [what is excluded, and why]
  • Scenarios covered: systems unavailable; site inaccessible; key people unavailable; a critical supplier down
  • Related plans: [disaster recovery plan, crisis management plan, incident response plan, with location]
  • Audience: [teams and roles that use this plan]

Writing for effects rather than causes keeps the plan short: there are many causes, but they lead to a handful of effects.

2. Roles and responsibilities

  • Plan coordinator: [name, phone], deputy [name, phone]
  • Who can activate the plan: [roles]
  • Lead for each critical activity: [activity: name, deputy]
  • IT recovery lead: [name], deputy [name]
  • Communications lead: [name], deputy [name]

Every role has a named deputy with the same authority. A plan that depends on one person stops working the day that person cannot be reached.

3. Key contacts and communication channels

  • Call tree: [who calls whom, in what order]
  • Internal contacts: [staff, personal phone numbers]
  • External contacts: [key suppliers, ICT providers, key customers, insurer, authorities where relevant]
  • Fallback channel: [a channel independent of corporate email and directory, for example a group on personal phones]
  • Message templates: [first notice to staff, notice to customers, location]

4. Conditions for activation and deactivation

  • Activate when: [for example: a critical system is down and the estimated recovery exceeds the tolerable downtime from the BIA; the site is inaccessible; a critical supplier cannot deliver]
  • Who decides: [role], informing [role]
  • Deactivate when: [checks completed: systems and data verified, backlog under control]
  • Who declares the end: [role]

Write the conditions so that one person can decide in minutes, not after a meeting.

5. Order of recovery

  1. [critical activity, tolerable downtime from the BIA]
  2. [critical activity, tolerable downtime]
  3. [critical activity, tolerable downtime]

6. Critical activity sheets (one per activity)

  • Activity: [name]
  • Owner and deputy: [names]
  • Tolerable downtime (from the BIA): [hours or days]
  • Recovery objectives of the systems it uses: [RTO and RPO, from the disaster recovery plan]
  • Dependencies: [people, systems, data, sites, suppliers]
  • Trigger for this sheet: [condition]
  • Workaround procedure: [numbered steps, written for someone who did not write them]
  • Return to normal: [how manual work is re-entered and checked]

This is the core of the plan and the section most often missing. NIST SP 800-34 recommends plans that are clear, concise and easy to carry out in an emergency, even by staff unfamiliar with the plan or the systems, with checklists and step-by-step procedures where possible.

7. Required resources

  • Backups and redundancies: [what, where, how the disaster recovery plan restores them]
  • Workplaces and connectivity: [alternate site, laptops, connection independent of the corporate network]
  • Paper and offline material: [emergency forms, last export of open orders, customer list]
  • Contracts: [replacement suppliers, recovery commitments of ICT providers]

8. Return to normal operations

  • Checks before switching back: [systems and data verified as reliable]
  • Re-entry of manual records: [who enters them, who checks a sample]
  • Log of actions taken during the event: [where it is kept]
  • Formal close: [who signs, lessons learnt meeting within (days)]

9. Testing, review and approval

  • Exercise calendar: [tabletop on (scenario), date; recovery test on (system), date]
  • Review triggers: [planned interval; after significant incidents; after significant changes to operations, systems or suppliers]
  • Contact list check: [more often than the rest of the plan, for example quarterly]
  • Approval: [management body], minutes reference [ref]

Filled-in example: one critical activity sheet

An illustrative example, not taken from a real case: a manufacturing company whose ERP runs in the cloud with a provider. The scenario is the ERP being unavailable; the activity is order fulfilment. The values are the kind a BIA might produce, not benchmarks.

  • Activity: customer order fulfilment (intake, picking, shipping).
  • Owner and deputy: logistics manager; deputy the warehouse supervisor.
  • Tolerable downtime (from the BIA): in this example, two working days, after which deliveries with contractual penalties are missed.
  • Dependencies: cloud ERP, label printers, courier, up-to-date customer list and price lists.
  • Trigger: the ERP provider cannot confirm recovery by the end of the shift; the logistics manager decides and informs the plan coordinator.
  • Workaround procedure:
    1. print the latest list of open orders and the customer master data from the offline archive;
    2. record new orders on the emergency form, numbered in sequence;
    3. prepare priority shipments following the key customer list;
    4. use the courier's paper waybills;
    5. update the manual shipment log every day.
  • Resources: emergency forms, offline archive refreshed every evening, direct courier contact, one laptop with a connection independent of the corporate network.
  • Return to normal: orders and shipments recorded by hand entered into the ERP, sample check with finance, sheet closed and signed by the owner.

A sheet like this fits on one page and can be followed by someone who did not write it. The full plan is a short framework document (document control and sections 1 to 5, 7, 8 and 9) plus one sheet per critical activity.

How the template maps to NIS2, DORA and ISO 22301

NIS2

Article 21(2)(c) of Directive (EU) 2022/2555 lists "business continuity, such as backup management and disaster recovery, and crisis management" among the cybersecurity risk-management measures of essential and important entities, and Article 20(1) has the management bodies approve those measures and oversee their implementation: that is the approval line in document control. The detail depends on each Member State's transposing law and, for the digital providers covered, on point 4.1 of the Annex to Implementing Regulation (EU) 2024/2690, which also asks for a BIA (4.1.3) and for plans tested, reviewed and updated at planned intervals and after significant incidents or changes (4.1.4). More on our NIS2 page.

DORA

For financial entities, Article 11 of Regulation (EU) 2022/2554 requires an ICT business continuity policy implemented through documented arrangements, plans, procedures and mechanisms. Among its aims (Article 11(2)): continuity of critical or important functions, a preliminary estimate of impacts, damages and losses, and communication and crisis management actions. Four points shape the template:

  • a BIA of exposures to severe business disruptions (Article 11(5));
  • tests of the ICT business continuity plans and the ICT response and recovery plans at least yearly, and after substantive changes to ICT systems supporting critical or important functions (Article 11(6)), with cyber-attack and switchover scenarios for entities other than microenterprises;
  • specific attention to critical or important functions outsourced to ICT third-party service providers (Article 11(4));
  • readily accessible records of activities before and during disruption events when the plans are activated (Article 11(8)): the log in section 8.

Entities under the simplified framework of Article 16 are outside Articles 5 to 15, but Article 16(1) still asks them to ensure the continuity of critical or important functions through business continuity plans and to test them regularly. See our DORA page.

ISO 22301

The standard is voluntary and certifiable. Clause 8.4 covers business continuity plans and procedures: response structure (8.4.2, sections 2 and 4 of the template), warning and communication (8.4.3, section 3), business continuity plans (8.4.4, section 6) and recovery (8.4.5, section 8). Clause 8.5 is the exercise programme, section 9. How certification works is on our ISO 22301 page.

Five checks before you sign it off

  • The numbers come from your BIA. A copied template with copied downtimes describes another company.
  • The business wrote the activity sheets. If only IT wrote the plan, you have a recovery plan for systems and no answer on how to ship or invoice in the meantime.
  • Every name has a deputy and a current number. A broken call tree is usually found on the day it is needed.
  • The plan is reachable when systems are not. If the only copy sits on the file server or in corporate email, there is no plan.
  • It has been exercised. NIST SP 800-34 separates tabletop exercises, where people discuss their roles in a scenario led by a facilitator, from functional exercises, where they carry out their duties in a simulated environment. A two-hour tabletop on one activity sheet shows more gaps than a document review.

Where to start

If there is no plan today, a workable order is: a BIA on the activities that carry revenue, the framework document with roles and activation conditions, one sheet for the first critical activity, and a tabletop exercise on that sheet. Then extend to the other activities. If you want a second view on your plan against NIS2, DORA or ISO 22301, talk to our team.

Frequently asked questions

At minimum: purpose, scope and audience; roles and responsibilities with deputies; key contacts and internal and external communication channels; conditions for activating and deactivating the plan; the order of recovery; recovery plans for each critical activity with recovery objectives; required resources, including backups and redundancies; and how activities return to normal from temporary measures. That is the list in point 4.1.2 of the Annex to Implementing Regulation (EU) 2024/2690. Add document control (owner, approval, version, distribution) and a testing and review section.
Only the structure. The tolerable downtimes, priorities, dependencies and workarounds have to come from your own business impact analysis and from the people who run each critical activity. A template filled with someone else's values describes another company.
As short as it can be while still usable. A practical format is a brief framework document (roles, contacts, activation, resources, return to normal, testing) plus a one-page sheet per critical activity. NIST SP 800-34 Rev. 1 recommends clear, concise plans with checklists and step-by-step procedures that staff unfamiliar with the plan can follow.
Senior management. Under Article 20(1) of the NIS2 Directive the management bodies of essential and important entities approve the cybersecurity risk-management measures, which include business continuity, and oversee their implementation. For financial entities, Article 5(2)(e) of DORA has the management body approve, oversee and periodically review the implementation of the ICT business continuity policy and the ICT response and recovery plans. Record the approval and its date in the document control section.
DORA Article 11(6) asks financial entities to test their ICT business continuity plans and ICT response and recovery plans at least yearly and after substantive changes to ICT systems supporting critical or important functions. Implementing Regulation (EU) 2024/2690 asks the digital providers it covers to test and review the plans at planned intervals and after significant incidents or changes. ISO 22301 requires an exercise programme in clause 8.5.

Let's talk about your security.

A 30-minute call to understand where you stand today and tell you, with no commitment, where it pays to start.

Book a call