- Published
- Last reviewed
A backup can be restored while the service is still unavailable. The files may be intact, yet the staff who need them cannot sign in, or nobody can authorise a return to normal operation. Rehearse the work that needs to resume.
Imagine a property maintenance team taking urgent repair requests by phone while its scheduling system is down. The dispatcher can log a new call but cannot see which jobs already have a team assigned.
Agree what counts as recovery
Bring the service owner, the person who runs the work, and the provider responsible for recovery. Agree the longest tolerable interruption, how much recent work can be reconstructed, and which decision a deputy can make if the owner is unavailable. In this example, recovery means a dispatcher can identify open jobs, allocate a new one, and reconcile requests taken by phone without sending two teams to the same address.
Separate the discussion from the restore
A tabletop is a discussion exercise. Use it to rehearse the first call, the switch to manual handling, and who can approve restart. If the decision also requires proof of recovery, agree a separate, authorised restore in an isolated environment using synthetic records. Have the service owner witness the agreed work and record elapsed time, including any wait for access or approval.
Give the next exercise a purpose
Record the result as demonstrated, missed, or not established under the conditions tested. If the team discussed how to restore access but never tried it, mark that step untested. Give the gap an owner and a retest date. If a recent exercise already answered the decision, review that result before commissioning another.
DDAI view: The useful result is knowing which part of the service can resume, who can authorise it, and what remains uncertain.