When Things Break: The Mid-Trip Recovery Script
Boats break. Chefs cancel. Weather shifts. Suppliers flake. A premium trip's distinguishing moment is often the recovery — handled well, the failure becomes the trip's strongest story. Here's the script.
Over a season of 60-80 trips, something breaks mid-trip on roughly 20-40% of them. Not catastrophically — catastrophic failures are rare — but meaningfully: the boat captain's engine seizes the morning of the planned day on Vis; the chef cancels four hours before the reservation due to a family emergency; the ferry route to Lastovo gets canceled by a sudden tramontana wind; the villa's water pump fails at 23:00 on a Saturday.
The frequency of these moments is the boring truth of premium operations. The interesting truth is that how the DMC handles them determines whether the trip ends in a referral or in a polite-but-cool goodbye. A smooth trip produces a competent-DMC review. A disruption-handled-well trip produces a story — something the client tells friends by name three months later.
This article is the recovery script. Not the anticipated-disruption case (see /articles/plan-b- deliverable for that), and not the client-initiated- change case (/articles/handling-changes). This is the unanticipated mid-trip failure — and the specific conversation and operational pattern that turns it into the trip's strongest moment.
The five recovery rules
Across every failure mode, five rules separate the recoveries that build trust from the ones that erode it. They're not surprising; they're hard to execute under pressure, which is why they need to be rehearsed before the moment.
1. The DMC owns the message — never the supplier
The boat captain's engine broke. The chef canceled. The hotel double-booked. None of these appear in the client-facing message. The framing is always "we had a tightening in the day's schedule" or "we're adjusting Tuesday's plan" — never "Marin's boat broke down."
Why: the supplier name in the client-facing failure message does three things wrong simultaneously. It throws the supplier under the bus (damaging the DMC's relationship). It triangulates the client (now they know who to blame, and the DMC becomes a messenger). It reveals the operational seam (the trip had a single point of failure that the DMC didn't mitigate).
The premium frame: the DMC is the trip, and the trip is adjusting. The supplier doesn't feature. Internally, the DMC has a full conversation with the supplier about what went wrong. Externally, the client sees one consistent voice handling things.
2. The alternate plan is named, not negotiated
The wrong move: "Marin can't take you out today — what would you like to do instead?"
Premium clients are paying to have decisions absorbed. Asking them to choose between options at the moment of failure inverts the value proposition. The DMC who asks is the DMC who didn't already have the backup in hand.
The right move: present the alternate as the plan. "Change of plan for today — sea conditions are shifting, so the boat day moves to the inland Konavle valley instead. Goran (the guide, not me — same name) picks you up at 09:00. Coffee's still at 08:30 downstairs." Specific, complete, not a question.
The client can override if they have strong preferences ("actually, could we do the spa morning today and the Konavle tomorrow?"). But they're overriding a plan, not constructing one. The difference is enormous on the energy axis.
3. The fix is faster than the disruption
The disruption surfaces; the fix lands within 60-90 minutes (or 15-30 minutes for during-the-day in-flight issues). The premium DMC's operational speed is part of the recovery's value.
What "fast" means in concrete terms:
- Initial acknowledgment within 10 minutes
- A short message confirming the issue is known and being worked. 'On it; back to you in 30 minutes with the plan.'
- Full alternate plan within 60-90 minutes for anticipated-but-broken days
- If the boat day was supposed to start at 09:00 and the call comes at 06:00, the client should have the new plan in writing by 07:30 at the latest.
- Full alternate plan within 20-30 minutes for in-flight issues
- If the chef cancels at 17:00 for a 19:30 dinner, the client should know the replacement plan by 17:30.
The speed isn't about heroics; it's about pre-built relationships. The DMC who calls 3-5 supplier contacts in their phone (with whom they have working relationships) and lands a replacement in 20 minutes is operating differently from the DMC who Googles alternates. The Plan-B contingency notes in /articles/plan-b-deliverable are the planned half; relationship-density is the unplanned half.
4. The replacement should match the trip's register, not just the slot
A failure on a high-end booked dinner shouldn't replace with "any open table"; it replaces with a comparable-register restaurant the DMC has a relationship with. A canceled premium boat day shouldn't replace with a generic ferry trip; it replaces with a private inland experience at the same quality level.
The premium-DMC's mental model: the trip's register is a constant. The specific blocks are variables. When a variable changes, the register stays fixed. The client should never feel like the trip downgraded — even when the original plan was structurally better, the replacement should be structurally equivalent in quality and care.
5. Address it once, never again
The disruption happens. The recovery lands. The client accepts and moves on. From this point forward, the DMC does not bring up the failure again. Not the next day with "sorry again about yesterday's changes," not in the closing-day conversation with "hopefully Tuesday's situation didn't affect your overall trip," not in the post-trip Day-3 message with anything reference-able.
The premium frame: the trip went as it went. The failure isn't a story we keep returning to; it's a moment that resolved. The DMC who keeps surfacing it amplifies its salience in the client's memory. The DMC who handles it once and lets it sit allows the client to move past it — and often to remember it later as the moment the trip got interesting.
Worked example: the morning-of boat failure
06:23 on the morning of the planned Vis boat day. Marin, the boat captain, calls. The starboard engine isn't turning over; the marina mechanic estimates 4-6 hours to diagnose, possibly longer. The day's plan was a 09:00 departure from Hvar to Vis with a swim stop at the Pakleni islands en route, lunch on Vis, afternoon at the Blue Cave, evening return.
The recovery sequence:
06:25 — first acknowledgment to client
Quick note — change to today's plan.
We've had a tightening in the day's schedule. Working on the alternate now — back to you in 20 minutes with the new shape of the day. Coffee's still at 08:30. Sit tight.
One message, three sentences. Names the issue without blame, sets the timeline (20 minutes), reassures coffee is still on. Buys the DMC space without leaving the client in silence.
06:25-06:40 — operational work
DMC pulls up phone contacts. The pre-built fallback plan for boat-day failures: inland Konavle valley with the guide Goran (different person from the trip lead), who keeps a flexible Saturday morning specifically for this kind of last-minute pickup. DMC texts Goran: "Hartmann family, family of four, originally Vis boat. 09:00 pickup from the Hvar hotel for the Konavle day. Lunch at Konoba Dubrava. OK?" Goran replies within 4 minutes: "Yes, on it. Will text the driver."
DMC simultaneously messages the Hvar hotel concierge about the change of plans (driver coming at 09:00, no breakfast service interruption needed).
06:43 — full plan to client
Anna, Klaus —
New shape for today: instead of the Vis boat day, we're swapping in the inland Konavle valley with Goran (the guide, not me — same first name). Same energy as the Vis day — outdoor, lunch at a working konoba you won't find in any guidebook, the kids will have water to swim in at the second stop. Pickup at 09:00 from the hotel; back here around 17:00. Same dinner reservation as planned this evening.
Marin will be back on the water Thursday if you want to make up the boat day — totally fine if not. Either way, today shifts inland. Let me know if you want any specific tweaks.
— [Trip lead]
Two paragraphs. Names the alternate as the plan. Frames it positively ("same energy") without over-justifying. Offers the Thursday makeup as a take-it-or-leave-it option. Closes with a one-line override invitation in case the family has strong preferences.
06:50 — client response
Most premium clients respond within 5-10 minutes with some version of "great, see you at 09:00." A minority push back or ask questions — and the DMC handles those in continuing conversation. The crisis moment is over by 07:00.
The rest of the day
The Konavle day runs. It turns out to be a genuinely good day. The family enjoys the inland register; the kids have time at the spring; lunch is memorable. The recovery doesn't require constant attention from the DMC — Goran handles the day; the DMC checks in mid-afternoon with a single "hope the day's landing well" message and gets a thumbs-up reply.
The next day — no follow-up on the failure
The DMC doesn't mention the boat failure the next morning. The trip continues as if Tuesday's plan had always been the Konavle valley.
Three months later, the client tells a friend the trip's best day was the inland day they weren't expecting. The friend asks the DMC's name. The trip becomes a referral.
The four common failure modes
Across a season of operations, four failure modes account for ~80% of mid-trip disruptions. Each has a recovery pattern worth pre-building:
- Supplier mechanical / scheduling failure. Boat engine, vehicle, restaurant closure. Most common. Recovery: pre-built alternate from the parallel-supplier roster (you should have 2-3 backups per critical supplier). Speed: 60-90 min.
- Weather disruption. Sea state, storms, heat extremes. Plan-B contingencies in trip-build cover most of these. Speed: anticipate 24-48 hrs ahead, communicate by evening before.
- Client illness or family emergency. Less frequent but emotionally loaded. Recovery: absorb the logistical burden completely, offer flexibility, don't make money the topic. Speed: respond immediately, don't worry about formal alternates until the client has stabilized.
- Group dynamics / unexpected client needs. Kids tired, an adult overworked from emails, an in-law dynamic surfacing. Often presents as 'we'd like to slow down tomorrow.' Recovery: simplify the day in place rather than rebuild. Speed: same-day.
What kills the recovery
- Defensive opening lines
- 'We are so deeply sorry...' / 'This is in no way reflective of our standards' — long apologies signal panic. The client reads them and concludes things are bad. Matter-of-fact opening, alternate plan, move on.
- Throwing the supplier under the bus
- Already named. The supplier name doesn't appear in the client-facing message even when the supplier is genuinely at fault.
- Mixing refund language into the recovery message
- 'We're happy to discuss any compensation' attached to the alternate-plan message muddles both. If a refund is appropriate (rarely), it's a separate conversation after the trip.
- Asking the client to choose between options
- Already covered. Premium clients pay for decisions absorbed. Choose for them; let them override if they care.
- Bringing the failure up again the next day
- Already covered. The recovery resolved; surfacing it again amplifies the salience in the client's memory.
- Charging differently because the alternate cost more or less
- Premium-trip pricing is a fixed bundle. Cost asymmetries between the original and the alternate are the DMC's problem, not the client's. Don't itemize.
The pre-build that makes recovery possible
The recovery script depends on infrastructure built during the trip-build phase. Three concrete items:
- Plan-B contingencies on critical blocks. From /articles/plan-b-deliverable. The blocks most likely to fail (boat days, outdoor activities, weather-dependent meals) carry a contingency note at trip-build time naming the trigger condition, alternate block, specific alternate supplier, and forward implication. The mid-trip recovery reads from this; it doesn't construct from scratch.
- Parallel-supplier roster for key categories. From /articles/sourcing-guides and /articles/supplier-relationships. You don't have one captain; you have one anchor captain plus 2 backups with whom you have working relationships. Same for guides, drivers, key restaurants. The roster is the infrastructure that makes 30-minute recovery possible.
- Pre-rehearsed messaging templates. Not literal templates — those read as cold — but a mental script. The opening line ('we've had a tightening in the day's schedule'), the alternate-as-plan framing, the no-supplier-naming discipline. Rehearsed enough that under pressure the DMC doesn't have to invent the wording.
The compounding trust effect
A specific psychological effect worth naming: trips where one recovery happens often outperform trips where nothing breaks at all on the relationship axis. The client whose trip ran perfectly has a great time and remembers it as a great trip. The client whose trip had one recovery has a great time AND a specific story about the moment the DMC saved the day. The story is what gets repeated.
This isn't an argument for manufacturing recoveries. It's an observation about why recoveries matter: the moments of demonstrated competence under pressure are some of the strongest referral generators in the entire trip arc. The DMC who can execute the recovery script consistently is the DMC whose disruption-prone trips become the referral-generators in their book.
The short version
Five rules: DMC owns the message (never the supplier), alternate is named not negotiated, fix is faster than the disruption (60-90 min for anticipated, 20-30 min for in-flight), replacement matches the trip's register, address it once and never again. Four common failure modes (supplier failure, weather, illness/ emergency, group dynamics) each with a pattern. Pre-builds that make recovery possible: Plan-B contingencies on critical blocks, parallel-supplier rosters, rehearsed messaging templates. The trips that have one recovery handled well often outperform the trips that ran perfectly — the story is what gets repeated.
Recovery isn't the failure's consequence; it's the operational competence the failure surfaces. The DMC who can run this script consistently has a structural advantage that's invisible until the moment it's needed, and then enormous.
