The preparedness cycle: from knowing your ground to changing it

Emergency planners have drawn preparedness as a circle for decades. UK guidance describes integrated emergency management as six related activities: anticipate, assess, prevent, prepare, respond and recover. Sinkaos uses a finer loop with ten stages, because the work a team leader actually does between two operations is more varied than "prepare".

• KNOW. The area, sites, buildings, hazards, people and kit as they are today.
• PREPARE. Preplans, contingencies and checklists written before anything happens.
• PLAN. A specific operation: sectors, routes, roles, tasks, and a plan B.
• RESOURCE. The right people with valid qualifications, and kit that works.
• TRAIN. Exercises built from real plans, at real sites.
• EXECUTE. The operation itself.
• ADAPT. Switching to the prepared alternative when conditions change.
• LEARN. The debrief: what was planned, what happened, and why they differ.
• CHANGE THE WORLD MODEL. Findings go back into what the team knows.
• REPEAT. The next operation starts from there.

The world model is the team’s shared picture of its ground, kept between operations: maps and floor plans, access routes and hazards, cameras and sensors, who is qualified for what, and which kit is ready. In most organisations it is spread across a shared drive, a spreadsheet of contacts, a few laminated maps and the memory of two experienced people.

Every stage of the loop reads from it. A plan is only as good as the map it was drawn on; a roster is only as good as the qualification records behind it. That is why the ninth stage writes back to it.

They break between LEARN and CHANGE. The debrief happens, a report is written, and the findings sit in it. JESIP calls this the gap between lessons identified and lessons learned, and runs Joint Organisational Learning (JOL Online) so that UK responders can show their lessons were acted on. Inquests and inquiries now ask exactly that.

A lesson is learned when something a person will use next time is different: a hazard marked on the map, a step added to a preplan, a drill added to the training calendar, a spare added to the kit list. If nothing in the world model changed, the next operation starts from the same place as the last one.

1. 01
   Know

   The fair field, its three gates, the river path, the first aid post and the six radios the council owns are already in the atlas from last year.
2. 02
   Prepare

   The council’s event safety plan has a contingency for a lost child and one for a thunderstorm, each with its own checklist.
3. 03
   Plan

   The organiser splits the field into four zones, assigns stewards and marks Gate 2 as the fallback exit.
4. 04
   Resource

   Two first aiders’ certificates expire before the fair. The roster flags it and two others are booked.
5. 05
   Train

   Stewards walk the lost child procedure on the field the week before.
6. 06
   Execute

   On the day, reports, tasks and positions sit on one map. Signal at the river end is poor, so phones queue reports and send them later.
7. 07
   Adapt

   A storm warning comes in at 15:40. The thunderstorm contingency goes out and Gate 2 opens.
8. 08
   Learn

   The replay shows Gate 2 took eleven minutes to open because its padlock key was with the wrong steward.
9. 09
   Change the world model

   The key holder becomes part of the Gate 2 record, the opening step is added to the contingency, and a key box is added to the kit list.
10. 10
    Repeat

    Next year’s fair starts from that version, and so does the Christmas market on the same field.

Sinkaos keeps the world model as a persistent atlas and uses it at every stage: plans and exercises are drawn on it, rosters and mission packs come from its records, the operation runs on it offline, and findings from the debrief are written back to it with an owner. See Sinkaos for council emergency response or the glossary entry on the world model.