The Plan B Itinerary: When to Send It, How to Frame It
Premium travel breaks — weather days, supplier flakes, illness, regional closures. The DMCs that handle these well send a Plan B itinerary, not an apology email. Here's the document and the moment.
Premium travel breaks. Croatia gets unexpected rain in August; the boat captain's engine seizes the afternoon of the planned day on Vis; the chef closes for a family emergency two days before the booked dinner; a regional ferry strike shifts the whole week's travel logistics on the day the family is supposed to move to Hvar. None of this is rare. Over a season of 50-80 trips, something breaks mid-trip on roughly 20-40% of them.
What separates the premium DMCs from the rest isn't whether things break — that's constant. It's how they handle the break. The generic-agency response is an apology email and a refund offer. The premium response is a different document: a Plan B itinerary, sent in advance of the disruption when possible, on the day-of when not.
This article is about when to send it, how to structure it, and the specific framing that turns a service failure into a relationship-deepening moment.
What a Plan B itinerary is
A Plan B itinerary is a structurally separate document from the main trip. Same family, same dates, same DMC — different blocks for the days where the original plan fails. The document the client receives looks like their itinerary, but with the contingencied blocks swapped for their alternate versions and a quiet accent dot marking the changes.
The premium implementation handles two cases:
- Anticipated disruption: weather, sea state, seasonal closures. The DMC saw the forecast 24-48 hours out. The Plan B lands in the client's inbox or WhatsApp before the change is needed. The client knows what's happening tomorrow before tomorrow comes.
- Real-time disruption: supplier failure, illness, sudden closure. The change happens during the day. The Plan B replaces the affected block(s) in real time. The DMC's job is to absorb the disruption invisibly — the client experiences the swap, not the failure.
Both cases use the same underlying document mechanic. The difference is timing and how the DMC frames the communication around the swap.
The mechanical structure
In myDMC, every block carries an optional Plan-B contingency field — a one-line description of what happens if the original block can't happen. The plan-b preview variant swaps each contingencied block for its alternate; non-contingencied blocks proceed as planned for that moment. Print that view when you need it as a file — the Generate PDF pipeline does not render the variant yet.
For a 6-day trip, typically 5-8 blocks carry contingencies. The trips that genuinely break usually break in only one of those blocks; the Plan B PDF is the document that reflects exactly that block's swap. The client sees the rest of the trip continue, with one alternate routing.
When to send the Plan B
Three trigger windows, each with a different framing:
24-48 hours ahead (anticipated)
The forecast is showing a meaningful weather change for the day after tomorrow. The boat day will be uncomfortable or unsafe. The DMC sees this on Sunday afternoon for the Tuesday boat day.
The message that goes out Sunday evening:
Anna, Klaus —
Quick heads-up for Tuesday: the swell forecast just jumped to 1.8m by mid-morning, which puts the Vis boat day past the comfortable threshold for kids on a three-hour open-water leg. We're swapping in the inland Konavle valley day instead — same arc (lunch outdoors, swimming somewhere, slower pace), different geography. Marin's on standby for Thursday if the sea calms; if not, we'll lock in a different boat day next year.
I'll send the updated Tuesday document tonight — same shape, different specifics. Text if you want to hear the alternate before then.
— Goran
Two paragraphs. Names the reason (not too defensively, not minimizing). Names the alternate (specific, not vague). Frames the future (Marin standing by for Thursday, the ongoing relationship). Signs off in voice.
Followed by the Plan-B PDF — same document the family already has, with Tuesday's block replaced. The family opens the new document and sees the trip continue, just with one different day.
Morning-of (in-progress)
The captain calls at 06:30 with an engine problem; the chef's in the hospital from food poisoning; the venue closed unexpectedly. The DMC has 90 minutes to execute the swap.
The message that goes out at 07:15:
Quick note — change of plan for today.
Marin's engine threw a problem this morning so the Vis boat day isn't happening. Bumping in the backup: Goran (the guide, not me — same name) is picking you up at 09:00 for the Konavle valley instead — lunch with the family at the konoba you won't find in any guide, and the kids will have water to swim in at the second stop. Same kind of day, different geography.
Sending the updated day in 20 minutes. Coffee's still at 08:30 in the breakfast room.
Three sentences. Faster than the anticipated case because the family is about to start their day — they need to know now, in summary, with the new pickup time. The updated document follows; the immediate message carries the essentials.
The during-the-day swap (real-time)
The boat day is half over and the wind picks up. The captain pulls into a sheltered cove for lunch as planned; the afternoon's open-water leg is no longer safe. The DMC's job during lunch is to communicate the swap to the family in person or by message:
Just so you know: Marin's saying the afternoon wind is shifting on us, so instead of the open crossing to Korčula we're going to head into Vis town for the afternoon — different beach, different lunch spot, much easier sea. Quieter version of the day, but the kids will still get their swim time. Picking us up again at 17:00 for the run back to Hvar.
During-the-day swaps don't need a new PDF; they need a clear conversational message that names the swap, why, and what happens next. The Plan-B PDF gets used for the anticipated and morning-of cases; the during-the-day case is verbal/messaged.
What the Plan B document looks like
Same as the main itinerary, with three small differences:
- Cover identifies it as Plan B. 'Plan B Itinerary · No. 247' on the cover, with a small accent dot before the title. The client sees instantly that this is a swap document, not a replacement.
- Swapped blocks render their contingency content. What was 'Boat day to Vis with Marin' is now 'Konavle valley day with Goran (the guide)' — same block structure, alternate content.
- Non-swapped blocks render unchanged. The other days, the other blocks within affected days, stay exactly as they were. The document looks like the trip mostly continued; only the necessary parts changed.
The visual continuity is the entire point. A separate "here's the new plan" document that looks nothing like the original itinerary signals improvisation. The Plan B that looks like the original itinerary with one block changed signals control — the DMC anticipated this; the swap is part of the system, not a panic response.
How to write Plan B contingencies
The contingency line on each block is written at the original trip-build time, not at the moment of the disruption. The DMC who writes contingencies during the panic is the DMC scrambling; the DMC who wrote them during the build is the DMC who's already three steps ahead.
The four-part format that works for each contingency:
- The trigger condition. What has to be true for the Plan B to fire. 'If the swell is over 1.5m' / 'If the chef cancels' / 'If the ferry is canceled.' Specific, falsifiable.
- The alternate block. What replaces the original — a different activity, different supplier, different geography. Should have the same character as the original (active day stays active, slow day stays slow), not just be a logistical substitute.
- The specific alternate supplier. Already lined up, not 'we'll figure out a backup if needed.' The chef's backup is a specific other chef. The boat day's backup is a specific other captain or a specific inland day with a specific guide.
- The forward implication. Does the trip continue normally after the swap? Is something else shifting? One line: 'Rest of the day unchanged' / 'Will push the spa session from Wednesday to Thursday to free up Wednesday morning.'
A good contingency reads as a real plan, not a hedge. "If something goes wrong, we'll figure something out" isn't a contingency; it's a gap. The contingency that names the specific alternate supplier and the structural arc preserves the trip's character regardless of which version actually happens.
What kills Plan B execution
- No pre-written contingencies
- Building the alternate plan during the disruption is too slow and produces lower-quality alternates than building it during the trip-build. By the time the disruption hits, the DMC's bandwidth is consumed by other operational issues — there's no slack to source a great alternate.
- Apologies that are too long
- 'We are so deeply sorry for this disruption and want to assure you that this is in no way reflective of our standards' tells the client this is unusually bad and the DMC is panicking. The premium framing is matter-of-fact: 'change of plan; here's what's happening; same arc.'
- Refund offers in the same message as the Plan B
- Mixing the alternate-plan message with 'we'll refund the difference' confuses the framing. The alternate plan stands on its own; if a refund is appropriate, it's a separate conversation after the trip ends.
- Excessive detail in the Plan B message
- Three sentences in the message; the rest in the PDF. A wall of text in the immediate communication signals overwhelm. The PDF holds the detail.
- Blaming the supplier in the client-facing message
- 'The boat company let us down today' is the wrong framing even when it's true. The DMC owns the trip; the supplier name doesn't appear. The captain's engine is 'we had a tightening in the schedule today,' not 'Marin's boat is broken.'
The trust dynamic
Counterintuitively, trips with one Plan B execution often outperform trips with zero disruptions on the client-relationship axis. The reason: the smooth trip shows the DMC doing competent work. The disruption-handled-well trip shows the DMC doing extraordinary work.
The family who experienced the original plan running smoothly remembers a great trip. The family whose boat day got swapped to a brilliant inland alternative remembers that day — the moment the DMC saved the trip. Six months later, they tell that specific story to friends asking about Croatia. The smooth trip becomes a general recommendation; the disruption-handled trip becomes a specific anecdote.
This isn't an argument for manufacturing disruptions. It's an observation about why Plan B execution matters: the moments of recovery are often the moments that produce the strongest referral stories. The DMC who can execute well under disruption is the DMC whose clients talk about them by name.
What the Plan B is not
- A worst-case plan
- Plan B isn't 'if the entire trip falls apart, here's the backup trip.' It's 'if this specific block fails, here's the swap for that block.' Block-level, not trip-level.
- A negotiation
- The Plan B is delivered as the plan, not as a request for the client to choose between A and B. Plan A is what's happening unless conditions force Plan B; once they force it, Plan B is what's happening. Premium clients don't want to make the call between bad options; they want the DMC to make it.
- A discount opportunity
- The Plan B should deliver the same trip value as Plan A, not a cheaper version. If the alternate genuinely costs less, the DMC absorbs the savings (or credits a small amount as a courtesy); the trip doesn't get downgraded along with the routing.
- The default plan
- Plan B is the swap, not the trip. DMCs that ship Plan A and Plan B as parallel options on the original proposal are confusing the client — pick the trip you'd actually deliver, hold the alternate for when it's needed.
The cumulative effect
A DMC running Plan B execution well across a season accumulates a reputation for being the kind of agency that handles disruption. That reputation is operationally valuable in two ways:
- Premium clients increasingly self-select toward DMCs with this reputation
- Travel agents and concierges know which DMCs handle weather days well and route accordingly. The reputation pre-qualifies inquiries.
- Suppliers prefer working with these DMCs too
- A supplier whose own service has a hiccup wants to work with a DMC who handles it professionally — no client-facing blame, clean recovery. The DMCs with the reputation get supplier loyalty in return.
The Plan B feature isn't a backup — it's marketing. The trips that execute well under disruption become the trips that get talked about.
The short version
Plan B is a separate document with the contingencied blocks swapped, sent 24-48 hours ahead (anticipated), morning-of (in-progress), or used as the script for a during-the-day verbal swap. Contingencies are written during the trip-build, not during the disruption — four parts: trigger condition, alternate block, specific supplier, forward implication. The framing is matter- of-fact, not apologetic; no supplier-blaming in client messages; no refund offers mixed with the alternate-plan communication. Trips that execute Plan B well often outperform smooth trips on the relationship axis.
Most premium DMCs handle disruption reactively. The premium ones treat it as a designed-in feature of every trip and execute it as part of the operating system. The documents and the framing are the visible mechanics; the underlying habit is what separates the agencies that compound from the ones that don't.
