Technical Recovery Plan Template

The Technical Recovery addresses who, what, where, when, why, and how to recover something – whether it be an IT system, data network, or other process. The following is a list of various dimensions of what must be known or possessed to recover a certain system or project in order to make trade off decisions and/or have a successful system recovery. Some of this information can also be complied and placed in separate directories for lists.

  • Purpose – set the context for which the system provides value.
  • Scope – what the system does and does not support.
  • Background – explain business requirements that assist the reader in understand why the server/application/process exists.
  • Assumptions – a list of things that were assumed when this plan was written (i.e. technical qualifications required for person executing plan, etc.)
  • Dependencies – anything else that must be in place (i.e. specific database server, essential IT servers, etc.)
  • Tech Support – the names and 24-hour contact numbers of primary and secondary support persons for the specified system.
  • System Users – the primary end users for the system. They should be called to verify a system has been successfully recovered.
  • Server Requirements – in terms of CPU, RAM, “C: drive” size and type, etc.
  • Disk Space Requirements – the total disk storage required for local disks, SAN disks, etc.
  • Connectivity Requirements – describes the network configuration (i.e. VLANs, trusts, opened firewall ports, etc.)
  • Support Software – a list of supporting utilities that may be needed.
  • Application Requirements – listed in case a software application must be changed during recovery.
  • Database Requirements – the type and version of the database program supporting the system. This needs to include required permissions, databases, and table connections needed.
  • Special Input Data – beyond what’s in the company’s backup media, such as data stored in a different off-site location or external data feed.
  • Licensing Requirements – may be relevant since in some cases, loading a system on new hardware may require a license change by the software manufacturer.
  • Special Printing Requirements – instructions for setting up printed output for an application to include special forms.
  • Service Contracts – support the system’s components to include days and times of coverage, etc. Include the expiration date. Describe how to contact the vendor or whoever provides support. Information should be available through the command center and the administrative plan.


Michael Herrera is the Chief Executive Officer (CEO) of MHA. In his role, Michael provides global leadership to the entire set of industry practices and horizontal capabilities within MHA. Under his leadership, MHA has become a leading provider of Business Continuity and Disaster Recovery services to organizations on a global level. He is also the founder of BCMMETRICS, a leading cloud based tool designed to assess business continuity compliance and residual risk. Michael is a well-known and sought after speaker on Business Continuity issues at local and national contingency planner chapter meetings and conferences. Prior to founding MHA, he was a Regional VP for Bank of America, where he was responsible for Business Continuity across the southwest region.

Leave a Reply

Your email address will not be published. Required fields are marked *

Business continuity consulting for today’s leading companies.

Follow Us

© 2024 · MHA Consulting. All Rights Reserved.

Learn from the Best

Get insights from almost 30 years of BCM experience straight to your inbox.

We won’t spam or give your email away.

  • Who We Are
  • What We Do
  • Blog