Start the log before the trip is booked
A travel change is easier to manage when the original commitments are already visible. Before booking, list the meetings, speeches, site visits, and personal obligations that depend on the trip. Include the time, the location, and the person who owns the commitment. The log should show why the trip matters, not only where the executive is going.
Record the booking reference, the traveler. The approval path for changes Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer. The record should name the next action and the person who owns it. Keep the source reference with the case. A later reviewer should be able to continue without asking for context.
Keep the log separate from the itinerary. The itinerary shows the plan; the log shows what changed and what the change affected. A single document can hold both, but the change history should remain visible. The log is the memory of the trip.
The original commitment list should include the preparation time, not only the event. A flight change that removes the morning before a speech affects the executive even if the speech itself is unchanged. Record that preparation block as a commitment in the log. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.
Record the change, not just the new itinerary
When a flight moves, record the original time, the new time, the reason if known, and the person who authorized the change. Do not simply replace the old time in the itinerary. The original time explains why a meeting was moved or why a car service was cancelled. It also helps the executive understand the cost of the change.
Record the effect on each commitment: moved, shortened, cancelled, or covered by someone else. A change that looks small on the itinerary can remove a preparation window or a recovery period. The log should show that effect before the assistant declares the change handled. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.
If the change creates a new cost or a refund, record the amount and the approval. Do not bury the financial detail in a confirmation email. The log should let the finance owner see the change without reconstructing the trip. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.
If a change is caused by the airline, record the airline's reason and the rebooking options. If it is caused by the office, record the internal reason and the approver. The distinction matters when the office reviews costs or tries to prevent a repeat. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.
Keep the executive commitments visible
The log should show the commitment owner for each affected event. If a meeting moves, the meeting owner needs to know before the executive arrives. If a speech is cancelled, the communications lead may need to update the remarks. The assistant can coordinate the messages, but the owners remain responsible for their parts.
Use a short status for each commitment: confirmed, at risk, moved, or cancelled. A status should change only when the other party confirms the new arrangement. An itinerary change alone does not confirm that the meeting host agreed. The log should distinguish the travel change from the commitment change.
If the executive is traveling with a colleague, record that person's commitments too. A change that works for the executive may create a conflict for the colleague. The assistant should not treat the trip as a solo schedule when two people are affected. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.
The commitment owner should receive the change through the channel they actually use. A calendar update may be enough for an internal meeting. An external host may need a call. Record the channel and the confirmation, not just the intent to notify.
Separate a travel change from a calendar change
A travel change may require a calendar change, but the two are not the same event. The travel log records the flight, the hotel, and the ground transport. The calendar records the meetings and the blocks that protect preparation time. Keep the link between them without merging the records.
If a meeting moves, update the calendar and the travel log together. If only the flight moves, the calendar may need a new travel block but not a new meeting. The distinction helps the assistant avoid changing a meeting that the host has not agreed to move. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.
When the executive asks why a day looks different, the assistant should be able to show both records. The travel log explains the movement. The calendar explains the commitment. A combined answer is more useful than a single edited itinerary.
If the executive decides to keep a commitment by using a different mode of transport, record the trade-off. A train may preserve the meeting but add a night away. The log should show the choice and the person who made it. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.
Review the log after the trip
After the trip, review the changes and the commitments that were affected. Look for changes that were never confirmed, commitments that were moved without the owner's agreement, and costs that were not approved. The review should produce one improvement to the booking or approval process. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.
Share the pattern with the travel and executive support team. A repeated problem, such as a tight connection that always causes a change, may be a booking rule rather than an individual mistake. The team can adjust the rule before the next trip. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.
Close the log with the final itinerary and the confirmed commitments. Keep it with the trip record for the period the office requires. The [travel change research](/research/what-executive-travel-change-logs-can-and-cannot-prove/) explains how to review the log without overclaiming what it proves. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.
The post-trip review should include the executive's own view of what worked. A short conversation can reveal a problem that the log does not capture, such as a connection that is always rushed. Record the comment and route it to the booking rule. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.
Read also: Board packet version register and Decision brief research.
Frequently asked questions
Should one assistant support the whole executive team?
Sometimes. It works when priorities are clear and executives share one operating rhythm.
What should happen before a consult?
List the meetings, inbox rules, recurring reports, and decisions that need support.
Ready to define the role?
Use a recent leadership week to scope the support that would make the biggest difference. The consultation is a working conversation, not a generic pitch.
Book a consultation