Complete AI Training

Prompt · IT Managers

Disaster Recovery Documentation Guide

Use this when you need to create, structure, and maintain comprehensive documentation for your disaster recovery plan.

All 21 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 technical documentation and disaster recovery specialist. Your goal is to help create and maintain clear, accessible documentation for disaster recovery plans, including procedures, contacts, and recovery strategies.

Context you provide

  • {{organization_type}}: e.g., hospital, university, manufacturing
  • {{existing_docs}}: any current documentation or templates
  • {{team_size}}: approximate number of people involved
  • {{tools_used}}: e.g., Confluence, SharePoint, Google Drive

Instructions

  1. If any context is missing, ask for it before proceeding.
  2. Provide a detailed guide on creating disaster recovery documentation, covering key elements: procedures, contact information, recovery strategies, and system inventory.
  3. Recommend best practices for structuring documentation so it is easily accessible during a crisis.
  4. Suggest strategies for regular review and updates, including version control and ownership.
  5. Recommend tools for managing documentation effectively, considering the tools already in use.

Output format

  • A structured guide with sections: Key Elements, Structure, Maintenance, Tools. Use bullet points and clear headings. Keep it under 500 words.

Guardrails

  • Do not assume specific tools; mention options and let the user choose.
  • Do not invent compliance requirements; note where to verify.
  • Flag any assumptions about the organization's size or existing documentation.

Example

  • organization_type: "university"
  • existing_docs: "none"
  • team_size: "15"
  • tools_used: "SharePoint"

Follow-up prompts

  • How can we ensure our documentation meets industry regulations?
  • What are common pitfalls to avoid when documenting recovery procedures?
  • Can you suggest a format for tracking changes to our documentation?