A travel itinerary template: the columns, and a filled-in example

Nine columns cover almost every trip. Keep one row per stop, or per time block on a busy day, and resist adding more until a column has earned its place. Each of the nine answers a question someone will otherwise ask in the group chat.

• Date: one row per day or time block. It anchors everything else and lets you sort and filter.
• Time: a start time, or the word flexible. It keeps mornings from quietly collapsing.
• Activity: one line in plain words, the thing you will actually do.
• Location: an address or place name you can paste straight into a map.
• Booking reference: the confirmation number or none. It saves the thirty seconds of panic at a counter.
• Cost: an amount and a currency, so a group can split and settle later.
• Booked by: a name, which tells everyone who to ask and who is owed money.
• Notes: opening hours, dress code, deposit rules, anything you would otherwise search for again.
• Status: confirmed, maybe or idea. This is your queue of maybes to rank.

For three or more travelers, add three more: who is in for each activity, which room each person is staying in, and a vote tally on the maybes. The room column answers who is sleeping where before anyone has to ask on arrival, and the vote column replaces the chat thread where opinions go to die.

Skip the columns that feel thorough and never get used. Weather is something everyone checks anyway, a packing list belongs in its own document, and a mood or vibe column becomes decoration. A good rule is that any column left empty across two trips gets deleted.

The best way to judge a template is to see one somebody filled in. This example is illustrative, a plan for six friends, built on the nine columns above.

Day one is arrival only. The group lands in the afternoon, takes a taxi or a train to an apartment in Alfama, does a grocery run, and eats at a place on the corner. The notes column says no plans, because a late flight should not break anything.

Day two puts Belém in the morning, a long lunch, and free time from mid-afternoon, because six people will not all want the same afternoon. Day three is Sintra, with one booked train and nothing else fixed. Day four is the group's pick day, chosen from the votes on the maybes. Day five is breakfast, packing and the airport.

The cost column carries the arithmetic. Each row records the amount, the currency and who paid, so settling up at the end is a filter rather than an argument. If two people split a train ticket, the row says who paid and who owes half.

The rule that holds up best is one anchor per half-day, and everything else stays a maybe. An anchor is the thing that needs a booking or a reservation, such as the train to Sintra or the dinner on day four. Everything else is written in pencil, so a long lunch or a rainy morning costs nothing.

Leave buffer rows on purpose. A plan with an activity every two hours breaks the first time someone wants a second coffee. If half of day two and most of day three are unassigned, the organizer can say that nothing is booked until dinner instead of improvising a rescue.

Check every stop on a map before it goes in the confirmed status. A place that looks central in a listing can be a long walk from everything else, and that is far easier to catch in a spreadsheet row than on the pavement.

Print one page per traveler when there may be no signal or an official may want paper. Some airlines and border officials ask for proof of onward travel, and a phone with a flat battery proves nothing. Put dates, addresses and booking numbers on the page, and check each country's entry requirements first; GOV.UK's foreign travel advice lists them country by country.

Remote legs are the other case. Google Maps lets you download an area to use without signal, but its own help page notes that transit, bicycling and walking directions are unavailable offline, so a printed route or screenshots still matter for anything done on foot.

Keep the spreadsheet while the plan is still moving. Dragging a museum from Tuesday to Thursday, comparing three hotels and reordering a day are cheap in a sheet with filters and copy and paste. Once the plan freezes, a spreadsheet stops being useful on the ground.

Keep one master template and switch columns on and off. The core stays the same: date, time, activity, location and notes.

• Solo: hide rooms, votes and settlements. Keep notes for costs and bookings, since nobody else is checking your arithmetic.
• Couple: add one column for who is booking what, and keep a short list of maybes you each want to rank.
• Group: add room, vote status as yes, maybe or no, the amount owed, and a settled column. The vote column matters most before anything is booked.
• Cruise: replace the evening with two columns, port and all-aboard time. Missing the all-aboard time means the ship leaves without you.

Arrival day needs three rows: transport from the airport, one meal and check-in. Leave the rest blank on purpose, so a delayed flight cascades into nothing.

Day two gets one anchor, either booked or timed, and a column of maybes the group can rank on the fly. Jet lag decides what gets cut, not the plan. For groups, mark who is staying where and the meeting point for the anchor, so nobody is texting at nine in the morning while half the group is still asleep.

Google Sheets has the least friction for a group: paste the link and everyone is in. Google's sharing options include a viewer, commenter and editor role, and an anyone-with-the-link setting. Giving most people the commenter role keeps the plan intact while still letting them flag problems.

The tradeoff is that nobody owns the plan, so votes and room assignments end up in comments that get missed. One rule fixes most of it: the organizer is the only person who marks rows as confirmed.

A template holds your columns, but it cannot fill them, tally the votes or chase the friend who never opens the sheet. It has no opinion on whether two stops are thirty-five minutes apart, and it goes stale when someone books a different flight. If you enjoy building the plan, keep the spreadsheet.

Ollin starts from the other end. Describe the trip in a sentence and it drafts a day-by-day plan, and everyone you invite opens it from a link in the browser. Changes show up live for the whole party, the group can rank the maybes with group picks, assign rooms, chat beside the plan, and split expenses and settle up. It is free for up to 15 travelers on a trip.

The honest limits matter too. An AI plan can name a place that has since closed or misjudge a transfer, so check real places against a map or the venue's own page before booking. Ollin hands you to partners to book rather than selling anything itself, and a spreadsheet will always be more flexible about its own columns.