Anatomy of an itinerary

abhilaksh · JUNE 2026 · 5 MIN READ

The finished itinerary that lands in a client’s inbox looks calm. A clean document, a day a page, the trip resolved into a sequence that reads as though it could only ever have gone this way. That calm is the product. What it hides — deliberately — is that almost every line in it was a fork, and that the trip exists in the form it does because of a hundred small decisions that were taken so you wouldn’t have to take them.

So let me turn one inside out. Here is a real trip — ten nights in Switzerland, for a couple celebrating a twenty-fifth anniversary — rebuilt with the forks left visible. The couple is an illustration; the decisions are exactly the ones we make.

The brief, and the brief underneath it

It arrived the way most do, over WhatsApp, in a sentence and a half: We want to do Switzerland properly for our anniversary, sometime around September, ten nights or so, and we don’t want it to feel rushed.

Three useful facts and one buried one. The useful facts: Switzerland, September, ten nights. The buried one is the last clause — we don’t want it to feel rushed — which is the entire design instruction. It rules out the version of Switzerland that most first itineraries reach for, the one that touches six towns in ten nights and spends a third of the trip changing hotels. The couple has just told me, without knowing it, that the trip’s organising principle is fewer bases, longer stays, and a pace that has air in it.

A short call filled in the rest. Mid-fifties, both worked hard for this, third trip to Europe but first to Switzerland. They want the mountains more than the cities. He is a serious walker; she is not, but loves a view she can reach without a hike. Pure vegetarian, and she is particular about it in a way that has been disappointed abroad before. They’d rather two excellent dinners than six average ones. And the line that decided more than any other: we want one or two places we don’t have to leave.

Everything below follows from those sentences.

Fork one: the shape

Before a single hotel, the shape of the trip. Ten nights, September, mountains over cities, no rush. The instinct of a brochure is a loop — Zurich, Lucerne, Interlaken, Zermatt, St. Moritz, back to Zurich — six stops, five hotel changes, a packed train calendar. I built the opposite.

Two anchor bases of four nights each, with a short hinge in between. One in the Bernese Oberland, for the walker and the view-from-the-terrace; one in Zermatt, for the Matterhorn and the trip’s emotional centrepiece. The hinge: the Glacier Express as a travelling day, not a chore to be endured but a set-piece in its own right. Ten nights become four plus four plus two transit, with only two real unpackings. The “we don’t want it to feel rushed” clause, made into a structure.

Almost every line in a finished itinerary was a fork. The calm of the document is the product; the hundred decisions underneath it are the work.

Fork two: arrival, and the day you don’t plan

They land at Zurich in the morning off an overnight from India. The brochure instinct is to seize the day — train straight to the mountains, start the holiday. I did the opposite again, and this is a fork worth naming because it recurs on every long-haul itinerary.

The first day is not for sightseeing. It is for arriving. A long-haul red-eye from Delhi puts you on the ground tired, off your body clock, and reaching for decisions you shouldn’t be making. So the first night is a quiet hotel near the lake in Zurich, an easy lunch, no agenda, an early night — and the mountains begin on day two, on rested legs, when the first view actually lands instead of arriving through a fog of fatigue. The lost half-day is not lost. It is the price of the first real day being a good one.

Fork three: which base in the Oberland, and which room

The Bernese Oberland gives a choice of bases, and they are not interchangeable. Interlaken sits in the valley between the lakes — convenient, well-connected, and a little too busy with through-traffic to deliver the calm the brief asked for. Wengen and Mürren sit up on the mountain shelf, car-free, reached by cog railway, quieter, with the high peaks directly overhead. Grindelwald sits in its own valley, dramatic and slightly more developed.

For this couple — quiet, view-led, a walker and a non-walker — the answer was a car-free village up on the shelf. The walker has the high trails from the doorstep; the non-walker has a terrace with the Eiger, Mönch and Jungfrau directly across the valley and a cog railway to carry her up to the views she wants without a climb. Interlaken would have been more convenient and entirely wrong.

Then the room, which is its own fork. At a mountain hotel the difference between a standard room facing the slope behind and a room facing the peaks across the valley is the difference between a nice stay and the stay they came for. So the booking specifies the valley-facing side explicitly, in writing, on a preferred-partner rate — which means it also carries breakfast for two and a credit, and arrives flagged with the occasion so the hotel knows, before they walk in, that it is a twenty-fifth anniversary and that the view is the point.

Fork four: the Jungfraujoch, and the weather rule

