A disaster recovery plan is a written set of steps that gets your systems and data back after an outage, ransomware attack, hardware failure or site loss. A usable checklist covers eight things: what you depend on, what an hour of downtime costs, how fast and how current each system must come back, who does what, how backups are built and secured, the recovery steps in order, how you communicate, and how often you test. A plan that has never been restored from is a guess, so the checklist below ends where most plans fail: testing. For a business that would rather not carry this alone, our Backup & Disaster Recovery service builds and maintains it as part of managed IT.
TL;DR
- Start with a business impact analysis: list critical functions, the systems behind them, and what downtime costs. Everything else follows from it.
- Set a recovery time objective (RTO) and recovery point objective (RPO) for each system, not one number for the whole company.
- Name a recovery owner, a backup, and a call tree, and write down the exact criteria that declare a disaster.
- Follow the 3-2-1 backup rule, encrypt and isolate copies, and restore from them on a schedule.
- Review the plan at least yearly, and test it with a tabletop exercise first, then a real restore.
Table of Contents
- What a disaster recovery plan covers, and what it does not
- The disaster recovery plan checklist
- Extra items for regulated businesses
- Common mistakes
- Our perspective
- Get the plan built and kept current
- FAQ
- Sources
What a disaster recovery plan covers, and what it does not
Three documents are often confused. The business continuity plan covers the whole organization: staff, critical functions, facilities and suppliers. The disaster recovery plan sits inside it and covers restoring IT. The incident response plan covers detecting, containing and managing a security incident. TechTarget's comparison draws the same lines, and one ransomware event can trigger all three at once.
Ready.gov, FEMA's preparedness site, says an IT recovery plan should be developed together with the business continuity plan, with priorities and recovery times set during the business impact analysis. If you need the wider documents, see our guides to a small business continuity plan and an incident response plan. This checklist stays on the IT side.
The disaster recovery plan checklist
1. Inventory what you run
You cannot recover what you have not listed. Ready.gov advises starting with an inventory of hardware (servers, desktops, laptops, wireless devices), software applications and data. Add where each item lives (office, cloud, vendor), who administers it, and which license keys or installation media you need to rebuild it.
Typical gaps: a forgotten file server under a desk, a cloud app only one employee can log into, a line-of-business database nobody documented. Our guide to building an asset inventory for a small business shows a format that stays current.
2. Run a business impact analysis
A business impact analysis (BIA) asks what happens to the business when a function stops. The FFIEC IT Examination Handbook, which bank examiners use, describes a BIA as identifying every business function, ranking it by criticality, analyzing interdependencies between processes and systems, and defining recovery priorities and the resources needed. Costs include lost business and legal or regulatory exposure.
In practice, make a table with one row per function:
| Function | Supporting systems | Cost of an hour down | Depends on |
|---|---|---|---|
| Client billing | Accounting app, database, email | Your own figure | Internet, identity login |
| Loan or case intake | SQL database, document system | Your own figure | Network, file storage |
| Patient scheduling | Practice management, phone system | Your own figure | Internet, vendor hosting |
NIST's guidance on business impact analysis adds that criticality comes from the harm of losing availability and must account for system interdependencies. If your email depends on a single login service, that login service is as critical as email.
3. Score the risks you plan for
List the disasters realistic for your location and industry: ransomware, accidental deletion, hardware failure, power loss, fire, flood, earthquake, a vendor outage. Atlassian's guide suggests scoring each threat by likelihood and impact so high-impact, high-likelihood scenarios get attention first. A simple 1 to 5 scale for each is enough. Southern California businesses should include earthquake and wildfire-related power shutoffs in the list.
4. Set RTO and RPO for each system
These two numbers are the core of the plan:
- Recovery time objective (RTO): how long a system can be down before the damage becomes unacceptable.
- Recovery point objective (RPO): how much recent data you can afford to lose, measured backward from the failure.
AWS's disaster recovery guidance says the business impact analysis should quantify the impact of a disruption to each application, including cost, reputation and compliance effects, and then determine how quickly the application must return (RTO) and how much data loss is tolerable (RPO), weighing the cost of recovery.
A method that works for a small business:
- Rank each system into tiers. Tier 1 is anything that stops revenue or patient or client service. Atlassian's guide uses the same idea: tier 1 is mission-critical and guides recovery order.
- Ask the owner of each function: "If this were gone for four hours, what breaks? For a day?" Write the answer in money and in compliance terms.
- Set the RPO from how much work is re-creatable. A mortgage loan system taking transactions all day cannot lose a day of entries, so its RPO is far shorter than a document archive that changes weekly.
- Check cost. A near-zero RTO and RPO means replicated infrastructure and is priced accordingly. Lower the target for systems where the business impact does not justify it.
- Confirm the backup design can actually meet each number. RPO drives how often you back up; RTO drives how you restore.
Our disaster recovery cost guide walks through budgeting once targets are set.
5. Assign roles and activation criteria
Most failed recoveries are failures of ownership. The State of Ohio's disaster recovery planning template is a clear model. It requires a business point of contact, a recovery coordinator, a technical recovery contact, a plan manager and a coordinator who tracks progress and escalates. Its activation criteria are concrete, such as an outage expected to run longer than the RTO or facility damage that makes a system unavailable within the RTO.
For a small business, one person can hold several roles, but each role needs a named backup. Write down:
- who may declare a disaster, and the exact trigger (for example, "system down and not fixable within its RTO");
- who notifies staff, in what order, and by which method (call tree, text, a channel that does not depend on your own email);
- who contacts vendors, your insurer, customers and, where required, regulators;
- after-hours contact numbers stored outside the systems that may be down.
NIST SP 1300, the Cybersecurity Framework quick-start guide for small business, also asks that you know who holds recovery responsibilities and keep a comprehensive recovery communications plan.
6. Build backups that survive the disaster
Backups are the part of the plan that either works or does not. CISA's small business guidance recommends the 3-2-1 rule: three copies of data, on two types of media, with one copy off-site. It also advises automatic, regular backups, physical security, encryption and offline copies, and being able to roll data back at least seven days.

