NEWFollow the cyber threat vectors into the dark. Register for Jedi Declassified Threat Briefing >Register Now
Guides/Overview/Online Reader
FREE RECOVERY TEMPLATE

IT Disaster Recovery Plan Template

Build a recovery plan your team can actually use. Use the section list to navigate.

6 min read·7 Sections··
Section:Key contacts
Section 1 · Response

Key contacts

List the people who need to be contacted during an incident, and in what order. Keep this list somewhere accessible outside your main systems - in case those are the systems that are down.

• Incident lead (makes decisions and coordinates the response)
• Technical lead (executes containment and restore steps)
• Communications lead (informs staff, customers and suppliers)
• IT support provider / managed service provider contact details
• Cyber insurer claims contact
• Key supplier contacts (Microsoft 365, line-of-business apps, internet provider)
Section 2 · Priorities

Critical systems and recovery priorities

List the systems your business cannot function without, in the order you would restore them. This helps everyone focus when time is tight.

• Email and communication (Microsoft 365, Teams)
• Line-of-business application(s) - e.g. accounts, CRM, practice management
• File storage and collaboration (SharePoint, OneDrive)
• Phones and VoIP
• Website and customer-facing systems
• Finance and payroll systems
Rank these by how quickly the business feels the impact if they are unavailable.
Section 3 · Targets

Recovery time and recovery point targets

For each critical system, define two targets:

• Recovery Time Objective (RTO): how long can this system be down before it seriously hurts the business?
• Recovery Point Objective (RPO): how much data can you afford to lose? This drives how often you need backups.

Example: email might have an RTO of 4 hours and an RPO of 15 minutes. A shared marketing drive might tolerate an RTO of 24 hours and an RPO of 1 day.

Document these targets for each system so your IT team or provider knows what to aim for.

Section 4 · Recovery

Backup locations and how to restore

List where your backups are held and how to get to them. If your main systems are encrypted or unavailable, you need to know exactly where the clean copies live.

• Microsoft 365 backup platform - URL and login details
• Device image backups - location and software
• On-premise or server backups - physical location
• Immutable / offsite copy - location and access method
• Last known-good restore point date
• Who has access to restore (with contact details)
Backups that have never been tested are not backups. Record the date of the last successful restore test.
Section 5 · Incident

Ransomware response steps

If ransomware hits, follow these steps in order:

• 1. Disconnect affected devices from the network immediately (do not power off - isolate at the network level)
• 2. Contact your incident lead and IT support provider
• 3. Disable affected user accounts and force sign-out across Microsoft 365
• 4. Identify the scope - which devices, accounts and files are affected
• 5. Preserve evidence - take photos, screenshots and notes before cleaning anything
• 6. Restore from clean, immutable backups - do not pay the ransom
• 7. Rebuild affected devices from known-good images
• 8. Reset all credentials and enforce MFA before re-enabling accounts
• 9. Review how the attack entered and close the gap
Section 6 · Comms

Communication plan

Decide in advance who communicates with whom, and when. Templates written in advance save critical minutes during an incident.

• Internal staff update - what happened, what to do, what not to do
• Customer holding message - reassurance without overpromising a timeline
• Supplier notification - if they are affected or needed for recovery
• Regulator notification - if personal data is involved (ICO within 72 hours under UK GDPR)
• Insurer notification - to start the claims process
• Media holding statement - if the incident may become public
Keep communication templates in a format accessible even if email is down (e.g. printed copies or a separate cloud account).
Section 7 · Maintenance

Testing schedule

A plan that is never tested is a hope, not a plan. Schedule regular tests so your team knows what to do before they need to do it.

• Quarterly tabletop exercise - walk through a scenario with the team
• Annual timed restore test - restore a core system and measure how long it takes
• After each test, update the plan with what worked and what didn't
• Review contacts and access details every 6 months
• Confirm backups are completing and immutable copies are intact
The best time to test your disaster recovery plan is before you need it.
Take Action

Ready to make recovery real?

We help UK SMEs build tested recovery plans, with immutable backups and restore drills. See our cloud backup and business continuity resources to get started.