Case Study 25.1: Three Versions in One Field

📜 From the Field

A Tier 3 illustrative composite. The couple, the vendors, and the timings are constructed; the mechanism is not. A wedding that runs late for no identifiable reason is almost always this, and it is the failure planners are least equipped to diagnose because there is no single moment where anything went wrong.

The situation

Ottilie Marchetti and Rasheed Bello. 165 guests. A converted granary, mid-August.

Their planner, Corinne, is experienced and thorough. She produced a master timeline in month seven and revised it four times, which is normal and correct.

Version Issued Changed
v1 −16 weeks —
v2 −11 weeks Ceremony 4:00 → 4:15
v3 −6 weeks Dinner service 6:45 → 7:00 · toasts 8:15 → 8:30
v4 −3 weeks Cake moved before the first dance
v5 −9 days Family photographs 20 min → 30 min; cocktail hour extended to 6:45

Every revision was correct. Every version was sent to everybody. Nothing was mislabelled.

And on the day, five vendors were working from three different versions.

Who had what

💰 Run the Numbers: what was actually in people's hands

Version held Why
Caterer v3 Printed it at −6 weeks for their operations meeting. v4 and v5 arrived by email and were not printed
DJ v5 Read it on a phone that morning
Photographer v4 Printed at −3 weeks. Did not see v5, which changed her block
Florist v3 Only needed the morning; assumed nothing had changed
The venue v5
The couple v2 The only one they had ever printed
Wedding party A group chat message from −5 weeks Ch.24
Corinne v5

Four versions live in one field.

What happened, minute by minute
5:20 The photographer starts family photographs, budgeted at 30 min in v5 and at 20 in her v4 She plans to finish at 5:40
5:40 She is halfway. She has been working to twenty minutes and there are twelve combinations
5:52 Family photographs end. Twelve minutes over her plan, on time for v5 Nobody is wrong
5:52 Portrait session — she has 8 minutes before her v4 says cocktail hour ends
6:00 She takes the couple away. v4's cocktail hour ends at 6:30; v5's at 6:45
6:35 The caterer, working from v3, begins service v3 says dinner at 6:45; they are pre-plating
6:38 The couple are still outside. Guests are being seated
6:45 Guests seated. Couple arrive at 6:47 15 min later than v3's caterer expected
6:47 Caterer has been holding plated starters for 12 minutes They go out at 6:52, and they are cold
7:10 The DJ, on v5, cues the welcome for 7:00 It has already happened
8:30 Toasts. The caterer, on v3, has cleared for 8:15 and the room has been waiting 15 minutes
8:52 Toasts end, 22 min over — four speakers, and Corinne is now compressing
9:20 First dance, against a planned 9:00

Nobody made a mistake. Every person did exactly what their document said.

The diagnosis

🔍 Why Does This Work? There is no moment in that sequence where anybody was wrong, and that is precisely why the failure is so hard to see and so hard to fix afterwards.

The photographer was on time for her version. The caterer pre-plated correctly for theirs. The DJ cued accurately from v5. Each vendor was competent and each was working from a document Corinne had sent them.

The failure is not in any of the five acts. It is in the space between the documents, and nobody owns that space except the planner.

And it produced a wedding twenty minutes late with no identifiable cause — which is exactly what §25.8 warns about, and which the couple experienced as "it just seemed to run a bit behind all evening."

The three specific failures

1. Email is not distribution.

v4 and v5 were emailed to everybody. The caterer received both and printed neither, because their operations process runs from a printed BEO folder assembled at −6 weeks (Chapter 14).

Sending is not receiving. §25.8: a vendor who has not acknowledged has not received it.

2. No version was named on the page in a way that mattered.

Each document said "v3," "v4," "v5" in the header. A caterer holding v3 in a marquee at 6:30 has no way to know that v5 exists — and no reason to check, because v3 is a document they were sent by the planner.

"FINAL — 12 August" on the last one would have made every other version visibly stale.

3. The changes were not stated.

No version said what had changed. v5 changed the family-photo block by ten minutes and extended cocktail hour by fifteen — two lines out of about ninety — and a photographer who received v5 would have had to diff two four-page documents to find them.

"CHANGED FROM v4: family photographs 30 min (was 20). Cocktail hour to 6:45 (was 6:30). Nothing else." at the top would have taken twelve seconds to read.

What it cost

💰 Run the Numbers
Starters held 12 minutes and served cold The one thing guests noticed
Welcome cued after it happened Minor
Room waiting 15 min before toasts Real, and it is the dip (Ch.22)
Toasts 22 min over, uncompressed because Corinne was managing the caterer
First dance at 9:20 instead of 9:00 20 minutes
Dancing 20 minutes shorter

No curfew at this venue, so the dancing was not cut — it ended at 12:20 rather than 12:00.

Which means the real cost was: cold starters, a flat twenty minutes before the toasts, and Corinne spending the evening reconciling rather than watching the room.

Discussion Questions

1. Corinne sent every version to everybody. What more could reasonably be asked of her?

Discussion **Three things, and none of them is more work than she was already doing.** **1. Confirmation, not distribution.** §25.8: a vendor who has not acknowledged has not received it. **The mechanism is one line in the email** — *"please reply 'got it' so I know you have the current one"* — and a list of who has replied. **It sounds trivial and it is the whole fix.** Corinne would have discovered at −8 days that the caterer had not acknowledged v5, and one phone call would have closed it. **2. A change summary at the top of every version.** Twelve seconds to read, ninety seconds to write. **It converts a four-page diff into two lines.** **3. "FINAL" rather than "v5."** A version number is only meaningful to somebody who knows how many versions exist. **A word is meaningful to somebody holding a piece of paper in a field.** **And the thing that is genuinely harder, which is why this case is not simply about carelessness:** the caterer's operations process runs from a printed folder assembled at −6 weeks. **That is their system and it is a reasonable one for a business doing four events a weekend.** **A planner who knows this — and it is knowable, by asking — sends the caterer a printed copy of the final version, by hand, at the −2 week meeting.** Which is Chapter 12's point about knowing how your vendors actually work, arriving as a scheduling problem.