Decide what goes into the backup, too. CISA lists customer and client records, employee and HR data, financial and payroll data, email, configuration files and software settings, and website and operational databases. Do not forget SaaS data such as Microsoft 365 or Google Workspace mailboxes, and SQL databases, which need application-aware backups to restore cleanly.
For a deeper look, read our guides on the 3-2-1 backup rule with test restores and a 3-2-1-1-0 ransomware backup strategy. If your public website is a WordPress site, include it in the plan and keep a documented procedure for recovering from WordPress errors.
7. Write the recovery runbook
For each tier 1 and tier 2 system, document the steps in order, so a tired person at 2 a.m. can follow them. The Ohio template's sequence is a good skeleton:
- Assess the outage and confirm the activation criteria.
- Identify the recovery location (original site, alternate office, cloud).
- Identify required resources and retrieve backup and installation media.
- Rebuild hardware and operating system if needed.
- Restore the system from backup.
- Validate: confirm data is current and intact, and that users can log in and work.
- Escalate and notify at each stage, then return media and close the event.
NIST SP 1300 adds two details worth copying: assess the integrity of backed-up data before restoring from it (so you do not restore malware), and prioritize recovery by organizational needs and affected assets. Include dependency order, for example identity and network first, then databases, then applications.
8. Test, then keep testing
CISA says scheduling backups is not enough: organizations should regularly test partial and full restores and write a restoration plan, because some found restore times far longer than expected after ransomware.
CISA's resource guide on service continuity describes three levels of exercise: a tabletop review of plans and procedures, a partial-function recovery with part of the infrastructure available, and a full-function recovery of an entire service or system. It says annual testing is usually enough for most services, with quarterly or monthly tests for very critical or fast-changing ones. Plans should be updated whenever material changes occur and reviewed at least annually.
A workable schedule:
| Activity | Frequency |
|---|---|
| Restore a sample of files or a mailbox | Monthly or quarterly |
| Restore a full tier 1 system to a test environment | At least yearly |
| Tabletop exercise with the recovery team | Yearly |
| Update contacts, inventory and RTO/RPO | After any major change, and at least yearly |
Record how long each restore took and compare it with the RTO. If the number is off, fix the design, not the target.
Extra items for regulated businesses
Healthcare. The HIPAA Security Rule's contingency plan standard requires a data backup plan, a disaster recovery plan and an emergency mode operation plan, plus procedures for testing and revising them. Your plan should show how electronic patient data is restored and how care continues while systems are down.
Banks and mortgage companies. The FFIEC handbook expects recovery priorities and dependencies to come from a documented BIA. Keep evidence of the analysis, the tests and the results, because examiners ask for them. Treat SQL databases as tier 1 with an RPO set from transaction volume.
Law firms. Document how client files and the matter management system return, and how privileged data stays encrypted in backups and during restore.
Our Compliance & Security Audits cover HIPAA, GDPR, SEC, SOC 2 and CMMC.
Common mistakes
- One RTO for everything, which either overspends or underprotects.
- Backups on the same network as production, reachable by ransomware.
- Plans stored only on the server that is down. Keep printed and offline copies.
- No named backup for the recovery coordinator.
- Never timing a restore.
- Forgetting cloud and SaaS data, vendors and internet service as dependencies.
Our perspective
We have one view on disaster recovery: the checklist is easy and the discipline is hard. Most small businesses can fill in an inventory and an RTO table in an afternoon. What separates a plan from a document is someone who owns the restore tests, reviews the plan when systems change, and watches the environment the other 8,000 hours a year.
That is why we run recovery as part of proactive managed IT, with 24/7 monitoring, backup and disaster recovery, and security under one team, rather than as a binder delivered once. Preventing the incident is cheaper than recovering from it, and recovering quickly is cheaper than recovering slowly. We work with Southern California businesses that have compliance obligations such as HIPAA and SEC-aligned requirements, so the plan we help build is tied to the evidence those obligations ask for.
Our backup restores are designed to be proven, not assumed. Read our tax-season restore case study for what that looks like.
Alex
Get the plan built and kept current
Secure Techies is a managed IT provider for small and mid-size businesses in Southern California. Our Backup & Disaster Recovery service sits alongside Managed IT Services and Cybersecurity Solutions, with flat-rate transparent billing and no long-term contracts, 24/7 local support and a 99.9% uptime guarantee.

