Business continuity plan: how to write one, with a template outline and IT recovery
A business continuity plan sets out how your company keeps its most important work going when something goes wrong: a ransomware attack, a cloud outage, a fire, the loss of a key supplier or key people. A good business continuity plan is short enough to use under stress, names who decides what, says which activities come back first and how fast, and has been tested. This guide walks through the business impact analysis, recovery objectives, the IT recovery plan, testing, the legal requirements under NIS2 and DORA, and a template outline.
Legal text referred to was read on 12 November 2026: Directive (EU) 2022/2555 (NIS2), Regulation (EU) 2022/2554 (DORA) and Regulation (EU) 2016/679 (GDPR). The NIST contingency planning guide, SP 800-34 Rev. 1, is a useful free reference for the IT part.
Continuity, disaster recovery and incident response
| Plan | Question it answers | Owner |
|---|---|---|
| Business continuity plan | How do we keep serving customers and meeting obligations during a disruption? | Management, with each business unit |
| IT disaster recovery plan | How do we restore systems and data, in what order and how fast? | IT, with the system owners |
| Incident response plan | How do we detect, contain and report a security incident? | Security or IT, with legal and communications |
| Crisis communication plan | Who tells what to staff, customers, authorities and media? | Management and communications |
They work together. The continuity plan sets the priorities, the disaster recovery plan restores the systems behind them, and the incident response plan handles the attack that often causes the disruption in the first place.
Step 1: business impact analysis
The business impact analysis, or BIA, decides what the plan protects. For each business activity, ask:
- What happens if it stops for an hour, a day, a week? Lost revenue, missed legal deadlines, contract penalties, harm to customers or patients, reputation.
- From what point does the damage become unacceptable? That is the maximum tolerable downtime.
- What does it depend on? People, premises, systems, data, suppliers.
- Can it run in a reduced or manual way for a while?
The result is a ranked list of critical activities with their dependencies. DORA makes this step explicit for financial entities: Article 11(5) requires a BIA of exposures to severe business disruptions, using quantitative and qualitative criteria and scenario analysis. For everyone else it is simply the step that stops a plan from protecting the wrong things.
Step 2: recovery objectives
Two numbers per critical system turn the BIA into an IT requirement:
- Recovery time objective (RTO): how long the system may be unavailable before it must be back.
- Recovery point objective (RPO): how much data, measured in time, you can afford to lose. An RPO of one hour means backups or replication at least every hour.
Set them per system, not one figure for everything. The order system may need an RTO of four hours and an RPO of fifteen minutes; the intranet may wait three days. Short objectives cost more, so the BIA justifies where they are needed.
Step 3: strategies for each dependency
| Dependency | Typical continuity strategies |
|---|---|
| Systems and data | Backups with an offline or immutable copy, replication to a second region, documented restore procedures, a tested order of recovery |
| Cloud and SaaS suppliers | Data exports you can use elsewhere, an exit plan, a second provider for the most critical service |
| People | Deputies for key roles, written procedures, access for more than one person |
| Premises | Remote work, an alternative site, equipment that can be replaced quickly |
| Other suppliers | Alternative suppliers, stock buffers, contract terms on their continuity |
| Communication | Contact lists stored outside the main systems, an alternative channel if email is down |
One rule from practice: the plan and the contact list must be reachable when your systems are not. A plan stored only on the file server that ransomware has encrypted is not a plan.
Step 4: the IT disaster recovery plan
NIST SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems (May 2010, updated 11 November 2010), describes the IT side in detail and is free to use. Its approach fits companies of any size: for each system, document the backup method and location, the restore procedure step by step, the people who can perform it, the order of recovery with dependencies (identity and network before applications), and how to check that the restored system and data are correct. The GDPR asks for the same capability for personal data: Article 32(1)(c) lists the ability to restore the availability of and access to personal data in a timely manner after a physical or technical incident, and 32(1)(d) a process for regularly testing it.
The backups behind the recovery plan are covered in our backup strategy guide.
Step 5: roles, activation and communication
- Who declares a disruption and activates the plan, with a deputy.
- A small crisis team: management, IT, operations, communications, with clear decision rights.
- Communication templates for staff, customers, suppliers and, where required, authorities.
- A log of decisions and actions, needed later for reports, insurance and lessons learned.
Scenarios worth writing down
Plans work best when they are tested against concrete scenarios rather than "a disaster". Most small and midsize companies cover these five:
| Scenario | What the plan should answer |
|---|---|
| Ransomware encrypts servers and laptops | Which clean backups exist, where systems are rebuilt, how work continues manually until they are, who talks to customers |
| A critical cloud or SaaS service is down for days | What can be done without it, whether data can be exported and used elsewhere, the supplier's own continuity terms |
| The office or warehouse cannot be used | Remote work, an alternative site, equipment replacement, mail and deliveries |
| Key people are unavailable | Deputies, written procedures, shared access to accounts and passwords through a vault |
| A key supplier fails | Alternative suppliers, stock buffers, contract rights |
Step 6: test and maintain
A plan that has not been tested will fail in ways nobody predicted. Test in increasing depth: a tabletop walk-through of a scenario with the crisis team, a technical restore of a critical system into a clean environment, then a full exercise. Record what failed and fix it. Review the plan after every major change and at least once a year. DORA Article 11(4) requires financial entities to periodically test their ICT business continuity plans, notably for critical or important functions outsourced to ICT third-party providers.
What NIS2 and DORA require
Under NIS2, Article 21(2)(c), essential and important entities must have business continuity measures, such as backup management and disaster recovery, and crisis management, as part of their cybersecurity risk-management measures. Our NIS2 compliance guide explains who is in scope. DORA, which has applied to EU financial entities since 17 January 2025, goes further: Article 11 requires a comprehensive ICT business continuity policy, documented response and recovery plans, independent internal audit reviews of those plans for entities other than microenterprises, periodic testing and a business impact analysis.
A business continuity plan template outline
- Purpose, scope, owner, version, date, next review.
- Activation: who declares, criteria, first steps in the first hour.
- Crisis team with deputies and contact details, stored offline as well.
- Critical activities from the BIA, ranked, with maximum tolerable downtime.
- Systems with RTO, RPO, backup location and recovery order.
- Continuity strategies per dependency: systems, suppliers, people, premises.
- Communication: audiences, channels, templates, legal reporting duties.
- Return to normal operations and lessons learned.
- Test plan and test log.
How we help
We build the technical part of continuity into the systems we build and run: backups with an immutable copy, infrastructure defined as code so an environment can be rebuilt, documented restore procedures, and restore tests with recorded results. Our managed IT services include backup monitoring and tested restores, and a security audit checks whether your recovery objectives are achievable today. Systems run in EU regions, in accounts in your company's name, so you are never dependent on us to get your data back.
Questions people ask
What is the difference between a business continuity plan and a disaster recovery plan?
A business continuity plan keeps the critical work of the business going during and after a disruption, whatever the cause: a fire, a supplier failure, a pandemic, a cyberattack. A disaster recovery plan is the IT part of it: how systems and data are restored. The continuity plan decides what must be back first and how fast; the disaster recovery plan delivers it.
What is the difference between a business continuity plan and an incident response plan?
An incident response plan handles a security incident: detect, contain, eradicate, recover, report. A business continuity plan handles any disruption to the business, of which a cyber incident is one. In a ransomware attack, both run at the same time: incident response deals with the attacker, continuity keeps customers served while systems are down.
Is a business continuity plan required by law?
For some companies, yes. NIS2 requires essential and important entities to have business continuity measures, including backup management, disaster recovery and crisis management. DORA requires financial entities to have an ICT business continuity policy and tested plans. For other companies it is not a general legal requirement, but customers, insurers and auditors increasingly ask for one.
How often should a business continuity plan be tested?
At least once a year for the whole plan, and after every major change in systems, suppliers or organisation. Restores of backups should be tested more often, for example every quarter for the most critical systems. A test that finds nothing wrong was probably too easy.
What is ISO 22301?
ISO 22301 is the international standard for business continuity management systems. Companies can follow it as a framework or be certified against it. A plan does not need certification to be useful, but the standard's structure is a good reference for larger organisations.
Sources
- Directive (EU) 2022/2555 (NIS2), Article 21(2)(c) (read 12 November 2026)
- Regulation (EU) 2022/2554 (DORA), Articles 11 and 64 (read 12 November 2026)
- Regulation (EU) 2016/679 (GDPR), Article 32(1)(c) and (d) (read 12 November 2026)
- NIST SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems (read 12 November 2026)