How a trip actually gets built

Every itinerary starts the same way — not with a destination, but with a conversation about how someone actually wants to travel. Pace, comfort with the unfamiliar, what "extraordinary" means to them specifically. Two clients heading to the same region can end up with entirely different trips, because the starting point was never the map.

From there, it's a process of narrowing rather than adding. It's tempting to build a longer, denser itinerary — more stops, more inclusions, more "value." In practice, the itineraries that work best are usually the ones that resist that instinct: fewer destinations, given more time each, planned around the specific conditions — season, ship, access — that make each one worth visiting properly rather than briefly.

This is where firsthand knowledge earns its place. Knowing which ship actually has the ice class to reach a specific bay, which season a particular waterfall is worth seeing, which departure dates avoid a region's least reliable weather window — none of that comes from a supplier's sales sheet. It comes from having asked the right questions, or having been there.

The last stage is the one that rarely gets mentioned: what happens if something changes. Weather shifts, a landing gets cancelled, a connection is missed. A good itinerary isn't just a strong plan — it's a plan built with enough judgment behind it to adjust well when reality doesn't cooperate. That's less about the document itself and more about who built it.

By the time an itinerary reaches a client, it's already been through several rounds of exactly this kind of scrutiny — not to make it longer, but to make sure every piece of it earns its place.