A plan that has actually been rehearsed
Business continuity and disaster recovery planning, then a tabletop exercise that finds out whether the plan survives contact with a real scenario.
The challenge
Most continuity plans have never been tested. The first rehearsal usually reveals that the recovery time objectives were optimistic and half the contact details are stale.
Scope — included and not included
Included
- Business impact analysis
- Recovery objectives definition
- Continuity and recovery plans
- Tabletop exercise design and facilitation
- Exercise report with improvement actions
Not included
- Implementing backup or DR infrastructure
- Full failover testing, which is separate
- Ongoing plan maintenance unless retained
How it works
01
Business impact analysis
What stopping actually costs, per process, per day.
02
Write the plans
Continuity and recovery plans with realistic objectives.
03
Run the tabletop
A real scenario, half a day, leadership and operations at the table.
04
Report and improve
What broke in rehearsal, fixed with dated actions.
What you receive
- →Business impact analysis
- →Continuity plan
- →Disaster recovery plan
- →Tabletop scenario pack
- →Exercise report with dated improvement actions
- →Evidence pack for ISO 22301 or A.5.29 to A.5.30
What we need from you
- ·Participation from leadership and operations
- ·Existing plans if any
- ·Half a day for the exercise
- ·A named plan owner
Timeline and engagement
2 to 4 weeks. Fixed scope. Annual re-exercise recommended.
Standards, methods and tooling
ISO 22301ISO 27001 A.5.29–A.5.30Portal hosted in Canada
Frequently asked questions