Disaster Recovery Plan Builder

Starter template • Save as HTML • Export as PDF
How this works: Techs fill out sections below. Use Save as HTML to download a re-editable file (data is embedded inside it). Use Export PDF for a professional print/PDF layout.
1. Client & Document Info Cover page + basics for this plan
Logo is embedded in saved HTML and appears on the PDF cover.
Hours of Operation

Set standard business hours for each day. Choose “Closed” or set open/close times.

Day Status Open Close
Sunday
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday

Cover Preview

Export PDF includes a clean cover page built from these fields.
No logo
Client:
Address:
Phone:
Effective:
2. Introduction Purpose, goals, applicability, and scope
Objective

The objective of this Disaster Recovery Plan is to provide guidance to ______________________ management for the restoration of Information Technology facilities. Where appropriate, this Disaster Recovery Plan should be activated in conjunction with the organization’s Business Continuity Plan.

This plan describes the IT framework and procedures to be activated in the event of a disaster occurring, to enable recovery of IT services provided to ______________________.

Although ______________________ has facilities located in multiple locations, this plan covers these facilities as well.

Major Goals
  • To minimize interruptions to normal operations.
  • To limit the extent of disruption and damage.
  • To minimize the economic impact of the interruption.
  • To establish alternative means of operation in advance.
  • To train personnel with emergency procedures.
  • To provide rapid restoration of service.
Purpose

This Disaster Recovery Plan establishes procedures to recover the IT System following a disruption. The following objectives have been established for this plan:

  • Maximize the effectiveness of operations through the following phases:
    • Notification/Activation phase to detect and assess damage and to activate the plan
    • Recovery phase to restore temporary operations and assess damage to the system
    • Reconstitution phase to restore system processing capabilities to normal operations
  • Identify the activities, resources, and procedures needed to carry out processing requirements during prolonged interruptions to normal operations.
  • Assign responsibilities to designated personnel and provide guidance for recovering the IT System during prolonged periods of interruption to normal operations.
  • Ensure coordination with other staff who will participate in the Disaster Recovery Planning strategies. Ensure coordination with external points of contact and vendors who will participate in the Disaster Recovery Planning strategies.
Applicability

The Disaster Recovery Plan applies to the functions, operations, and resources necessary to restore and resume ______________________ operations.

Scope

The scope of the procedures documented in this Disaster Recovery Plan is restricted to IT Infrastructure at ______________________.

The scope of the procedures covers the following systems:

Planning Principles

Various scenarios were considered to form a basis for the plan, and multiple assumptions were made. The applicability of the plan is predicated on the following key principles:

  • A major system (listed above) of ______________________ facility is inaccessible.
  • ______________________ is unable to perform IT System processing.
  • ______________________ will use a home office or temporary facility to recover IT System functionality during an emergency that prevents access to the original facility.
  • The designated equipment and infrastructure at the alternate site will be loaner and emergency equipment provided by external services.
    • The alternate site will be used to continue IT System recovery and processing throughout the period of disruption, until the return to normal operations.
Assumptions

The following assumptions were used when developing the Disaster Recovery Plan:

  • A key system (listed above) is inoperable at ______________________ and cannot be recovered within 48 hours.
  • Preventive controls (for example, generators, sprinkler systems, and fire department assistance) are fully operational at the time of the disaster.
  • Server equipment, including components supporting IT System, are connected to an uninterruptible power supply (UPS).
  • IT System hardware and software at the original site are unavailable for at least 48 hours.
  • Current backups of the application software and data are intact and available at an offsite or cloud location.
  • Equipment, connections, and capabilities (loaner or emergency) are reasonably available within 24 hours.
  • Service agreements are maintained with IT System hardware, software, and communications providers to support emergency system recovery.
  • A single site event has occurred, and all other service sites are operational.
  • The offsite storage standby site remains intact and accessible.
  • Qualified Disaster Recovery personnel are available and familiar with the procedures documented in this Plan.
Prerequisites

For disaster recovery to be effective it is agreed that:

  • An adequate backup of data should be lodged off-site.
  • Sufficient free space will be set aside on computer systems to handle any loaded data.
  • Insurers for ______________________ will be made fully aware of these arrangements.
  • A supply of up-to-date stationery will be stored at each site for printing.
  • A list of main staff contacts will be distributed, including home numbers and addresses.
Alternative Back-up Sites

