Six people in the document. One person on hold.

You share the itinerary and watch the names appear at the top. Someone adds a rooftop bar. Someone else pastes in a restaurant from a video. The dinner suggestion gets three hearts. You now have two more places to investigate.

By lunch, you’re checking whether the restaurant takes six, how far it is from the house, and whether the person who sent it saw the set-menu price. Everyone has contributed. Your afternoon has disappeared.

The useful question when choosing a shared itinerary app is what a friend can finish without handing it back to you.

Wanderlog supports live editing together. TripIt lets the owner grant editing access to a shared trip. Polarsteps lets travel buddies edit planned stops, with a recommendation to take turns. Google Docs works for a shared written itinerary. NomadCrew keeps an itinerary alongside the trip’s chat, expenses, and booking details.

Before moving the whole group over, invite one friend and ask them to add a dinner time, address, and price. Open it from your own account. That small test tells you whether the plan works for both the person contributing and the people following it.

Start with what your friends can edit

Sources: Wanderlog, TripIt, Polarsteps planning, Polarsteps group size, and Google Docs. Checked September 14, 2026.

For the wider choice, including money and group coordination, see which group trip app to use.

A heart is a response to the suggestion

Someone can love the look of a restaurant without agreeing to a €95 dinner. A heart reaction leaves the price, the guest list, and the booking in the same place they were before.

Keep suggestions in an “Ideas” section until the people going have agreed on the cost. Then put the plan in the itinerary with a status and a name: “Agreed, Jules is booking” or “Booked for six, Jules has the confirmation”.

The name belongs to the person following it through. Ask them first. Writing someone’s name beside a task doesn’t mean they’ve accepted it.

A confirmed stop needs enough detail that a friend can leave the house and find it without messaging you:

• The date and local time.
• The address or map link.
• Who is going.
• The expected cost per person.
• Whether it is booked, agreed, or optional.
• Who has the reservation details.

Keep personal booking codes and documents restricted to the people who need them. A public link can be forwarded beyond your group.

Give someone a decision they can finish

“Add anything you fancy” is a generous invitation to send links. Try asking for one complete piece of the day:

Jules, would you take Saturday dinner? Six people, around €25 each, walking distance from the house. Put an option in the plan by Thursday, and we’ll confirm who’s in before you book.

Jules knows the budget, the group size, the area, and the next step. They can decline the job, suggest another price, or choose a place without asking you to decide all four things.

When they volunteer, let them carry it through. Rechecking every menu and replacing each choice keeps you involved in precisely the work you meant to share. Step in if something breaks an agreed constraint, such as a deposit nobody approved.

Start with the group trip planning template. Give each contributor enough editing access to update their own part after a booking changes.

Leave the afternoon unclaimed

An empty afternoon can look unfinished in a shared document. Resist filling it merely because there’s a gap between lunch and dinner. “Free time; meet at Mesa at 19:30” is enough of a plan to let people go their own way.

Here’s an example of what the group needs to know. In your own itinerary, add the full address or a working map link where an address is mentioned below.

Allow travel time around the bookings. When one moves, the person handling it should update the itinerary and send a short note: “Lunch moved to 13:30; same address.” Everyone gets the change, and the shared plan stays useful after the first version.