Itinerary Template

What an itinerary actually is — and what it is not

The word “itinerary” is used loosely. A travel itinerary for a family holiday in Tuscany and a business conference schedule are both itineraries, but they serve different masters, contain different information, and are used in different contexts.

This template covers the broader category — any structured, multi-day, time-blocked plan where multiple parties need to know where to be and when. That includes business trips, conference schedules, wedding weekend timelines, relocation plans, sporting tournament programmes, and group travel for corporate away days.

What an itinerary is not: a packing list, a booking confirmation, or a wish list. It is an operational document. The distinction matters because an operational document must be precise about times, places, costs, and contacts. Ambiguity in an itinerary is not charming or flexible — it causes missed trains, wrong hotel lobbies, and conference talks attended by half the intended audience.

How this template differs from a travel itinerary

The travel itinerary template on this site focuses on holiday and leisure travel: outbound flights, accommodation check-ins, day-by-day tourist activities, restaurant bookings, airport transfers. It is a personal planning tool, usually used by the traveller alone.

This itinerary template is designed for the broader category:

Business trips. The focus is on meetings, client visits, conference sessions, and transport connections. The budget section includes expense categorisation for reimbursement. The contacts section includes client names and the travel manager’s emergency line.

Conference schedules. Session-by-session planning for multi-track events. Which sessions to attend, in which rooms, at which times, with enough buffer to travel between rooms and grab coffee.

Wedding weekends. Multi-party coordination across 2–3 days — rehearsal dinner logistics, ceremony day timeline, photographer slots, transportation between venues, hotel block information for out-of-town guests.

Relocation plans. Day-by-day logistics of moving: removal van arrival time, utility company switchover appointments, school enrolment dates, driving licence address update deadlines.

The structure is the same for all of these. The content is specific to the use case.

What every itinerary must include

1. Clear identification. Who is this itinerary for, what is the event or trip, and what are the overall dates? If this document is separated from its email chain and found in a hotel lost property, these fields tell someone how to return it.

2. Day-by-day time blocks. Each block needs: a start time (not just “morning”), an activity description, a location (full address, not just “the conference centre”), and a cost estimate if relevant.

3. Buffer time. Built into the schedule, not as an afterthought. A realistic itinerary includes travel time between locations. An optimistic one does not — and the optimistic one fails.

4. Contacts section. Hotel name, address, booking reference. Client name and mobile number. Conference registration desk phone. Corporate travel emergency line. These are the numbers people need when plans go wrong — which they do.

5. Budget section. Estimated costs by category. For business trips, this doubles as the baseline for expense reporting. For personal events, it helps prevent budget overrun.

6. Reference numbers. Flight numbers, booking references, hotel confirmation codes. Keep them in one place so they can be retrieved from one document rather than five email threads.

When each use case changes the template

Business trip itinerary. Add a “purpose” line for each meeting (client relationship, contract renewal, technical scoping — this matters for expense reimbursability). Include HMRC or IRS per diem benchmarks in the budget notes so the approver can cross-reference easily.

Conference itinerary. Add a session-level breakdown for each day (session title, speaker, room, time). Include the conference app download link and Wi-Fi details. Note networking events separately from formal sessions.

Wedding weekend itinerary. Include a wedding party contact list with roles (MOH, best man, wedding coordinator). Include dress code for each event. Include transportation logistics for each group (bridal party, immediate family, guests). Include the photographer’s timeline as a separate embedded section.

Relocation itinerary. Include service provider names and reference numbers (removal company, energy suppliers, council tax office). Build in contingency days for delays. Include a checklist of administrative tasks by date (DVLA address update: within 28 days of moving; electoral roll: as soon as possible; GP registration: first week).

Step-by-step: building the itinerary

Step 1 — Anchor the fixed commitments first. Start with the unmoveable items: flight departure and arrival times, conference session start times, wedding ceremony time. Everything else is scheduled around these.

Step 2 — Calculate travel time realistically. For every gap between fixed commitments, research the actual travel time. Google Maps travel-time estimates are reliable for UK train and road travel; build in 15% buffer for real-world conditions (delays, queues, navigation).

Step 3 — Add supporting logistics. Hotel check-in (confirm the property’s earliest check-in time — most UK hotels are 15:00 or later, US hotels 16:00). Restaurant reservations with the address and confirmation number. Conference registration desk with the reference.

Step 4 — Build the contacts block. Go through every entity in the itinerary and add a contact: hotel front desk, each client being visited, the conference organiser, car hire company, restaurant. This takes 15 minutes and saves enormous stress when something goes wrong.

