
Sector | County council, name withheld |
Scope | 14 department heads |
Programme | Two tabletops, TX-01 format |
Duration | 2 half days |
Result | 11 plan gaps, each with an owner |
Written for the client's leadership. The client's name and staff names are removed from this copy.
A county council had an incident plan written three years ago. Nobody had tested it, and half the people named in it had since moved jobs.
Theo Ashworth read the plan and wrote two scripts of five injects each. Clara Voss facilitated both half days with 14 department heads, out loud, with the people who would decide on the day.
Eleven gaps went on the list, each with an owner and a date to test it again. The second session tested the fixes to the first.
From the programme record. Each tabletop ran two hours.
When | Step | By | Outcome |
Week 1 | Incident plan read, one call with the chief executive's office | Theo Ashworth | Done |
Week 2 | Script 1 written: five injects, a ransomware morning | Theo Ashworth | Done |
Week 3 | Tabletop 1 with 14 department heads | Clara Voss | 7 gaps |
Week 6 | Script 2 written around the fixes | Theo Ashworth | Done |
Week 7 | Tabletop 2, same room | Clara Voss | 4 gaps |
After the programme | |||
Week 8 | Gap list with owners and test dates | Clara Voss | Delivered |
Month 6 | Retest booked for the open gaps | Client | Booked |
Gap | Owner | Retest |
No named lead for resident messages | Comms head | Month 2 |
Payroll fallback relied on one person | Finance head | Month 3 |
Phone tree out of date | IT head | Month 1 |
No order for bringing services back | Chief exec's office | Month 4 |

In the room | 14 |
Injects | 10 |
Gaps found | 11 |
We found out who would answer the press in a quiet room, not on the morning it happened.
One named lead for resident messages
A written order for bringing services back
The plan reviewed every spring