The recovery exercise was skipped to save time. How should I report readiness?
Unverified recovery readinessReport the exercise as not performed and explain which recovery assumptions remain untested. Agree a safe test or a justified launch limitation with the accountable owner. Do not convert a planned exercise into completed assurance because the launch date is close.
What to do now
- List untested recovery assumptions
- Assess their operational consequences
- Arrange a safe exercise or launch limitation
- Record the actual evidence and decision
When to escalate
The service's required recovery capability remains unproven at launch.
The service owner and authorized operational decision maker
Example
A limited pilot is approved while the full-service restoration exercise is scheduled and owned.
Mistake to avoid
Marking recovery ready because a procedure exists on paper.
Prevent a repeat
Test whether receiving teams can operate and recover the service without depending on informal project-team support.
Suggested ApprovedFlow setup
- Tasks
- Documents
- Approvals
Keep handover tasks, operating evidence and the acceptance decision linked to the project while retaining monitoring and incident control in the actual service tools. See the platform
Related cases
- We are replacing an old service. When can we switch it off?Unverified retirement readiness
- Business data errors continue after launch. Who should fix them?Undefined operational data ownership
- How do we report forecast changes over time?Lost forecast history
- Training attendance was high, but users still cannot finish tasks. What now?Training activity mistaken for readiness