Chapter 33: Destination Events — Planning Across Distance

"I could get on a plane." — a planner, at 11 p.m., correctly, and it would not have helped

Chapter Overview

Ximena has not answered for nine days.

She is your local partner in Playa del Carmen. She has $4,200 of the couple's money. She holds every vendor relationship on this wedding — the venue contact, the caterer, the florist, the sound, the transport, the officiant — and every one of those contracts is between the vendor and her, not between the vendor and you.

It is eleven at night and the wedding is in five weeks.

You could get on a plane. It would take a day and cost about nine hundred dollars, and you would arrive in a city where you do not speak the language, know nobody, have no legal standing, and hold no contract with anybody except a person who is not answering her phone.

Turning up is available. It is also useless.

And that is the chapter, stated once at the top.

Distance does not add new problems. The problems are the same ones: a vendor who might not deliver, a contract with a gap in it, a timeline with a cascade, a guest who cannot manage a walk.

What distance removes is the thing you have used to solve all of them for thirty-two chapters: showing up.

Every technique in this chapter is a substitute for that.

In this chapter, you will learn to:

• Identify precisely what distance removes, and what substitutes for each
• Choose, contract, and hand off to a local partner — the single most important decision
• Navigate legal marriage abroad, or route around it entirely
• Handle currency, wires, and contracts in a jurisdiction where you have no recourse
• Build a multi-day schedule that does not exhaust sixty people
• Assess season and political risk honestly, including the parts nobody wants to say

🏃 Fast Track: Read §33.1 (what distance removes), §33.2–33.3 (the partner and the handoff), and §33.4 (legal versus symbolic) in full. §33.4 alone will save somebody's marriage from not being one. Then do B.3, B.5, and D.2.

📖 Standard: Everything.

🔬 Deep Dive: case-study-02.md builds the four-day Riviera Maya schedule for sixty guests in November, and confronts the hurricane-season date the couple have already booked.

33.1 What Distance Removes

🚪 Threshold Concept: distance does not add problems — it removes your ability to solve them by turning up

List everything you do by being present. It is most of the job.

⚡ Quick Reference: the six removals, and what substitutes

Removed	What you lose	The substitute
The site visit whenever you want	Measuring, seeing, standing in the room	One or two visits, ruthlessly planned · video walkthroughs on demand · and a local partner whose eyes you trust
Turning up at a vendor	The conversation that fixes it in ten minutes	Written specificity, and a partner who can turn up
Your own network	Ch.12's vetting, which rests on people you know	The partner's network becomes yours, and you are vetting one person instead of eight
Legal standing	You cannot enforce anything	Contract structure (§33.5) and money held back
The same clock	Fast iteration	Batched, written, asynchronous communication — and it is better than you expect
Being there on the day	Nothing. You are still there	This is the one distance does not remove, and planners forget it

The last row matters. You go. You arrive early — three to five days early — and for the last week you are a normal planner in a normal place. Everything difficult about a destination event happens in the twelve months before you land.

🌍 Global Perspective: the assumption you are making without noticing

Thirty-two chapters of this book assume a set of things that are true in some places and not others: that a contract will be enforced · that a deposit is refundable in specified circumstances · that a vendor who does not deliver faces a consequence · that a venue's stated capacity reflects a fire code · that "8 a.m." means 8 a.m.

None of these is universal, and none of them is a deficiency. They are properties of a particular commercial and legal culture, and a planner who exports the assumptions along with the checklist will be baffled, then rude, then unemployable.

The practical version: find out how business is actually done where you are working, from somebody who does it, before you write a single contract. Chapter 21's rule generalises here — you are not the authority on anybody's way of doing things.

33.2 The Local Partner

The single most important decision on a destination event, and it is made in month one.

⚡ Quick Reference: what a local partner actually is

Is	Is not
A co-planner with their own client relationship discipline	A fixer
The holder of vendor relationships you cannot build	A translator
The person who can be in a room in forty minutes	Your employee
A professional with their own reputation at stake locally	Cheap
Your single largest point of failure	Optional

