Chapter 26: The Run Sheet and the Production Book

"The palest ink is better than the best memory." — a Chinese proverb, widely quoted in several forms

Chapter Overview

At 4:26 p.m. the planner is holding a black A5 ring binder with a rubber band around it, and it is open at page eleven.

It is raining slightly. There is no table. The light is going. Somebody is asking a question about the cake and somebody else is asking about parking, and the binder is being held open with one thumb while the other hand does something else.

That object — its size, its weight, what page it falls open at, and whether it can be read at arm's length in poor light by somebody who is not calm — is the subject of this chapter.

Not the information. The object.

Chapter 25 produced a master timeline. This chapter turns it into eleven documents and one binder, and the central move is small enough to state in a sentence.

A timeline says what happens. A run sheet says who does it. Everything else follows from that column.

In this chapter, you will learn to:

• Convert a timeline into a run sheet with an owner against every line
• Assemble the production book's ten sections
• Build a contact sheet and an escalation tree that survive somebody being missing
• Design a document that works at 4:26 p.m. in bad light in one hand
• Decide what goes on paper, what on a phone, and what on a wall
• Keep eleven derived documents consistent with one source

🏃 Fast Track: If you have stage-management, AD, or event-production experience, skim §26.2 and read §26.1 (the owner column), §26.5 (document design under stress), and §26.7 (the single source problem) in full. §26.5 is the one that differs from ordinary document practice: it is about what a document does to somebody who is holding it while three people talk to them. Then do exercises B.2, B.4, and D.1.

📖 Standard: Everything. And build the artefacts rather than reading about them.

🔬 Deep Dive: Work case-study-02.md, which assembles the complete Reyes–Whitfield production book — and finds that two of its ten sections do not exist yet.

26.1 The Column

🚪 Threshold Concept: a timeline says what happens; a run sheet says who does it

The difference is one column and it changes the document's function entirely.

A timeline is a description. It can be read, agreed, and filed. Nothing in it will fail visibly, because nothing in it is anybody's.

A run sheet is an allocation. Every line has a name against it, and a line with no name is immediately visible as a line that will not happen.

Chapter 24's rule, stated as a document-design principle: an unassigned task is an unhappened task — and a run sheet is the instrument that makes unassigned tasks findable.

What a run sheet line contains

⚡ Quick Reference: five fields, and only five

Field		Example
Time		19:20
What	A verb. Not a noun	STRING LIGHTS ON
Who	A name. Not a role	Trey
Cue	What triggers it, if not the clock	Sunset — do not wait for a signal
Exception	What to do if it cannot happen	If Trey is not at the console — Planner, switch is taped, marked A

The fifth field is the one nobody includes and it is the reason this chapter exists.

⚠️ Common Pitfall: roles instead of names

"Catering to serve" · "Rentals to place tables" · "The bar team will handle it"

A role cannot be looked at. At 1:40 p.m., "rentals" is four people in a field and none of them has read anything.

A name can be found. And when the name is wrong — when Marco has been replaced by somebody else that morning — the wrongness is visible, which a role's is not.

Where a name is genuinely not knowable in advance — a rental crew lead, a bar shift — the entry is the company plus "lead, name on the day", and the run sheet has a blank to be filled in at 7:05 a.m. A blank that gets filled is a mechanism; a role is not.

The exception line

A run sheet without exception lines is a plan for the day going well.

It is one clause and it takes ten seconds: "if not — [what], [who]."

26.2 The Ten Sections

A production book is not a folder of everything. It is ten sections, in an order, and the order is what makes it usable.

⚡ Quick Reference: the production book

	Section	Why it is here
