Key Takeaways: Crisis Management

The one thing

A crisis is a decision made under worse conditions than usual.

Same triage, same sixty seconds, with less information, more noise, and somebody standing in front of you.

Which means the preparation is the same preparation — and almost everything in a crisis was either answered by a document in month six or was never going to be.

The ten claims

1. Three kinds: answered already · needs a decision now · cannot be solved. The commonest error is deliberating about a type 1. The most damaging is treating a type 3 as a type 2, which is a planner trying to project-manage a grief.

2. A rain plan is five things, not a sentence. The alternative specified · a decision deadline set by the physical work, backward · a named decider · the evidence · and a crew of four, named, told in advance, probably not used. The crew is always the missing one.

3. The point of no return is a time, not a judgment — and if the evidence at the deadline is genuinely 50/50, you take the indoor option. Wrong indoors is a wedding in a barn on a dry day.

4. The decider should not be the couple, and almost every couple agrees with relief. The authority is real and revocable: "if either of you feels strongly, ring me in the next ten minutes."

5. Build the playbook by substitutability, not by scenario. A scenario playbook is infinite; a substitutability playbook has four rows and category D is four entries long: officiant, caterer, venue, power.

6. An unanswered phone at T−90 is treated as absent and the response is started — because starting is reversible and waiting is not. Standing two caterers down at 4:12 costs an apology.

7. Reduce the problem. You are not replacing a three-course dinner. You are feeding a hundred and fifty people something, tonight.

8. Medical has no hierarchy. If it might be serious, call emergency services before checking, before finding family, before asking — and send somebody to the gate, because an ambulance will not find a track.

9. You cannot fix a family, and believing you might is how planners end up in the middle of something that predates them by thirty years. You can separate people, remove an audience, buy time, and protect the couple's day.

10. Some crises cannot be solved. Attend to the person · remove the audience · take the logistics off everybody, which is the actual service · let the couple decide what the day does · then run the wedding.

Threshold concepts

🚪 A crisis is a decision made under worse conditions than usual.

🚪 A crisis costs you the thing it is not about.

The second-order failure — the sweep that did not happen, the guest who was not met — is what people actually remember, and it is invisible because nobody can see an absent action.

Which produces the rule: the first thing you do in a crisis is say out loud what you are dropping.

🚪 In safety, the planner's authority is larger than their contract.

Nothing grants it. You have it anyway — and it is only usable if you decided in advance that you would use it. Nobody improvises courage at 9:40 p.m.

🚪 A capacity is a number about an activity, not about a room.

The barn seats 89 for a dinner and holds 211 for a ceremony, and it was carrying the wrong one for eighteen chapters.

The ten minutes

When a vendor has not arrived:

0–2 call, second number, office — establish late versus absent · 2–4 tell the venue · 4–6 two other suppliers, for whatever they can send · 6–8 secure the bar and anything edible · 8–10 tell the couple.

And then reduce the problem.

Telling them

Reassurance (if true) · the fact in one sentence · what has been done · what you need from them.

Never in reverse. "There's been an incident" takes forty seconds to reach the reassurance, and those are forty seconds of a person imagining the worst thing.

And the fourth clause's limit: it is about problems, not people. Anything that has happened to a person is told. Anything that has happened to a plan is not.

What this chapter added to the project

Eighty-nine was never the number.

The barn seats 89 for a dinner — twelve square feet a head, at rounds — and the barn was never going to serve dinner. Dinner has been in the tent since Chapter 13.

A ceremony is six square feet a head, the chairs sit on the dance floor, and the barn holds 211.

The finding survived eighteen chapters and three audits because it was never wrong. Every document agreed, because all of them were copies of one line. An audit finds contradictions; it cannot find a consistent error. Only re-derivation catches it, and no instrument in this book does that automatically.

And with the capacity question dissolved, the real hole was visible: the rain plan was a room and was never a schedule. At 5:02 a hundred people stand up in a barn full of chairs with nowhere to go for eighty-eight minutes.

Rebuilt: ceremony in the barn on the uplighters with the festoon dark, so the 7:20 cue survives · cocktail hour in the tent · dinner forward to 6:00 · barn reset during dinner · dancing at 8:00 · 10:30 unchanged.

The crew was three wedding guests and an assumption. Two hands from Wildrye — $40 retained, $120 if used. Danny and Tomás stay, second.

The deadline recomputed to 1:45 and the planner kept 1:25, spending the twenty minutes on margin rather than on forecast.

Three new findings, at −3 weeks, in a project audited three times: the officiant's permission runs to a named priest (Fr. Emmanuel Rusike, confirmed) · there is no backup caterer in September, and the floor is two restaurants and $2,200–3,500 · Tomás is the gate runner and on the rain crew, so Beatriz is the alternate.

**Contingency: $888.69**, with $120 earmarked.

And the book kept its promise. Harvest & Thyme had double-booked and had known for nine days. A restaurant eleven miles away sent its entire evening service in three cars; 150 people ate at 7:15; $2,890 against $8,400 never paid. They danced until one.

The two things that planner got wrong — no second phone number, and telling the couple seven minutes later than necessary — are what this book has been correcting ever since.

What is still open

Spaced review

From Chapter 27: the decision protocol's fourth clause, and its hardest limit. Problems, not people.

From Chapter 26: the emergency page — the address a satnav accepts, the what3words, and what a vehicle can and cannot reach. In the rain variant there are two what3words, and the ambulance access is better, not worse.

From Chapter 25: the cascade, which answers "is this a crisis at all?" in twenty seconds — and which, arriving from an unexpected direction, is why a plan written about one hour did not notice the hour after it.

From Chapter 12: the failure question, and its organised answer. Vetting effort belongs almost entirely in category D.

From Chapter 9: insurance, and the fact that a claim is decided by whether somebody wrote it down that night.

Before Chapter 29

Chapter 29 is guest experience and accessibility, and it opens with a finding this chapter produced and did not resolve.

Bring the containment sequence — and specifically item 3, taking the logistics off people. Chapter 29's argument is that most of what makes a wedding difficult for a guest is invisible to everybody except the guest, and that the fix is almost always to ask rather than to provide.