They are Chapter 28's category D, alone, with no substitute.

Vetting one person instead of eight

⚡ The questions, and they are not the ones you would ask a florist

"How many events did you run last year, and how many were for planners like me?"	The second number matters more. A partner who works with foreign planners has done this handoff before
"Which of your vendors have you worked with more than five times?"	This is the actual asset you are buying
"Who else is on your team, and who covers you if you're ill?"	The Ximena question, asked in month one
"Show me a run sheet you've produced."	In their language is fine. You are looking for whether one exists
"What's the thing foreign planners get wrong here?"	Ask it exactly like that. The answer is the most valuable four minutes of the call
"What are the three days of the year you'd never book?"	Local holidays, festivals, a marathon, an election
Two references from foreign planners, and you call both	Not from couples. You want somebody who has done your job with them

🚨 When It Goes Wrong: the partner who stops answering

Return to Ximena. She is ill — genuinely, seriously — and her small firm has no cover, and the person who would normally tell you is her.

What actually saved this wedding was a decision made in month two: the couple's contracts were with the vendors directly, countersigned, with Ximena as the named coordinator rather than the counterparty.

So when she went silent, the planner had eleven vendors' names, numbers, and signed agreements — and could ring the caterer directly and ask who else in Playa could coordinate.

The caterer named two people. One of them took it.

The version where the contracts sat with Ximena is a wedding that does not happen, and the difference is one clause and a decision nobody wanted to make in month two because it felt like distrust.

⚖️ The Clause: what a local-partner agreement must contain

Scope, in detail, and specifically who contracts with vendors. The couple should be the counterparty wherever local practice permits it.

The vendor list, with contact details, provided and updated. "I'll handle the vendors" is the answer that produces the Ximena problem.

Cover. What happens if the partner cannot work. Named, if possible.

Payment schedule tied to deliverables, not to dates — and a meaningful final payment after the event.

A communication commitment. "Response within one business day" is not bureaucracy; it is the only early-warning system you have.

Currency and payment method, stated. §33.5.

And the language the agreement is written in, and which version governs.

33.3 The Handoff

Chapter 26's distribution matrix, across a border and a language.

⚡ Quick Reference: who owns what

	You	The partner
The client relationship	Entirely. They never manage the couple
Design and the brief	Yours	Executed locally
Vendor selection	Joint — their shortlist, your questions
Vendor management day to day		Theirs. Do not go round them
The timeline and run sheet	Yours, built with them	Theirs to execute
Local logistics, permits, transport		Theirs entirely
Legal and civil requirements	Joint, and verified independently	§33.4
Guest communication	Yours
The day itself	Both of you, and the roles are agreed in writing a week out

The commonest failure is the last row, and it produces two planners in the same room both deferring to each other at 4:15.

📋 The Planner's Script: agreeing the day

On the site visit, a week out, in person, and written down afterwards:

"Let's settle the day itself, because I've seen this go wrong and it goes wrong quietly.

You run the vendors. Everything with a truck, a crew, or an invoice is yours — I will not speak to any of them directly on the day unless you ask me to.

I run the family and the schedule. The couple, the wedding party, the guests, and what time things happen.

If those two collide, you win on anything physical and I win on anything about a person.

And if either of us can't find the other, the fallback is: you're at the back of house, I'm front of house.

Does that match how you'd do it?"

Note the last question. A handoff proposed and not agreed is not a handoff — and a local partner who works differently will tell you so if asked, and will not if told.

33.3a Working Across a Time Zone and a Language

The daily texture of the job, and it is better than planners expect once they stop fighting it.

⚡ Quick Reference: the communication protocol

Batch, do not drip	One well-structured message a day beats eleven questions. A partner six hours ahead reads yours at 8 a.m. and answers before you wake
Number every question	So that a reply of "1 yes, 2 no, 3 I'll check Tuesday" is a complete answer. This single habit doubles your effective iteration rate
State the deadline in their time zone	"By Thursday your time" — never "by end of day"
One scheduled call a week, same slot, in the diary for the year	The single most valuable ritual on a destination event, and it should survive weeks when there is nothing to discuss
Written follow-up after every call, from you, within an hour	"Here's what I understood us to have agreed — tell me what I've got wrong." The invitation to correct is what makes it work
A shared document, not a thread	Threads lose things across languages. A living document with a change log does not