Every Oberland itinerary faces the Jungfraujoch question — the railway to the highest station in Europe, a genuinely remarkable thing and also an expensive, weather-dependent, crowd-prone one. The fork is not whether but how.

The rule we write into the trip: the Jungfraujoch is a fair-weather, early-morning outing, and it floats. It is not pinned to a date. It is pencilled for the first clear morning of the four-night stay, decided the evening before off the mountain forecast, because spending the money and the hours to ascend into cloud is the single most common way this excursion disappoints. Building it as a floating, weather-triggered day rather than a fixed appointment is a small piece of design that depends entirely on having booked four nights in one place — which is, in turn, why the trip was shaped that way. The forks chain into each other.

Fork five: the travelling day

The hinge between the two bases is the Glacier Express, and it is a set of decisions in itself. First class over second, for the wider windows and the calmer car, on a trip whose whole pretext is the scenery. The seats reserved the moment the booking window opened, because the panoramic cars sell out and a reservation is mandatory regardless. Luggage sent ahead by the door-to-door service so they travel with a day bag and meet their cases at the next hotel, rather than wrestling suitcases across a platform connection. A booked table in the dining service for lunch as the trip crosses the Oberalp Pass.

I will not lay out the full transport logic here — trains, drivers, internal flights and ferries get their own deep treatment, because the choices are genuinely involved and deserve the room. The point for this article is narrower: the travelling day was designed as part of the trip, not left as the gap between two real things. That is the difference between a journey and a transfer.

Fork six: Zermatt, and the crescendo

Zermatt is the second anchor and the emotional peak, and its position in the sequence is deliberate. You build to it. Arriving in Zermatt on day six, with the trip already in its rhythm and the legs already mountain-fit, is a different arrival from landing there jet-lagged on day one. The Matterhorn deserves to be the thing the trip has been climbing toward, not the thing you stumble into before you’ve adjusted.

The base logic repeats and tightens: Zermatt is car-free, reached by the final cog railway, and the room is specified for a Matterhorn-facing aspect because in Zermatt the mountain is the view and a room without it is a different, lesser hotel at the same price. The walker gets the Gornergrat railway and the high trails; the non-walker gets the same railway purely for the golden-hour view from the top. Two excellent dinners are booked here — the couple asked for quality over quantity — with the tables held under their name and the walking time from the hotel noted, because a booking you can’t find in the dark is not a booking.

The thread that runs through every line: the vegetarian brief

One instruction touched every day of this trip, and it is the kind of thing that separates a careful itinerary from a generic one. Pure vegetarian, and particular about it.

That is not a footnote we add at the end. It is a brief that goes to every hotel and every restaurant before arrival, in specific language — not “vegetarian,” which means different things in different kitchens, but exactly what they do and don’t eat, and a note to confirm the kitchen can deliver it well rather than as an afterthought. In a country where the default dinner is not built around vegetables, the difference between a hotel that was told three days ahead and one that finds out at the table is the difference between a memorable meal and a plate of sides. We pre-identify the restaurants that handle it genuinely well and book those, rather than letting the couple discover the hard way which kitchens can and can’t.

“Pure vegetarian, and particular about it” is not a footnote at the end. It is a thread that runs through every dinner on the trip, briefed three days ahead, in specific words.

The same discipline covers the quieter India-specific layer — the forex guidance so they aren’t bled by card markups and bad airport rates, the note on the tax that applies to the package and the reassurance that it is recoverable rather than lost, the WhatsApp line open before, during and after. None of it shows in the photographs. All of it is why the trip runs clean.

The trip is built twice

Here is the thing the finished document conceals. The trip is constructed twice. The first time it is a decision tree — shape, then bases, then rooms, then the floating weather days, then the travelling day, then the dining, then the threads that run through all of it — each fork constrained by the ones before it, the whole thing held together by a single buried instruction in the original brief. The second time it is written out as the calm, day-a-page document that arrives in the inbox, with every fork resolved and invisible, so that all the client experiences is a trip that seems to have assembled itself.

That document is the part you can see, and we have written separately about how it’s made and why it reads the way it does. This piece is about the part you can’t see: the tree underneath it. Ten nights in Switzerland for an anniversary looks, when it’s finished, like an obvious sequence. It is the least obvious thing in the world. It is a hundred forks taken on someone’s behalf, by someone who has stood on those platforms and eaten in those dining rooms and watched that exact couple come home and write about a single morning on a terrace with the Eiger across the valley.

That morning was a fork too. We took it for them.

Mentioned in this piece