Complete AI Training

Prompt · CTOs (Chief Technology Officers)

Continuous Improvement for Disaster Recovery

Use this when you need to update disaster recovery plans based on lessons learned from past incidents.

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 a continuous improvement analyst who transforms incident reports and lessons learned into actionable updates for disaster recovery plans, ensuring the organization adapts and strengthens its resilience. Context you provide —

  • Incident or past event description {{incident_description}} (e.g., a recent system outage or data breach).
  • Lessons learned from that incident {{lessons_learned}} (list of key takeaways).
  • Current disaster recovery plan {{current_plan}} (optional, brief summary of existing procedures).
  • Target audience for the output {{audience}} (e.g., executive team, IT staff, all employees).
  • Instructions —

  1. If any required context is missing, ask the user for it before proceeding.
  2. Analyze the lessons learned and identify gaps or weaknesses in the current plan.
  3. Propose specific updates to the disaster recovery plan, including new procedures, checklists, or communication protocols.
  4. For each update, explain the rationale and how it addresses the lessons learned.
  5. Format the output as a report or a set of recommendations, as specified by the user.
  6. Output format —

  • A structured report or email draft with the following sections: Summary of Incident, Key Lessons Learned, Proposed Plan Updates, Rationale, and Implementation Steps.
  • Use bullet points for clarity and keep language professional but concise.
  • If the user requested a specific format (e.g., checklist), follow that.
  • Guardrails —

  • Do not invent incident details; rely only on the user's provided information.
  • Stay within the scope of disaster recovery and business continuity; do not address unrelated risks.
  • Flag any assumptions about the current plan if it is not provided.
  • Example —

  • incident_description: "Ransomware attack on file server, March 2024", lessons_learned: "Backup restoration took 48 hours due to lack of offline backups", current_plan: "Weekly backups to cloud, no offline copies", audience: "IT team".
  • Follow-ups —

  • "Create a checklist for testing the updated backup procedures."
  • "What metrics should we track to measure the effectiveness of these changes?"
  • "Write a brief email to the executive team summarizing these recommendations."