How do you build a day-by-day itinerary?
You build a day-by-day itinerary by writing every date of the trip, marking the dates already spent on transport, giving each remaining day one anchor, and leaving one block with nothing you will be charged for missing. Book in that order. The attractions come after the nights exist. The worked week uses invented cities and invented times. It shows the sequence of decisions, and it is not a sample you should copy onto a real map.
Start from the dates you already know
Write the calendar span before you write a single sight. If you are leaving on a Saturday and flying home on the following Sunday, you have eight dates, and several of them may already belong to airports. Put the fixed events on those dates next: a wedding, a conference session, a match. Those lines do not move to make room for a museum.
Then name the cities in the order you will actually travel. Choosing the order of cities comes before the day grid, because a city inserted out of line adds a travel day you have not drawn yet. Confirm airport codes in IATA’s code search when a flight is part of the order. The code on the ticket is the field you will land at, and a different field can move the hour you reach the neighborhood.
Count usable days with how many days to spend in a city. The day grid is that count, expanded so each date has a job. Arrival days, departure mornings, and hub nights stay on the calendar and stay off the list of days that receive an anchor.
Give every date a job title
Each date gets one of four labels, written in the margin before any activity is named.
A travel day is for moving between cities, or for the airport process around a flight. The label stays even if the vehicle runs overnight. What counts as a travel day is the test, including the morning you step off a night train.
An arrival day is the date you land or roll into a city and still have the transfer, the bags, and the check-in in front of you. It can share a date with a flight. It does not receive the reservation you would hate to miss.
A city day starts in the city, with no long-distance move in the middle of it. It can hold one anchor.
A slack block is a city day, or a half day, that you leave empty on purpose. How much slack to leave is the longer version. The day grid only needs the block to be visible, so later booking does not quietly fill it.
One anchor, then the hours around it
An anchor is the single booked thing that justifies the day: a timed entry, a meeting, a trailhead with a permit, a dinner you crossed the city for. Place it where a delay in the morning does not destroy it. Midday or early afternoon is the usual slot. The morning stays free for sleep, a slow start, or the last of a transfer. The evening stays free for a meal you can move.
A second place on that day should be close to the anchor, open to walk-in visitors, and easy to skip. If you want two anchors, they need two dates. Stacking them is how a 20-minute delay at a cloakroom becomes a forfeited second ticket.
Match the number of anchors to the number of city days. Two city days support two anchors. Extra ideas stay on a shortlist under the day, marked as unbooked. What a travel itinerary is keeps that shortlist from looking like a confirmation. When the trip crosses many time zones, CDC’s jet lag page says to consider arriving at least two days before any important event. How to plan the first days around jet lag is that pass, and the grid should already show those dates as light.
Book from the outside in
Buy in an order that matches how hard each piece is to change.
- Transport between cities, once the order is stable. On two tickets, the buffer is the decision in how much layover time you need. IATA’s minimum connecting time is the shortest official transfer interval for a connection the airline is willing to build, and it is a different number from that buffer.
- Lodging for the nights those tickets imply, in the neighborhood you will return to in the evening.
- The anchors, on the city days only, after the lodging address is known.
- Nothing on the slack block. A seller who needs a card number is not selling slack.
Read the change rule before you pay, especially on lodging. A prepaid night you cannot move will fight the slack block the first time a train slips. Hold the confirmations together. A day-by-day plan that lives in a chat thread, while the tickets live in five inboxes, will be wrong the first time one seller changes a time.
An illustrative week, built in order
Alden and Bruck are invented, and so is every clock time. The point is the order of the decisions.
The span is Saturday through the next Friday, seven dates. A flight lands in Alden on Saturday at 18:10 local. A train leaves Alden for Bruck on Tuesday at 10:00 and arrives at 13:40. A flight leaves Bruck on Friday at 11:20. No other transport is booked. The traveler has not crossed enough time zones to treat jet lag as the constraint, so the light first day is about the landing, not about the clock shift.
Jobs, written before any sights:
- Saturday. Arrival day in Alden. Dinner if the flight is on time.
- Sunday. City day. One anchor.
- Monday. Slack. The word “unbooked” is the whole plan.
- Tuesday. Travel day. Afternoon in Bruck is a walk at most.
- Wednesday. City day in Bruck. One anchor.
- Thursday. City day in Bruck. One anchor.
- Friday. Travel day. Morning flight. No anchor.
Only after those labels exist does the traveler pick the Sunday anchor and the two Bruck anchors. A museum that is closed on Sunday is either moved to a different city day or dropped. It is not pasted onto Saturday evening. A Tuesday food tour that starts at 11:00 is refused, because Tuesday is the train. The tour can move to Thursday only by replacing Thursday’s anchor, not by sitting beside it as a second prepaid entry.
The shortlist under Monday has a market and a park. Both stay unbooked. If Monday’s weather is poor, the traveler does something indoors that did not require a reservation. The week still has its three anchors.
When the first booking contradicts the grid
Sometimes the only reasonable flight lands on Sunday morning instead of Saturday night, or the train only runs on Monday. The grid changes before the anchors do. Sunday becomes the arrival day, Monday becomes the travel day, and one city day disappears. An anchor has to be cut, or the trip has to gain a date. Keeping all three anchors and also accepting the new transport is how the plan becomes a pile of reservations the days cannot hold.
Write the revised labels, then change the bookings that no longer fit. A confirmation kept after its date has become a travel day is the reservation you will miss.
Put the grid where the confirmations are
Forward the flight, train, and hotel emails to [email protected], or paste them, and Tineo turns them into a day-by-day itinerary you can share. Notes hold the “unbooked” label on the slack block, and polls are there when two people still disagree about an anchor. Itineraries can sync for offline use. Gmail connect is optional. The apps for iPhone, iPad, Mac, Android, and Windows, and the web app, are at tineo.ai/get.
Frequently asked questions
Should I pick activities before I pick dates?
Pick the dates and the nights first, then mark which of those dates are travel days. Activities belong on the dates that remain. Starting from a list of sights tends to stack several timed entries onto a date that is already spent on a train or a landing.
How many activities go on one day?
One anchor, meaning one reservation you would be sorry to miss, plus anything nearby that you can drop. A second prepaid entry at a fixed time on the same date turns a delay at the first door into a missed second door.
When do I buy the tickets for the plan?
Buy transport and lodging when the order of cities and the nights are stable enough that you accept the seller's change rules. Buy timed entries after those nights are reserved, and after you have marked at least one block with nothing you can miss.
What if two people want different days?
Write both versions against the same dates and the same travel days. The disagreement is about anchors, and the travel days stay shared because the flight does not split. A poll or a note on the shared trip records which version you are booking.
Related guides
- What is a travel itinerary?
A travel itinerary is the ordered list of where you will be, when you move, and where you sleep, written so the bookings and the plan can be checked against each other.
- How many days should you spend in a city?
No city has a universal day count, so you count usable days after arrival, give each day one anchor, and leave one block you do not schedule.
- How much slack should an itinerary leave?
An itinerary needs enough unbooked time to absorb the delay you are actually risking. There is no universal fraction of the trip to leave empty.
Sources
- IATA, airline and airport code search (accessed 2026-11-20)
- IATA, Station Standard Minimum Connecting Time (accessed 2026-11-20)
- CDC Travelers' Health, Jet Lag (accessed 2026-11-20)