Further Reading: After the Last Dance

On the citation tiers, see how-to-use-this-book.md.

This chapter has two halves and they belong to different literatures.

The first half — load-out, handback, reconciliation, gratuities — is trade practice. It is learned by doing it badly once, and the useful reading is contracts and your own jurisdiction's rules, not books.

The second half — the debrief, the finding log, the systems change — has a real and excellent literature, and it lives in aviation, medicine, software, and the military. None of it is about weddings and all of it is about this.

Tier 1 — Verifiable published sources

Reviewing your own work honestly

The US Army's After Action Review (AAR) doctrine. Start here. Free, short, and the four questions — what was supposed to happen · what actually happened · why was there a difference · what will we do differently — are §30.8 with better discipline. The critical design feature is that rank is suspended in the room, which is exactly what "you go first" is trying to buy.
Any current material on the blameless post-mortem from software operations. Google's SRE book has a good chapter on it, free online. The core finding — that you get accurate accounts only when nobody is being punished for producing them — is why §30.8 says never defend a finding.
Dekker, Sidney. Just Culture. On the line between a blameless review and one that never holds anybody accountable. A genuinely hard problem and this chapter does not solve it, since a planner reviewing themselves has nobody to be accountable to but the client.
Edmondson, Amy. The Fearless Organization and her earlier work on psychological safety. The founding research is on hospital teams and found that better teams reported more errors — which is the whole of §30.8's argument, established empirically, in a domain where it matters more.
Gawande, Atul. The Checklist Manifesto. Chapter 26 recommended it; here the relevant part is how a finding becomes a line on a checklist, which is §30.10's systems change.

Why lessons do not stick

Argyris, Chris, on single- and double-loop learning — the difference between fixing an outcome and changing the rule that produced it. §30.10's finding / lesson / systems-change distinction is Argyris, restated for one person with a spreadsheet. His paper "Teaching Smart People How to Learn" (1991, Harvard Business Review) is the readable entry point.
Any work on organisational forgetting and lessons-learned databases. The consistent finding across industries — that lessons-learned repositories are written and not read — is Case Study 30.2's change 10 arriving from the outside. Search: lessons learned failure, knowledge management post-project review.
Weick and Sutcliffe, Managing the Unexpected, again, for preoccupation with failure — the practice of treating small anomalies as information rather than as noise.

Memory, and why the photographs matter

Loftus, Elizabeth, on memory reconstruction and the malleability of recollection. §30.12's claim that photographs rewrite the day is not a metaphor, and Loftus's work on how post-event information alters memory is the mechanism.
Kahneman, on the remembering self versus the experiencing self, and the peak–end rule. This is the most useful single idea for anybody who runs events: what people remember is not an average of what they experienced. §30.6's return and §30.9's referral both sit at the "end."

Money, contracts, and the parts you must check locally

Your own contract templates, read specifically for: the handback time, the damage deposit terms, the collection window, and whether equipment may remain overnight. §30.3a's three questions come from this and nowhere else.
Your jurisdiction's rules on service charges, tips, and tip pooling. This varies enormously and is genuinely legally consequential — in some places a mandatory service charge is not a gratuity and need not reach staff, and the difference is the single most useful thing to know in §30.5.
Your jurisdiction's record-retention requirements for financial records. Seven years is a common figure and is not universal.

Tier 2 — Attributed professional practice

"The load-out is planned with the load-in." Practice, and near-universal among people who have done it badly once.
The five load-out categories and the claim that the couple's things produce every genuine loss. Observation.
The card-box protocol. Practice. The dollar range for a card box is a wide estimate and varies enormously by region and culture.
Two sweeps, and the claim that they find different things. The author's, and the mechanism — the first done from the list, the second done from the room — is a hypothesis rather than a finding.
The damage walk, and "a venue that receives a 7:15 message with photographs does not send the Tuesday email." Practice, stated more confidently than the evidence supports — it is one planner's experience of a small number of venues.
"One error in four invoices, half in your favour." An estimate, and it is the softest number in this chapter. Exercise C-work would improve it.
The gratuity schedule. Explicitly a US-shaped practice range, not a standard, and among the most regionally variable material in this book. Check locally, always, and check the contract first.
The return, and the claim that it matters out of proportion. Practice, and D.1 asks whether it is an ethical claim or a marketing one.
"What did I make harder than it needed to be?" The author's, and the strongest single technique in the chapter because it is free, takes ten minutes, and reliably produces answers.
Ending a vendor relationship explicitly. Practice, and D.8 concedes it is advice that is easy to give and costly to take.
The praise problem's four reasons, three inherited from Chapter 29 and one new: they do not know what was supposed to happen.
The finding / lesson / systems-change distinction, and the one-third ratio for a finding log. The ratio is a rhetorical device with no basis and D.6 says so.
The two-week window.

Tier 3 — Illustrative and constructed

All case-study material. Aurelia Sandoval and the Thorne Mill deposit; the Reyes–Whitfield reconciliation, its twenty-four findings, and the wrap-up. Constructed.

Three specific notes.

Case Study 30.2's reconciliation is internally consistent arithmetic on constructed inputs. The named lines sum to $40,600 budgeted and $41,564.78 paid; the drift is $964.78; the unallocated remainder is $437.31; the return is $299.22 and it checks. The numbers are a demonstration of a document, not a record of a wedding, and no reader should take any individual line as a price.

The contingency error is a deliberate construction. The book reported $826.69 for two chapters and corrects it here, and it is the same class of error as "the barn seats 89" in Chapter 28 — a number that is internally consistent and answering a narrower question than everybody believes. The repetition is intentional; whether a book should plant its own errors in order to catch them is a fair question and the answer is given in Case Study 28.2's discussion.

Case Study 30.1's nine-hour, $620 outcome is an estimate and the recovery figure is invented. DQ4's conclusion — that pursuing it was irrational and that the twenty minutes at 7 a.m. is what prevents the dispute from starting — is the transferable part.

Where to go next

Read the Army's AAR doctrine. Twenty minutes, free, and it will make your wrap-up better than any wedding-industry material will.

Then read Edmondson on psychological safety, or at least the summary of the hospital finding: better teams report more errors. Once you have that, §30.8 is obvious rather than uncomfortable.

Ask three vendors what planners make harder than it needs to be (C.3). Do this before you finish the chapter. It takes fifteen minutes and it is the highest-return exercise in Part VI.

Then do C.6 — take one finding and actually change the document. Then do the last line of the mini-project: open it in three months and check it is still changed. Most are not, and that finding is worth more than the other six.

And read Argyris on double-loop learning, so that the difference between "be more careful with times" and "the catering brief is populated from the rehearsal-confirmed duration" has a name you can use.

Part VII preview

Beyond the wedding — corporate events, galas and fundraisers, destination events, large-scale production, and sustainability.

Chapter 31 is corporate, and it opens with the one thing a wedding never has: an objective that somebody will measure.

Bring the reconciliation. The client you are about to meet will ask what the money bought, and will not accept "a lovely day" as an answer — which is a harder question than it sounds and, as Chapter 31 will argue, an enormously clarifying one.