Key Takeaways: The Run Sheet and the Production Book
The one thing
A timeline says what happens. A run sheet says who does it.
The difference is one column, and it is the difference between a document that describes a wedding and one that produces it.
A timeline is a description — nothing in it will fail visibly, because nothing in it is anybody's. A run sheet is an allocation, and a line with no name is immediately visible as a line that will not happen.
The ten claims
1. Five fields per line: time, a verb, a name, a cue, and an exception. The fifth is the one nobody includes. Every critical-path line gets one, every single point of failure, and every line whose failure is silent — because invisible failures are the ones a planner will not notice in time.
2. Names, not roles. At 1:40 p.m., "rentals" is four people in a field. A name can be found, and when the name is wrong the wrongness is visible. Where a name is genuinely unknowable: the company plus "lead, name on the day" and a blank filled in at 7:05.
3. Ten sections, tabbed, in order, and nothing else goes in. Contracts, budget, and correspondence stay in the car. A production book that is too thick does not get opened.
4. The contact sheet is sorted by arrival time, because at 8:10 you are looking for whoever should be here and is not. And every vendor has a second number, because a mobile in a field with no signal is not a number.
5. An escalation tree is finished when every branch ends somewhere. And one branch has no hierarchy at all: a guest who is seriously unwell means emergency services, immediately.
6. The emergency page is one page, printed twice, and somebody else knows where it is. It is the least likely page to be used and the worst one to be missing.
7. Design for 4:26 p.m. A5 · landscape · 11pt minimum · one hour per page · aligned time and name columns · ★ on cues · nothing in colour that matters · tabs findable by feel · a rubber band, not a clip · rain protection.
8. Three derived objects, and two get used more than the book. The pocket card (what you actually look at) · the A3 wall copy, which answers forty questions the planner would otherwise be asked · and the one-page vendor pack.
9. Four phases, four densities. A build written every thirty minutes hides a dependency; a reception written every five minutes is unreadable and mostly empty.
10. One source, eleven documents, generated rather than kept in step. Never edit a derived document — if a pack is wrong, the source is wrong. And the test is fifteen minutes: change one time, and hold eleven correct documents.
Threshold concepts
🚪 A timeline says what happens; a run sheet says who does it.
🚪 The page that no chapter owns.
Every section of a production book is the output of some earlier process — except the emergency page, which comes from nowhere. Which is exactly why it does not exist at most weddings, and it is the only section whose absence is invisible until the moment it is needed.
Anything that is nobody's obvious output has to be somebody's explicit job.
The vendor pack
One page: their tasks, plus what is before, what is after, and the next hard anchor.
A caterer who knows the toasts are at 20:15 knows what their overrun costs and will tell you they are running behind. A caterer who only knows "service 18:40" will absorb it silently.
Context converts an executor into a participant, and it costs three lines.
Building it
| −2 weeks | Chapter 24's confirmation loop and two-document comparison |
| −10 days | Chapter 25's re-derivation |
| −9 days | FINAL timeline issued |
| −8 days | Acknowledgements chased |
| −7 days | The run sheet — 3–4 hours, the longest single job |
| −6 to −4 | Packs, contact sheet, escalation tree, exceptions, emergency page |
| −3 days | The read-through, out loud, alone. Forty minutes |
| −2 days | Print. Two books, pocket cards, two A3 wall copies |
| Friday | The rehearsal changes things. Mark up in pen |
Not earlier than −7 days, because a book built at −3 weeks has three weeks of drift in it and feels finished.
And the read-through catches what scanning does not: a line with no owner · two lines at the same minute with the same person · a cue referring to something that moved · and a line you no longer understand, which means nobody else will either.
What this chapter added to the project
The book assembled: A5, 58 pages, ten tabs, rubber band, run sheet and emergency page in sleeves. Plus a pocket card, two A3 wall copies, a second complete book in the car, and eleven vendor packs.
And assembling it found things.
Eleven run sheet lines had no owner. Nine had been decided in an earlier chapter and never written where anybody would look for them. Two had never been decided at all — who receives 220 lb of ice, and who is the second person counting a bar inventory at 11 p.m.
A collision that had been in the plan since Chapter 15: the first ice delivery is at 1:00 and needs a four-hour chill; Ridgeline were arriving at 2:00. Their arrival moves to 1:00. $0, one call, and nobody had put the two times next to each other.
Four vendors had one number each — Trey, the photographer, the videographer, and the venue. Trey is the worst of them: one person, one mobile, four starred cues, at a site with no signal in the meadow. One email; three replied within a day.
Section 8 was partial. Chapter 13's strike plan predates eleven chapters of additions — 232 empties, 300 stems of green waste, unopened alcohol, a cake stand, and a bouquet, four of them unassigned and three of them somebody's property.
And section 10 did not exist. Twenty-five chapters and no emergency page — not because anybody decided against one, but because no chapter owned it. Chapter 9 did permits, Chapter 29 will do accessibility, and the one page that matters when somebody is unwell fell between them.
Written in twenty minutes. Satnav warning, what3words, two hospitals, a named first-aider, four guests' medical facts including Marisol Vega's auto-injector and where it is, next of kin, and the nearest landline.
And the generation test came in at fourteen minutes, inside the fifteen-minute standard — including the bar's pack, which changes because the toast pour moves with the toasts, which move with dinner.
What is still open
| Finding | Goes to |
|---|---|
| The videographer's second number and the venue's out-of-hours number — outstanding at −6 days | On the exceptions page as known gaps |
| The named first-aider — identified, not confirmed | Ch.29 |
| The rain variant's four-person crew — named, not told | Ch.28 |
| The strike assignments — provisional | Ch.30 |
| Nadine Hollis is on the emergency page and nobody has spoken to her | Ch.29 |
Spaced review
From Chapter 25: the distribution matrix decided who gets what; this chapter decides what the object is — and adds that the packs are generated from a single source rather than kept in step with it.
From Chapter 24: an unassigned task is an unhappened task. A run sheet enforces it by having a column that is visibly empty — the instrument does not solve the problem, it makes the problem findable, which is the same mechanism as Chapter 25's audit.
From Chapter 24: cues rather than a running order. Most starred lines have no clock dependency at all — the time tells the planner whether the day is on plan; the cue is what fires it.
From Chapters 14 and 18: a failure that produces no complaint produces no scar. Case Study 26.1's book was never opened and nothing went wrong, which is why the planner did not notice for four weddings.
Before Chapter 27
Chapter 27 is the day itself — real-time problem solving, the decision protocol, and being invisible.
Bring the book. Chapter 27's argument is that a planner's attention is the day's scarcest resource, and this chapter's entire purpose was to spend less of it on remembering things.