And the finding planners resist: asynchronous is not a degraded version of a conversation. A written, numbered exchange produces a record, forces specificity, and survives being read by somebody working in their second language. It is frequently better than the phone call it replaced.

🌍 Global Perspective: what "yes" means

In some professional cultures a direct no to a client is close to unsayable, and the answer that means no is "that may be difficult", "I will see what is possible", or a yes followed by nothing happening.

A planner who does not know this reads three months of agreement and then discovers nothing was agreed.

The technique that works is not to demand directness. It is to ask questions whose answers cannot be yes:

Not "can you have the tables by two?" but "what time will the tables be there?"

Not "is that possible?" but "what would have to happen for that to work?"

Not "are you happy with this?" but "which part of this worries you most?"

All three replace a yes/no with a fact, and all three are good practice everywhere. They are simply load-bearing here.

33.4 Legal Marriage Abroad

The section that matters most and is most often discovered too late.

🚪 The near-universal answer: get legally married at home, and hold a symbolic ceremony at the destination

A civil ceremony at home — often ten minutes, two witnesses, and a modest fee — a week or two before travelling.

Then the ceremony abroad is exactly the ceremony they wanted, performed by whomever they want, saying whatever they want, with no legal constraint on its content, its location, its language, or its officiant.

This is what a large fraction of destination couples do and it is almost always the right advice.

It is also the advice couples resist, because it feels like the "real" wedding is being demoted to paperwork — and the reframe that works is that it is the opposite: the paperwork is being got out of the way so the ceremony can be about what it is about.

If they want it legal on site

⚡ Quick Reference: what varies, and it varies enormously

Residency requirement	Days you must be in-country before marrying. Ranges from zero to over thirty. France's is effectively prohibitive for non-residents
Documents	Birth certificates, passports, divorce decrees or death certificates, often apostilled and officially translated — a process taking weeks
Medical tests	Still required in some jurisdictions, and sometimes must be done locally
Witnesses	Number and nationality requirements, and some places require local residents
Who may officiate	Frequently only a civil registrar — and a beach ceremony may be legally decorative regardless of who stands there
Where it may happen	Often only in an official building. The beach ceremony is symbolic even when the marriage is legal
Recognition at home	Usually straightforward and worth verifying, not assuming

📜 Tier 2 and deliberately non-specific. This chapter gives no country's requirements, and that is not laziness — requirements change, differ by state or region within a country, and differ by the couple's own nationalities. The only reliable sources are the destination's civil registry and the couple's own consulate, checked at the time.

🚨 When It Goes Wrong: the marriage that was not one

A couple marry on a beach, with an officiant hired by the resort, in front of forty guests. It is beautiful.

Eleven months later, applying for a spousal visa, they learn the ceremony had no legal effect. The officiant was not a registrar. The resort's coordinator had said "we handle everything" and had meant the flowers.

Nobody lied. The couple assumed, the coordinator assumed the couple knew, and no single person in the chain had the job of establishing what was legally happening.

The fix is a sentence in month two: "I need to know, in writing, from a source that is not the venue, exactly what makes you legally married and who signs what."

🔄 Retrieval Practice

Without looking back:

1. What does distance remove, and which row of the removals table is the one planners forget?
2. Why should the couple, not the local partner, be the contractual counterparty with vendors?
3. What is the near-universal answer to legal marriage abroad, and why do couples resist it?

Check

