
A recovery plan can look complete on paper and still stall because of a missing password, unavailable contact or undocumented dependency. A structured drill reveals gaps while there is time to address them calmly.
Practise before an incident
- Scenario and roles
- Recovery in a separate environment
- Measure and close gaps
Start with a scenario and boundaries
Choose a defined scenario: server failure, loss of site access or suspected ransomware. State which systems are included, the drill’s objective and permitted actions. In production, set a window, approvers and stop conditions so the test does not become an outage.
Practise decisions first
In a tabletop exercise, discuss the scenario without changing systems: who detects it, who decides, who communicates with employees and the sequence of actions. Check what happens when the administrator is unavailable too. The aim is to expose ambiguity, not simply read the document aloud.
Test recovery in a separate environment
Then practise technical recovery to an isolated location. Check data, applications, permissions and dependencies. This may reveal the gap between successfully copying files and restoring a service people can actually use.
Compare objectives with reality
Compare the recovery time and recovered data point with RTO and RPO objectives. Record successes, delays and who needed to help. A result slower than the target is useful planning information, not a reason to hide the test.
Turn gaps into tasks
- Assign an owner and deadline to every gap.
- Update instructions, contacts and required equipment.
- Retest the part that changed.
For background: Disaster recovery plan.


