Turn Your Vision into Success, Let It Fly with Us

Ensure Your Business Is Secure, Compliant & IT-Ready

Create a practical disaster recovery plan for your business using our free editable Word template or PDF guide. Identify critical systems, set recovery priorities, assign responsibilities and prepare your business to recover from unexpected disruption.

Disaster recovery plan template for SMEs

Table of Contents

Why disaster recovery matters for SMEs
What Should a Business Disaster Recovery Plan Include?

A practical plan should include:

  • Critical Business Systems: Identify the applications, servers, databases and services that the business depends on.
  • Recovery Priorities: Decide which systems must be restored first.
  • Recovery Time Objective (RTO): Define how quickly each critical system should be restored.
  • Recovery Point Objective (RPO): Establish how data loss the business can accept.
  • Backup Arrangements: Document where backups are stored and how they will be protected.
  • Responsibilities: Identify the employees and IT providers responsible, for recovery.
  • Communication Procedures: Explain how employees customers and suppliers will receive updates.
What is a Disaster Recovery Plan?

Disaster Recovery Plan Example

See a completed example of a DR Plan for a small UK business, including recovery priorities, responsibilities, and example disaster scenarios.

IT Disaster Recovery Plan Example

Explore a practical IT-focused recovery example covering Microsoft 365, servers, backups, internet failure, cyberattacks and ransomware.

Disaster Recovery Testing Checklist

 Use this practical checklist to test your backups, recovery procedures, incident response and business continuity arrangements.

Disaster Recovery vs Business Continuity
Area Disaster Recovery Business Continuity
Focus Restoring IT systems Maintaining business operations
Scope Technical recovery Organisation-wide response
Example Restoring file servers Continuing customer support
Objective Recover systems Keep the business running
The risks SMEs face without a DRP

Without a documented Disaster Recovery Plan, organisations will likely face:

More time to recover

While determining how to recover, there will be any access for staff to systems.

Loss of data

If there is insufficient data backups, there could be a loss of work done immediately prior to failure.

Business interruption

Business functions such as customer service, finance, and communications are interrupted.

Financial ramifications

Revenue lost due to business interruption, cost of recovering to PRE-incident operations could be substantial.

Non-compliance with regulations

In accordance to UK Data Protection Regulations, organisations need to be able to demonstrate that they manage the data in a responsible manner.

Problems with insurance

Many cyber insurers require proof of backup planning and recovery planning procedures.

Adopting resilience practices as suggested by frameworks such as Cyber Essentials can help the organisation further manage their overall risk.

A step-by-step guide for creating a DRP consists of:

You do not need to have a sophisticated technology set up to put together a Disaster Recovery Plan (DRP). Your most important task is to document the process to restore systems in the event of a disaster.

Step 1: Determine the critical systems used in your environment.

Step 2: Decide the order in which to restore the systems.

The order of restoration can range from those required to conduct business operations, to systems that can withstand a longer outage.

Step 3: Establish your RTO and your RPO.

By determining how long you can go without each system and how much data loss is acceptable, you can develop backup and recovery strategies.

Step 4: Document the recovery process for each system.

Clearly document the procedures for restoring all systems.

Step 5: Determine the people accountable for the recovery process and who provides assistance to them.

Identify the recovery process leader and who will assist.

Step 6: Create a communication process for internal and external clients.

Create a plan to inform employees, clients, and suppliers of developments during a disruption.

Step 7: Test the Plan.

Conduct frequent tests to ensure that your recovery processes will work when they are needed.

Full Disaster Recovery Plan Template

1. Document Control

2. Key Business Systems

List essential technology platforms.

Example table:

System Purpose Owner Location
Email platform Business communication IT provider Cloud
File storage Shared documents Operations Cloud / Server
Accounting software Financial management Finance team Cloud

3. Recovery Priorities

System Priority Maximum Downtime Business Impact
Email High 4 hours Communication disruption
File storage High 4 hours Staff unable to work
CRM Medium 24 hours Sales delays

4. Disaster Scenarios

5. Recovery Procedures

6. Backup Strategy

7. Incident Response Team

8. Communication Plan

Recovery Priorities, RTO and RPO: Practical Examples for SMEs

What Is RTO?

