Skip to content
Sovereign SecureSovereign Secure

Free template

Business Continuity Plan Template (Aligned to ISO 22301)

A copy-ready business continuity plan for UK organisations, free to download as an editable Word file, built on a business impact analysis, aligned to ISO 22301:2019 clause 8.4, with the cyber scenarios most likely to stop you trading and how to test the plan against them.

Prefer to talk? Call +44 161 523 5276

  • Ten copy-ready plan sections, free as a Word download
  • Business impact analysis worksheet with RTO and RPO
  • Mapped to ISO 22301 and ISO 27001

The short answer

A business continuity plan sets out how you keep your most important activities running, or restore them, after a disruption. It should include a business impact analysis, recovery time and recovery point objectives, roles and contacts, communications, recovery steps for each critical activity, and how the plan is tested. Test it at least once a year and after major changes.

On this page
  1. What should a business continuity plan include?
  2. How do you complete a business impact analysis?
  3. The business continuity plan template (BCP template)
  4. Which cyber scenarios should the plan cover?
  5. How do you adapt the template for a small business?
  6. How often should a business continuity plan be tested?
  7. How does this template map to ISO 22301 and ISO 27001?
  8. Why Sovereign Secure
  9. Need help turning the template into a working plan?

A business continuity plan is a written, tested procedure for keeping your most important activities going, or getting them back quickly, when something disrupts them: a cyber attack, a supplier failure, a power cut or the loss of a building. The free business continuity plan template below has ten copy-ready sections and a business impact analysis worksheet, and it is aligned to ISO 22301:2019, the international standard for business continuity management. Copy it from this page or download the business continuity plan template as an editable Word document with the worksheet, contact tables and an exercise log ready to fill in.

Use it as a starting point. A template only becomes a plan once your own impact analysis, contacts and recovery steps replace the bracketed text, and once you have tested it.

What should a business continuity plan include?

At minimum, a plan says what matters most, how fast it must come back, who decides and how you recover. The ten sections below cover that:

  1. Purpose, scope and activation
  2. Roles and contacts
  3. Critical activities and recovery objectives
  4. Invocation and escalation
  5. Communications
  6. Recovery procedures
  7. Resources and alternative arrangements
  8. Return to normal operations
  9. Testing and exercising
  10. Review and document control

Keep the core plan short enough to use under pressure. Detailed IT recovery runbooks, supplier contracts and floor plans belong in appendices.

How do you complete a business impact analysis?

Start here, before you write any plan section: the business impact analysis (BIA) decides what the plan protects and how fast. For each activity, work out how the impact of stopping it grows over time, then set four measures:

  • Maximum tolerable period of disruption (MTPD): the point at which the impact of not resuming becomes unacceptable.
  • Recovery time objective (RTO): the target time to resume the activity, which must be shorter than the MTPD.
  • Recovery point objective (RPO): the most data you can afford to lose, which sets your backup frequency.
  • Minimum business continuity objective (MBCO): the reduced level of service you can accept while recovering.

Copy this worksheet and add one row per activity. The business continuity plan example in the first row shows the level of detail to aim for; its timings are illustrative, not recommendations.

Activity Owner Impact if stopped MTPD RTO RPO Minimum service Dependencies Workaround
[Example: taking and fulfilling customer orders] [Head of operations] [Lost revenue from day 1, contract penalties from day 3] [3 days] [24 hours] [1 hour] [Orders by phone only] [E-commerce platform, payment provider, warehouse staff, courier] [Manual order log, courier booked by phone]
[Activity] [Name] [Financial, customer, legal, reputational] [Time] [Time] [Time] [Level] [People, premises, IT, suppliers] [Manual or alternative process]

The business continuity plan template (BCP template)

This is the BCP template itself. Copy the sections below into your own document, or use the Word version, replace everything in square brackets, and attach the completed BIA worksheet.

1. Purpose, scope and activation

This plan sets out how [Organisation] continues or restores its critical activities after a disruption affecting [sites, services, systems and teams in scope]. It applies to [staff, contractors and named suppliers]. Plan owner: [role]. Approved by: [director]. Last tested: [date]. Next review: [date, no more than 12 months away].

2. Roles and contacts