Step 5 — Add the budget table. List each cost category, the estimated amount, and leave the actual column blank to fill in on return. For UK business trips: transport, accommodation, meals (HMRC benchmark or actuals), registration fees, incidentals. For US: same categories, IRS Publication 463 per diem as reference.

Step 6 — Share before departure. Email the completed itinerary to yourself, to your travel manager or assistant, and to anyone who needs to reach you. A PDF attached to the trip’s calendar event is reliable. A shared cloud document is better for trips where plans are likely to change.

Common mistakes

Mistake 1: Unrealistic travel time between activities. Scheduling a meeting in Canary Wharf at 11:00 and another in the City at 11:45 in London is not possible by public transport at peak hours, unless you allow for a taxi and traffic. Pad inter-meeting travel time generously.

Mistake 2: Missing hotel check-in/check-out times. Arriving at a hotel at 12:00 for a conference that starts at 14:00 and discovering check-in is 15:00 is a common and entirely avoidable problem. Confirm early check-in with the hotel in advance, or add a luggage storage entry to the morning schedule.

Mistake 3: No emergency contacts. When a meeting is cancelled at 07:00 or a conference venue changes, you need a phone number. An itinerary that only has email addresses is not useful in a moment of urgency.

Mistake 4: Forgetting local currency or payment methods. For international travel, note which venues require local currency, which are card-only, and the nearest ATM to the hotel. Small friction points compound badly when you are tired and running late.

Mistake 5: Not sharing the itinerary before you leave. If you need to be reached in an emergency, someone needs to know your schedule. Send the completed document to a colleague or family member before departure.

Worked example: Helen Ward’s London business trip

Helen Ward | Director of Commodities, Bristol Metals Ltd
FT Commodities Global Summit, London | 21–23 May 2026

Day 1: Wednesday 21 May

• 07:30 — Depart home, drive to Bristol Temple Meads (allow 40 mins, M32 variable)
• 08:15 — Bristol Temple Meads. LNER advance ticket: 08:40 Bristol–London Paddington. Coach D, seat 34. Ref: LNR7841. Cost: £34.
• 10:45 — Arrive London Paddington. Elizabeth line to Westminster (18 mins). Walk 8 mins to hotel.
• 11:30 — Check in: Park Plaza Westminster Bridge, 200 Westminster Bridge Rd, SE1 7UT. Booking ref: PPW2604. Early check-in pre-confirmed. Tel: 020 7620 7200.
• 13:00 — Lunch with Marcus Tull, Head of Trading, Veritas Commodities. Aqua Shard, Level 31, 31 St Thomas St, SE1 9RY. Booking ref: AS2126. Estimated cost: £65.
• 15:30 — Arrive FT Summit registration, 1 Southbank Place, SE1 9HA. Collect lanyard and materials pack. Conference app: ftlive.app/commodities2026. Wi-Fi: FTSummit_Guest / Pass: CG2026.
• 18:30 — Welcome reception, Terrace Level, same venue. Dress: business casual. End: approx. 20:00.
• 20:15 — Return to hotel. Check restaurant pre-booking or room service.

Day 2: Thursday 22 May

• 08:00 — Breakfast (hotel, charged to room — max HMRC benchmark £10)
• 09:00–17:30 — FT Commodities Summit Day 1. Sessions: see conference app. Helen’s priority sessions: 09:00 Opening Keynote (Hall A); 11:00 European Energy Transition (Hall B); 14:00 Steel & Critical Minerals (Hall A); 16:30 Networking roundtables.
• 17:30–19:00 — Drinks reception, networking.
• 19:30 — Dinner: client evening with Veritas Commodities team. Oxo Tower Restaurant, Barge House St, SE1 9PH. Booking ref: OXO228. Estimated cost: £90 (to be expensed, client entertainment — confirm approver pre-approval obtained).

Day 3: Friday 23 May

• 08:00 — Breakfast, hotel.
• 09:00–13:00 — FT Summit Day 2. Priority: 10:30 Circular Economy panel (Room 4); 12:00 Commodities outlook 2027 (Hall A).
• 12:30 — Check out (luggage stored at concierge).
• 13:30 — Lunch (self-pay, estimated £15).
• 15:00 — London Paddington. LNER: 15:30 to Bristol Temple Meads. Coach C, seat 21. Ref: LNR7842. Cost: £34.
• 17:15 — Arrive Bristol. Drive home.

Budget summary:

Total approved: £600. Final actual: £388 — under budget due to conference lunch provision on Day 2.