1	THE RUN SHEET	First, always. It is what you are holding it open at
2	CONTACTS	§26.3. The second-most-turned-to page
3	THE FLOOR PLAN AND THE SEATING CHART	Ch.11. Somebody will ask where table nine is
4	VENDOR PACKS — one page each, in arrival order	Ch.25's extracts
5	THE CUE SHEET — lighting, sound, music	Ch.18, Ch.22
6	THE PHOTO PLAN — timeline, family matrix, PEOPLE list	Ch.23
7	THE CEREMONY — order, readings, cues, restrictions	Ch.20, Ch.21, Ch.24
8	THE STRIKE SHEET	Ch.13, Ch.30
9	THE EXCEPTIONS PAGE — rain, a missing person, a failure	Ch.25's variants, Ch.28
10	THE EMERGENCY PAGE	§26.4. Last, and it should be the easiest to find

Ten sections, tabbed, in that order. Nothing else goes in.

⚠️ What does not go in

Contracts. They are a laptop problem, not a field problem. A one-line summary of any clause that governs the day — the curfew, the removal deadline, the alcohol condition — goes on the exceptions page. The contracts stay in the car.

The budget. Nothing about the day is a budget decision, and Chapter 27's protocol governs the two or three that are.

Correspondence. Anything that mattered has become a line on the run sheet.

And anything that has not been read since it was printed. A production book that is too thick does not get opened, and thickness is the enemy of use.

26.2a A Page, Worked

The four densities, shown rather than described. These are pages 2, 6, and 9 of a real book.

🕐 THE BUILD — page 2 of 11 (every 15 min, owner and predecessor on every line)

Time	What	Who	Cue / after	If not
07:00	ACCESS. Tent erection begins	Rentals — lead TBC 07:05	—	07:30: call mobile, then depot 555-0188
07:15	4 signs placed (lane, gate done Fri)	Danny	—	Planner
07:25	Cable ramps checked and re-taped	Danny	—	Planner. Tape in the van
08:00	Generator and distro	Rentals	—	4 hrs float
08:30	Restroom trailer	—	—	5 hrs float
08:45	(Hair and makeup begins — rental house)	—	—	Separate chain
09:00	Barn: festoon + 12 uplighters	Rentals	Before anything else in the barn	3 hrs float
09:30	Kitchen marquee, 20 × 20	Rentals	—	Sundown arrive 11:00
10:15	★ TENT COMPLETE			If late: everything below moves
10:30	Flooring begins	Rentals	After tent
11:00	Sundown arrive	Marguerite	Kitchen marquee ready
11:00	String lighting rig — 400 ft, 5 runs, 9 ft AFF	Rentals	After tent · ladders out by 13:15	If late: 4 runs not 5
11:30	Dance floor, barn	Rentals	After barn lighting	2 hrs float
11:45	★ FLOORING COMPLETE

Note what is on every line: a name or a stated float, and an exception on everything with zero slack.

🕐 THE CEREMONY BLOCK — page 6 of 11 (every 2–5 min, cue-driven)

Time	What	Who	Cue	If not
15:45	Ceremony PA tested, officiant present	Trey	—	Battery PA — spare batteries in the case
15:55	Windscreens on all 3 mics	Trey	—
16:20	Wedding party to the meadow head	Beatriz	—
16:24	★ Planner's hand raised	Planner	—
16:25	★ PROCESSIONAL — song 1	Trey	Planner's hand DOWN
16:26	Officiant walks	Rev. Castellanos
16:27	Sam + Dennis + Marie — half a step ahead		6-ft aisle. Do not level up
16:28	Party, in pairs
16:29	★ SONG CHANGE — Alicia enters	Trey	Party clears the head of the aisle
16:34	Welcome	Rev. C.
16:36	★ The moment for the room	Rev. C.
16:37	Reading 1 — Elena	Elena	He sits down. Do not wait to be introduced	Printed copy in book §7
16:39	Address	Rev. C.
16:44	Reading 2 — Tomás (3:10)	Tomás	Same cue	Printed copy in book §7 — NOT his phone
16:47	★ ROSA — blessing, from her seat, in Spanish	Rosa	Rev. C. turns to her
16:49	VOWS			Cards held by Rev. C.
16:53	Rings	Danny	Rev. C. says "the rings" and looks at you	Best man has spares
16:56	Pronouncement
16:57	★ RECESSIONAL — loud, immediately	Trey	The kiss
16:58	★ ROSA MOVED OUT FIRST	Elena	Recessional starts	Beatriz
16:59	★ THE EXIT SENTENCE	Rev. C.		Planner says it
17:00	Front row moved	Beatriz
17:02	Trays at the meadow gate	Ridgeline

