Affiliate disclosure
Book titles on this page link to Amazon. As an Amazon Associate, DataField.Dev earns from qualifying purchases — at no additional cost to you.
Further Reading: The Rehearsal
On the citation tiers, see how-to-use-this-book.md.
This is the most procedural chapter in the book and its best sources are not about weddings at all. The four tests, the confirmation loop, and the reverse run are all versions of instruments developed in fields where a missed check has larger consequences — aviation, surgery, and theatre — and those fields have thought about them far more carefully than the wedding industry has.
Tier 1 — Verifiable published sources
Checklists and verbal confirmation — the strongest evidence base in this chapter
- Gawande, Atul. The Checklist Manifesto. The accessible account, and directly applicable. Its central distinction — between a DO-CONFIRM and a READ-DO checklist — is exactly the distinction between §24.5's tests and §24.3's script, and it is worth knowing which you are running.
- Haynes, Alex B. et al., "A Surgical Safety Checklist to Reduce Morbidity and Mortality in a Global Population" (2009), New England Journal of Medicine. The underlying study behind the WHO surgical checklist. Read it for the mechanism rather than the medicine: much of the effect appears to come from the team introducing themselves and stating their concerns out loud, which is §24.7's public assignment doing the same work.
- WHO Surgical Safety Checklist itself, which is one page and free. The "time out" step — everybody stops, and each person confirms their part aloud — is §24.5's reverse run.
- Degani, Asaf and Earl Wiener, on cockpit checklists and their design. Technical, and excellent on why a checklist that is too long stops being used, which is why §24.3 caps a rehearsal at forty-five minutes.
Briefings and crew resource management
- Aviation CRM literature. Search terms: crew resource management, pre-flight briefing, sterile cockpit. The core finding — that most failures are communication failures rather than technical ones — is §24.5a's nine-of-twelve, arrived at independently and with far better evidence.
- Weick, Karl E. and Kathleen Sutcliffe. Managing the Unexpected. On high-reliability organisations. The chapters on "deference to expertise" and "preoccupation with failure" are the theoretical version of running the tests when a rehearsal seems to be going well.
Theatre
- Any stage-management text — the standard works on calling a show. Theatre invented the cue (§24.6) and its vocabulary is more precise than events': a warning, a standby, and a go are three different things, and a planner who adopts them will brief better.
- Kelly, Thomas A. The Back Stage Guide to Stage Management. Practical, and the chapters on rehearsal process and on the prompt book map almost directly onto §24.3 and Chapter 26.
Instruction and memory
- Any current work on instructional design for procedural tasks — chunking, one instruction at a time, and the limits of working memory. §24.4's "one thing each person has to remember" is a working-memory constraint and it is well established.
- On physical marks rather than verbal descriptions: the relevant literature is on cued recall versus free recall. A taped X is a cue; "about here" requires reconstruction.
Tier 2 — Attributed professional practice
- The four jobs and their time allocations. The author's framework, and the allocations are practice.
- Forty-five minutes as the cap. A working figure, argued against in exercise D.2 on the grounds that it optimises for the planner's evening.
- The four tests. Assembled from what has gone wrong. Test 1 is Chapter 18's and is the strongest recommendation in Part V; Test 4 — the reverse run — is the author's and is the cheapest.
- 20–40% faster at a rehearsal than on the day. Observation, not measurement. Exercise C.2 asks you to measure it, and your number will be better than this book's.
- The twelve discoveries, and the nine-of-twelve ratio. Assembled from practice. The ratio is a claim about a distribution and it has not been counted properly — exercise C.1 asks you to keep your own list.
- The confirmation loop, and specifically the value of its second half. Real practice, and the author's strongest recommendation in the chapter after Test 1.
- The two-document comparison finding something "about a third of the time." A practice estimate, and it should be treated as an order of magnitude rather than a rate.
- "An unassigned task is an unhappened task." Chapter 27's rule, applied here in advance.
Tier 3 — Illustrative and constructed
All case-study material. Aoife and Tobias, Ravi, the walled garden and its five silent discoveries; the Reyes–Whitfield rehearsal, Tomás's reading, and a drainage channel four inches wide. Constructed.
And a note on Case Study 24.1's five findings: they are drawn from §24.5a's list of twelve and assembled into one wedding for teaching. No real wedding produces all five at once, and a reader who concludes that rehearsals routinely fail this badly has read it too pessimistically. The point is that each is individually common and each is individually cheap to prevent.
Where to go next
Run the four-minute test (exercise C.4), outdoors, with two people speaking quietly eighteen inches apart, and walk to forty feet. Then do it with a breeze. Ten minutes, and it is the single most valuable procedure in Part V.
Read the WHO Surgical Safety Checklist. One page, free, and it will take you four minutes. Then read §24.3 again and notice what it is.
Read one stage-management text on calling a show. The vocabulary alone — warning, standby, go — will improve every brief you write.
Time a processional twice (exercise C.2), once at rehearsal pace and once encumbered. Trust your number over this book's.
And keep your own list of discoveries. Every rehearsal you run, write down what it found. After ten weddings you will have a better version of §24.5a than this chapter's, specific to your market, your venues, and the mistakes you personally make.
Part VI preview
Execution — the timeline, the run sheet, the day itself, and what happens when it goes wrong.
It is where every document built so far is either used or found to be missing something, and Chapter 25 opens by absorbing a finding this project carried from Chapter 22 to Chapter 24 before anybody resolved it: one person had eight jobs and two of them were at the same time.