How to build a travel itinerary from your booking confirmations

Search “itinerary builder” and almost everything that comes back is a blank template. A drag-and-drop board where you add a card for each day. A Notion doc with headers for Day 1, Day 2, Day 3. A spreadsheet with columns for date, time, and activity. They all start from nothing and ask you to type in what you already booked — the flight number, the check-in date, the transfer time — copying it out of an email you already have.

That's not really building an itinerary. It's re-entering one you already assembled, one confirmation email at a time, into a second system that doesn't know about the first.

The usual tools, and where the work actually goes

Drag-and-drop itinerary builders. Good-looking, and genuinely easy to use once the data is in. The entire cost is getting it in — every flight, hotel and activity typed or pasted by hand, one card at a time. A 12-booking trip is 12 rounds of switching to your inbox, finding the right email, and copying the details across.

Notion or Google Docs templates.Flexible, free, and exactly as accurate as the last time you updated them. An airline changes a gate or a departure time and the template doesn't know — it just keeps showing what you typed in three weeks ago.

Spreadsheet templates. Same problem in a grid. Fine for a static packing list, less fine for the one document where being wrong about a time actually costs you a connection.

In every case, “building” the itinerary is manual transcription, and the itinerary is only ever as current as your last update.

What building an itinerary should actually mean

The information already exists. Every flight, hotel and transfer arrived as a confirmation with the date, time and reference number sitting right there in the email or PDF. Building an itinerary shouldn't mean retyping that — it should mean putting what you already have in order and showing you what's missing between the pieces: the night with no hotel booked, the connection that's tighter than it should be, the transfer that was never arranged.

That's a different job than a blank template. It's extraction and assembly, not data entry.

How Travel Sane does it

Paste the confirmation email, upload the PDF, or drop in a screenshot. A language model reads it — not a rigid template matching known formats, so a regional train booking or a non-English hotel confirmation parses as reliably as a major airline. It pulls out what matters: dates, times, locations, and the booking reference.

On Pro, you skip even the pasting — forward confirmations to your own Travel Sane email address as they arrive, and each one lands on the timeline by itself.

Every booking is placed on one chronological timeline in the order it actually happens, not the order you happened to book it. Then it checks what's between the bookings: a night with nothing booked, a connection too tight to make, a transfer that was never arranged. Each flag sits next to the booking it's about, so you see the problem in context instead of noticing it at the airport.

The free plan covers one active trip and up to 10 bookings — enough to build a real itinerary for a real trip before deciding whether you need more.

In practice

A two-week trip — four flights, three hotels, a rental car, and a train leg — took about ten minutes to load by pasting each confirmation in as it was found. No manual typing of dates or times. The timeline caught one unbooked night between a hotel checkout and the next check-in, and flagged a connection with less than the airport's posted minimum transfer time. Both were easier to fix a week out than to discover on the day.

Related: Travel Sane vs TripIt · How to keep track of multiple flight confirmations · How to plan a multi-city trip