Twenty-two lines in thirty-seven minutes, and almost none of them is clock-driven.

🕐 THE RECEPTION — page 9 of 11 (sparse, with clusters)

Time	What	Who	Cue	If not
18:32	Seated
18:34	Welcome — Manuel Reyes	Trey (MC)
18:40	Service — 13 min	Sundown
19:05	★ GOLDEN HOUR — 15 min, couple away	Photographer		If running late: skip. Do not delay the return
19:20	★★ STRING LIGHTS ON	Trey	Sunset. Do not wait for a signal	Planner. Switch taped, marked A, at the DJ table
19:35	Replenishment	Sundown
20:08	Bar closed — toast pour, 100 flutes	Ridgeline
20:15	★ TOASTS — Elena · Dennis · Marie	Trey (MC)	In that order
20:35	Cake cut — Bernarda's	Trey (MC)		Knife is in the barn, on the cake table
20:40	Barn festoon ON · 4 cocktail tables to barn	Danny	After the cake	Planner
20:45	★ FIRST DANCE	Trey
20:47	★ Floor opened DURING the song	Trey	Second chorus
20:45–21:05	★ NO PORTRAITS
21:00	★ ROSA — 5 min, not announced	Beatriz		Planner
21:10	Elena takes Rosa home	Elena
21:45	Late-night food	Sundown	Nothing that clears the floor
22:22	Festoon up / effects down 20%	Trey
22:30	★★ MUSIC AND BAR OFF	Planner		Not the DJ's decision

Eighteen lines across four hours, and five of them are clustered between 20:35 and 20:47.

🔄 Check Your Understanding

1. Why does the build page carry a predecessor column and the ceremony page a cue column?
2. On the reception page, three lines have "Planner" in the exception column. What do those three have in common?

Verify

1. Because they fail differently.

A build task fails when the thing before it has not finished. The useful information is what am I waiting for — so the column says "after tent," "kitchen marquee ready," "before anything else in the barn." It is Chapter 13's dependency graph, in a column.

A ceremony line fails when somebody misses a trigger. Nothing there is waiting for a predecessor to finish; it is waiting for somebody to say or do something. So the column says "he sits down," "the kiss," "Rev. C. looks at you."

And the deeper point: a build runs on clock plus dependency; a ceremony runs on cue almost entirely. A run sheet that uses one column for both is a run sheet that has not noticed. 2. All three are single points of failure where the failure would be silent.

The string lights at 19:20 — if Trey misses it, nothing breaks and the moment simply does not exist. Nobody would know it was supposed to. The cocktail tables at 20:40 — if Danny forgets, the floor has nowhere to put a drink and the cause is invisible (Ch.22). Rosa at 21:00 — if Beatriz misses it, an 88-year-old goes home and there is no photograph, and nobody finds out until a gallery arrives.

Which is the rule for exception lines: the critical path gets one because the failure is expensive; these get one because the failure is invisible, and invisible failures are the ones a planner will not notice in time to fix.

26.3 Contacts and Escalation

The second-most-turned-to page, and the one most often built wrong.

⚡ Quick Reference: the contact sheet

Column		Why
Company
The person who will be on site	By name	Not the account manager
Their mobile
A second number	The office, or a colleague	The field one that matters — a mobile in a field with no signal is not a number
When they are on site	Arrive and depart	So you know whether ringing is worth it
What they are responsible for	Three words