2. The couple were working from v2. Does it matter?

Discussion **Less than you would think, and the reason is §25.8's distribution matrix.** **A couple should not be holding the master timeline at all.** They should have twelve lines — the moments they are in, no load-in, no vendor names — **and a couple's version changes far less often than a master timeline does.** **Across five versions of Corinne's master, the couple's twelve lines would have changed twice:** the ceremony at −11 weeks, and the first dance moving with the cake at −3 weeks. **v5's changes — a photo block and a cocktail-hour extension — do not appear on a twelve-line version at all.** **So the honest answer: the couple holding v2 is a symptom rather than a cause.** It tells you Corinne was distributing one document to everybody, which is the actual error. **And there is a second-order cost that is real.** A couple holding a four-page operational document **will read it, will worry about it, and will ask about page three** — which consumes planner time in month six and produces anxiety that the twelve-line version does not. **§25.8's line holds: twelve lines is a service.**

3. The starters were held for twelve minutes and served cold. Whose failure is that, honestly?

Discussion **Split three ways, and the largest share is not where instinct puts it.** **The caterer's share is smallest.** They pre-plated at 6:35 for a 6:45 service, which is correct practice for plated service at 165 guests. **When the couple were not there at 6:45, they held — which is also correct** — and at twelve minutes they served, because holding longer is worse. **Every decision they made was right for the document they had.** **The photographer's share is real but small.** She took the couple away at 6:00 for a portrait session that her version said fitted. **She could have checked — "is cocktail hour until 6:30 or 6:45?" — and she did not**, because she had a document from the planner and no reason to doubt it. **And the largest share is the planner's, for a specific reason.** Corinne was the only person who knew that four versions were live. **Everybody else believed there was one document and that they had it.** **Which is the general form and it recurs:** in a system where one party has information nobody else has, **the failures land on that party even when every visible act was somebody else's.** **And the practical version:** a five-minute call to the caterer at −1 week — *"just walking through the evening, what time have you got for service?"* — would have found it. **§25.9's re-derivation is exactly this call, and Corinne did not make it because she had sent v5 and believed that was sufficient.**

4. The wedding was twenty minutes late all evening and the couple described it as "running a bit behind." Is a twenty-minute drift a failure?

Discussion **At this wedding, barely — and at a wedding with a curfew, entirely.** **This venue had no curfew.** The dancing ran to 12:20 rather than 12:00, the guests did not notice, and nothing was lost except the cold starters and the flat fifteen minutes before the toasts. **Change one fact — a 12:00 curfew — and the same twenty minutes is twenty minutes of dancing**, taken from the end, which Chapter 22 established is not where a party can afford to lose them. **Which is the useful finding: the severity of a drift is entirely a property of the venue's contract, not of the drift.** The same failure at Wildrye Farm, with a 10:30 cut-off, costs the couple a fifth of their dancing. **And there is a second cost that does not depend on the curfew and is easy to overlook.** **Corinne spent the evening reconciling.** From 6:38 onward she was managing the caterer, re-cueing the DJ, and recalculating — **which means she was not watching the room** (Chapter 22 §22.8), not seeing who had left, and not noticing the things a planner is uniquely positioned to notice. **A planner's attention is the day's scarcest resource** (Chapter 27), and this failure consumed most of it from 6:38 to 9:20. **The starters were the visible cost. The attention was the larger one.**

5. Design the distribution system that would have prevented this. Be specific about what changes and what it costs in planner time.

Discussion **Six changes, and together they add about forty minutes to the whole engagement.** | | | Cost | |---|---|---:| | **1. A distribution matrix** — who gets what, decided once at −12 weeks | §25.8 | **20 min, once** | | **2. Vendor extracts** rather than the master to everybody | Each vendor's part plus the three things around it | **30 min the first time, 5 min per revision** | | **3. A change summary at the top of every version** | Two lines | **90 sec per version** | | **4. "FINAL" with a date, not a number** | | 0 | | **5. A confirmation line, and a log of who has replied** | *"please reply 'got it'"* | **5 min per version to chase** | | **6. A −1 week call to the three vendors whose timing is load-bearing** | Caterer, DJ, photographer. *"What time have you got for [X]?"* | **15 min** | > > **Total across the engagement: about 40 minutes.** Against an evening spent reconciling. **And item 6 is the one to keep if you keep only one.** **It is not a distribution mechanism at all** — it is a verification. **It asks the vendor to tell you their number rather than telling them yours**, which is the only method that finds a discrepancy you do not know exists. **§25.9's re-derivation and this are the same act**, and the phrasing matters: *"what time have you got?"* not *"you've got 6:45, yes?"* — because the second one invites a yes and the first one produces information.

Connections

  • Chapter 12 — knowing how a vendor actually works; a caterer's printed folder assembled at −6 weeks
  • Chapter 14 — pre-plating for a 6:45 service, which was correct for the document they had
  • Chapter 22 §22.8 — the planner reading the room, which did not happen from 6:38
  • Chapter 23 — a photo block that changed by ten minutes and a photographer who did not see it
  • Chapter 25 §25.8 — versioning, the distribution matrix, and confirmation
  • Chapter 25 §25.9 — re-derivation, which is the same act as the −1 week call
  • Chapter 27 — the planner's attention as the day's scarcest resource
  • Chapter 30 — a couple who described it as "running a bit behind"