If the pre-arranged site proves to be unsuitable due to an unanticipated situation or event, an alternative site should be identified. The following criteria should be considered when selecting a site:

  • Sufficient working space for required personnel.
  • Adequate telecommunications access.
  • Proximity to existing ______________________ locations.
Alternative Site Details
Location Name Address Phone Notes Actions
Disaster Recovery Policy

This Disaster Recovery Plan complies with the ______________________ Disaster Recovery Planning policy as follows:

  • The organization shall develop a Disaster Recovery Planning capability to meet the needs of critical supporting operations in the event of a disruption extending beyond 72 hours.
  • The procedures for execution of such a capability shall be documented in a formal Disaster Recovery Plan and shall be reviewed at least annually and updated as necessary.
  • Personnel responsible for target systems should be trained to execute contingency procedures.
  • The plan, recovery capabilities, and personnel shall be tested to identify weaknesses of the capability at least annually.
Business Impact Analysis

Perform Business Impact Analysis to identify business critical activities and timeframes within which systems must be restored. Enter the time required to recover the relevant systems in relation to the support of the business-critical activities. Use this table as a reference when coordinating continuity activities between business functions and IT systems.

Business-Critical Activity Supporting System(s) Recovery Time Required Notes Actions
2. Operations Profile
System Description

Each system and a description of its function are outlined below.

System Description Actions
Governance and Accountability

______________________ sets forth an order of succession so that decision-making authority for the Disaster Recovery Plan is uninterrupted. The Disaster Recovery team is responsible for ensuring the safety of personnel and the execution of procedures outlined in this Disaster Recovery Plan.

Order Role Name / Organization Phone Email Notes Actions
Tip: Keep Order as 1, 2, 3… (DR Officer, DR Planning Coordinator, external/provider contacts such as Sundance Networks).
3. Document History Revision tracking, reference docs, distribution list
Paper copies are valid only on the day they are printed. Contact the author if you are in any doubt about of this document.
Revision History
Date Version Comments Actions
Track plan changes over time.
Reference Documents
Document Name Related Section Description / Location Actions
Link SOPs, network diagrams, vendor runbooks, etc.
Distribution List
Name / Role Email Phone Actions
Who receives this plan or updates.
4. Purpose, Scope & Assumptions High-level statements and operational context
5. Roles & Responsibilities Vendors, key contacts, and support resources

NOTE: Identify team names and leaders; do not include the actual names of personnel as these are subject to change.

Vendor / Support Org Service / Product Contact / Phone Notes Actions
Populate primary vendors (ISP, VoIP, MSP, LOB apps, backups, etc.).
6. Software List Paste current software used; build Application Profiles automatically

Recovery Point Objective (RPO) describes the age of the data you want to restore.
Recovery Time Objective (RTO) is the time needed to recover from a disaster.

Tip: Paste from an inventory export. Blank lines will be ignored; duplicates are removed.
7. Application Profiles Critical systems, RPO/RTO targets, priority
Application / System Priority RPO RTO Dependencies / Notes Actions
Example priorities: Critical / High / Medium / Low.
8. Inventory Profile Servers/workstations/printers and essential assets
Inventory Profile

Equipment needed in the event of a disaster is inventoried in the IT Asset Inventory spreadsheet. The total number of workstations should be at least half of the amount in the inventory.

Inventory Items

See the IT Asset Inventory spreadsheet for hardware and software.

Servers & Computers
Device Name Role OS Serial / Asset Tag Location Notes Actions
Include domain controllers, file servers, NAS, key workstations, etc.
Printers
Printer Model Location Notes Actions
Optional if not needed for DR.
9. Notification & Activation Trigger criteria, escalation, contact lists
Notification & Activation Procedures

Based on the assessment of the event, the plan will then be activated by the Community Manager.

  1. Employees notify the Disaster Recovery Planning Coordinator.
  2. The Disaster Recovery Planning Coordinator contacts the Community Manager and informs them of the event.
  3. The Disaster Recovery Planning Coordinator begins the assessment procedures.
  4. The Community Relations Manager notifies team members and directs them to complete the assessment procedures to determine the extent of damage and estimated recovery time.
Criteria for activating the Disaster Recovery Plan

Activate the Disaster Recovery Plan if one or more of the following criteria are met:

  1. One of the IT Systems is unavailable for more than 24 hours.
  2. Facility is damaged and will be unavailable for more than 72 hours.
  3. Planned disruption of an IT System for more than 72 hours.