Sorted by arrival time, not alphabetically. At 8:10 a.m. you are looking for whoever should be here and is not.

The escalation tree

Who to call when the first person does not answer — and it is a different document from the contact sheet.

⚡ Quick Reference: the tree, for five things that can go wrong

	1st	2nd	3rd
A vendor has not arrived	Their mobile	Their office	The venue's contact — they may know
Something electrical fails	The rental company's on-site lead	Their out-of-hours number	The venue's own electrician, if there is one
A guest is unwell	Emergency services if it is serious — no hierarchy, no delay	The named first-aider	The couple's designated family contact
A weather decision	The planner. It is theirs (Ch.28)	The venue
A dispute the planner cannot settle	The couple's designated decision-maker (Ch.27)

And the rule that makes it work: every branch ends somewhere. A tree with a branch that ends in "then I don't know" has not been finished.

🚨 When It Goes Wrong: the number that was a mobile in a field

A tent company's on-site lead has one number and it is a mobile. At Wildrye Farm there is intermittent signal in the parking field and none in the meadow.

At 8:40 a.m. he has not arrived, and the number rings out.

The second number is the whole point. An office, a depot, a colleague — anything that is answered by a person who can find out where a truck is.

Collect it, for every vendor, at −4 weeks. It is one question in one email and it is the difference between knowing and waiting.

26.4 The Emergency Page

One page. Last in the book, and it should be the easiest thing in it to find — a coloured tab, a different paper, anything.

⚡ Quick Reference: what is on it

The venue's full address, including what a satnav needs	And what a satnav gets wrong
What three words / a grid reference / a pin	For an ambulance. A farm track does not have a house number
The nearest hospital, name, address, and drive time
Emergency services number	Obvious, and put it there anyway
The named first-aider and where the kit is	Ch.29
The venue's own emergency contact, out of hours
Any guest medical fact you have been told — an auto-injector, a condition — and where the thing is	Ch.14, Ch.29
The couple's next-of-kin contacts
Where the nearest working landline is, if the site has poor signal

✅ Best Practice: the page you hope stays closed

Print it twice. One in the book and one in your pocket, folded.

And tell one other person it exists and where. A planner who is the only person who can find the emergency page is a single point of failure on the one page where that matters most.

It takes twenty minutes to build and it is the least likely page to be used and the worst one to be missing.

26.5 Designing for 4:26 p.m.

The section that differs from ordinary document design, because the reader is not calm, not seated, and not alone.

⚡ Quick Reference: eleven rules

1	A5, not A4. It is held in one hand
2	Landscape for the run sheet. Times on the left, and the eye scans a row
3	11pt minimum, and 12 is better. It is read at arm's length in falling light
4	One hour per page, or one clear block. Never a page that breaks mid-block
5	Times in bold, in a column, aligned
6	Names in a second column, aligned — so the eye can find "who" without reading "what"
7	★ on anything that is a cue rather than a task
8	Nothing in colour that matters — it will be photocopied, and it is dark
9	Tabs that can be found by feel
10	A rubber band, not a clip. A clip fails in a pocket
11	And it survives rain. A plastic sleeve on the run sheet and the emergency page, minimum

⚡ And one convention that starts here and holds for the rest of this book: operational documents are in 24-hour time.

Chapter 25's timeline was a planning artefact and it was written in the hours people speak in — the ceremony at 4:25. A run sheet is not read, it is scanned, by somebody being spoken to — and 16:25 cannot be misread as 4:25 a.m. by a crew member at the end of a fourteen-hour day, where 4:25 can.

So: prose and client-facing documents in 12-hour, everything operational in 24-hour — the run sheet, the build schedule, the cue sheet, the emergency page, and the ceremony-hour sheet (Ch.40). From here on, that is what this book does.

🎤 From the Field

I changed three things about my production book after one wedding, and all three were physical.