If you want your RTOs, backups and recovery runbooks documented and tested by the team that also monitors your systems, talk to Secure Techies.
FAQ
How often should I update my disaster recovery plan?
Review it at least once a year and whenever something material changes, such as a new line-of-business application, a cloud migration, a new office or a change in recovery staff. CISA's service continuity guidance gives the same cadence. Update contact lists after every staffing change.
What is the difference between RTO and RPO?
RTO is how long a system can be unavailable. RPO is how much recent data you can lose. A system with a four-hour RTO and a one-hour RPO must be back within four hours, with data no more than an hour old.
What is the 3-2-1 backup rule?
Keep three copies of your data on two types of media, with one copy off-site. CISA recommends it for small businesses, along with encryption, offline copies and regular restore tests.
Do I need a disaster recovery plan if my data is in the cloud?
Yes. Cloud providers keep their platforms running, but deleted files, compromised accounts and ransomware still affect your data. Your plan should cover how you recover mailboxes, shared drives and applications, who has access, and which settings and configurations you must rebuild.
Is a disaster recovery plan required for HIPAA?
Yes. The HIPAA Security Rule's contingency plan standard includes a disaster recovery plan, a data backup plan and an emergency mode operation plan, along with testing and revision procedures.
Sources
- Business continuity vs. disaster recovery vs. incident response, TechTarget
- IT Disaster Recovery Plan, Ready.gov
- FFIEC IT Examination Handbook: Business Impact Analysis
- NIST IR 8286D: Using Business Impact Analysis to Inform Risk Prioritization
- Data Disaster Recovery Plan: Steps & Strategies, Atlassian
- Business impact analysis and risk assessment, AWS Whitepaper
- State of Ohio Disaster Recovery Planning Template
- NIST SP 1300: Cybersecurity Framework 2.0 Small Business Quick-Start Guide
- Back Up Business Data, CISA
- Cyber Guidance for Small Businesses, CISA
- CRR Resource Guide: Service Continuity Management, CISA
- HIPAA Rules on Contingency Planning, HIPAA Journal
- WordPress Error Recovery: A Step-by-Step Guide
