Disaster Recovery Plan Outline
Define recovery objectives and procedures.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Draft a disaster recovery plan outline for [SYSTEM_NAME]. Business criticality and acceptable downtime: [CRITICALITY]. Data loss tolerance: [DATA_LOSS_TOLERANCE]. Architecture overview: [ARCHITECTURE]. Backup methods now: [BACKUPS]. Translate my tolerances into recovery time and recovery point objectives, and compare three strategies (backup and restore, pilot light, warm standby) in a table of RTO, RPO, cost direction and complexity. Recommend the one my numbers support. Write the sections of the plan: scenarios covered, roles, decision authority, restoration steps in order with dependencies, communication plan, and testing schedule with success criteria. Include a test plan for a restore drill with measurable outputs. Make clear what is unknown and must be tested rather than assumed. Add a table that maps every system component to its recovery order and dependencies, so that restoration can follow a sensible sequence. Include a communication template for stakeholders at three moments (declaration, update, resolution) and a section on third-party dependencies and what to do if a provider is itself down. Close with a one-year testing calendar. Add a worked recovery-time budget for the recommended strategy. Break the recovery into steps (declare, provision, restore data, repoint traffic, validate), give a time estimate range for each step taken from my inputs or marked as a placeholder to measure, add them up, and compare the total with the recovery time objective, saying plainly if it does not fit. Add a section called What We Do Not Know with the five assumptions most likely to be wrong, each paired with the test that would settle it. Include a decision record explaining why the two strategies not chosen were rejected, a table of dependencies on people (who can restore, who can approve, their backups), and a rule that the plan is considered untested until a full restore drill has met the target once. End with an annual calendar of tests, one tabletop and one partial restore at least, each with the success criterion and the person who signs off the result.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.