Published September 13, 2026. Reading estimate uses 200 words per minute; completing the worksheet takes additional time.
Define recovery beyond a restart
A restart can restore a process without establishing that the appliance has returned to an accepted state. A recovery exercise should identify what must be restored, which boundaries must remain intact, and who decides the system may resume its intended work.
Choose a bounded scenario that can be exercised safely in the approved environment. State the starting baseline, dependencies, expected outcome, and stop conditions. Do not improvise destructive tests in a production environment because a checklist mentions recovery.
Separate the exercise clock from the claim
Record a clear start event and end event before measuring duration. “Time to recover” is ambiguous if one team stops the clock when the process starts and another waits for operating checks and approval. Break the timeline into events that a reviewer can interpret.
Retain the observation method, units, and missing observations. A single exercise is evidence about that scenario, not a service-level guarantee or a statistically meaningful reliability claim. If you publish a result, its scope and limitations should travel with the number.
Observe people and dependencies as well as systems
The exercise should reveal whether required contacts are reachable, authority is understood, dependencies are available, and the written sequence is usable. A technically correct procedure that depends on an unavailable approver is still an operating gap.
Record deviations as they occur. Distinguish an expected pause from an unexpected failure, and note any manual intervention outside the documented procedure. Do not erase those details from the final timeline merely because the system eventually resumed service.
Make return to service a separate decision
After restoration, verify the agreed baseline and work boundaries, reconcile evidence, and obtain the required approval. If a condition is not met, record the restriction or remaining work rather than assuming successful startup means full recovery.
Use the record below for preparation and observation. Put sensitive logs in the approved evidence store and reference them from the worksheet. The goal is an understandable sequence and an owned improvement list, not a public disclosure of recovery secrets.
Your working record
Adapt these criteria to the engagement. The CSV includes blank evidence, status, owner, and review-date fields. Nothing is pre-marked as passed. Scroll the table horizontally on small screens.
| Record | Detail to capture | Acceptance check |
|---|---|---|
| Scenario and baseline | Approved scenario, exact system profile, dependencies, and scope. | Exercise is safe and explicitly authorized. |
| Start event | Timestamp, time zone, event definition, and observer. | The clock begins at the agreed event. |
| Restoration observations | Events, timestamps, procedure references, and interventions. | A reviewer can reconstruct the sequence. |
| Validation | Baseline and work-boundary checks after restoration. | The agreed acceptable state is demonstrated, not assumed. |
| Return to service | Approver, decision, restrictions, and end timestamp. | The end event includes the required approval. |
| Deviations | Unexpected behavior, impact, evidence reference, and owner. | Each deviation has a disposition and follow-up criterion. |
Worked example: interpreting a recovery timeline
Illustrative data—not a RookHaven benchmark: an exercise starts at 10:00, the appliance is reachable at 10:12, validation completes at 10:20, and the owner authorizes return to service at 10:24. Reachability took 12 minutes; the agreed start-to-approval interval took 24 minutes. Calling both “recovery time” would hide a meaningful difference.
The worksheet should retain all four events and the agreed end condition. If the exercise target was return-to-service approval within 20 minutes, the observed 24-minute interval did not meet that target, even though the appliance was reachable earlier. The follow-up is to examine the delay and repeat an approved exercise—not to change the target after seeing the result.
Source context & further reading
Further reading on recovery planning and improvement. The exercise and example on this page are illustrative, not measured product results.
Use this planning aid alongside an approved engagement scope and qualified review. Illustrative examples are not customer results or product test evidence. The actual agreement determines permission, responsibilities, and acceptance.