one page for the whole trip.
itineraries and trip plans everyone can open, with the confirmation numbers in one place instead of eleven emails.
what could i make before a trip?
01 / what this isa trip generates an absurd amount of paperwork and none of it is in one place. flight times in an email, the hotel in a different email, the reservation someone else made in a text message, the thing you wanted to do on the second afternoon in a browser tab that is now closed. the group chat becomes the itinerary by default, which means the answer to any question is "scroll up".
a page fixes it for the cost of one afternoon of tidying. you tell your assistant who is going, when, and what is already booked, and it writes a page with the days in order, the confirmations where you can find them, and the maybes kept separate from the things that are actually happening. you send one link instead of forwarding six emails, and everyone has it offline once they have opened it.
the honest bits: the page is public to anyone holding the url, so confirmation numbers on it are only as private as the link — use references rather than full booking credentials if that matters to you. it does not sync between people. and an anonymous page expires after 24 hours, which is not a trip; claim it and the link you sent the group keeps working until you are home.
in this cluster.
02 / 2 recipesplan it before you are standing in it.
hold the decisions, options and budget for a trip while it is still being planned
the days, in order, for everyone.
give everyone on the trip one link with the days, times and confirmations
questions.
03 / questionscan i share it with everyone on the trip?
yes — send them the url. there is nothing to install and nothing to sign into, which matters when half the group will open it once on a phone in an airport. what they will not get is the ability to edit it; changes go through whoever asks their assistant for them and republishes.
does it work without signal abroad?
once the page has loaded, yes. it is one self-contained file with no runtime requests, so it keeps showing your itinerary with data turned off. open it before you fly, or add it to your home screen, and it is there when you land.
should i put booking references on a public page?
decide deliberately. anyone with the link can read the page, and links get forwarded within a group and sometimes beyond it. flight numbers and hotel names are usually fine; full booking credentials, passport details and payment information are not — keep those out and reference them instead.
what happens when plans change?
ask for the change and republish over the same url. the link everyone already has shows the new version, which is the main reason to do this as a page rather than a pdf you would have to send again and explain.