Business Travel Itinerary Template: Formats You Can Copy

Most itineraries break at the same point. Someone forwards a flight confirmation, a hotel confirmation and three calendar invites, and that gets called the itinerary. Then the traveler is standing at a curb in a city they don’t know, scrolling through six emails looking for the hotel address.

I’m Nir Sabato, co-founder of Catch. Business travel is one of the jobs executives hand us, and the pattern repeats. Booking is rarely the hard part. Holding the whole trip in one readable document, the kind that survives a schedule change, is where it usually comes apart.

This page hands over the templates. First, what belongs on the document and why each field earns its spot. Then three formats you can copy straight into a doc or a spreadsheet: a single-day trip, a multi-day multi-city trip, and an executive itinerary with prep notes and contacts sitting against every meeting.

What belongs on a business travel itinerary

Every field on a good itinerary answers a question the traveler is going to ask at some specific moment. If it doesn’t answer one, cut it. A long itinerary nobody reads is worse than a short one that gets used.

Flights: number, terminal, and confirmation code

Not just “UA 1123, 7:40 a.m.” The flight number is what finds the gate on a departure board. The terminal decides how early the car has to leave, since at an airport like JFK, moving between terminals can eat twenty minutes. And the confirmation code, meaning the six-character record locator rather than the thirteen-digit ticket number, is the only thing an agent asks for when a flight moves.

Put the arrival time on the line too. The traveler needs it, and so does whoever is meeting them.

Hotel: full address, phone, and check-in time

The address is what gets typed into a rideshare app at 11 p.m. The property’s direct number, not the chain’s central reservations line, is what you call when the room isn’t ready. Check-in time matters for one reason: it decides whether the bags come along to the first meeting.

If the room is held for a late arrival, or somebody arranged early check-in, write it down. That’s the detail that goes missing between the booking and the front desk.

Meeting blocks: location, floor, and a named contact

A meeting block needs a street address, the floor or suite, the name of the person to ask for at reception, and a mobile number for them. An address on its own doesn’t get you far in a building with a security desk and thirty tenants.

The contact number is the field people skip and then need most. When traffic is worse than anyone planned for, the gap between arriving late and arriving late having warned someone is a single text.

Ground transport between everything

Airport transfers usually get planned. The middle is what gets skipped: hotel to first meeting, meeting to meeting, last meeting back to the airport. Put a line between every two fixed points, with the method and an honest travel time. Already booked? Add the confirmation. Not booked? Write “rideshare, 20 min” so at least the time is budgeted.

Time zones, written explicitly

Every time on the itinerary should carry its zone: 9:40 a.m. CT. That isn’t fussiness. Fly San Francisco to Chicago and you’ll spend the day with a phone on one zone, a laptop on another, and a calendar invite built by someone sitting in a third. Writing the zone on each line takes the arithmetic out of it.

The rule that holds up: put every time in the destination time zone, and mark the departure with its own local zone. A flight is the only line where two zones legitimately belong.

An emergency and support line

One short block, top or bottom: the airline’s rebooking number, the hotel’s direct number, the corporate travel desk if there is one, the traveler’s own mobile, and one person internally who knows the trip well enough to make a decision on it. Those five numbers cover most of what actually goes wrong on a trip.

The craft: how to lay it out

Three habits separate an itinerary that holds up from one that’s abandoned by Tuesday morning.

Times run in destination time. Set the whole document in the local time of wherever the traveler is actually standing. In my experience, home-zone times are the single most common reason a meeting gets missed on a two-zone trip.

Buffers get written in, not assumed. Thirty minutes between meetings in a city you know, forty-five in one you don’t, measured door to door rather than address to address. Give the buffer its own line on the document, something like 12:30 - 1:15 p.m. CT - Travel + buffer, because a gap that isn’t written down gets filled by someone else’s meeting request.

Keep one version that updates. Don’t email a new file every time something shifts. Park the itinerary in a shared doc or sheet with a stable link, stamp a Last updated: line at the top, and send that link once. When the flight moves, the document changes and everyone already has it. Attachments spread: inside a day, four people are working from three different versions of the trip. A link keeps everyone on the current one.

A fourth, smaller one: keep an offline copy. A PDF or a screenshot on the phone covers the twenty minutes of any trip when there’s no signal and you need the hotel address.

Business travel itinerary template 1: one-day trip

The simplest format worth using. Fly in, two or three meetings, fly out. Copy it into a doc and swap the placeholders.

BUSINESS TRIP - [CITY] - [DATE]
Traveler: [Name] · Mobile: [+1 ...]
Last updated: [Date, time]
All times in [DESTINATION TIME ZONE].