The binder went from A4 to A5, because I had spent an evening holding an A4 folder against my hip like a tray.

The run sheet went landscape, because I kept losing my place vertically while somebody talked to me.

And I put a rubber band round it, because it had fallen out of a car and I spent four minutes in a car park at 6:50 a.m. picking up a wedding.

None of those is about information design. They are about an object being carried by a person who is doing something else.

The three derived objects

A production book is not the only thing on site, and two of its derivatives get used more.

⚠️ Common Pitfall: nobody puts anything on a wall

An A3 run sheet taped inside the kitchen marquee costs one print and answers about forty questions.

Every one of those questions would otherwise be asked of the planner, and Chapter 27's argument is that a planner's attention is the day's scarcest resource.

Print two. One in the kitchen, one where the crew break.

26.6 The Run Sheet, Section by Section

A wedding's run sheet is not one document — it is four, and they behave differently.

⚡ Quick Reference: the four phases

	Runs	Density	Governed by
The build	Access → 45 min before guests	Dense — every 15 min	Dependencies (Ch.13). Every line has an owner and a predecessor
The ceremony block	Guests → cocktail hour	Very dense — every 2–5 min	Cues (Ch.24). Almost nothing here is clock-driven
The reception	Cocktail hour → the last song	Sparse — every 15–30 min, with clusters	A mix. The clusters are the moments (Ch.22)
The strike	Last song → removal	Moderate	Dependencies again, in reverse

The commonest error: writing all four at the same density. A build written every thirty minutes hides a dependency; a reception written every five minutes is unreadable and mostly empty.

The cue column

Chapter 24 established that on the day nobody is holding a document. The run sheet is the exception — the planner is holding one — but everybody else is working from cues.

Which means the cue column has two jobs:

For the planner: what triggers this, so you know whether you are late.

For briefing: it is the sentence you said at the rehearsal, written down, so you can repeat it identically.

And note that three of those four have no clock dependency at all. The time is there so the planner can tell whether the day is running to plan; the cue is what actually fires it.

26.6a The Vendor Pack

One page, in their hand, on arrival — and it is the document that does the most work per word in the whole system.

⚡ Quick Reference: what is on one page

Their name and the planner's, with mobiles	At the top, large
Their arrival time and what must already exist	Ch.25 §25.7
Their tasks, with times
The three things around them	What is before, what is after, and the next hard anchor
Anything specific to them that is not obvious	The 32-inch doorway · the restriction · the do-not-play list
What to do if something is wrong	A name. Not "let us know"
And the date and version	Ch.25

Worked, for Sundown:

📄 SUNDOWN PROVISIONS — Reyes/Whitfield — FINAL, 10 Sept

Planner: [name] 555-0102 · Marguerite: 555-0173

You arrive 11:00. The kitchen marquee (20 × 20, outside the tent) is complete at 10:45. Power is from the generator — your stated draw is 2,900 W and we are close to capacity, so please tell me if anything changes.

17:07	Trays at the meadow gate — palomas and sparkling
18:32	Guests seated. Welcome at 18:34
18:40	Family-style service — 13 min. 13 rounds
19:35	Replenishment
19:55	Clear
20:15	TOASTS — please do not clear or serve during these
20:37	Cake and coffee — the cake is the family's, on the barn's cake table
21:45	Late-night food — hand pies, at the back of the barn
22:30	Bar and music stop. Venue condition

Specific to you: 32-inch interior doorway · the whole menu is nut-free (Marisol Vega, table 6, anaphylactic — plated portion, hand-delivered, confirmed at the table) · Yusuf Demir, table 8, chicken not pork · vegan vessel to tables 4, 9, 12 · Ines Reyes, table 3, plated coeliac portion.

12 vendor meals, after the guests and before the toasts.

If anything is wrong, find me. Not the couple.

One page. Everything they need and nothing they do not.

⚠️ Common Pitfall: the pack that is a shortened timeline

