Most itineraries are built forwards. You pick the arrival date, add the things you want to see in the order you found them, and keep going until the days run out. The result is almost always the same: a trip that is front-loaded with energy and back-loaded with logistics, and a final two days spent doing admin instead of anything you would remember.
Building backwards fixes this, and it takes about twenty minutes.
Start with the day after you get home
Write down what that day is. Work? A wedding? School run? Then ask what state you need to be in for it.
This single question determines more of the trip than the destination does. If you have a Monday morning meeting, a Sunday-night landing is a mistake regardless of how good the fare was. If you have nothing for three days, a red-eye is free.
Then the last full day
Protect it. Do not put a five-hour transfer, a checkout at 6am or a bucket-list item on it.
The last full day should be in the place you liked most, doing the thing you already did once and wanted to do again. This is the single highest-return change most people can make to an itinerary, and almost nobody makes it, because when you build forwards the last day is just whatever is left.
Then the return transfer, properly
Count backwards from the flight, honestly:
- Time at the airport before departure, for the airport you are actually leaving from.
- Transfer time, in that city, at that hour, in the traffic that exists.
- Checkout and packing.
- Breakfast, because otherwise you will not eat.
Add them up. That number is how much of your last day the flight consumes. Most people discover it is the whole day and plan accordingly for the first time.
Then place the hard-booked things
Some elements cannot move: a permit with a fixed date, a train that runs twice a week, a festival, a booked trek. Put those in next, because everything else has to flex around them.
This is also the point where impossible trips reveal themselves. If the fixed items do not fit with adequate travel time between them, the trip is too short and you find out now rather than on day four.
Then the buffer days
One buffer per week, minimum. Not a rest day exactly; an unassigned day.
It absorbs the delayed flight, the day you feel unwell, the place you want a second go at, the weather. A trip with no slack converts every minor problem into a cascade of cancellations. A trip with one free day per week absorbs almost everything without you noticing.
The instinct is to fill these. Do not. If you reach the end of the trip having used none of them, you got three good unplanned days.
Then arrival, and only then
Now place the arrival. Two rules:
The first day is not a real day. Whatever the flight, however short, treat it as half. Jet lag, the hotel not being ready, learning how to cross the road, finding out that the SIM card place shut at six. Plan one easy thing and nothing else.
Do not put the most expensive or most weather-dependent thing on day one. If it is cancelled you have the whole trip to reschedule. On day eight of nine you have nothing.
Finally, fill the middle
Only now do you add the things you actually wanted to see. You will find you have fewer slots than you expected, which is the point. The list gets cut by the shape of the trip rather than by exhaustion halfway through.
Two things that help here:
Group by geography, not by interest. All the things in one district on one day, even if they are unrelated. Transit is the hidden cost in every itinerary.
One anchor a day. One thing that must happen. Everything else on the day is optional. A day with three anchors is a day where you will be late for two of them and enjoy none.
What this looks like in practice
A nine-day trip planned backwards typically ends up as: half a day arriving, seven usable days of which one is buffer, and a last day mostly consumed by the flight. Six real days.
People find that number depressing the first time they see it. It is the same six days they always had. The difference is that now they are spending them deliberately.