─── TRAVEL ───
06:10 Car to [Home Airport] - [Service / confirmation]
07:40 Depart [SFO] · Terminal 3 · [UA 1123] · Conf: [ABC123]
13:52 Arrive [ORD] · Terminal 1 · Baggage: carry-on only
14:15 Car to city - [Service], approx. 45 min

─── ON THE GROUND ───
15:30 MEETING 1 - [Company]
 [123 Main St, 14th Floor]
 Contact: [John Miller], [+1 ...]
 Purpose: [One line]
16:30 Travel + buffer - 30 min, rideshare

17:00 MEETING 2 - [Company]
 [456 Oak Ave, Suite 900]
 Contact: [Mark Reed], [+1 ...]
 Purpose: [One line]
18:00 Travel to airport - approx. 50 min in traffic

─── RETURN ───
20:15 Depart [ORD] · Terminal 1 · [UA 2240] · Conf: [ABC123]
22:50 Arrive [SFO] · Terminal 3
23:15 Car home - [Service / confirmation]

─── IF SOMETHING GOES WRONG ───
Airline rebooking: [+1 ...]
Travel desk: [+1 ...] / [email]
Internal contact: [Name], [+1 ...]

Nothing in there is decorative. Every line is either a location the traveler has to reach, the transport between two of them, or a number to call when something changes.

Corporate travel itinerary template 2: multi-day, multi-city

Once a trip crosses a time zone or a city line, the flat list stops working. Break it by day, and give each day a one-line header saying where the traveler sleeps that night. That one line prevents the most expensive itinerary mistake going: a hotel booked in the city you left that morning.

BUSINESS TRIP - [CITY A] → [CITY B] → [CITY C]
[Start date] - [End date]
Traveler: [Name] · Mobile: [+1 ...]
Last updated: [Date, time]
Times shown in each day's LOCAL zone; zone marked per day.

═══ DAY 1 - [MON, DATE] - [City A] - Night: [Hotel A] ═══
Zone: [ET]
07:40 Depart [SFO] T3 · [UA 1123] · Conf: [ABC123]
16:05 Arrive [EWR] Terminal C
16:45 Car to hotel - approx. 60 min
18:00 Check in - [Hotel A], [Address]
 Direct: [+1 ...] · Conf: [HTL-88221] · Late arrival guaranteed
19:30 Dinner - [Restaurant], [Address] · with [John Miller]

═══ DAY 2 - [TUE, DATE] - [City A] - Night: [Hotel A] ═══
Zone: [ET]
09:00 MEETING - [Company], [Address, floor]
 Contact: [Name], [+1 ...]
10:30 Travel + buffer - 45 min
11:15 MEETING - [Company], [Address, floor]
 Contact: [Name], [+1 ...]
13:00 Open - [work block / lunch]
15:00 MEETING - [Company], [Address, floor]

═══ DAY 3 - [WED, DATE] - [City A] → [City B] - Night: [Hotel B] ═══
Zone: departs [ET], arrives [CT]
08:00 Check out - [Hotel A] · bags with concierge / in car
09:15 Car to [LGA] - approx. 40 min
11:20 Depart [LGA] · [UA 2417] · Conf: [DEF456]
13:10 Arrive [ORD] (CT)
14:00 Check in - [Hotel B], [Address]
 Direct: [+1 ...] · Conf: [HTL-91004]
16:00 MEETING - [Company], [Address, floor]

═══ DAY 4 - [THU, DATE] - [City B] → home ═══
Zone: [CT]
09:30 MEETING - [Company], [Address, floor]
11:00 Check out - [Hotel B]
11:30 Car to [ORD] - approx. 45 min
14:05 Depart [ORD] T1 · [UA 2240] · Conf: [DEF456]
16:40 Arrive [SFO] T3
17:10 Car home

