Building Security Readiness Before a Crisis

Readiness is decided long before the event, and mostly by decisions that did not feel like readiness decisions at the time. Who held which key. Whether the procedure was ever read aloud. Whether the monitoring contract specified a response or only a notification. Whether anyone had written down which of two people decides.

This piece is about the difference between a plan and a document, and about which parts of readiness can usefully be established in advance.

The document problem

Nearly every organization and most well-advised families have an incident document. Very few have a practiced procedure. The two are frequently confused because they contain the same words.

A document becomes a procedure through three transformations, none of which happen automatically.

It has to be held by the people who would execute it, in a form reachable under the conditions where it would be needed. A response plan stored on a network drive is unavailable during exactly the class of event that makes it relevant. A plan held only by the person most likely to be traveling is similarly conditional.

It has to be short enough to act on. The useful part of an incident plan is the first ten minutes, and the first ten minutes fit on one page. Everything after that benefits from deliberation and does not need to be memorized. Plans that attempt completeness produce documents nobody reads, which is functionally identical to having none.

It has to be rehearsed at least once. Not extensively — once is disproportionately valuable compared to zero. A single walkthrough reliably surfaces the assumptions that reading does not: that a phone number is out of date, that the named person has left, that two people each believed the other would make the call, that the procedure requires information nobody has access to at that hour.

A plan that has never been spoken aloud is a hypothesis. The rehearsal is the experiment, and it fails cheaply.

What can be decided in advance

The value of preparation lies almost entirely in decisions that are hard to make well under pressure and easy to make well in advance. Three categories matter most.

Authority. Who decides, and who decides when that person is unreachable. This is the single most valuable thing to settle beforehand and the one most often left implicit. Under pressure, ambiguous authority does not produce a thoughtful discussion; it produces delay while everyone waits for someone else, or it produces two contradictory actions.

Thresholds. What conditions change the posture, and by how much. Deciding in advance that a particular category of contact triggers assessment, or that a specific condition suspends travel, removes the hardest judgment from the moment when judgment is least reliable. Thresholds are also what allow a program to respond proportionately rather than either over-reacting to everything or normalizing a slow escalation.

Contact paths. Who is called, in what order, through what channel, and what the alternative is when the primary channel is unavailable. This is clerical work with an unusually high return, and it decays quickly — numbers change, people leave, providers reassign accounts. A contact list that has not been verified within the year should be assumed wrong.

What cannot usefully be pre-decided

Preparation has limits, and pretending otherwise produces plans that are ignored the first time reality diverges from them.

Specific tactical responses generally cannot be scripted, because the useful response depends on details that are unknown in advance. A plan that specifies exactly what to do in a situation it cannot anticipate will be discarded at the moment of use, and discarding one part of a plan tends to discredit the rest.

Attempting to enumerate scenarios is similarly unproductive past a small number. The set of possible events is unbounded; the set of useful responses is small. Planning against a handful of response modes — evacuate, shelter, verify, escalate, notify — covers far more ground than planning against a long list of imagined events.

And the emotional reality of an actual event cannot be planned around. It can only be made less consequential by reducing how many decisions have to be taken in that state. Which is the argument for pre-deciding authority, thresholds, and contacts, and for keeping the first-ten-minutes page short.

Readiness is mostly maintenance

The uncomfortable observation is that most of the work of readiness is not planning. It is keeping ordinary things current.

An access register that reflects who actually holds access. A contact list that has been verified. A property record that matches the systems actually installed. Monitoring arrangements that specify a response rather than a notification. Staff who have been told what the procedure is, including the ones hired since it was written.

None of this is interesting, and none of it feels like preparing for a crisis. It is nevertheless what determines whether the response is competent, because a response executes against the state of the program as it actually is, not as the plan assumes it to be.

This is also why readiness cannot be established in a project and then left. A program that was ready two years ago and has not been reviewed since is not ready; it is a program with an out-of-date claim about itself.

The test worth applying

There is a single diagnostic that separates programs that are ready from programs that believe they are.

Ask someone who would plausibly be first to know — a member of household staff, a site supervisor, a duty manager — what they would do, and who they would call. Do not ask the person who wrote the plan.

If the answer is immediate and correct, the program is ready. If the answer is "I'd find the document," it is not, and no amount of additional planning changes that. If the answer names a person who no longer holds the role, the plan has been on paper long enough to have gone stale.

That test takes two minutes and it is more informative than reviewing the document, because it measures the only property that matters: whether the preparation reached the people who would have to act on it.

Everything else in readiness is downstream of that.