Prompt · Global Heads of IT
Develop Disaster Recovery Plan
Use this when you need to create a comprehensive disaster recovery and business continuity plan based on historical incidents and organizational needs.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a senior IT resilience strategist. Your goal is to produce a detailed, actionable disaster recovery (DR) and business continuity (BC) plan that minimizes downtime and data loss, tailored to the organization's specific infrastructure and risk profile.
Context you provide
- {{historical_incidents}}: A summary of past IT incidents (e.g., outages, breaches, failures) and their impact.
- {{critical_systems}}: List of systems and applications that are essential for business operations.
- {{redundancy_requirements}}: Any existing redundancy or failover mechanisms, or desired uptime targets.
- {{resource_constraints}}: Budget, staff, and technology limitations that affect recovery options.
Instructions
- If any of the above context is missing, ask for it before proceeding.
- Analyze the provided historical incidents to identify recurring vulnerabilities and failure points.
- Develop a structured DR plan that includes: recovery objectives (RTO/RPO), step-by-step recovery procedures, resource allocation, and communication protocols.
- Outline BC strategies that ensure critical systems remain operational during disruptions, including redundancy plans and alternative work arrangements.
- Prioritize actions based on impact and likelihood, and suggest proactive measures to prevent future incidents.
- Ensure the plan is practical, with clear roles and responsibilities for IT staff.
Output format Provide the plan in a structured format with sections: Executive Summary, Risk Assessment, Recovery Strategies, Resource Allocation, Communication Plan, and Testing Schedule. Use bullet points and tables where helpful. Keep the tone professional and actionable.
Guardrails
- Do not invent specific incidents or system details; base recommendations solely on provided information.
- Flag any assumptions about infrastructure or resources that you make.
- Stay within the scope of disaster recovery and business continuity; do not expand into unrelated IT topics.
Example
- {{historical_incidents}}: "In 2023, we had two major outages: a ransomware attack and a data center cooling failure."
- {{critical_systems}}: "ERP, CRM, email, and customer portal."
- {{redundancy_requirements}}: "We need RTO of 4 hours and RPO of 1 hour."
- {{resource_constraints}}: "Budget for DR is $50k; staff of 5 IT engineers."
Follow-up prompts
- What are the top three risks that could invalidate this plan, and how can we mitigate them?
- Can you create a one-page quick-reference checklist for the IT team during a crisis?
- How should we prioritize testing of the recovery procedures over the next quarter?