PlanningBy ArrivLast checked
How to plan an itinerary by day
Group the stops by geography before you think about the clock, then put each day in one part of the city and order it so you move in a line. Hang each day on whichever booking already has an hour attached to it. Then leave one block a day unplanned, because that block absorbs the long lunch and the thing you find on the way.
Geography before the clock
Most bad itineraries fail on scatter, because four reasonable stops arranged as a star around your hotel cost you two hours of transit while the same four in a line cost twenty minutes. You can usually see which one you have built the second the pins land on a map.
This is also why choosing a neighborhood to stay in carries so much weight, since a base in the middle of your days beats a cheaper room that adds forty minutes to every morning. That ride is a tax you pay daily, and it compounds once the week is long.
Fixed times are the skeleton
A timed museum entry, a dinner reservation, or a train decides where the day bends, and everything flexible arranges itself around that. Try it the other way round, filling the day first and slotting the fixed things in later, and you will spend an evening rebuilding it once something slips.
Write each day as blocks: morning, after lunch, evening. Clock times promise a precision you will not hold, and the first slip makes the whole day feel like a failure even if you missed nothing. How much to put in each block is a separate question, though the answer is a shorter one.
A Chicago Saturday, ordered
Start with the pin that has a time on it: a 10:30 museum entry, a 7pm table, and then put everything else on that side of town. Walk between stops, or take one transit hop, because a place sitting alone across the river belongs to a different day, however essential it looked in the planning doc.
A Chicago weekend and a San Diego weekend are already built this way, so you can use them as a shape: one cluster a day, meals inside the cluster, one block left empty. Swap the pins and keep the geography, because the geography is the part doing the work.
What to do with leftovers
Every trip collects places that did not fit, which is why you keep those as a maybe list pinned to the nearest day. If lunch runs short you have somewhere to go, and if lunch runs long the day still worked, because the reservation and the empty block were the plan all along.
A clock-time itinerary ("2:15 the gallery, 3:40 the cafe") breaks at the first queue, while a block itinerary (morning gallery, after lunch a cafe or a walk) absorbs it. That is the whole trick, and it is also why sharing a live plan beats a PDF with hours printed on it.
Once you have a 10:30 museum entry near the lake and a 7:30 dinner in the same neighborhood, a Saturday in Chicago writes itself. Morning is the museum, lunch is a ten-minute walk away, and the afternoon is the nearby park or nothing at all. Evening is the dinner you booked, which means anything in another neighborhood moves to Sunday.
Rebuilding a PDF at 4pm on a phone with twelve percent battery is how groups miss the table, so keep the leftovers loose while the skeleton stays fixed. Two things carry the day: the booking with an hour on it, and the block you left deliberately blank.
Step by step
- 01
Map every place first
Get each stop onto a map with an address, because the clusters show up straight away once they are all in one place.
- 02
Assign clusters to days
One area per day, and if you have a place sitting alone across town, pair it with the day that ends nearest to it.
- 03
Drop in the fixed times
Reservations and timed tickets go on their day first, so the rest of that day can form around them.
- 04
Order each day as a path
Sequence the stops so you walk in one direction and never double back across the same bridge twice.
- 05
Leave one block empty
One a day, because that is the difference between a schedule and a trip.