What Is RPO?

Example: Recovery Priorities for a Small Business

Priority System or service Example RTO Example RPO Reason
1. Critical Identity and administrator access 2 hours 1 hour Recovery teams need secure access to manage affected systems.
2. Critical Email and staff communications 4 hours 1 hour Staff need to coordinate recovery and communicate with customers.
3. High Essential business files 8 hours 4 hours Employees need access to operational documents and records.
4. High Accounting and invoicing 8 hours 4 hours The business needs to manage payments, invoices and financial records.
5. Normal CRM and non-essential reporting 24 hours 8 hours Some customer management and reporting activities may be temporarily delayed.

How to Set Your Recovery Priorities

1

Identify Critical Business Activities

List the services employees need to serve customers, process orders, receive payments and maintain essential business operations.

2

Assess the Impact of Downtime

Consider lost revenue, customer commitments, contractual obligations, regulatory responsibilities and potential reputational damage.

3

Identify System Dependencies

Identify which systems rely on other services. For example, email and accounting software may depend on identity services, internet connectivity or a third-party provider.

4

Agree RTO and RPO Targets

Consult business owners, department managers and IT support staff to establish realistic recovery time objectives (RTO) and recovery point objectives (RPO).

5

Confirm Recovery Arrangements

Review backup frequency, restore times, access arrangements, available equipment and supplier recovery commitments to check whether the agreed targets can be met.

6

Document Recovery Approval

Name the person responsible for setting recovery priorities, approving key decisions and authorising the return to normal business operations.

Review and Update Your Recovery Targets

Testing and Maintaining a DRP

Disaster Recovery Readiness Checklist

Step 6: Implement a backup strategy.

System Priority Maximum Downtime Business Impact
Email High 4 hours Communication disruption
File storage High 4 hours Staff unable to work
CRM Medium 24 hours Sales delays

FAQs

1. Does the Law Require Disaster Recovery Planning (DRP) in the UK?

There is no legal requirement for a disaster recovery plan, but all businesses must follow UK data protection laws by safeguarding data that is personal.

2. How Often Should You Test a DRP?

In most cases, small and medium-sized businesses should evaluate their DRP at least once a year to determine its effectiveness.

3. Who is Responsible for the DRP?

In most cases, the IT Director, Operations Director, or an external IT vendor is responsible for the disaster recovery plan.

4. What Level of Detail Do I Need to Include in the DRP?

A DRP should have sufficient detail so that all employees can execute the recovery steps when necessary.

5. Are Cloud-Based Backup Services Sufficient for Disaster Recovery?

While they can be valuable, cloud-based backup services need to be verified and tested regularly as part of your disaster recovery plan.

About This Guide

The Computer Support Centre developed this document to assist small to medium-sized UK businesses in developing and executing an operationally sound disaster recovery framework.

This document provides simple tangible guidance for business owners, operations managers, and IT assisting organisations in developing a realistic disaster recovery plan without undue technical complexity.

Instead of emphasising theory, this document provides practical recovery methodologies, checklists, and structured templates designed for UK SMEs. The ultimate aim of this publication is to assist organisations in decreasing overall downtime, safeguarding key data and increasing their organisation’s resiliency towards cyber crime, hardware failure, and any other unforeseen disruption.

Ransomware Recovery Plan for Small Businesses

Ransomware attacks can disrupt business operations, encrypt important files and affect access to critical systems. Read our Ransomware Recovery Plan for Small Businesses for practical steps to isolate affected devices, protect backups and restore business systems safely.

Conclusion

A disaster recovery plan should be considered more than an IT policy it represents a practical safeguard used for the rapid recovery of your organisation when the unexpected occurs. A few hours’ downtime can severely impact your business processes delay the provision of services to your clients; and create a financial loss.

Fortunately, disaster recovery does not have to be complicated: Businesses who have identified their critical systems; agreed on realistic recovery priorities; continue to maintain reliable backups and produce documentation on clear recovery procedures can generally prevent downtime to their operations due to cyber incidents; outages; or hardware failures.

In summary, an effective Disaster Recovery Plan ensures that when a disruption occurs, your employees know in advance what to do who is responsible and how to restore the systems. Simply put, preparing today eliminates confusion tomorrow.