---
name: travel-itinerary
description: Use when asked to build a travel itinerary — a day-by-day schedule of transport, lodging, activities, and confirmations for a trip — whether from scratch, from a list of bookings, or by organizing scattered confirmation emails into one usable document.
---

# Travel Itinerary

A travel itinerary is a chronological, day-by-day plan for a trip: what
happens when, where each leg starts and ends, and what's already booked
versus still open. Its job is to be the single document a traveler
actually checks while moving, not a comprehensive trip report written
after the fact.

## Key components

- **Trip overview** — dates, destinations in order, and travelers
  covered, at a glance before the day-by-day detail.
- **Day-by-day schedule** — each day as its own block, times in the
  **local time zone for that leg** (see below), with enough white space
  that it's skimmable at a glance rather than read start to finish.
- **Transport legs** — mode, carrier, departure/arrival points and
  times, confirmation number, and seat/booking class for each flight,
  train, ferry, or rental car pickup/drop-off.
- **Lodging** — name, address, check-in/check-out dates, confirmation
  number, and how to reach it from the previous transport leg.
- **Activities and reservations** — anything time-bound and booked
  (tours, restaurants, timed tickets), distinguished from flexible or
  unplanned time.
- **Contacts** — phone numbers for airlines, hotels, tour operators,
  and any local emergency numbers relevant to the destination.
- **Buffer and contingency** — deliberate slack around tight
  connections, and a fallback note for anything with a real chance of
  disruption (a short layover, a border crossing, a weather-sensitive
  activity).

## Time zones

State every time in the time zone of the place it happens, and label it
explicitly (e.g. "10:40 PM local" vs. "1:40 AM home time") rather than
converting everything to one zone — the traveler needs to know what
their watch or phone will say on the ground, not what time it is at
home. A flight or overnight train that crosses zones should show both
the departure zone and arrival zone times so the elapsed duration isn't
misread as shorter or longer than it is.

## Working from real bookings vs. drafting a plan

- **Organizing existing confirmations** — when the traveler already has
  bookings (forwarded emails, PDFs, confirmation numbers), the
  itinerary's job is to merge them into one chronological document
  without inventing details; flag anything referenced but not actually
  provided (e.g. a hotel address that wasn't in the confirmation)
  rather than guessing at it.
- **Drafting a plan before booking** — when nothing is booked yet, mark
  the whole itinerary (or the still-open parts) as a proposal, and keep
  transport times realistic against actual schedules and connection
  times rather than optimistic best-cases, since the point of drafting
  first is to catch impossible connections before money is spent.

## Common pitfalls

- **No buffer around tight connections** — a itinerary that assumes
  every transfer goes exactly to plan breaks on the first delay;
  build in realistic minimums for immigration, baggage claim, or
  transfers between transport modes, not just posted minimum connection
  times.
- **Times with no time zone stated** — ambiguous once a trip crosses
  even one zone, and actively misleading across several.
- **Confirmation numbers scattered instead of attached to the leg they
  belong to** — defeats the point of consolidating everything into one
  document.
- **Mixing booked and aspirational items with no visual distinction** —
  a traveler needs to see at a glance what's locked in versus what's
  still an idea.
- **Itinerary drifts from what actually gets booked** — once a flight
  time changes or a hotel is swapped, the itinerary needs updating too,
  or it stops being trustworthy as the one document to check.

## Learn more

- [[project-charter]] and [[statement-of-work]] for the same
  discipline — a formal, structured document that's the reference point
  when details are later disputed — applied to a trip instead of a
  project.