The group trip itinerary template that actually gets used
Most itineraries fail on format, not content. Here is a template you can copy, plus the six rules that determine whether anyone opens it twice.
The Sail Team7 min read
A group itinerary has exactly one job: answer the question someone has right now, without them texting you. Most itineraries fail at this — not because the information is missing, but because it is arranged for the person who wrote it rather than the person reading it in a taxi.
Below is the structure we recommend, followed by the rules that make it work. Copy it directly.
The template
Header — the four things asked most often
- Where we're staying: full address, plus the gate or unit code
- Check-in / check-out: dates and times, not just dates
- Group chat: one link, stated once
- Emergency contact: one name, one number
This block goes at the very top of every day's view, not just page one. Repetition is not clutter when the reader arrives mid-document.
Per day — the anchor, then the rest
Each day gets a single line that summarizes it, then the fixed items in time order, then a genuinely-labeled open block. Like this:
FRIDAY — Arrival + group dinner. 3:00pm check-in, 141 Rua Nova (code 4482#). 8:00pm dinner, Taberna do Mar, booked under Alvarez, 15 min walk. Everything else: open.
One line per fixed item. Time first, because time is what people scan for. Location second. The detail that prevents a text message — the booking name, the door code, the walk time — third.
Footer — what people need to have decided
- Anything requiring a booking your group has not made yet, with the deadline
- What to bring that is not obvious — hiking shoes, cash, a passport for the ferry
- Who owns what, so questions route to the right person instead of to you
Six rules that decide whether it gets read
1. Times before descriptions
People scan itineraries for numbers. "8:00pm — dinner at Taberna" is found instantly; "Dinner at Taberna, which we've booked for 8pm" is not. Lead with the time on every single line.
2. Fixed and flexible must look different
If the 6am departure and the maybe-we'll-hike are formatted identically, your group treats both as suggestions — and one of those is a flight. Bold the fixed items, or give them their own section. Then say explicitly that the rest is open, because unlabeled empty space reads as "not planned yet" and generates exactly the questions you were trying to prevent.
3. Addresses, not place names
"The rooftop place" is meaningful to you and to nobody else. Every location gets a full address that can be pasted into a maps app. This one change eliminates a startling share of day-of messages.
4. One document, one link, one version
The moment a second version exists — an updated PDF, a screenshot in the chat — half your group is reading the wrong one, and you will not find out until someone shows up an hour late to a restaurant that moved. Share a link that updates in place, never a file.
5. It has to work on a phone, offline
Nobody opens a laptop on a trip, and international data is unreliable at exactly the wrong moments. Short lines, no wide tables, and a format that survives a screenshot. Better still, push the day's plan to people by text so it is already sitting in their messages when the signal drops.
6. Put the next thing first
A person opening the itinerary almost always wants the next event, not the trip overview. A static document cannot do this, which is the one place a tool genuinely beats a doc: Sail shows the current day first and texts the group the details on the morning they matter.
What to leave out
- Options you are still deciding between — decide, then publish
- Backup plans, unless the primary plan is weather-dependent
- Anything that only matters to one person; text them directly
- Prices, in the copy people carry — money belongs in its own document
Each of these adds a decision for the reader, and every decision is a chance to close the document and text you instead.
Using it
The template is the easy part. The maintenance is what kills itineraries — the restaurant changes, the ferry moves, and the version in everyone's screenshots is now wrong. If you want the structure without the upkeep, Sail's itinerary builder produces this format and keeps one live copy for the whole group.
For the wider process around the itinerary, see how to plan a group trip. If the trouble is getting commitments rather than logistics, start with getting your group to RSVP. Plans and limits are on the pricing page.
Frequently asked questions
How detailed should a group trip itinerary be?
Fix anything with a reservation, a ticket, or a departure time, plus one anchor activity per day and one group dinner. Leave the rest genuinely open and label it as open. Groups resent schedules that fill every hour, and they stall without any structure at all.
What is the best format for sharing a trip itinerary?
A single link that updates in place, readable on a phone. Avoid PDFs and screenshots — the moment the plan changes, outdated copies are circulating and you have no way to recall them. Pair the link with a text on the morning of each day, since that is when people actually look.
Should each day have a backup plan?
Only for weather-dependent plans. Backups for everything else double the length of the document and make readers unsure what is actually happening, which produces more questions than it prevents.