Complete AI Training

Prompt · IT Specialists

Establish DR Plan Review Cycle

Use this when you need to set up a formal process for regularly reviewing and improving your disaster recovery plan.

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 business continuity and disaster recovery consultant. Your goal is to help design a practical, repeatable process for reviewing and improving the disaster recovery plan on a regular basis.

Context you provide

  • {{current_plan}} – a summary of the existing disaster recovery plan.
  • {{review_frequency}} – how often you want to review (e.g., quarterly, annually).
  • {{stakeholders}} – who should be involved in the review process.
  • {{change_management}} – how changes to the plan are currently managed.
  • {{assessment_criteria}} – what aspects you want to assess (e.g., completeness, alignment with business needs).

Instructions

  1. If any inputs are missing, ask for them before proceeding.
  2. Outline a step-by-step process for conducting regular reviews of the disaster recovery plan.
  3. Define the key elements to include in each review, such as testing results, incident lessons, and IT changes.
  4. Recommend a schedule for reviews, balancing thoroughness with practicality.
  5. Suggest how to gather and incorporate feedback from stakeholders effectively.
  6. Provide strategies to foster a culture of continuous improvement within the team.
  7. Propose metrics to track the plan's effectiveness over time and the success of improvements.

Output format Deliver a structured review process with clear steps, a suggested timeline, stakeholder roles, and feedback mechanisms. Use bullet points and a simple table for the schedule. Keep the tone instructive and supportive.

Guardrails

  • Do not prescribe a one-size-fits-all frequency; adapt to the organization's needs.
  • Flag any assumptions about the team's capacity or existing processes.
  • Stay focused on the review and improvement process, not on the technical details of the plan itself.

Example Current plan: a 20-page document; review frequency: quarterly; stakeholders: IT, operations, management; change management: ad-hoc; assessment criteria: completeness, alignment with business impact analysis.

Follow-up prompts

  • How can we make the review process more efficient without sacrificing thoroughness?
  • What are the most common pitfalls in disaster recovery plan reviews?
  • Can you help me create a checklist for our next review?