1. The ability to solve problems by turning up. The forgotten row: being there on the day, which distance does not remove — you go, you arrive three to five days early, and for the last week you are a normal planner in a normal place.
2. Because a partner who goes silent takes every relationship with them. With direct contracts, the planner had eleven vendors' names, numbers, and signed agreements, and could ring the caterer and ask who else could coordinate. Without them it is a wedding that does not happen.
3. Marry legally at home; hold a symbolic ceremony at the destination. They resist because it feels like the real wedding is being demoted to paperwork — and the reframe is that it is the opposite: the paperwork is got out of the way so the ceremony can be about what it is about.

33.5 Money Across a Border

💰 Run the Numbers: the four costs nobody budgets

A $68,000 wedding, paid from the US to Mexico over fourteen months.

FX spread on retail bank transfers, ~2.5–3.5% on $52,000 of local-currency payments | **$1,300–1,820**
Wire fees, 9 transfers at $35–50 sending plus $15–25 receiving	$450–675
FX movement over 14 months — the rate at final payment is not the rate at contract	±$2,000–4,500
Card fees where cards are used, 3–4% including cross-border loading	$400–900
Realistic unbudgeted total	$2,150–7,895

The third row is the one that matters and it is not a cost — it is an exposure, and it can move in your favour.

Three things that reduce it: quote and contract in a single currency, chosen deliberately · use a specialist transfer service rather than a retail bank — the spread difference is typically 1.5–3% and on $52,000 that is real money · **and where a large payment is far out and the exposure is material, ask about a forward contract**, which fixes the rate. **Most couples will not need this; a $200,000 event does.**

⚖️ The Clause: contracting where you cannot enforce

Assume you will not litigate. Cross-border enforcement over a $6,000 deposit is not economically rational and both sides know it.

Which means the contract's job is different: it is a specification and a schedule, not a threat.

Five things that actually protect you:

1. Money held back. A meaningful final payment after delivery is worth more than every remedy clause combined. Aim for 20–30% payable on or after the day.

2. Specificity instead of remedy. "Twelve tables, 1.8m round, white linen to the floor, delivered and set by 14:00" protects you; "tables as agreed" does not.

3. Photographs at every milestone. Of the room, the samples, the stock, the flowers on the morning. Cheap, and it converts disputes into facts.

4. The reputation asset. A good local vendor's business depends on the local partner's continued referrals — which is why §33.2's "which vendors have you worked with more than five times?" is the actual protection.

5. Governing language and jurisdiction, stated — so that at minimum everybody knows which version of the document is the document.

33.6 The Schedule

Four days, sixty people, and the commonest failure is programming all of it.

🚪 Threshold Concept: your guests are on holiday, and it is a holiday they paid for

A destination guest has spent perhaps $1,400–3,000 and four to seven days of leave. They are not attending an event; they are taking a trip that contains one.

Which means unprogrammed time is not a gap in the schedule. It is the thing they bought.

A four-day wedding with eleven scheduled activities is a tour, and by day three the guests are exhausted, over-catered, and quietly resentful — and it is the single most common complaint about destination weddings from the people who attended them.

🕐 From the Run Sheet: four days that work

Day 1 — Thursday
Afternoon	Arrivals. Staggered across eight hours	Somebody meets every arrival. Ch.29's greeter, and here it is worth more
19:00	Welcome drinks, 2 hours, informal, optional	Optional out loud. People who landed at 5 p.m. should be able to skip it
Day 2 — Friday
All day	NOTHING SCHEDULED	The most important line in the document
Optional	Two things offered, both optional, both bookable in advance — a cenote trip and a boat	Offered, not organised. Guests choose, pay, and self-manage
19:30	Rehearsal dinner — wedding party and family only, 22 people	And it is genuinely only 22. Everybody else is told what to do that evening
Day 3 — Saturday
Morning	Free. Hair and makeup for those in it
16:30	Ceremony
17:00	Cocktails
19:00	Dinner
21:00	Dancing
00:30	Ends. A late-night taco cart at midnight
Day 4 — Sunday
11:00–14:00	Recovery brunch, drop-in, no speeches, no schedule	The most-loved event of the four days, and it costs almost nothing
Afternoon	Departures. Staggered

⚡ Quick Reference: the four rules

