🔬 Case Study 33.2: Four Days in November — The Date Is Not Moving
📜 Tier 3 — Illustrative. Tessa Nkemelu, Diego Salcedo, their guests, and every figure here are constructed. The arithmetic is internally consistent on constructed inputs, and the legal material is deliberately non-specific. The method transfers; the numbers do not.
The brief
Tessa Nkemelu and Diego Salcedo. 60 guests. Four days in the second week of November. Riviera Maya. $68,000.
And one fact that is not negotiable: the resort is booked and the deposit is paid.
They booked it themselves, eleven months out, before hiring a planner, because it was thirty per cent cheaper than February.
The planner is engaged at −14 months — which is late for a destination event and is normal.
The distance audit
Done in week one, in writing, and it becomes the plan.
| Removed | Substitute chosen |
|---|---|
| Seeing the venue | Two visits: three days at −9 months, seven days at the wedding. Plus a standing offer of video walkthroughs, used four times |
| Turning up at a vendor | Ximena Rul Bravo, engaged at −13 months |
| The planner's own network | Ximena's — and the vetting question is "which vendors have you worked with more than five times?" Seven of the eleven qualified |
| Legal standing | Contracts to Tessa and Diego, Ximena named as coordinator. §33.5 |
| The same clock | One batched numbered message a day; one scheduled call every Tuesday, 08:00 Pacific / 10:00 Playa, in the diary for fourteen months |
| Being there on the day | Not removed. Planner arrives Sunday for a Saturday wedding — six days |
🔍 Why Does This Work: the audit is the schedule
Every row produced a commitment with a date on it, and by week two the planner had a fourteen-month calendar rather than a to-do list.
The Tuesday call is the item people cut and it is the one that matters. Fifty-eight calls across fourteen months, many of them four minutes long and about nothing — and it is why day seven of Case Study 33.1's silence was noticed as a silence rather than as a gap.
The legal position
Resolved in month two, and it took one conversation and two emails.
📋 The Planner's Script: month two
"There's one thing I want to sort before we do anything else, because it decides what kind of ceremony we're designing.
Legally marrying in Mexico as foreign nationals is possible and it is a process — documents that need apostilling and official translation, a residency window, witness requirements, and in some states a medical test. It varies by state, it changes, and I am not the person who should be telling you what it is.
What I'd recommend, and what most couples in your position do, is this: get legally married here, quietly, two weeks before you fly. Ten minutes, two witnesses, a registrar.
And then the ceremony in Mexico is exactly the ceremony you want. Your uncle can officiate. It can be in Yoruba and Spanish and English. It can be on the sand at 4:30 and nobody has to be in an office in Playa del Carmen at eleven on a Tuesday.
I know that feels like the real one is being demoted to paperwork. I'd put it the other way round — we're getting the paperwork out of the way so the ceremony can be about what it's actually about."
Tessa's mother objected for about a week and then became the plan's strongest advocate, on the grounds that it meant the ceremony could be in Yoruba.
Verification, done anyway: the planner wrote to the state civil registry and to the couple's own consulate, received two written answers, and filed them — because §33.4's rule is that the source is not the venue, and because a decision made on an assumption is not a decision.
Ximena
⚡ The vetting, month three
Question Answer Events last year, and for foreign planners? 34, of which 19 Vendors worked with more than five times? Seven of eleven Cover if you are ill? "My colleague Rodrigo." Named. Not contracted A run sheet you have produced? Sent within two hours, in Spanish, and it was good What do foreign planners get wrong here? "They ask if something is possible. Everything is possible. They should ask what time it will happen and who is bringing it." Three days you would never book? Two local festivals and the Sunday of a marathon Two references from foreign planners Both called. Both positive. One volunteered that she is slow in the two weeks around Semana Santa 🚪 The answer to question five became the project's working practice.
"They ask if something is possible. Everything is possible."
From month three, every question the planner sent was constructed so that its answer was a fact. Not "can we have the ceremony at 4:30?" but "what time does the sun hit the ceremony point, and what time do the beach clubs next door turn their music on?"
The second question produced the single most useful piece of information in the project, in month four: the beach club 90 metres north plays amplified music from 5 p.m. on Saturdays and the resort has no ability to stop it.
The ceremony moved from 5:00 to 4:15.
The four days
🕐 From the Run Sheet
THURSDAY 12:00–20:00 Arrivals, staggered across eight hours Ximena's team meets every single one at the airport. 14 transfers 19:30 Welcome drinks. Two hours. Optional, and said so in writing three times 19 of 60 skipped it and that was the design working FRIDAY All day NOTHING The line the couple argued about for six weeks Offered A cenote trip (booked by 22 guests) and a boat (booked by 11) — offered, not organised. Two links in the guest email $0, and no liability 19:30 Rehearsal dinner: 18 people The wedding party, the parents, and the officiant SATURDAY Morning Free. Hair and makeup for nine people from 11:00 16:15 CEREMONY — moved from 17:00 Because of a beach club 90 m north 16:50 Cocktails, beach terrace 18:30 Dinner 19:04 Sunset Ch.18's argument, at a different latitude 20:30 Dancing 00:15 Taco cart The most-photographed thing of the weekend 01:00 Ends Resort's noise curfew SUNDAY 11:00–14:00 Recovery brunch. Drop-in, no speeches, no seating plan $1,840. The event everybody talked about Afternoon Departures 🚨 The empty Friday, and the six weeks of argument about it
Tessa and Diego wanted to programme it. A group excursion, a lunch, a beach games afternoon. Their reasoning was warm and completely understandable: these people have flown a long way and we should look after them.
The planner's position, held across six weeks and three conversations:
"They didn't fly a long way to see a schedule. They spent two thousand dollars and a week of annual leave to be somewhere warm with people they like. The most generous thing you can do on Friday is nothing."
What settled it was not the argument. It was a question: "of the four days, which one do you think they'll talk about in five years?"
Tessa said the wedding, and then said "and probably the Friday, actually."
The money
💰 Run the Numbers: the cross-border costs, budgeted
$68,000 total, of which ~$49,000 paid in pesos across 11 transfers over 13 months.
Budgeted Actual FX spread — specialist service at ~0.6% rather than a bank at ~3% $294** | **$312 Wire fees, 11 transfers $605** | **$605 Card fees on ~$6,000 of card payments | **$240** $261 FX movement over 13 months ±$2,500 stated as exposure** | **−$1,940 (favourable) Net effect +$762 in the couple's favour The specialist transfer service saved roughly $1,176 against a retail bank on the same $49,000, which is more than the entire recovery brunch cost.
And the FX movement is reported as what it was: luck. The planner's note in the file reads "we were 1,940 dollars lucky and the couple should not learn from this."
💰 What it cost the guests
Per couple Flights ×2 $780–1,340 Resort, 4 nights $920–1,480 Food outside the wedding, transfers, activities $380–700 Total $2,080–3,520 Invited: 108. Attended: 60. Conversion 56%.
And the save-the-date, sent at −11 months, contained this sentence:
"We think four days will cost about $2,400 a couple all in, and there's a cheaper hotel ten minutes away that several people are using. And genuinely — come for two days if that works better. We'd rather see you for two than not at all."
Eleven guests came for two days. Four of them told Tessa afterwards that they would not have come at all without that sentence.
The hurricane conversation
Held once, at −13 months, and written down.
⚡ The risk assessment, as filed
The week Second week of November — the tail of the season, after the August–October peak The historical picture Significant tropical activity affecting the Yucatán in that specific week is uncommon but not rare. The planner pulled the actual climate record rather than repeating a impression The failure mode Not rain. Cancún airport closing for 24–72 hours — and 60 guests arriving from nine cities across three days Insurance Travel-disruption and event-cancellation cover, purchased at −12 months. Named-storm exclusions apply once a storm is named, which is why it is bought early and not in October Contingency clause Negotiated into the resort contract: a date-change option within 12 months at no penalty in the event of a government-declared emergency or airport closure The communication plan A drafted, unsent message to all 60 guests, plus a WhatsApp group created at −6 months and used for nothing until it was needed It was not needed. Nothing happened. The weather was perfect.
And the planner's own note is the honest one: "We were right to prepare and we were also lucky, and I cannot tell those apart from inside this one wedding."
What went wrong
Three things, reported in the debrief.
🚨 1. The airport transfers
14 transfers, staggered across eight hours, and two of them were 50 minutes late because a flight landed early and the driver was still on a previous run.
Four guests waited in an arrivals hall for 50 minutes after a five-hour flight.
The finding: the transfer schedule was built from scheduled landing times, not from scheduled landing times plus a buffer plus the drive time back. Chapter 25's cascade, and nobody had drawn it.
🚨 2. The rehearsal dinner grew to 26
From 18. Four sets of parents' friends were "obviously" going to be included and nobody said no early enough.
Cost: $640, absorbed. The real cost was that the rehearsal itself was skipped, because 26 people in a restaurant is a dinner and not a rehearsal, and on Saturday the processional had a genuine confusion about who walked with Tessa's aunt.
🚨 3. The taco cart's power
It arrived at 23:40 for a midnight service and needed a 20-amp supply nobody had specified.
Ximena solved it in nine minutes with an extension from the pool bar — which is precisely what a local partner is for, and is also exactly the Chapter 18 question that had been asked about every other vendor and not about this one, because the taco cart was booked in month eleven and was fun.
The result
| Budget | $68,000 |
| Spent | $66,410 |
| Returned | $1,590 |
| Ximena's fee | $5,800 |
| Planner's own days on site | 6 |
| Guests | 60 of 108 invited |
| Guests who came for two days because they were told they could | 11 |
Discussion Questions
DQ1. The couple booked a hurricane-season date before hiring a planner. What is the planner's actual obligation, and what did this one do?
Consider
**Not to move it — that ship sailed with the deposit — and not to pretend it is fine.** **The obligation is to make the risk explicit once, properly, in a conversation the couple remember having, and then to mitigate it and stop raising it.** §33.8's script does all three, and **the "and then I won't raise it again" is doing real work**: a planner who mentions hurricanes at every meeting for thirteen months has converted a managed risk into thirteen months of anxiety. **What this planner did that was better than the script:** **pulled the actual climate record for that specific week** rather than repeating a general impression, **bought insurance at −12 months precisely because named-storm exclusions bite later**, and **negotiated a date-change clause into the resort contract** — which is the only mitigation that actually addresses the failure mode. **And the drafted, unsent message plus a dormant WhatsApp group is the cheapest preparation in the case study.** **It cost twenty minutes and it is the difference between a crisis and a message.**DQ2. Ximena's answer — "they ask if something is possible" — changed the project's working practice. Why is that question so much worse than it sounds?
Consider
**Because *"is it possible?"* has a socially obligatory answer in most service relationships and in some cultures nearly a compulsory one.** **"Yes" costs the vendor nothing today. It defers the difficulty to a moment when the planner will not be in the country.** **And the replacement is not a trick — it is a request for a different class of information.** *"What time will it be there and who is bringing it?"* **cannot be answered with a courtesy**, because it requires a fact that either exists or does not. **The demonstration is the beach club.** *"Can we have the ceremony at 4:30?"* would have produced *"of course."* **"What time do the beach clubs turn their music on?"** produced 5 p.m. on Saturdays, **which moved a ceremony by forty-five minutes and is the kind of thing that would otherwise have been discovered at 5:02 on the day.** **And the general form is worth extracting: replace questions about permission with questions about mechanism.** It is good practice everywhere; **at distance it is the difference between planning and hoping.**DQ3. The planner held the empty Friday for six weeks against warm, generous, well-meant pressure. Was that worth six weeks?
Consider
**Yes, and the reason is that it was the only decision in the schedule that could not be reversed later.** **Every other item — the brunch, the taco cart, the transfer plan — could be added or cut at −2 months.** **A programmed Friday, once announced to sixty people, is announced**, and unprogramming it reads as a cancellation. **And notice what actually settled it: not the argument.** *"Of the four days, which will they talk about in five years?"* **converted the planner's position into the couple's own conclusion** — which is Chapter 3's client-management material and Part V's principle arriving together: **the planner supplied a question and the couple supplied the decision.** **The honest counter, which D.5 asks for:** an empty day is also a day when sixty people who flew a long way do not see the couple. **Tessa and Diego spent Friday moving between the pool, the cenote group's return, and a long lunch with six cousins** — which is more contact with more people than any programmed activity would have produced, and that is the actual argument.DQ4. The rehearsal dinner grew from 18 to 26 and the rehearsal was skipped. Trace the mechanism.
Consider
**Nobody expanded it. It expanded, four people at a time, each addition individually unarguable.** **And the failure is not the $640 — it is that the event changed category without anybody noticing.** **A rehearsal dinner for 18 is a working meal with a rehearsal in it. A dinner for 26 is a party**, and you cannot run a processional rehearsal at a party without embarrassing everybody. **Chapter 24 established that a rehearsal is the last chance to find a wrong thing while it is still Friday.** **This wedding gave that up in exchange for eight people's feelings, and paid for it on Saturday** with a genuine confusion about who walked with Tessa's aunt. **The systems change is specific: the rehearsal dinner's guest list has a stated cap and a stated reason, given to both sets of parents at −4 months** — *"it's eighteen because we're actually rehearsing, and everyone else has a free evening in Mexico"* — **which is a much easier sentence at −4 months than at −4 days.** **And it generalises: an event that has a working function needs its function stated, or it will be socially optimised into a party.**DQ5. The FX moved $1,940 in the couple's favour and the planner wrote "the couple should not learn from this." Unpack that.
Consider
**It is Case Study 28.1's DQ2 arriving in a different currency: outcome is not evidence of decision quality.** **The couple's experience is that the money went their way.** The lesson available to them is *"exchange rates work out"* — which is false, and which will cost them on the next one. **What was actually a good decision was the specialist transfer service: $1,176 saved on the spread, deterministically, by a choice.** **What was luck was the $1,940.** **And the note matters because it is in the file.** **A planner who records which of their good outcomes were decisions and which were luck is building the only useful kind of experience** — Chapter 30's finding log, applied to a success rather than a failure. **Most planners only interrogate their failures**, which produces a career-long overestimate of how much of their good work was skill. **The line "we were 1,940 dollars lucky" is the correction, written down at the moment it is still knowable.**DQ6. The taco cart's power was the one vendor whose Chapter 18 question was never asked. Why that one?