How to Build a Business Trip Itinerary That Holds Up on the Day

A work trip is not a short holiday. What makes it stressful is rarely the travel itself. It is that four different people booked pieces of it, none of them talked to each other, and you are the one standing in an airport at 6am trying to remember whether the car meets you at arrivals or at the hotel.

Holidays forgive a vague plan. You wander, you eat late, nothing breaks. A business trip does not forgive anything, because it has fixed points with other people's time attached to them. Miss the connection and you are not just inconvenienced, you have moved a meeting that took three weeks to schedule.

Here is how to build a business trip itinerary that holds up: what belongs on it, how to assemble it when you did not make half the bookings, and how to keep the expense side clean while you are still travelling.

Why a work trip breaks differently

Three things go wrong on business trips that almost never go wrong on holidays.

The bookings come from everywhere. The travel desk books the flight and sends a PDF. You book the hotel yourself because the approved one was full. The client's assistant mentions dinner in a calendar invite. A colleague forwards a train ticket as a screenshot. Four sources, four formats, and no single place where the trip exists.

The calendar is not the itinerary. Your work calendar knows the meetings. It does not know the flight is delayed, that the hotel is forty minutes from the office, or that the return train is the last one of the day. A calendar shows commitments. It does not show whether they are physically possible.

The trip ends with homework. Every receipt you did not photograph is a small tax on a future evening, and the expense report only gets harder the further you get from the thing you paid for.

What belongs on a business trip itinerary

Not everything. A good work itinerary is short enough to read on a phone while walking. These are the pieces that earn their place.

• Every travel segment, in order. Flights, trains, and the airport transfer, with times and confirmation numbers. The transfer is the one people leave off and the one that strands them.
• Where you sleep each night, with the address in a form you can hand to a driver, and the check-in time if it is late.
• The fixed commitments, with location and who you are meeting. A meeting without an address is a meeting you will be late to.
• Travel time between the fixed points. This is the difference between a list and a plan. Two meetings across town are not two calendar entries, they are two entries and the hour between them.
• The things that only matter if something goes wrong. The booking reference for the return leg, the hotel phone number, the name of whoever can move a meeting for you.

What does not belong: anything nobody will read. A twelve page itinerary is a document you open once.

Building it, step by step

1. Collect the bookings in whatever form they arrived

The instinct is to retype everything into one clean document, and it is why most people never build the itinerary at all. Retyping a confirmation is ten minutes of transcription with a real risk of a wrong digit in the one field you cannot afford to get wrong.

Collect instead. Forward the emails, upload the travel desk's PDF, drop in the screenshot of the train ticket. The goal is that everything is in one place, not that it is tidy.

2. Put the commitments next to the logistics

Once the travel is in, add the meetings to the same day-by-day view. This is the step that turns a folder of bookings into something useful, because it is the first moment you can see the day as it will actually happen. A 9am on the far side of the city, the day after a flight that lands at 11pm, looks fine in a calendar and looks obviously wrong on an itinerary.

3. Add buffers where they matter, not everywhere

Padding every gap makes the plan longer and no safer. Put the buffer in three places: the connection, the airport transfer on arrival day, and whatever sits immediately before the most important meeting of the trip. Those three carry nearly all the risk.

4. Photograph receipts at the moment of payment

Thirty seconds at the taxi door, not a hunt through a coat pocket in two weeks. Attach it to the expense where the amount is recorded, so the photo sits beside the number it explains. The same photo in your camera roll answers nothing, because you will never find it among four hundred others. This is the habit that shortens the expense report most, and the one people adopt last. Our guide to building a travel expense report covers the rest.

5. Share the parts other people need

Your colleague needs the whole plan. The client needs to know when you land. Whoever is covering at home needs the return time and nothing else. Sending a screenshot of everything to all three is how booking references end up in group chats.

The day-of test

Before you leave, read the itinerary as though you are already tired. One question per day: if I did exactly what this says, in order, would it work? Most broken business trips are visible the moment you ask that, usually as a gap forty minutes shorter than the journey inside it.

Then check it opens on your phone with no signal. A plan behind an airport wifi login is a plan you do not have when you need it.

Being fair about the tools

TripIt effectively invented this category and stays dependable when confirmations arrive as clean email text, which corporate travel desks often produce. The friction shows up on other formats, and the sharing most useful for work sits in the paid tier.

Tripsy is a lovely app if you live on Apple devices, built more for personal travel than reimbursement. Wanderlog is strong at the deciding-where-to-go stage, a phase business trips skip entirely: you are not choosing the city. Your company's expense system is good at the money and knows nothing about your day.

The gaps land in the same places each time: formats that are not clean email text, what it costs to include a colleague, and whether the plan is any use offline.

Where Petrel fits

Petrel Voyage is built around the assumption that you did not make all your own bookings, which is the defining fact of business travel.

• Any format goes in. Forwarded emails, PDFs from the travel desk, screenshots, photos of a paper voucher, calendar files, or a CSV export. Hand Petrel the mess and it builds one day-by-day plan, usually in under a minute. Trains, buses, and ferries sit alongside flights, which matters if your week is Brussels to Cologne rather than hub and spoke.
• Work trips stay separate from personal ones. They sit on their own tab, so a conference in March does not get tangled up with a long weekend in April, and the expense side stays clean.
• Receipts attach where the money is, images or PDFs, and the trip produces a print-ready expense report with dates, categories, and totals, plus the receipts appended. It is built to be handed straight to whoever approves it.
• Live flight status on the flight card. Gate, terminal, and delay information sit against your flight, so you are not cross-checking an airline app against a separate plan. To be precise: Petrel shows status when you look, it does not yet send proactive delay alerts. Our post on flight status tracking is specific about that line.
• Colleagues are free. Invite someone travelling with you and they can view and edit without paying for anything. For everyone else there is a view only link that needs no account at all, and it deliberately leaves out your booking codes, costs, and receipts, so sending a client your arrival time does not hand them your ticket references.
• It opens offline. Your plan is readable with no signal, in a taxi from an airport whose roaming you never sorted out. Honestly stated: readable, not editable, so logging an expense mid flight waits until you land.
• The first trip is free, with every feature and no account, which means you can test it on a real work trip before deciding anything.

On privacy, plainly, because work travel carries client names and internal meetings: Petrel does not connect to or scan your inbox. You forward what you choose, and that is all it sees. Your bookings are not sold, and they are not used to train AI. Our page on why we built it this way sets out the reasoning.

The short version

Gather the bookings in whatever format they arrived rather than retyping them. Put the meetings in the same view as the travel, so you see the day instead of a list. Buffer the connection, the arrival transfer, and the run up to the meeting that matters. Photograph receipts as you pay. Share the right slice with each person, and check it all opens without a signal.

Do that and the trip stops being something you hold in your head at 6am. You can set your next one up at https://petrelvoyage.com, or start from a route in the itinerary library. The first trip is free, with no account and no credit card.