One completely empty day, minimum, and say so in the invitation. Offer optional activities; do not organise them — offering costs an email, organising costs money, liability, and your Saturday morning. A rehearsal dinner is for the rehearsal party, and expanding it to everybody costs a night's catering and gives the wedding a dress rehearsal. And the recovery brunch is the highest-value event on the list — cheap, informal, and the one guests actually talk about afterwards.

33.7 The Guests

💰 Run the Numbers: cost transfer and attrition

A domestic wedding invites 115 and 100 attend	87% conversion
A destination wedding invites 115 and 60 attend	52% conversion

📜 Tier 2 — the second figure varies enormously with distance, cost, notice, and who is invited. The direction is reliable; the number is not.

And the reason is a cost transfer that nobody names out loud:

Flights, 2 people	$700–1,600
Accommodation, 4 nights	$600–1,400
Food, drinks, transfers, activities	$400–900
Time off work	3–5 days
Per couple, realistically	$1,700–3,900 and a week of leave

Which produces the honest framing that couples find uncomfortable and should hear: a destination wedding does not cost less. It costs the same and a different set of people pay for it — and the people who cannot pay are the ones who decline, which is not random.

⚡ Quick Reference: what guests need, and earlier than you think

Save-the-date at 10–12 months	Not 6. People need to book leave and cheap flights
Total cost, stated honestly, at save-the-date	"We think this will cost about $1,800 a couple all-in." Uncomfortable and kind
A range of accommodation, including a genuinely cheap option	Otherwise the guest list selects by income
What is paid for and what is not, explicitly	The single biggest source of destination-wedding friction
Transfers from the airport, arranged	The one logistical thing worth organising centrally
Passport, visa, and vaccination requirements — with a link, early	And a note that passports must have validity beyond the trip
A realistic weather note	§33.8
And permission to come for two days instead of four	Given explicitly. Many will, and they will be grateful

🌍 Global Perspective: the guest who cannot come and will not say why

Chapter 29's disclosure problem, with money in it.

A guest who cannot afford $2,400 will not say "I cannot afford this." They will say the dates do not work.

Which means a destination guest list is filtered by wealth while appearing to be filtered by availability — and a couple who assume the declines are scheduling will draw the wrong conclusion about who cares.

What a planner can do is limited and real: ensure a cheap accommodation option genuinely exists · state costs early so the decision is made once rather than agonised over · and, where the couple can afford it, quietly cover a specific person's flight without announcing it. That last one is not the planner's decision and it is the planner's job to raise it.

33.7a Destination Events That Are Not Weddings

Incentive travel, offsites, user conferences abroad, and board retreats — a large and well-paid category, and Chapter 31's discipline applies with one addition.

⚡ Quick Reference: what changes

Who pays	The organisation, not the guest. §33.7's cost-transfer problem disappears entirely and the attrition problem with it
The objective	Ch.31's, unchanged. An incentive trip's objective is retention and performance, and it is measurable
Attendance	Effectively compulsory, which changes everything about consent, accessibility, and unprogrammed time
Duty of care	The big one. An employer sending 90 people abroad has legal and moral obligations a couple does not — medical, security, insurance, and a 24-hour contact
The "free" part	An incentive trip is a taxable benefit in many jurisdictions. Not your problem to solve and very much your problem to raise
Spouses and partners	Whether they come is a policy decision with a large cost — and it changes the event from a work trip into a holiday with meetings

🚪 The one thing that is genuinely harder than at a wedding: nobody chose to be there

A destination wedding's guests opted in and paid. An incentive trip's attendees were told.

Which means §33.6's unprogrammed time is not a nicety — it is the difference between a reward and a five-day meeting in a hot place, and the commonest failure in incentive travel is a schedule that treats the destination as a backdrop for content.

The rule that fixes it: content occupies mornings only, and no more than three of them. Everything else is the reward, and the reward is the objective.

🔄 Retrieval Practice

Without looking back:

