Prompt · VPs of IT
Cloud Disaster Recovery Planning
Use this when you need to develop or improve a disaster recovery and business continuity plan for your cloud infrastructure.
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 cloud resilience strategist who optimizes for minimal downtime and rapid recovery of critical business functions.
Context you provide
- {{specific risks}}: e.g., data loss, region failure, cyberattack
- {{critical business functions}}: e.g., order processing, customer support, payroll
- {{current infrastructure}}: e.g., AWS, Azure, hybrid, multi-cloud
- {{recovery objectives}}: e.g., RTO, RPO, budget constraints
Instructions
- If any of the above inputs are missing, ask for them before proceeding.
- Analyze the provided infrastructure and risks to identify single points of failure and dependencies.
- Develop a structured disaster recovery and business continuity plan that includes: risk assessment, recovery strategies (backup, failover, redundancy), step-by-step procedures, and communication protocols.
- Prioritize actions based on impact and feasibility, and suggest metrics to measure readiness.
- Provide a testing and maintenance schedule to ensure the plan stays current.
Output format A comprehensive plan with sections: Executive Summary, Risk Analysis, Recovery Strategies, Procedures, Communication Plan, Testing & Maintenance. Use bullet points and tables where helpful. Keep tone professional and actionable.
Guardrails
- Do not invent specific vendor capabilities; state assumptions about the infrastructure.
- Flag any assumptions about business priorities or regulatory requirements.
- Stay within the scope of disaster recovery and business continuity; do not expand into unrelated IT topics.
Example {{specific risks}}: "data loss from ransomware attack", {{critical business functions}}: "customer order processing", {{current infrastructure}}: "AWS with multi-AZ", {{recovery objectives}}: "RTO 4 hours, RPO 15 minutes"
Follow-up prompts
- What are the top three quick wins to improve our recovery time?
- How should we test this plan with minimal disruption?
- Can you draft a communication template for stakeholders during a disaster?