Copy this group itinerary template
Paste this into your trip notes or shared planner. Duplicate the day block for each date, then replace the prompts with confirmed details. Leave uncertain items marked as undecided rather than making the plan look more final than it is.
TRIP: [Trip name]
DATES: [Start date] – [End date]
GROUP CHAT / PLAN: [Link or location]
TRIP LEAD: [Name]
TRAVEL DAY — [Date]
• Arrival / departure: [Time, terminal or station]
• Booking: [Provider + reference]
• Address / meeting point: [Full address]
• Getting there: [Route, transfer or pickup owner]
• Buffer: [Time allowed for delays]
• Plan B: [What to do if delayed]
DAY [#] — [Date] — [Area / overnight location]
MORNING [Time] — [Activity or free time]
Where: [Address / map link]
Booked by: [Name] | Ref: [Reference]
Cost: [Amount + who pays]
AFTERNOON [Time] — [Activity or travel]
Where: [Address / map link]
Booked by: [Name] | Ref: [Reference]
Cost: [Amount + who pays]
EVENING [Time] — [Meal / event / open plan]
Reservation: [Name, time, reference]
Plan B: [Nearby alternative or free option]
SHARED DETAILS
• Accommodation: [Address, check-in, booking contact]
• Important tickets / confirmations: [Where stored]
• Shared costs still to settle: [Item — amount — owner]
• Packing or accessibility notes: [Only what the group needs]
• Last updated: [Date, time, person]What to put in each itinerary entry
Time and place
Include the local time and a usable address or map link. For transfers, include the departure point as well as the destination.
Booking proof
Keep the confirmation reference or ticket easy to find. Avoid putting sensitive payment details in a shared itinerary.
Owner and cost
Name the person holding the booking and note whether a cost is shared or personal. This prevents a vague “someone booked it” from becoming a last-minute problem.
Room to change
Mark flexible plans as flexible. Add a simple fallback for the few reservations or connections where a change would affect everyone.
Keep the plan realistic, not packed
A group itinerary is a coordination tool, not a minute-by-minute script. Give travel between places a buffer, leave some unscheduled time, and make it clear when people can choose their own activity. A plan that can absorb a late train or a tired afternoon is more useful than a perfect-looking schedule nobody can keep.
For each day, choose one or two anchors that matter to the group. Add meals, reservations and transport where timing is important; keep optional ideas in a separate list. That makes it easy to see what is confirmed and what can still move.
When a shared trip app is more useful than a document
A copied document can work for a short trip with few changes. When the group is juggling plans, bookings, costs and packing, keeping everything together is easier than searching chat history for the latest version. Troupe is an iPhone app for organizing group trips and splitting expenses, with shared trip details for the people coming along.
Use the template above on its own, or see Troupe’s trip-planning features. You can also read about a shared travel itinerary on iPhone and a group-trip budget planner.
Ready to keep the itinerary and trip costs together? Get Troupe on the App Store
A filled-in example
| Day and time | Plan | Booked by | Notes |
|---|---|---|---|
| Fri 15:00 | Check in at the house | Sam | Key code in the group chat |
| Fri 19:30 | Dinner at the harbour | Priya | Table for eight; set menu |
| Sat 09:00 | Coastal walk, 8 km | Nobody; open | Bring water; wet-weather plan is the museum |
| Sat 13:00 | Lunch on your own | Free time until 17:00 | |
| Sat 19:00 | Cook at the house | Alex shopping | Dietary notes in the trip |
| Sun 10:00 | Check out | Sam | Everyone strips beds |
Notice what makes it usable: one owner per booking, a free block, and a fallback for weather.
Questions people ask
How detailed should a group itinerary be?
Fixed points only: travel, check-in, bookings and meeting times. Leave the rest open.
Who should own it?
One organiser keeps it current, and everyone can see it. In Troupe, the trip is shared with the group so nobody is working from an old screenshot.
How much free time should there be?
At least one unscheduled block per day. Groups move slowly.
What goes wrong most often?
Nobody knowing who booked something. Put a name on every booking.