A flight is moved to an earlier departure. The executive arrives at the airport to find the booking was changed but the car service was not. The trip happens, the meeting starts late, and the assistant spends the next day apologising.
A weekly travel pack prevents that. It is a short document for the week ahead with the itineraries, the confirmations, the contacts, and the open decisions. It takes an hour to prepare and saves the surprises that email threads create.
Start with the week view
List every trip in the week with the purpose, the dates, and the cities. A single trip can look simple until it is placed beside the others and the travel time becomes visible.
Record the travel days and the days that are already committed. A pack that ignores the rest of the week produces a schedule that cannot be kept.
Confirm the bookings
Check the flight, the hotel, the car, and the transfer against the itinerary. Record the confirmation numbers and the times.
Do not rely on memory or on a forwarded email. A confirmation is only useful when it is checked against the current plan.
Include the local contacts
List the people the executive will meet, their roles, and the best number. Add the hotel and the local office where relevant.
Record the contact for each meeting. A pack without contacts forces the executive to search through email at the destination.
Flag the open decisions
List the travel-related decisions still open: a return time, a hotel choice, a dinner, a guest. A decision made at the airport is usually a worse decision.
Record the owner and the deadline for each. The pack should make the decisions visible before the trip, not during it.
Add the practical details
Include the terminal, the check-in time, the hotel address, and the dress code where it matters. The small details are the ones that cause the delays.
Keep the pack to two pages at most. A long pack is not read, and the details that matter are buried.
Send it at a fixed time
Choose a day and time, such as Thursday afternoon for the following week, and send the pack then. A predictable rhythm makes the pack part of the routine.
If a booking changes after the pack is sent, send a short update with the changed line. Do not resend the whole document for one change.
The one-page rule
A travel pack should fit on one screen or one printed page. The one-page limit forces the assistant to choose the details that matter and leave the rest in the links.
If the pack must be longer, add a second page only for the confirmations. The itinerary and the decisions stay on the first page.
When a trip changes
Update the pack and send only the changed section. A full resend for one flight change adds noise and makes the pack look unreliable.
Record the change and the time it was sent. The record shows that the executive was informed before the airport.
A worked example
A trip has two flights, a hotel, a car, and three meetings. The pack lists the itinerary, the confirmation numbers, the contacts, and one open decision about the return time.
The executive sees the decision on Thursday and confirms the return. The car is adjusted before the trip, and the airport surprise never happens.
Who receives the pack
Send the pack to the executive and to the person covering during travel. The cover needs the itinerary and the contacts even if they are not travelling.
Do not send it to a wide list. The pack contains personal details and should go only to the people who need them.
Review the pack after the trip
Ask the executive what was missing and what was unnecessary. A repeated gap is a template change.
Record the feedback and update the pack. The next trip should be easier, not the same.
What the pack does not do
The pack does not make the bookings or replace the travel policy. It makes the week visible and the decisions timely.
It also does not remove the need for live support during disruptions. The pack is the plan; the assistant is still the person who fixes it.