Part VI: Execution

Chapters 25–30

Part V was what a wedding is for. Part VI is whether any of it survives contact with a Saturday.

And the register changes again. Part IV opened with a plate, a queue, a watt, and eleven cents. Part V opened with people — a father at the top of an aisle, an eighty-eight-year-old woman in a kitchen.

Part VI opens with times. 1:52 p.m. 11:04. 4:02. 22:16. Six chapters and every one of them begins at a moment with a clock attached, because that is what execution is: the point at which a fourteen-month project becomes a sequence of instants in which somebody either does a thing or does not.

What this part covers

Chapter 25 — Timeline Construction builds backward from the fixed points and finds that delay is directional. The cascade, the float, and the discovery that the margin you are holding is only useful if you know which way the next thing is waiting.

Chapter 26 — The Run Sheet and the Production Book turns a timeline into instructions. An instrument does not solve a problem — it makes the problem findable. The distribution matrix, exception lines, the escalation tree, the read-through — and the discovery, after twenty-five chapters, that the emergency page belonged to no chapter and did not exist.

Chapter 27 — Day-Of Execution is where you stop planning and start deciding. Triage in four questions, the sixty-second decision, position hour by hour, and attention as the scarcest resource — ahead of time and energy. The day, counted: 211 decisions, 147 of which died at the first question, and twenty-three that took thirty-five minutes in total.

Chapter 28 — Crisis Management narrows the claim: a crisis is a decision made under worse conditions than usual. Three kinds, the rain plan as five things rather than a sentence, the failure playbook by substitutability, and §28.8 — the crisis that cannot be solved, which most material on this subject omits.

Chapter 29 — Guest Experience and Accessibility is the chapter that turns the instruments around and points them at a person. Almost everything that makes an event hard for a guest is invisible to everybody except that guest, and they will not tell you — which makes guest experience an information problem, not a design problem.

Chapter 30 — After the Last Dance closes it: the load-out, the handback, the reconciliation, and the argument that a debrief producing only praise has failed.

The idea underneath

Part I's principle was surface it early. Part II's was verify the specific thing against a written standard. Part III's was measure it, then draw it. Part IV's was the best thing available is usually free. Part V's was the planner's contribution is almost never a decision.

Part VI's is: the work was done in month six.

Chapter	Looks like a day-of skill	Is actually
25	Keeping to time	An arithmetic done in month four, and knowing which way delay travels
26	Knowing what happens next	A document somebody wrote so that nobody has to remember
27	Deciding fast	Noticing which decisions have already been made
28	Staying calm in a crisis	Having answered it in a document, or having accepted that it cannot be answered
29	Noticing a guest is struggling	Having asked a question in February that they could answer
30	Learning from experience	Changing a document within two weeks

Every row is the same shape. The visible competence is real and it is downstream of something written months earlier by somebody who was not under pressure.

Chapter 27 states it as the Part's threshold concept:

The decisions that take fifteen seconds are the ones that were made in month six.

And Chapter 30 states its inverse, which is the harder half:

A finding that does not change a document, a template, or a checklist has not been learned.

The instruments, and their common flaw

Part VI built six.

The timeline (25) · the run sheet and its audit (26) · the sweep (27) · the failure playbook and the incident note (28) · the guest walk (29) · the finding log and the reconciliation (30).

Every one of them finds things. Between them they produced, on one wedding: nineteen open findings at the audit, eleven at the sweeps, four from a single crisis review, eight from one guest's walk, and twenty-four at the close.

And they share a flaw, which Chapter 30 names at the end:

An instrument that finds and does not assign is a device for producing a well-documented list of problems you still have.

The stationery misallocation was caught by an audit in month nine and was still wrong eleven months later — because caught and fixed were the same column. That is the last systems change in the Part and it is the one that makes the other five instruments worth anything.

What you should have built

If you have done the Project Checkpoints, the Reyes–Whitfield folder now contains:

A timeline built backward from the 10:30 amplified-music cutoff, with the cascade mapped and 45 minutes of front margin — which Chapter 27 spent 25 seconds deciding not to use
A production book with a distribution matrix, exception lines, an escalation tree, and an emergency page that no chapter owned until somebody made it somebody's explicit job
A decision protocol agreed in six minutes in May — a $200 spending number, change how not what, one named person, and a fourth clause that Alicia amended herself
A rain plan that is five things: the barn on the uplighters with the festoon dark so the 7:20 cue survives, cocktail hour in the tent, dinner at 6:00, and two paid hands at $40 retained
A failure playbook by substitutability, with category D — officiant, caterer, venue, power — prepared in full
A ceremony hour that finally has a plan: fourteen reserved seats, water at the top of the walk, a car from the gate for six named guests, and Rev. Castellanos bringing the microphone to Rosa rather than Rosa walking to the front
A finding log with twenty-four entries, nine of which are about the planner
A reconciliation, closed, and $299.22 going back

The three things Part VI found about itself

One: the barn seats 89 for a dinner it was never going to serve.

Open since Chapter 10, re-read at three audits, and never wrong. Every document agreed because all of them were copies of one line. An audit finds contradictions; it cannot find a consistent error, and the only instrument that catches this is re-derivation — which nothing in this Part does automatically.

Two: the ceremony hour was never planned.

The reception had a floor plan to 36 inches, a seating chart with names, a dietary matrix mapped to tables, and a run sheet to the minute. The ceremony had a processional order, a duration, and a chair count — no seating, no reserved rows, no ushers' brief, no water, and no plan for the woman who had to speak.

Every wedding does this, and so does almost every book.

Three: the contingency was tracked against the wrong thing.

The project counted the three occasions when somebody deliberately spent contingency money. It never counted the ninety-odd occasions when a line moved. $964.78 of drift, $437.31 that was never allocated to anything at all, and a number reported to the couple for a year that was $527.47 too high.

Same class as the barn. Internally consistent, correctly maintained, and answering a narrower question than everybody believed.

What Part VI could not solve

The track.

Fourteen guests over seventy walked 200 metres of grass at 4:10 and one could not. Chapter 27 spent ninety seconds and six minutes of float on her and never asked whether anybody else was struggling — the planner's own note as the thing they got wrong. Chapter 29 closed it with water, benches, and a car.

But the general form is not closed, and it is stated plainly in Chapter 29: a planner cannot see who needs something, twenty to thirty of a hundred guests need something, and almost none of them look like it. The only instrument is a question asked early enough to be answered, and this project asked it seven months late.

What's next

Part VII takes the same skills into different rooms — corporate events, galas and fundraisers, destination events, large-scale production, and sustainability.

And it opens by removing the thing every chapter so far has been able to assume.

A wedding has no objective. It has a couple, a budget, and a hope. Chapter 31's client has an objective, in writing, that somebody in a different department will measure — and will not accept "a lovely day" as an answer.

That is a harder question than it sounds. It is also, as Part VII will argue, an enormously clarifying one.