Role Responsibilities Primary Deputy Out-of-hours contact
Continuity lead Invokes the plan, chairs the response team, keeps the decision log [Name] [Name] [Number]
Operations lead Restores critical activities in priority order [Name] [Name] [Number]
IT lead Restores systems and data to the RTO and RPO [Name] [Name] [Number]
Communications lead Staff, customer, supplier and media messages [Name] [Name] [Number]
People lead Staff welfare, working locations and pay [Name] [Name] [Number]

Add external contacts: IT or managed service provider, cloud providers, landlord, insurer, bank, key suppliers and utilities.

3. Critical activities and recovery objectives

List each critical activity from the BIA in priority order with its owner, RTO, RPO and minimum service level. Recover activities in this order unless the continuity lead decides otherwise.

4. Invocation and escalation

Invoke the plan when [criteria, for example: a critical activity is likely to exceed half its RTO, a site is unusable, or a cyber incident affects core systems]. [Named roles] can invoke it. The continuity lead records the time, the reason and every major decision in the decision log.

5. Communications

Agree how the team will talk if email, phones or chat are unavailable or compromised, for example a personal-number call tree or a separate messaging account. Prepare holding statements for staff, customers and suppliers. Only [role] speaks to the media.

6. Recovery procedures

For each critical activity, write the steps for the first hour, the first 24 hours and until normal service returns, with who does each step and what they need.

7. Resources and alternative arrangements

Record alternative premises or remote working arrangements, spare equipment, how to restore from backups, alternative suppliers and any manual workarounds. Check that backups are kept separate from the systems they protect and that restores have been tested.

8. Return to normal operations

Set the criteria for standing down, the checks before systems return to full use, and how backlogs and manual records are brought back into normal systems.

9. Testing and exercising

Test this plan at least once a year and after significant changes. Record each exercise, its findings and the actions taken.

10. Review and document control

Review the plan after every exercise, real invocation and significant change, and at least every [12 months]. Keep a version history and make sure everyone with a role can reach the current copy, including offline.

Which cyber scenarios should the plan cover?

Cyber incidents disrupt a business differently from a fire or a flood: the building is fine, but systems, data or communications are not. Test your recovery steps against each of these:

Scenario What stops working What the plan must cover
Ransomware Servers, laptops and possibly backups Restoring from backups the attacker could not reach, clean rebuilds, manual workarounds
Email and cloud account takeover Email, file sharing and collaboration tools A separate communication channel and how staff work without the main tenant
Outage at a cloud or software provider A platform you rely on, such as payments or finance Workarounds, provider status updates and a fallback provider where the RTO demands one
Managed service provider compromise Remote access to your systems Cutting the provider’s access and recovering without them
Internet or telephony failure Online sales, calls and remote working Backup connections and alternative routes for customers

Responding to the attack itself belongs in your incident response plan template; the continuity plan keeps the business trading while that happens. For prevention, see how to prevent ransomware.

How do you adapt the template for a small business?

Keep it short. A business with one site and a handful of staff can usually cover everything on a few pages:

  • Combine roles. One person can be continuity lead and communications lead, as long as each role has a named deputy.
  • List three to five critical activities, such as taking orders, paying staff and serving existing customers, and fill in the BIA worksheet for those only.
  • Write down the workarounds you would really use: working from home, taking orders by phone, a spare laptop, a second internet connection.
  • Keep supplier details in the plan, especially your IT support company, the cloud services you rely on and your insurer.
  • Keep a copy off your systems, printed or on a personal phone, in case email and file storage are unavailable.

If customers or public sector buyers ask how you protect against cyber attacks as well, Cyber Essentials is the usual starting point for a small business.

How often should a business continuity plan be tested?

At least once a year, and after significant changes to sites, systems, suppliers or people. ISO 22301 requires an exercise programme run at planned intervals and when there are significant changes, and expects you to act on the results.

Method What it tests
Plan walkthrough Contacts, roles and documents are current
Tabletop exercise Decisions, escalation and communication against a realistic scenario
Technical recovery test Backups restore within the RPO and systems return within the RTO
Live or simulation exercise Whether teams can actually work from alternative sites or systems

The NCSC’s free Exercise in a Box includes scenarios that small organisations can run themselves.

How does this template map to ISO 22301 and ISO 27001?

Each section supports a clause of ISO 22301:2019 and the continuity controls in ISO/IEC 27001:2022 Annex A.

