Set RTO and RPO tiers for your systems
Leadership wants recovery targets and you need a defensible way to set them system by system.
- You get
- A tier table with RTO, RPO, backup method and business reason, ready for your DR plan.
- Works in
- ChatGPT
- Claude
- Copilot
- Gemini
Fill in the blanks
A few words each is enough. Leave a blank empty and the assistant will ask you or assume.
Describe, don't paste: no CUI, personal data, hostnames, IP addresses or credentials. What you type stays on this page until you copy it or open it in an assistant.
Your prompt0 of 1 filled
Help me set recovery time objectives (RTO) and recovery point objectives (RPO) for our systems. Our systems: [List each system: name, purpose, who uses it, and what happens if it's down for a day] Put identity, DNS, networking and the backup system itself in a Tier 0, since everything else depends on them. Group the rest into three tiers. For each tier give an RTO, an RPO, the backup frequency and recovery method that would meet them, and one sentence on the business reason. Then: - Challenge any system that looks over-tiered. - Flag any system whose RTO is shorter than the RTO of something it depends on. - Flag where a tier would be expensive to hit, and suggest a cheaper fallback. Present it as a table I can paste into our disaster recovery plan. Some details above are still in square brackets. Ask me for them before you answer, rather than guessing.
Before you paste
Most organizations put too many systems in Tier 1. Let it push back.
Then check the answer
Disaster recovery plan template
Drop the tier table straight in
More planning prompts
All 28 prompts- Check your backups against the 3-2-1-1-0 ruleYou want to know whether your backup copies would survive ransomware that goes after backups first.
- Plan and record a restore testYou need to prove backups actually restore, for yourself and for an assessor or insurer, not just that the jobs succeeded.
- Review your disaster recovery plan like an auditorYou have a DR plan, but it hasn't been tested or read critically in a while.
- Work out what Microsoft 365 doesn't back up for youSomeone asked "doesn't Microsoft back that up?" and you need a clear answer for your tenant.
- Check whether your AI data can be recoveredYour team uses AI tools, vector databases or agents, and no one has asked what happens if that data is lost or poisoned.
Want a person to check the answer?
AI gets you a first draft. A KELYN engineer can tell you whether it would hold up in an assessment or a real recovery.