Further Reading: Timeline Construction

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

This chapter has the strongest transferable literature in the book and the weakest wedding-specific one. Critical-path method, buffer management, and schedule risk are mature fields with real evidence. What is not established is which of their findings survive contact with a wedding, and §25.6's claim that variance is concentrated in four places is practice rather than measurement.

Tier 1 — Verifiable published sources

Critical path and network scheduling

• Kelley, James E. and Morgan R. Walker, on the origins of the critical path method (1959). Worth reading the original argument — CPM was invented for chemical-plant maintenance shutdowns, which are far closer to a wedding load-in than to a software project.
• Project Management Institute, PMBOK Guide, chapters on schedule management. Dry, standard, and correct. Read the sections on activity sequencing and float rather than the whole thing.
• Any current text on network diagrams and precedence relationships. The vocabulary — finish-to-start, lag, lead, total float versus free float — is more precise than the one this chapter uses, and a planner who learns it will build better dependency charts.
• Goldratt, Eliyahu M. Critical Chain. The main challenger to classical CPM, and directly relevant: its central claim is that buffers placed per-task get consumed and buffers placed at the end of a chain do not. §25.6's "one buffer at the end of the load-in chain, not per task" is Goldratt's argument, and exercise E.2 asks you to test the rest of it.

Schedule risk and estimation

• Hofstadter's Law, stated in Gödel, Escher, Bach: "It always takes longer than you expect, even when you take into account Hofstadter's Law." Frivolous-sounding and empirically robust.
• Buehler, Roger, Dale Griffin, and Michael Ross, on the planning fallacy — the finding that people underestimate their own task durations even when they know they habitually do. This is why §25.9 re-derives from sources rather than from the last version, and why §25.6's buffers are held rather than published.
• Flyvbjerg, Bent, on reference-class forecasting and optimism bias in large projects. The method — estimate from what similar things actually took, not from what this one should take — is exactly what Chapters 14, 20, and 23's duration tables are for.

Versioning and document control

• Any configuration-management or document-control standard from engineering or aviation. ISO 9001's document-control clause is four paragraphs and it is §25.8, written for factories.
• The literature on shared mental models in teams — search shared situation awareness, common operating picture. Case Study 25.1's four-versions-in-one-field is a situation-awareness failure and it has a name in fields that take it seriously.

Adjacent scheduling practice

• Broadcast rundowns. A live television rundown is a wedding timeline with harder anchors and better tooling. Any television production text on rundowns and back-timing is directly applicable — and back-timing is §25.3's method, named.
• Film assistant-director practice — the call sheet, the one-liner, and the day-out-of-days. A call sheet is Chapter 26's run sheet, refined over a century.
• Theatre and event production schedules, and Chapter 13's list.

Tier 2 — Attributed professional practice

• The audit, in four columns. The author's, and it does not appear in any other wedding-planning text. Exercise B.7 asks you to run one.
• The five hard anchors and the hard/soft test. Practice.
• "The ceremony is usually soft, with ~15 minutes of float." Observation, and it is the claim most experienced planners push back on. Test it against your own venues.
• The four buffers and the variance table in §25.6. The direction is well founded — hair and makeup and family photographs genuinely do overrun and dinner service genuinely does not — but the magnitudes are practice, and exercise C.5 asks you to gather your own.
• The hidden buffer, and the rule that the person delivering the thing is told the truth. Practice, and exercise D.4 argues it is deception.
• The cascade's three-place comparison. The author's construction, and it is a teaching device rather than a measurement.
• "A vendor who has not acknowledged has not received it." Practice, and it is the single most transferable line in the chapter.
• The distribution matrix and the vendor extract. Practice, and the "three things around them" rule is the author's.

Tier 3 — Illustrative and constructed

All case-study material. Ottilie and Rasheed, Corinne, and four versions in one field; the Reyes–Whitfield audit, master timeline, and the nineteen findings. Constructed.

And a note on Case Study 25.2's audit: the nineteen findings are the ones this book actually accumulated across Chapters 10–24, and the claim that eight of them were never tabulated is a claim about this book's own record-keeping. It is left in because it is true and because it is the failure the chapter is about.

All prices — $200 for a generator upgrade, $25 for a bouquet delivery — are plausible and will be wrong for your market.

Where to go next

Get a real timeline and find the critical path (exercise C.1). Most wedding timelines have never had one drawn, and you will frequently find that the planner who wrote it could not have told you where the float was.

Read Goldratt's Critical Chain, or at least its argument about buffers. It is a business novel and it reads quickly. Then look again at §25.6 and decide whether four buffers is right.

Run an audit (exercise B.7) on a project you are actually working on, honestly, in four columns. Count the findings before you start and again after.

Learn the precedence vocabulary — finish-to-start, lag, total float, free float. It takes an hour and it makes every dependency conversation with a vendor more precise.

And watch a broadcast rundown being back-timed if you ever get the chance. It is §25.3's method executed by people who do it daily, against anchors that genuinely cannot move.

Chapter 26 preview

The run sheet and the production book — the operational form of everything this chapter constructed.

A timeline says what happens when. A run sheet says who does it, what they need, and what happens if they cannot — and the production book is the object a planner is physically holding at 4:26 p.m.

Bring the master timeline and the distribution matrix. Chapter 26's first job is to turn one document into eleven.