How to Plan a Multi-City Trip Without Losing the Thread

A multi-city trip is not a longer version of a normal trip. It is a different shape, and it breaks in different places.

One destination means one arrival, one bed, one departure. Three destinations means three of each plus two moves between them, and every move is a small trip of its own with its own confirmation, its own station, and its own way of going wrong. The admin does not grow with the number of cities. It grows with the number of joins between them.

So this is a guide to the joins: route first, then pacing, then the four facts every stop needs, then how to keep all of it readable in an unfamiliar station on one bar of signal.

Start with the route, not the cities

The most common way to wreck a multi-city trip is to pick the places you want and work out the transport afterwards. Do it the other way round: the transport between your stops decides how many stops you can sensibly have.

Most routes fall into one of three shapes, and it is worth knowing which one you are building before you book anything:

• The line. Fly into one end, out of the other, moving forward the whole time. No backtracking, and it usually wants an open-jaw ticket rather than a return.
• The loop. In and out of the same airport, with a circuit in between. Simpler and often cheaper to book, and it costs you the leg back to the start.
• The hub. One base, day trips out and back. You unpack once, and the days out stay cheap and cancellable when the weather turns.

The hub is the shape people skip because it feels less ambitious, and it is very often the better trip. Four nights in one city with two day trips beats four cities in four nights nearly every time, at a fraction of the admin.

Count nights, not days

A stop that looks like two days is frequently one usable day. You arrive at four in the afternoon and leave at ten the next morning: an evening and a breakfast.

The honest unit is nights, and the honest rule is that a travel day is not a day. Moving between cities costs a morning and an afternoon by the time you have packed, checked out, traveled, found the next place, and checked in. Budget that day as spent and you will be pleasantly surprised. Budget it as free and every stop will feel rushed.

A workable default for two weeks is three stops, not five. Two nights minimum anywhere you have to unpack, three or four anywhere you actually want to see.

Book the joins before the fun

Order matters more than usual here, because each booking constrains the next one. Lock the moves first, then the beds, then everything with a time on it.

1. The long flights in and out. These set the outer edges of the trip and are the least flexible thing you will buy.
2. The moves between cities. Trains, ferries, buses, short flights. This is the real constraint. A seven hour train you did not know about will quietly delete a stop.
3. The beds. Now that you know when you arrive and when you leave, book against nights rather than against hopes.
4. The fixed and prepaid things. Tours, tables, timed museum tickets, anything non-refundable.

This order also surfaces the unreachable stop early, while there is still time to change the route instead of the trip.

Four facts per stop

For each city on the route, you want four things written somewhere you can read without a signal:

• How you arrive. Which station or terminal, and at what time.
• Where you sleep. The address in the local language, plus the check-in window, the single most commonly missed detail on a multi-city trip.
• How you leave. Which station, at what time, and how long it takes to get there from where you slept.
• What is fixed. Anything prepaid, with its confirmation code.

With those four for every stop, the trip survives almost anything else going wrong. Without the departure station for city two, you find that out in city two.

The handoff days are where it fails

Ask anyone about a multi-city trip that went badly and the story will be set on a moving day. Not on a beach and not in a museum. In a station, a lobby, or a taxi. Handoff days have a pattern worth planning around:

• Check-out is earlier than the train. You have four hours and a suitcase. Check whether the hotel holds bags before you arrive, not after.
• Check-in is later than the arrival. The same problem in reverse. Most places hold a bag, and very few mention it unprompted.
• The two legs are not on one ticket. Miss the connection and it is entirely your problem to solve and pay for. Worth knowing before you cut the margin thin.
• The confirmation is in a different app from the last one. This is the small one that gets you, at the barrier, holding up a queue.

Give every moving day a deliberate margin, and give it more when the next thing after arrival is prepaid.

Then there is the assembly problem

Here is the part that is nobody's fault and everybody's problem. A three city trip is typically booked across six to ten providers: two airlines, a rail operator, three hotels, a car, a couple of tours. Each confirms in its own format, at its own time, and none of them know the others exist.

So the route lives in your head and the details live in fourteen places. Some are emails, some are PDF attachments, one is a screenshot a friend sent, and one is a photo of a paper voucher from a ferry company with no website worth speaking of. The plan is complete and unreadable, which on a moving day is the same as not having it.

That is the actual work of a multi-city trip, and the part worth handing to software. Deciding that Ghent deserves two nights is judgment. Retyping a train confirmation is not.

A pre-departure checklist

1. Every leg and every night sits in one timeline, in order, moves between cities included.
2. Each stop has its arrival, its address, its departure, and its confirmation codes.
3. The plan opens with no signal. Test that in airplane mode before you leave home, not at the airport.
4. Everyone traveling with you sees the same plan, not a screenshot of it from nine days ago.
5. Moving days have margin, and you know in advance which one is tight.

Being fair about the tools

TripIt has been doing the forward-a-confirmation trick longer than anyone and is very good at it, with a mature paid tier.

Wanderlog is strong on the research half: maps, saved places, and routing between them while you are still deciding where to go.

Tripsy is a genuinely lovely piece of design if you are in the Apple ecosystem and want something native.

Where Petrel fits

Petrel Voyage is built for the assembly problem specifically. Send it whatever the booking arrived as, and it builds the route.

• Any format. Forwarded emails, PDFs, screenshots, photos of paper vouchers, even a spreadsheet. That regional ferry is exactly the case this exists for.
• Day by day, in order. Flights, trains, hotels, and reservations land in one timeline with travel times between stops, so a moving day reads as a sequence rather than a scavenger hunt.
• Live flight status sits on the flight card, next to the hotel it affects, which is the only place that information is useful.
• Offline for viewing. Your plan opens without a signal, addresses and confirmation codes included. To be precise about it: offline means readable, not editable, and live status still needs a connection to refresh.
• Free collaborators. Anyone on the trip can view and edit without paying, and you can split costs between you, so a change on a moving day is one edit instead of four text messages.
• Receipts and a print-ready expense report, which matters more here because the costs are spread across more countries and currencies. Plus public share links for whoever is meeting you, and an automatic recap email once the trip ends.

On privacy, plainly: Petrel does not connect to or scan your inbox, does not sell your data, and does not train AI on your bookings. You forward what you want organized, and that is all it sees. Our page on why we built it this way goes into the reasoning.

If you would rather start from a route than from a blank page, the itinerary library has multi-city routes with suggested nights per stop and how to get between them. And if the offline part is what you care about most, our offline travel checklist covers how to test it before you need it.

The short version

Pick the route shape before the cities. Count nights, not days, and treat every moving day as spent. Book the joins first and the beds second. Know four facts for every stop, and keep them somewhere that opens without a signal and that everyone on the trip can read. Then the trip stops being a stack of confirmations you hold in your head, and turns back into the thing you booked it for.

You can build your route at https://petrelvoyage.com. The first trip is free, with no account and no credit card. If you want the basics first, our guide to building a trip itinerary walks through it step by step.