Contingency Planner is the tool for what the risk register only points at: what you actually do when a risk realises. One plan per risk — scenarios, numbered response steps, owners. The tracker writes itself, and the Status Board shows in one screen what's confirmed and what's still a gap.
One sheet per plan. A tracker sheet at the front, maintained by hand. It was serious work by serious people — and the tool fought them the whole way.
A file you may recognise
Every plan in it was written by someone who knew exactly what to do. The workbook just couldn't say it out loud when it mattered.
The thinking was never the problem. The workbook was. Keep the discipline, replace the tool.
A contingency plan system with an engine. Each plan holds the header an authority expects — lead function, responsible manager, decision owner, communications lead, impacted functions, stakeholders — plus the fields that make a plan real: an activation trigger ("stand at 90% and 500+ ticket holders inbound"), the first 15 minutes, key contacts, resources, stand-down criteria. Per scenario, the numbered response steps: who does what, in what order, under which procedure. The tracker and the readiness numbers compute themselves from the plans.
Start from your risk register: paste its rows and every risk becomes a plan stub with its ID, title, lead and owner carried over. Or start from the plan library — the classic event contingencies, pre-drafted with scenarios and steps.
The structure follows contingency plans used from Olympic winter venues to the Lahti 2017 World Championships — including one that was activated on a sold-out Saturday, and held.
| ID | Plan — what has happened | Activation trigger | Lead | Steps | Readiness | Status |
|---|---|---|---|---|---|---|
| 14 | Venue parking runs out on peak day | 85% fill, arrivals at forecast | Transportation | 7 | Ready | Confirmed |
| 16 | Below −20 °C on competition days | 07:00 reading −20 °C or below | Operations | 3 | Ready | Under review |
| 36 | Stands full while ticket holders arrive | Section at 90%, 500+ inbound | Security | 7 | Ready | Confirmed |
| 39 | Sales and payment systems go down | POS down > 10 min venue-wide | Sales | 2 | 1 gap | In progress |
| 62 | Air traffic disruption delays teams | — | Transportation | — | 3 gaps | Open |
The overview is generated from the plans — plan count, scenarios, steps, status, readiness. There is no second sheet to maintain, so it cannot go stale.
Response steps renumber themselves when you add, remove or reorder. The chain someone reads out on the radio always matches the chain on the screen.
Paste rows straight from Risk Register's Excel export — or any list. Each risk becomes a plan stub with its ID, title, lead and owner carried over. Plan 14 answers risk 14.
Parking full, power out, stands at capacity, workforce no-show — 16 plans pre-drafted with scenarios and response steps from real events. Add one, then make it yours.
A plan is ready when it has an activation trigger, a decision owner, a lead, a responsible person, a scenario and steps. Gaps are flagged and counted — and plans nobody has reviewed in 90 days flag themselves stale.
Any plan prints as the classic A4 contingency sheet — header, scenarios, numbered steps. The tracker prints A3 landscape. View-only links for the steering group, no accounts needed.
"Are we ready?" Full screen: plans by status, confirmed counts, the gap list. Click a status to see its plans. Toggle to gaps only and you're looking at the exact to-do list between today and event week.
Print it as an A4 status report for the board and the authorities. Twenty-two sheets never answered this question. One screen does.
The free test runs on a full example event — eight plans in different stages. Everything works, nothing saves. When you want your own plans saved and shareable, one payment.
Pairs with Risk Register: the register says what might happen, the planner says what you do when it does. Three tools in the toolbox — any three for €199.
No. Contingency Planner runs in the browser — laptop, tablet or phone. Your events save automatically to your account.
Yes, by design. Export your register to Excel/CSV, paste the rows into 📋 Paste risks, and every risk becomes a plan stub with the same ID, title, lead and owner. It also takes any plain list, one risk per line — you don't need Risk Register to use it.
No. You send a view-only link — the tracker, or the Status Board directly. Or you print: any plan as the classic A4 sheet, the whole tracker as A3 landscape.
No. Paste the tracker list to create the plan stubs in one go, then move each plan's steps over as you review it — the review was due anyway, and this time it sticks.
Then the event went well. Most plans are never activated — you will probably never look at them again. Write them anyway: the one time a plan is needed, it is needed in minutes, by name, with numbered steps.
The full tool on an example event with eight plans. Open them, edit steps, check the Status Board, print a plan sheet. Nothing saves — 100 people can test at once and never see each other's changes.
Two minutes in the demo tells you more than this page can.