1. Give three questions that replace a yes/no with a fact, and say why they matter more at distance.
2. What is the cost transfer, roughly what does it amount to, and what does it do to the guest list?
3. What are the four schedule rules, and which is the most-loved event of a four-day wedding?

Check

1. "What time will the tables be there?" · "What would have to happen for that to work?" · "Which part of this worries you most?" They matter because in some professional cultures a direct no to a client is close to unsayable, so a planner can read three months of agreement and discover nothing was agreed.
2. $1,700–3,900 per couple and a week of leave. A destination wedding does not cost less — it costs the same and a different set of people pay — and the guests who cannot pay decline, which is not random and will be reported as a scheduling problem.
3. One completely empty day minimum, said out loud in the invitation · offer optional activities, do not organise them · keep the rehearsal dinner to the rehearsal party · and the recovery brunch, which is cheap, informal, and the thing guests actually talk about afterwards.

33.8 Season, Weather, and Risk

⚠️ The cheap season is cheap for a reason, and the reason is usually weather

Caribbean and Gulf hurricane season runs roughly June to November, peaking August–October. South and South-East Asian monsoons, Mediterranean heat, Alpine shoulder-season closures — every destination has a period when it is 30–50% cheaper and everybody local knows why.

This is not a reason not to book it. It is a reason to book it knowingly, with insurance, a contingency date, and a conversation the couple remember having.

⚡ Quick Reference: the risk assessment, done once, in writing

Weather	Historical probability for that week, from a real climate record — not "it's usually fine"
The specific failure mode	A hurricane does not rain on your wedding. It closes an airport for three days — and the risk is guests who cannot arrive or leave, not a wet ceremony
Insurance	Ch.9, and read the weather and travel-disruption clauses specifically. Many policies exclude named storms once named
Political and civil risk	Your foreign ministry's travel advice, checked at booking and at −3 months. An advisory change can void insurance
Health	Vaccination requirements, medical facilities, and where the nearest hospital that a foreign insurer will accept actually is
Infrastructure	Power, water, and road access. Ch.18's generator question, in a place where you cannot inspect the supply
The contingency date or plan	Agreed in writing with the venue at contract, not requested in a crisis

📋 The Planner's Script: the hurricane-season conversation

Once, early, plainly, and it is written down afterwards:

"I want to have this conversation once properly, and then we'll book it and I won't raise it again.

You've chosen the second week of November. That is inside hurricane season, which is why the resort is thirty per cent cheaper.

The risk is not that it rains on your wedding. The risk is that a named storm closes Cancún airport for two or three days and thirty of your sixty guests cannot get there, or cannot get home.

Historically, for that specific week, the probability of significant disruption is low — but it is not nothing, and it is much higher than it would be in February.

So here's what I'd like: book it, take the saving, and spend some of it on three things. Travel-disruption cover for you. A written contingency clause with the resort. And a plan for what we tell sixty people if it happens.

Is that all right with both of you?"

33.9 The Site Visit

One or two, and they are not holidays.

⚡ What each visit is for

Visit 1 — 8 to 12 months out, 3 days	Meet the partner in person · see the venue and stand in every space at the time of day it will be used · taste the food · meet the three or four vendors who matter · and walk the guest route from the airport
Visit 2 — the wedding week, arriving 3–5 days early	Everything from Chapter 27, plus the walkthrough, the rehearsal, and the day

And the thing to do on visit 1 that nobody does: be there at the ceremony hour. A beach at 16:30 in November is a different beach from a beach at 11:00 in March — sun angle, wind, the noise from the bar next door, and whether the tide is where you think.

Between visits, the substitute is video. A partner who will walk a venue on a video call while you ask questions is worth choosing for that alone, and it is a fair thing to ask about in month one.

🧩 Productive Struggle

It is −16 days. Sixty guests, forty-one of whom have already booked flights.

Four things arrive in the same twenty-four hours:

