What actually belongs in a travel itinerary you hand a client
Search for an itinerary template and you get a hundred beautiful documents. Most of them are designed to be looked at once, at the kitchen table, by somebody who is excited about a holiday. Almost none of them are designed for the moment that matters: a tired person in a terminal at 6am who needs one specific fact in under ten seconds.
Those are different documents. This is about the second one.
The test a template has to pass
Stand in a check-in queue. Your traveller has your itinerary open on a phone, one hand on a suitcase. Someone in a uniform asks a question. How long does it take to find the answer?
Every recommendation below comes from that test. It is not about beauty. A gorgeous PDF that requires pinch-zooming to read a booking reference has failed, and a plain list that surfaces it instantly has passed.
The eleven things that have to be there
Per flight segment:
- Flight number and operating carrier. Not just "your flight to Rome". The operating carrier matters and is often not the one they booked with — codeshares send people to the wrong desk.
- Departure and arrival times, with the local time zone named. See below; this is the one everybody gets wrong.
- Airport and terminal. "London" is four airports. Heathrow is five terminals.
- Their booking reference. Theirs specifically — see below.
- Ticket number where the airline issues one separately. When a flight is cancelled and the traveller is on the phone to the airline, this is what gets asked for, and it is exactly when nobody can find it.
Per hotel:
- Full address in the local language. A taxi driver in Tunis does not need your English transliteration; they need what is written on the building.
- Check-in and check-out windows, not just dates. A 14:00 check-in and a 22:10 landing are a conversation worth having in advance.
- The property's phone number. Direct, not the booking platform's call centre.
For the trip:
- Who to call, in order. You, then the local operator, then the emergency number of the destination country. Emergency numbers differ; 112 does not work everywhere.
- What is already paid and what is not. Transfers especially. This is the single most common cause of an awkward moment on arrival.
- Entry requirements as you verified them, with the date you checked. Rules change and an undated claim ages badly.
The three that cause the phone call
Times without time zones. An itinerary that says a flight lands at 22:10 is ambiguous unless it says whose 22:10. A Barcelona–Tunis flight departs 21:25 and lands 22:10, which looks like a 45-minute hop and is actually 1h45 — Tunisia is an hour behind Spain in summer. Every itinerary should carry the zone, and any system generating one should know that a flight can arrive "before" it left.
One booking reference for a group. Two travellers on the same flight routinely hold different locators, because they booked separately or through different agencies. An itinerary with a single "confirmation code" field gives one of them somebody else's reference — a code that does not exist under their name and fails at the desk. That is worse than no code at all: it sends them into a queue to argue about it. If people hold different references, the document has to say so, per person.
Gate numbers printed in advance. They are not knowable weeks out. Printing one is not a helpful guess, it is a wrong answer with a confident face. Leave it empty and say when it will be known.
What a static template cannot do
Here is the honest limit of the whole genre: the document is correct at the moment you export it and decays from then on.
A schedule change at 3am does not update a PDF. A gate assignment three hours before departure does not appear in a Word file. A traveller who wants to know whether check-in is open cannot ask a document — so they ask you, at whatever hour it happens to be where you are.
Everything in the list above is a snapshot problem, and every agency solves it the same way: send the document, then spend the trip patching it by hand over WhatsApp.
The version that stays true
The alternative is an itinerary that is a live view of the booking rather than a photograph of it. Same eleven facts, but the flight times come from the operational feed, the traveller's own booking reference is the one they see, and a change reaches them because something is watching for it rather than because you happened to notice.
That is what we build Viaquo to do — the itinerary your travellers hold is the itinerary you are looking at, and when it changes, they hear about it from you without you having to be awake.
If you want the shorter version of the same argument: the template is not the hard part. Keeping it true is.
Related: An AI travel assistant must not invent flight times · Time zones and the traveller's clock · Load your first trip