─── STANDING DETAILS ───
Airline rebooking: [+1 ...] · Travel desk: [+1 ...]
Loyalty: [Airline #] · [Hotel #]
Internal contact: [Name], [+1 ...]

The day header carrying the hotel name earns its keep here. So does the zone line. On the day the trip crosses from Eastern to Central, both zones show up once, at the top, rather than getting quietly mixed into every row underneath.

Executive travel itinerary template 3: with prep notes and contacts

An executive itinerary is a different document. Where to be is maybe half of it. The rest is what the meeting is for, who’s in the room, what was agreed last time, and what has to come out of this one. This is the format that belongs in front of a CEO or a VP of Sales heading into four client meetings across two days.

[EXECUTIVE NAME] - [CITY] - [DATES]
Prepared by: [Name] · Last updated: [Date, time]
All times [DESTINATION ZONE]. Mobile: [+1 ...]

TRIP OBJECTIVE
[One or two lines: what this trip is supposed to produce.]

──────────────────────────────────────────
LOGISTICS AT A GLANCE
Out: [DATE] · [UA 1123] · [SFO] T3 05:30 → [ORD] T1 09:40 · Conf [ABC123]
 Seat [2A] · TSA Pre · Carry-on only
Return: [DATE] · [UA 2240] · [ORD] T1 20:15 → [SFO] T3 22:50 · Conf [ABC123]
Hotel: [Name], [Full address] · Direct [+1 ...] · Conf [HTL-88221]
 Check-in [15:00] (early check-in confirmed) · Check-out [12:00]
 7-min walk to [Meeting 1 address]
Car: [Service], booked for all legs · account [####]
──────────────────────────────────────────

09:40 ARRIVE - car waiting, driver [Name], [+1 ...]
 Bags to hotel; no check-in needed before Meeting 1.

10:30 MEETING 1 - [Company]
 [Address, 14th Floor] · ask for [John Miller] at reception
 Attendees: [Name, title] · [Name, title]
 Primary contact: [John Miller], [+1 ...], [email]
 Context: [Last conversation, date, what was agreed]
 Objective: [What we want out of this meeting]
 Prep: [Deck / contract / number to have open]
 Watch: [Open issue, objection, or sensitivity]

11:45 Travel + buffer - 30 min, car held

12:15 LUNCH - [Restaurant], [Address] · with [Mark Reed]
 Reservation under [Name] · Conf [####]
 Context: [Why this lunch matters]

14:00 MEETING 2 - [Company]
 [Address, Suite 900] · security desk, photo ID required
 Attendees: [Name, title]
 Primary contact: [Name], [+1 ...]
 Objective: [One line]
 Prep: [One line]

15:30 OPEN - [work block at hotel / call window]

17:00 MEETING 3 - [Company]
 [Address] · Contact: [Name], [+1 ...]
 Objective: [One line]

18:30 Car to [ORD] - approx. 50 min · driver confirmed 17:45

─── SUPPORT ───
Airline rebooking [+1 ...] · Hotel direct [+1 ...]
Travel desk [+1 ...] · Internal [Name] [+1 ...]

Three fields do most of the work here. Context stops an executive walking in cold to a relationship somebody else has been managing. Objective makes the meeting measurable, so afterward you know whether it worked. Watch is the one-line warning: the renewal still open, the person who was unhappy last quarter, the number nobody wants raised before Thursday.

The spreadsheet version

Past about a dozen moving parts, or once several people need to filter it, a sheet beats a document. One row per event, and these columns:

Day	Time	Zone	Type	What	Address	Contact	Phone	Conf #	Notes
Tue	07:40	PT	Flight	UA 1123 SFO T3 → ORD T1	-	-	-	ABC123	Seat 2A
Tue	15:30	CT	Meeting	[Company] QBR	123 Main St, 14F	John Miller	+1 …	-	Deck v4
Tue	16:30	CT	Transit	Rideshare, 30 min	→ 456 Oak Ave	-	-	-	Buffer held

The Type column is what makes the sheet worth the trouble. Filter to Flight and you have the travel spine. Filter to Meeting and you have the agenda. The driver only ever needs the Transit rows.

Where the itinerary builds itself

All three of these templates assume someone fills them in, then keeps filling them in every time the flight moves.

That’s the part Catch takes on. Catch is an AI executive assistant that books business travel end to end, flights, hotels and ground transport, acting as the travel agent itself rather than pointing you at a search page. You ask in Slack, email, text or a phone call. Or Catch spots the trip first, from your calendar and inbox, and comes back with the flight and a hotel near where the meetings actually are. It books within your company’s travel policy and picks up your preferences as it goes: airline, seat, hotel, room type.

Since Catch made the bookings, it also holds the itinerary: confirmation codes, terminals, addresses, check-in times, and the transport between every fixed point, in one place that updates instead of a fresh attachment each time. It keeps managing the trip afterward too, watching for a better rate and rebooking where the booking is flexible, calling the hotel about a room detail, arranging late checkout when the return flight moves. It acts when it has enough context to act, and comes back with a specific question when a decision genuinely needs you.

Pricing is $99 per month, flat, voice included, no per-call fees. It works across Slack, email, text message, iMessage and phone, sets up in under three minutes, and is SOC 2 Type II certified and CASA Tier 2 verified. The focus is business travel rather than consumer trip planning, and expenses and reimbursement stay outside what it covers today.

Frequently asked questions