A pack that lists only the vendor's own tasks tells them nothing about whether a delay matters.

The three things around them are the whole point. 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.

26.6b Building It

The book is assembled in a specific order, at a specific time, and both matter.

🕐 The assembly, backward from the wedding

−2 weeks	Chapter 24's confirmation loop and two-document comparison	Before anything is written
−10 days	Chapter 25's re-derivation — every duration from its current source
−9 days	Master timeline FINAL issued, with the change summary	Ch.25
−8 days	Acknowledgements chased. Anybody who has not replied is called
−7 days	Run sheet built from the timeline — the owner column, the cues, the exceptions	The longest single job: 3–4 hrs
−6 days	Vendor packs generated. Contact sheet, escalation tree
−5 days	Cue sheet, photo plan, ceremony order, strike sheet assembled
−4 days	The exceptions page and the emergency page	§26.4
−3 days	Read the whole book, straight through, out loud	§"the read-through"
−2 days	PRINT. Two complete copies. Pocket cards. Two A3 wall copies	§26.9
−1 day	Vendor packs printed; one delivered by hand at the rehearsal
Friday	The rehearsal changes things. Mark them up in pen	Ch.24
Saturday 06:30	Anything marked up on Friday is re-checked. Blanks filled at 07:05

The read-through

Three days out, alone, out loud, start to finish. It takes forty minutes and it finds things.

⚡ What a read-through catches

A line with no owner	The single commonest, and it is invisible when scanning
Two lines at the same minute with the same person	Chapter 23 found one of these and it took twenty-three chapters
A cue that refers to something that was moved	"After the cake" — when the cake moved
An exception that names somebody who is not there at that time
A page break in the middle of a block	§26.5 rule 4
And a line you no longer understand	Which means nobody else will either

Out loud matters. Reading silently, the eye completes what it expects. Saying "at eight forty, Danny moves four cocktail tables from the tent to the barn" makes you notice that Danny is also handing over the rings at 16:53 — which is fine, and you noticed.

26.7 One Source, Eleven Documents

Chapter 25's versioning problem, one layer down.

The master timeline is one document. The production book contains a run sheet, eleven vendor packs, a cue sheet, a photo plan, and a ceremony order — all derived from it.

Change dinner by twelve minutes and six documents are wrong.

🚨 When It Goes Wrong: the derived document that did not get updated

The master timeline moves the toasts from 7:55 to 8:15 (Chapter 25).

What must change: the run sheet · the caterer's pack · the bar's pack (the toast pour moves too) · Trey's cue sheet · the announcement script · the photographer's pack.

Six documents, and it is the sixth that gets missed.

✅ Best Practice: the single source

One document is the source and everything else is generated from it. Not "kept in step with" — generated.

In practice	A spreadsheet or a table where each line is tagged with who it belongs to, and the packs are filtered views
Which means	A change is made once and every derived document is right
And when a change is made	Regenerate everything, reprint everything, and re-date everything — even documents whose content did not change, so nothing on site carries an old date
The discipline	Never edit a derived document. If a vendor pack is wrong, the source is wrong

And the test: how long does it take to change one time and have eleven correct documents in your hand? If the answer is more than fifteen minutes, the system is manual and it will fail on the Thursday.

The reprint rule

Anything printed more than 48 hours before the wedding is reprinted.

Not because it has changed — because you cannot be sure it has not, and a reprint costs four dollars.

🔄 Check Your Understanding

1. Why "generated" rather than "kept in step with"?
2. Dinner moves twelve minutes at −6 days. Which documents are wrong, and which one gets missed?

Verify

1. Because "kept in step with" is a task somebody has to remember to do, eleven times, under pressure, at −6 days.

Generation is a property of the system. If each line of one table is tagged with who it belongs to, the packs are filtered views — change the line once and every derived document is correct with no further action.

