Key Takeaways: Timeline Construction

The one thing

The timeline is the product, and it inherits everything.

A master timeline is not a fresh document. It is the point at which every unresolved thing in the project becomes a time, or fails to — an unfunded item becomes a moment when somebody discovers there is no money; an estimate that was true in month four becomes a block that is the wrong length.

Which is why the first act of timeline construction is not construction. It is an audit.

The ten claims

1. Audit first, in four columns, with "living with it" as a legitimate status. A project with nineteen open findings and five months to go will not close all nineteen, and marking them all "pending" produces a plan that depends on nineteen future events.

2. Three kinds of open finding: resolved but not transferred (most of them, and an afternoon's work) · genuinely open (build both, or build the variable it moves) · and structural (buffer it or accept it, and say which).

3. Build backward from hard anchors, of which there are fewer than people think. The test: what happens if it moves by twenty minutes? A cost is soft; a breach, an impossibility, or a person who is not there is hard.

4. The ceremony time is usually soft — the invitation fixes the arrival, not the start — and its fifteen minutes of float is the most useful in the day. Held, not spent.

5. Forward planning hides the failure at the end. Backward planning shows it at the top, where earlier access, a day-before install, or a different arrival time are still available.

6. Find the critical path and note that it is short. At most weddings it is six consecutive tasks with zero float across about four hours — and the planner's attention should be concentrated there, not spread evenly. Those are the fragile hours, and they are also when a planner is most tempted to go and deal with something else.

7. Run the compression test: what would you do if each critical task ran 25% long? The output is a list of what you can act on and what you cannot — and the tent is almost always the second.

8. A wedding is two chains — the build and the people — and they meet once. Planners build the first well and the second badly, because the second is eleven people in a house fifteen minutes away.

9. Four buffers, about 65 minutes, in four places: hair and makeup · family photographs · the ceremony · the toasts. Dinner is not one, because it is arithmetic rather than variance. And a buffer people know about is not a buffer — publish the earlier time, hold the later one, and tell the one person delivering the thing.

10. Version everything, state the change at the top, name the last one FINAL with a date, log distribution, and confirm receipt — because a vendor who has not acknowledged has not received it.

The cascade

Delay at a wedding is not additive. It is directional.

Which produces the day's operating rule: before spending attention on a delay, ask which chain it is in and whether the next thing has float. Most delays at a wedding do not matter, and a planner who treats them all identically will be exhausted by two o'clock.

Float versus buffer

A buffer is time you added. Float is time the structure already contains.

Float is discoverable and free; a buffer is a decision and costs. And the trap: float built into the published plan stops being float and becomes a later start time. Plan to 4:25 and hold 4:40.

Threshold concepts

🚪 A timeline inherits everything.

🚪 The fragile hour.

Most of a wedding day is robust. A vendor twenty minutes late at 9:00 a.m. is a non-event; the same vendor at 1:00 p.m. delays the wedding. The question is never how late somebody is — it is what the next thing is waiting for.

What this chapter added to the project

The audit found nineteen open findings where the book had counted eleven. The eight extra had been mentioned once, in a paragraph, and never tabulated — which is precisely the failure the audit exists to catch.

Eleven closed in two afternoons, one email, and $225. Six being lived with. One already resolved. And one genuine conflict that had never been put next to itself:

Chapter 19 said signage goes on site the day before. Chapter 8 §3 says access begins at 7:00 a.m. on the day. Both were correct in their own chapters and neither had ever been read against the other. Resolved: the two signs on public land go up Friday evening; the four on the venue's land at 7:15 Saturday. $0.

The generator, closed properly. Sundown re-confirmed at 2,900 W rather than 3,200 — family style holds rather than finishes — and the −4 week plug-in sweep found a photographer's video light (accepted, 200 W) and a phone-charging station (declined, with a reason). Margin from 237 W to 612 W, 97.6% to 93.9%.

And then $200 of a 2.4% contingency spent on a 15 kW generator anyway — which makes the headline financial risk worse to remove the headline technical one, and that trade is stated rather than assumed. A reserve held against unknown risks while a known one sits at 94% of capacity is a reserve being held for the wrong thing.

Five hard anchors, and the one everybody thinks is hard — the ceremony — has fifteen minutes of float that is being held.

The critical path: six tasks, zero float, 7:00 a.m. to 3:10 p.m., with 45 minutes of margin at the front that is not to be spent. The fragile hours are 1:00 to 3:10, and the planner is physically in the tent for them.

The compression test names the exposure: the tent. Nothing can be added if it runs long, which is why Chapter 13's wind clause matters more than anything else on four pages.

Re-derivation found two moved durations and one expired one. The ceremony at 36:25 rather than 35:15 (Chapter 24's rehearsal), the caterer at 2,900 W, and Chapter 14's toast time at 7:55 which Chapter 22 had already superseded at 8:15 — because Chapter 14's block was built before golden hour was scheduled. Which moved the toast pour from 7:51 to 8:08.

Eleven parties, ten confirmations, and one printed copy delivered by hand, because this chapter's own case study found a caterer working from a six-week-old print.

What is still open

Spaced review

From Chapter 13: the load-in as a dependency graph. A list of times always looks plausible; a dependency diagram cannot hide a conflict — and it is why buffers do not go between load-in tasks.

From Chapter 14: service duration is arithmetic, not variance. A predictable block does not need a buffer; it needs the ratio to be right, which is a month-six conversation.

From Chapter 20: any estimate given to a client has an expiry, and the planner owns restating it. §25.9's re-derivation is that rule made procedural.

From Chapter 24: the confirmation loop and the two-document comparison. Nine of twelve rehearsal discoveries are communication failures, and the same is true of a timeline's.

Before Chapter 26

Chapter 26 is 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.