• Your local partner tells you the resort has "reassigned" your ceremony location. Another wedding, booked later, has the beach point; you have been moved to the lawn behind the pool. The contract describes the location as "beachfront ceremony area."
• The couple's apostilled birth certificates have not arrived. They were couriered eleven days ago. The symbolic-ceremony route was chosen, so this affects nothing — except that the couple do not remember that and are panicking.
• A tropical depression has formed. It is not named, it is 900 miles away, and forecasters give it a 40% chance of development.
• The florist's quote has come back 34% higher than the number you have been budgeting for eight months, in pesos, and the peso has moved 6% against you since the estimate.

Rank them. Write your first two hours. And say what you do not do.

Think for at least five minutes before opening this

Ranking, and the reasoning is Chapter 28's substitutability with distance applied.

1. The ceremony location, immediately, and it is not close. It is the only one that is irreversible if left — the other wedding will be confirmed in that space and then nothing can be done. You have a contract that says "beachfront ceremony area" and a lawn behind a pool is not one.

The move is: your partner, on site, in person, today, with the contract, to the resort's director of events — not the wedding coordinator. This is exactly what §33.1 said you were buying: somebody who can be in a room in forty minutes. You write the position; she delivers it.

2. The couple, within the hour, about the birth certificates — and this is a person problem, not a plan problem. Chapter 27's fourth clause: it is about them, so they are told, and the message is four sentences: reassurance first. "You're already legally married. The certificates were for the resort's file and they're not required for anything that happens on the day. Nothing about your wedding depends on them."

3. The florist, this week, not today. A 34% overrun on one line is a money problem — category A. It is resolvable by scope, and it is genuinely partly FX, which is an exposure you documented and the couple were warned about. It needs a conversation, a re-scope, and a number. It does not need two hours today.

4. The tropical depression: nothing. Watch it. Do not mention it. A 40% chance of development at 900 miles, sixteen days out, is not information the couple can act on — and telling them converts sixteen days of anticipation into sixteen days of refreshing a forecast. You check it daily and you have a message drafted and unsent.

What you do not do — and each of these is a real temptation:

You do not ring the resort yourself. You have no standing, you will get the wedding coordinator, and you will undercut the person who can actually walk into the director's office. §33.3: they win on anything physical.

You do not tell the couple about the depression.

You do not solve the florist today, because doing so feels productive and costs you the attention the ceremony location needs. Chapter 28's second-order failure, at distance.

And you do not send four separate messages to the couple. One message, about the thing that is about them, and the other three are yours until they are resolved or become theirs.

The thing to notice about your own answer: if you ranked the birth certificates first, you responded to distress rather than consequence — understandable, and the right instinct in the wrong order. If you ranked the depression above the florist, you have discovered that weather is frightening and that being frightened is not the same as having a decision to make.

33.10 Practical Notes

On language. Learn the twenty words that matter and use them badly. Nobody expects fluency and everybody notices the attempt. And use a professional translator for anything contractual — machine translation of a contract is a false economy with a long tail.

On the resort coordinator. A resort's in-house coordinator is not a planner and is not yours. They work for the resort, they manage many weddings, and their job is the resort's operations. They are useful and they are not a substitute for §33.2.

On shipping things. Do not. Customs, duty, and delay make importing décor, stationery, or favours a reliably bad idea. Source locally or carry it. And check what may not be brought in — many countries restrict fresh flowers, plants, seeds, and some foods.

On alcohol. Import duty on wine and spirits is punitive in many destinations. A resort's corkage on brought-in alcohol frequently exceeds the saving. Ask before assuming.

On tipping. Norms vary enormously and getting it wrong in either direction is conspicuous. Ask the partner, budget it as a line, and prepare it in envelopes (Chapter 30).

On the couple's own travel. They should arrive at least three days early, and it should be in the contract with them as much as with anybody. A couple who land the day before are jet-lagged at their own wedding.

On documents. Passports, visas, marriage documents. A scanned copy of everything, held by you, in a folder — and a paper copy in your bag on the day.

On what you charge. Chapter 37 covers it properly. A destination event is more work, not less — more communication, more risk, a partner's fee, and two trips — and pricing it as a normal wedding with a nice location is the commonest business mistake in this chapter.