The test is fifteen minutes: change one time and have eleven correct documents in your hand. If it takes longer, the system is manual, and manual systems fail on the Thursday — which is exactly when the change arrives.

And the discipline that follows: never edit a derived document. If a vendor pack is wrong, the source is wrong — because a pack edited directly will be silently overwritten by the next generation. 2. Six are wrong: the run sheet · the caterer's pack · the bar's pack, because the toast pour moves with the toasts · the DJ's cue sheet · the announcement script · the photographer's pack.

The one that gets missed is the bar's, and the reason is instructive: the bar has no line at 18:40. Nobody thinks of the bar when dinner moves, because the bar is not doing anything at dinner.

But the toast pour is 100 flutes in the five minutes before the toasts (Chapter 15), and the toasts are downstream of dinner. A second-order dependency, in a different vendor's document, with no visible connection to the thing that changed.

Which is precisely what generation solves and what "keeping documents in step" does not, because keeping them in step requires somebody to have thought of the bar.

26.8 What Is on Paper and What Is Not

⚡ Quick Reference: paper, phone, or wall

	Where	Why
The run sheet	Paper, in the book. And A3 on two walls	Battery, glare, wet hands, and it must be readable by somebody who is not you
The pocket card	Paper, in a pocket
Contacts	Both. Paper in the book, and every number in your phone before the day	You will call from the phone and read from the paper
The emergency page	Paper, twice
Floor plan and seating chart	Paper	People point at it
Photographs of anything	Phone
Vendor contracts	Neither — in the car
The group chat	Phone, and it is not a document (Ch.24)
Anything you might need to send somebody	Phone

⚠️ Common Pitfall: the planner whose entire day is on a phone

It works, until: the battery, the signal, the rain, the glare at 4 p.m., and the fact that a phone cannot be handed to somebody.

The specific failure that matters most: at 4:26 p.m. somebody asks a question and you have to unlock a phone, find an app, scroll, and read — while they watch you. A binder falls open at the right page.

And there is a professional dimension. A planner looking at a phone reads, from six feet away, as a planner looking at their phone. A planner holding a document reads as a planner working. It is unfair and it is real.

Carry both. The phone is for calling and sending; the paper is for reading and showing.

26.9 Practical Notes

On building it. The book is assembled at −1 week and finalised at −48 hours. Not earlier — Chapter 25's re-derivation happens first, and a book built at −3 weeks is a book with three weeks of drift in it.

On the second copy. Print two complete books. One is yours; one is in the car or with an assistant. A production book that is lost at 9 a.m. is a wedding run from memory, and the second copy costs eleven dollars.

On handwriting on it. Do. The book is a working document and it should be marked up all day — a time struck through and rewritten, a name added, a note about who asked what. It is also, afterward, the single best input to Chapter 30's debrief.

On the couple's copy. They do not get one. Twelve lines (Chapter 25), on one card, and that is a service rather than a withholding.

On what a vendor does with their pack. Most will glance at it and put it in a van. That is fine and it is not a failure — the pack's job is to be available when they need to check something, and the one time in ten that it is consulted is worth the nine.

On the strike sheet. It is written when everybody is fresh and executed when everybody is exhausted, which is why it is the section most worth over-specifying. Chapter 30.

On after the wedding. Keep the marked-up book. It is the record of what actually happened, it is the best evidence you will ever have about your own estimates, and at some point somebody will ask you a question about that wedding two years later.

On the assistant's copy. If there are two of you, the second book is not a spare — it is a working copy, and the two of you should have agreed which sections each of you owns. Two people both trying to run everything is worse than one person running everything.

On what to write in pen on the day. Times as they actually happen, next to the planned ones. It costs four seconds a line and it is the only source of real duration data you will ever have — and Chapters 14, 20, 23, and 25 all rest on numbers that somebody, somewhere, wrote in pen on a run sheet.