If the plan is to be activated, the following steps occur:

  1. The Disaster Recovery Planning Coordinator will notify all Managers and Supervisors and inform them of the details of the event and if relocation is required.
  2. Upon notification from the Disaster Recovery Planning Coordinator, Managers and Supervisors will notify their respective teams. Team members are to be informed of all applicable information and prepared to respond and relocate if necessary.
  3. The Disaster Recovery Planning Coordinator will begin preparing Community Center for work locations including location for server.
  4. The Disaster Recovery Planning Coordinator will notify the remaining personnel of the status of the incident.
Stage 1: Decision to Invoke Disaster Recovery Plan

In the event of a disaster, perform the following steps before deciding to INVOKE the Disaster Recovery site. There are two scenarios for a disaster occurrence.

Staff / Key Contacts
Name Role Phone Email Notes Actions
Include decision makers and technical contacts.
Emergency Evacuation & Out-of-hours Response

Deploy the emergency evacuation plan.

Out-of-hours

In this scenario:

  1. The Facilities Manager will be notified by Alarm Company. Contact Emergency Services, such as the local Fire Station and Police.
  2. The Facilities Manager will contact the Disaster Recovery Manager and Coordinator with details of the problem.
  3. When safe to do so, the Disaster Recovery Coordinator will evaluate the situation.
  4. Following the evaluation, the DR Manager will contact Management and explain the situation.
Stage 2: Invoke Disaster Recovery Site

The Disaster Recovery Coordinator will contact Maintenance to prepare areas in Community Center for alternate location.

Action Plan
Stage 3: Contacting Third Party Recovery Team

The DR Coordinator will engage Sundance Networks (Sundance Networks, Inc.) to begin the recovery process.

Stage 4: Contacting Maintenance

The Disaster Recovery Coordinator will contact the Maintenance Department and identify who is required to be onsite in the Disaster Recovery facility.

Employee Position Phone Number Email Address Actions
Stage 6: Remote Users

The Disaster Recovery Coordinator will contact all personnel who are not required on the Disaster Recovery site to notify them of the invitation and to ask them to stand by for further instruction later.

Employee Position Phone Number Email Address Actions
CSV headers: Employee, Position, Phone Number, Email Address (or Name, Position, Phone, Email).
Damage Assessment Procedure

Utilize the following procedure to assess the extent of the damage to the system and/or facility. Involve appropriate vendors as necessary.

Response Checklist

The response procedure is critical to efficiently managing a disaster situation and reducing the impact on business operations. The following tasks must be completed by the responsible party and used as the trigger for the initial response to the disaster scenario. This checklist ensures all relevant activities have been performed within the required time frames.

Ref Activity Responsibility Timeframe Signoff Actions
10. Recovery Procedures System playbooks with objectives, preconditions, and tasks
Add one playbook per system. Use templates and customize.
11. Testing & Maintenance Plan tests, cadence, and update process
12. Additional Notes Anything unique to the client environment
13. Return to Normal Operations Original site restoration and plan deactivation
Original Site Restoration
Task Performed By Signoff By
Plan Deactivation

Considering each disaster is different and plan deactivation is unique to the situation. A checklist should be developed for the particular plan deactivation; however, it should include the following essentials.

  • Ensure that sensitive information is managed properly.
  • Ensure that equipment and materials are returned to the appropriate location.
  • Instruct team members to return to the original site.
14. Communications Plan Stakeholder updates, employee/client messaging

Describe the communication process in the event of a disaster situation. External communication is required to keep key stakeholders informed of project status, issues, and risks.

Communications Schedule

The following table shows the communication for the project.

What Audience Frequency Prepared By Purpose Media
Message to Employees
Role Message
will provide employees with a safe alternative-working environment as required.
has ensured that facilities will be available to ensure employee safety.
will rapidly alleviate the current problem at hand and provide continuous updates on the situation.
will provide appropriate contact information to all employees.
is the single point of contact for inquiries.
Message to Clients
Role Message
has ensured that facilities will be available to ensure client’s safety.
can continue the exceptional, expected service to our clients.
can continue to meet all financial, legal, and Current Company obligations.
is working to rapidly alleviate the current problem at hand and will provide continuous updates on the situation.
provides a single point of contact for such inquiries.

(Communications Plan content below will be replaced with an improved layout.)