How to share an itinerary with a group

Somebody exports the itinerary on Tuesday, the dinner moves on Wednesday, and on Saturday two people are standing outside the old restaurant, texting. Every format that produces a copy has that failure built into it, so the reminder to re-download does nothing.

Viewing has to cost nothing, because if you make people create an account, about a third of a group of eight will decline and then ask their questions in the chat anyway. A read-only public link solves that, and it has to work on a phone on cellular data, since that is where it gets opened. A spreadsheet technically shares, so try reading one on a pavement in the rain.

The current stops, which day each one sits on, and the bookings attached to them. That covers the person who only wants to know where dinner is, and the person adding a café they walked past. Planning with friends usually fails at this handoff rather than at picking the city.

Timing matters here, because a link sent too early teaches people to ignore it. Send it when the house and the flights are real, and nudge it once the night before the first day. Send it the week you start planning and it goes out with three empty days on it, so the group learns there is nothing to check. A link with two confirmed bookings gets opened.

The booker edits, and everyone else views on a phone with no account required. One or two people who are actively adding restaurants get edit rights, because eight editors in a group of eight is how a maybe bar quietly becomes Saturday night while the person holding the reservation is asleep.

Send the link once, in the chat that already exists, because a second itinerary in a side thread is how half the group ends up at last week's restaurant. Bachelorette weekends fail this way constantly, and so do ordinary friend trips.

A PDF export, a screenshot of somebody's notes app, a Google Doc that demands a login, a Maps list you have to request access to: each of those hands out a copy, which is the problem. The dinner will move, and the copy will sit there being wrong until somebody notices.

If you need the plan on a plane with no signal, export it the morning of the flight. Keep that copy as a backup and keep working in the live link, so the group only has one address to remember. When a reservation changes, update the link and tell everyone the URL has not moved.

One thing helps more than it should: put the street address and the name the table is booked under right on the plan, because half the group will arrive by taxi and a driver needs an address.

The test is simple, because a group either knows where to walk or it does not. Somebody opens the link on a phone at 7:40pm and knows within five seconds where to walk. If you cannot manage that, you are holding a document, and documents lose to a moved reservation every time.