Template section ISO 22301:2019 ISO 27001:2022 Annex A
BIA worksheet, section 3 8.2.2 Business impact analysis 5.30 ICT readiness for business continuity
Sections 2 and 4 8.4.2 Response structure 5.29 Information security during disruption
Section 5 8.4.3 Warning and communication 5.29
Sections 6 and 7 8.3 Strategies and solutions, 8.4.4 Business continuity plans 5.30, 8.13 Information backup, 8.14 Redundancy
Section 8 8.4.5 Recovery 5.30
Section 9 8.5 Exercise programme 5.30
Section 10 7.5 Documented information, 8.6 Evaluation of business continuity documentation and capabilities 5.29, 5.30

A plan on its own is not enough for ISO 22301 certification, which assesses a whole business continuity management system, including the risk assessment, internal audit and management review behind the plan. Firms within the scope of the PRA and FCA operational resilience rules, such as banks, insurers and payment institutions, also set impact tolerances for important business services, and their continuity plans should support them.

Why Sovereign Secure

  • ISO 27001 certified: our own information security management system is independently audited.
  • ISO consultancy across 12 standards, including ISO 22301 and ISO 27001. Certification audits are carried out by our partner certification body, MQA International, which makes its own certification decisions.
  • Testing that supports recovery planning: penetration testing and red team assessments show how an attacker could reach the systems your plan depends on.
  • UK company since 2012, headquartered in Accrington, Lancashire, with offices in Los Angeles, Singapore, Dubai and Dhaka.

Need help turning the template into a working plan?

Tell us your sites, critical services and whether you are aiming for ISO 22301 or ISO 27001, and we will explain how our consultancy can help and give you a fixed quote. Contact us or call +44 161 523 5276.

Last reviewed October 2026 by the Sovereign Secure assessment team.

Trusted by banks, payment providers and global brands

  • Accor
  • Fiserv
  • JCPenney
  • Ticketmaster
  • Nitecrest
  • Cashplus
  • Ahli United Bank
  • Kuwait Finance House
  • AYA Bank
  • Bank of Palestine
  • Liquid Pay
  • DataFlow Group
  • Wilmington
  • The Growth Company
  • Wahyukart

FAQ

Frequently asked questions

Can't find your answer? Call us on +44 161 523 5276 or send us a message.

What should a business continuity plan include?

Scope and activation criteria, roles and contacts, a summary of your business impact analysis, recovery objectives for each critical activity, communications, step-by-step recovery procedures, alternative resources, return to normal operations, and how the plan is tested and reviewed.

Is there a free business continuity plan template?

Yes. The template on this page is free to copy and adapt, or you can download it as an editable Word document. Many UK councils also publish simple templates, because the Civil Contingencies Act 2004 requires local authorities to give businesses advice on business continuity.

How often should a business continuity plan be tested?

At least once a year, and whenever something significant changes, such as a new site, system or key supplier. ISO 22301 requires exercises at planned intervals and after significant changes, and expects you to act on what each exercise finds.

What is the difference between RTO and RPO?

The recovery time objective (RTO) is how quickly an activity or system must be running again. The recovery point objective (RPO) is how much data you can afford to lose, measured back from the moment of disruption, and it drives how often you back up.

What is the difference between a business continuity plan and a disaster recovery plan?

A business continuity plan keeps the business delivering its critical activities, using people, premises, suppliers and workarounds. A disaster recovery plan is the technical part that restores IT systems and data, and it should meet the RTO and RPO the continuity plan sets.

How is a business continuity plan different from an incident response plan?

An incident response plan deals with the security incident itself: containing it, investigating it and notifying the right people. The continuity plan keeps the business running while that happens. Most cyber incidents need both; see our incident response plan template.

Is this template enough for ISO 22301 certification?

No. A plan is one part of ISO 22301. Certification also needs a scoped management system with a policy, risk assessment, continuity strategies, an exercise programme, internal audit and management review, assessed by an independent certification body.

Free consultation

Talk to an assessor

We aim to reply within one working day, and send a fixed quote once your scope is confirmed.

  • PCI SSC-approved QSA, QPA, CPSA, P2PE and 3DS assessors
  • IASME-licensed Cyber Essentials certification body
  • Clients across the UK, US, Europe, Middle East and Asia since 2012

“We are satisfied with the quality of work delivered by Sovereign Secure and would happily recommend them to any company that requires consultancy and guidance in obtaining their ISO 27001 certification.”

Edmund How, Managing Director, Onesecure Asia. Read the full testimonial

By sending this form you agree to us contacting you about your enquiry. See our privacy policy.

We aim to reply within one working day. The first consultation is free.