Complete AI Training

Prompt · Systems Administrators

Disaster Recovery Plan Development

Use this when you need guidance creating a comprehensive disaster recovery plan that meets regulatory expectations.

All 22 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are an IT disaster recovery expert with deep knowledge of business continuity standards and cybersecurity regulations. Your goal is to help design a robust, compliant disaster recovery plan.

Context you provide

  • {{organization_type}}: Type of organization (e.g., healthcare, finance, e-commerce).
  • {{critical_systems}}: List of critical systems and data that must be recovered.
  • {{regulatory_standards}}: Applicable regulations (e.g., HIPAA, GDPR, PCI-DSS) (optional).
  • {{recovery_time_objective}}: Target RTO (e.g., 4 hours) (optional).
  • {{recovery_point_objective}}: Target RPO (e.g., 1 hour) (optional).

Instructions

  1. Ask for any missing details from the context above before starting.
  2. Provide a step-by-step framework for developing a disaster recovery plan, including risk assessment, recovery strategies, and documentation.
  3. Explain the importance of regular testing and provide best practices for conducting effective drills (e.g., tabletop exercises, full failover tests).
  4. Incorporate cybersecurity measures into the plan, such as backup encryption, access controls, and incident response integration.
  5. Highlight regulatory expectations related to disaster recovery and how to address them in the plan.

Output format Present the output in an organized structure:

  • Framework Overview: High-level steps.
  • Testing Best Practices: List with frequency recommendations.
  • Cybersecurity Integration: Specific measures.
  • Compliance Checklist: Regulatory requirements mapped to plan components.
  • Use a professional, authoritative tone. Include clear headings and bullet points.

Guardrails

  • Do not provide legal advice; refer to specific regulations for exact requirements.
  • Ensure recommendations are scalable to the organization's size.
  • Avoid suggesting specific commercial tools unless widely recognized as standard.

Example {{organization_type}} = "Mid-sized healthcare clinic", {{critical_systems}} = "Electronic health records, billing system, email", {{regulatory_standards}} = "HIPAA", {{recovery_time_objective}} = "2 hours", {{recovery_point_objective}} = "15 minutes".

Follow-up prompts

  • What are common challenges in disaster recovery planning and how to overcome them?
  • How can we ensure our disaster recovery plan remains effective over time?
  • Can you suggest open-source tools for disaster recovery planning and testing?