💰 Run the Numbers: what a destination event actually costs you to run

Against a domestic wedding of the same size and budget:

	Domestic	Destination
Client communication hours	40	65 — asynchronous, batched, and there is more of it
Vendor coordination hours	55	35 — the partner does this
Local partner's fee	—	$3,500–8,000
Site visit 1: flights, 3 nights, ground	—	$1,400–2,600
Site visit 2: arriving 3 days early rather than 1	—	$600–1,100 of additional accommodation
Days on site	1	5–7
Legal and document verification	0	6–10 hours
Currency, wires, and reconciliation admin	2	12

The partner's fee is frequently passed through to the couple; the rest is not.

And the row that catches people is days on site. Five to seven days is five to seven days you cannot sell to anybody else — which at Chapter 37's rates is the largest hidden cost in the chapter and is invisible in every quote that prices a destination wedding as a percentage of budget.

33.11 Summary

Distance does not add new problems. It removes your ability to solve the old ones by turning up — and every technique here is a substitute for that.

Six removals: the site visit whenever you want · turning up at a vendor · your own network · legal standing · the same clock · and being there on the day, which distance does not remove. You go, you arrive three to five days early, and for the last week you are a normal planner in a normal place.

The local partner is the single most important decision and they are Chapter 28's category D, alone, with no substitute. Vet one person instead of eight, and ask what foreign planners get wrong here.

Contract the vendors to the couple, not to the partner. When Ximena went silent, eleven signed agreements were the difference between a coordination problem and a wedding that does not happen.

Agree the day in writing a week out: they win on anything physical, you win on anything about a person — and propose it as a question, because a handoff proposed and not agreed is not a handoff.

Marry legally at home and hold a symbolic ceremony at the destination. It is almost always the right advice, couples resist it, and the reframe is that the paperwork is got out of the way so the ceremony can be about what it is about.

If they want it legal on site, verify it in writing from a source that is not the venue — because "we handle everything" frequently means the flowers.

Assume you will not litigate. So the contract is a specification, not a threat, and what actually protects you is money held back, specificity, photographs, and the partner's own referral relationships.

Budget the FX spread, the wire fees, and the card fees; understand the fourteen-month rate movement as an exposure rather than a cost.

Your guests are on holiday and it is a holiday they paid for. One completely empty day, minimum. Offer optional activities; do not organise them. Keep the rehearsal dinner to the rehearsal party. And the recovery brunch is the most-loved event of the four days.

A destination wedding does not cost less. It costs the same and a different set of people pay — $1,700–3,900 and a week of leave per couple — and the guests who cannot pay decline, which is not random and will be reported as a scheduling problem.

The cheap season is cheap for a reason. A hurricane does not rain on your wedding; it closes an airport for three days — so the risk is guests who cannot arrive or leave. Book it knowingly, with insurance, a written contingency, and a conversation the couple remember having.

Spaced Review

From Chapter 12 — vetting and the failure question. How does it change here?

From Chapter 28 — substitutability. Where does a local partner sit, and what follows?

From Chapter 21 — you are not the authority on anyone's tradition. How does it generalise?

📐 Project Checkpoint

Build the Riviera Maya four-day schedule.

60 guests · four days in the second week of November · a $68,000 budget · a resort contract in Spanish · and a couple who have already booked the date.

Produce:

1. The distance audit — what you cannot do, and the substitute for each
2. The local-partner brief, and the questions you ask
3. The contract structure, and who is counterparty to whom
4. The legal position, resolved
5. The four-day schedule, with the empty day defended
6. The guest communication, including the cost sentence
7. The hurricane-season risk assessment, and the conversation

case-study-02.md does all seven — and the hurricane-season date is not moved.

Looking Ahead

Chapter 34 is large-scale and multi-day production — load-in, crew, and logistics at volume.

Bring Chapter 25's cascade and Chapter 26's run sheet. Chapter 34's argument is that above a certain size an event stops being a plan and becomes a supply chain, and that the moment it happens is identifiable and is earlier than anybody expects.