On the book's weight. Ten sections, tabbed, in A5, is about sixty pages. If yours is a hundred and twenty, two of the ten sections have become filing cabinets — usually vendor packs (which should be one page each) and the ceremony section (which should be an order and a set of cues, not a liturgy).

🔄 Check Your Understanding

1. Why is the production book assembled at −7 days rather than −3 weeks?
2. What does the read-through catch that scanning does not?

Verify

1. Because a book built at −3 weeks is a book with three weeks of drift in it.

The order matters and it is fixed: Chapter 24's confirmation loop and two-document comparison at −2 weeks · Chapter 25's re-derivation at −10 days · the FINAL timeline at −9 · and only then the run sheet.

Every one of those steps changes something. A book assembled before the re-derivation contains durations that have since moved — and worse, it feels finished, which means the changes get patched in rather than regenerated.

And the counterweight: not later than −7 days either, because the run sheet is three to four hours of work and it needs the read-through, the printing, and a Friday. 2. A line with no owner, and two lines at the same minute with the same person.

Reading silently, the eye completes what it expects. A blank in a column is not a word, so it is not read; and two entries for the same person on different pages are never adjacent.

Saying it out loud forces the sentence to be complete. "At eight forty, [nobody] moves four cocktail tables" is audibly wrong in a way that a blank cell is not.

And the same-person collision is exactly what took this book twenty-three chapters to find — Elena as a signing witness at 5:08 and a photo wrangler at 5:10 — which a forty-minute read-through would have caught in a fortnight.

26.10 Summary

A timeline says what happens; a run sheet says who does it. The difference is a column, and a line with no name is immediately visible as a line that will not happen.

Five fields per line: time, a verb, a name, a cue, and an exception — and the fifth is the one nobody includes. Every line on the critical path gets one; so does every line with a single point of failure and every line whose failure is silent.

Names, not roles. A role cannot be looked at; a name can, and when the name is wrong the wrongness is visible.

Ten sections, tabbed, in order, and nothing else goes in. Contracts stay in the car. A production book that is too thick does not get opened.

The contact sheet is sorted by arrival time and every vendor has a second number, because a mobile in a field with no signal is not a number.

The escalation tree ends somewhere on every branch.

The emergency page is one page, printed twice, and somebody else knows where it is.

Design for 4:26 p.m.: A5, landscape, 11pt minimum, one hour per page, times and names in aligned columns, ★ on cues, nothing in colour that matters, tabs findable by feel, a rubber band, and rain protection.

Three derived objects, and two get used more than the book: the pocket card (eight times, four numbers) · the A3 wall copy, which answers forty questions the planner would otherwise be asked · and the vendor pack.

Four phases, four densities. A build written every thirty minutes hides a dependency; a reception written every five minutes is unreadable.

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 have eleven correct documents in your hand.

Paper for reading and showing; phone for calling and sending. And a binder falls open at the right page while somebody is watching you.

Spaced Review

From Chapter 25 — the distribution matrix. What does this chapter add to it?

From Chapter 24 — an unassigned task is an unhappened task. How does a run sheet enforce it?

From Chapter 24 — cues rather than a running order. Where do they live now?

📐 Project Checkpoint

Build the Reyes–Whitfield run sheet and production book.

You have Chapter 25's master timeline — FINAL, 10 September — and everything derived from it across twenty-five chapters.

Produce:

1. The run sheet, four phases at four densities, with all five fields on every line
2. The exception lines — every critical-path line, every single point of failure, every silent failure
3. The ten sections, and an honest note about which of them do not exist yet
4. The contact sheet, by arrival time, with second numbers
5. The escalation tree, every branch ending somewhere
6. The emergency page
7. The three derived objects — pocket card, wall copy, vendor packs
8. The generation test: change dinner by twelve minutes. How long to eleven correct documents?

case-study-02.md assembles all of it — and finds two sections missing.

Looking Ahead

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 whole purpose was to spend less of it on remembering things.