Travel itinerary: the whole trip on one page for the group

Each day's plan, the bookings, what's paid and who to call, for everyone on the trip.

2 live examples

The example: Eight days in Andalusia for a family of six

Three cities, three couples, one shared bill

Eight days in Andalusia for a family of six

Open the example

The names and numbers are made up.

What to notice

  • Every booking carries its reference on the line where it happens: the train on day 4 shows coach 4, seats 5A to 7B and RTK94P.
  • Thursday starts with the one warning that could cost the group its visit: bring your passport, because the Alhambra checks it against each ticket.
  • The money adds up where everyone can see it: €3,657 paid so far, €354 to pay in Córdoba, €1,337 per couple.

The prompt that starts one like it

Turn my trip notes into a travel itinerary as a single HTML page: [dates, places, who's coming, and each booking with its time, address and confirmation number]. Open with the route and a row of days that jumps to each one. Under every day, list times, places and booking references, and mark what's paid. End with where we're staying, the shared costs with each person's share, and who to call. It has to read well on a phone. Then publish it on sharable.link with a password.

The example: Three days at a Denver conference for a team of five

One booth, one talk, a filter for each person

Three days at a Denver conference for a team of five

Open the example

The names and numbers are made up.

What to notice

  • Six buttons filter the page: press Leilani and the schedule shrinks from 30 lines to 18, and under Flights only her Chicago booking is left.
  • Booth shifts name names and hours, so the stand is never empty: Tomasz and Ben open on Tuesday at 2:30, and Gwen and Leilani take over at 4:00.
  • The expense rules are five short entries, among them $70 a day for meals when there's no group meal and a receipt for anything over $25.

The prompt that starts one like it

Make a team trip page as a single HTML page: [conference, city and dates, who's going, each person's flights and booking references, the hotel, and the sessions, booth shifts and dinners with who has to be at each]. List each day by time and name who every line is for. Add buttons that show one person's trip at a time. Put flights, the hotel, the expense rules and who to call in a side column. Make it work on a phone. Then publish it on sharable.link with a password.

Whoever plans a trip spends the week answering the same questions: what time is the train, which hotel is it tonight, did we already pay for that. A good itinerary answers them before anyone asks. Here are two finished ones, for six people in southern Spain and for five colleagues at a conference, with the prompt that starts each. It's a page to read, so nobody can edit it or check things off.

Who it's for

The person who did the booking, sending to everyone else who's coming: a family, a group of friends, a team at a conference. Send it a week or two ahead, once bookings are firm.

It earns its place on trips with several stops, timed tickets or a shared bill. For a weekend at one hotel, a message with the address will do. While the group is still choosing where to go, use a shared document.

What a good one contains

  • The route at the top. Seville, Córdoba, Granada, then Málaga to fly home, with the nights in each and the train time between them.
  • A box for each day that jumps to it. At 7 a.m. nobody wants to scroll past Saturday to find Thursday. In the example, today's box changes color during the trip.
  • Times written the way the tickets write them. The example says once that every time is local and 24-hour, like the station boards.
  • Warnings on the day they apply. "Pack tonight" sits under Monday, the night before the first train.
  • A name on each line, when people split up. In the conference example a button per person hides everyone else's lines: for Leilani, 30 become 18.
  • Where you're sleeping, with a phone number. Address, check-in and check-out times and the front desk's number, for a taxi driver or a late arrival.
  • What's paid and who owes what. Each shared cost shows its sum, such as three rooms for three nights at €140, then a total and a share, which saves an awkward conversation on the last night.
  • Who to call. The planner first, a backup second, then the emergency number and the insurance line with its policy number.

Check it against the tickets

Check every time against the ticket itself. A timed entry that's wrong by half an hour costs the group the visit. Check that each date falls on the weekday written beside it.

Leave gaps. One day in the example is headed "Nothing booked, on purpose", and two dinners say the same. Fill every hour and people feel behind by lunchtime.

Keep passport numbers and card details off it. When a booking changes during the trip, change the page in the conversation where you made it and tell the group to reload.

How to send it

With a password. It says where you'll sleep each night and lists booking references and phone numbers. Post the link in the group chat and pass the password on some other way.

Every page you publish gets one link that opens in any browser. You choose who can open it: anyone with the link, anyone with the password, or only the people and company domains you name, who sign in with Google or Microsoft. Change the page later and the link stays the same.

Make yours in Claude

Add the connector once, then publish from any Claude conversation and get a link to send.

Add to Claude

Already have the file? Upload it here.

More in personal and events

  • Resume: Your work history on one page that opens from a link and prints on a single sheet.
  • Wedding website: The date, the place, the day's plan and how to reply, on one page a couple sends to every guest.
  • Party invitation: One link for the group chat with the date, the door, what to bring and how to say yes.
  • Recipe card: A recipe for whoever asked for it, with servings that rescale and steps a cook can follow.
  • Workout plan: A coach's plan for one client: every session's sets, reps and loads, plus the missed-session rules.
  • Packing list: What everyone packs for one specific trip, who carries the shared gear, and what stays at home.
  • All use cases

Keep reading