What counts as a disruption
A disruption is any change that threatens a commitment the executive cannot easily move. A delayed flight, a cancelled connection, a hotel without a room, or a meeting that runs past its travel buffer all qualify. The playbook should define the threshold in advance so the assistant does not debate whether an event is serious while the clock runs. A written threshold also keeps the response proportionate to the actual risk.
Not every inconvenience needs the full response. A late taxi is different from a missed international connection, and treating them the same exhausts the desk. Rank disruptions by the commitment at risk rather than by how dramatic they feel. The ranking helps the assistant decide who to call first and what authority to use.
Build the trip file before departure
The trip file should contain the itinerary, confirmation numbers, meeting contacts, local addresses, and the decision rules for changes. It should also contain the principal's preferences, such as aisle seats, dietary needs, and the maximum acceptable connection time. A file built only from confirmation emails misses the context needed to make a fast substitution. The extra context is what turns a confirmation file into a recovery tool.
Keep one current version in a location the principal and the backup can reach. Include a printed or offline copy for international travel where data access may fail. The file should name the travel agency contact, the airline desk, and the hotel escalation path. During a disruption, the assistant should not be searching for a phone number.
Set decision rights for rebooking
The executive should decide in advance what the assistant may change without calling. A common rule allows the assistant to rebook within a set budget and keep the same arrival day, while a change that adds a night or alters a client meeting requires approval. Write the rule down and include the amount, the class, and the acceptable delay. A written rule also lets the assistant act without interrupting a meeting to ask.
Decision rights should also cover who can approve an expense after the fact. If the assistant rebooks a flight at a higher fare, finance needs to know the reason and the approval path. A short note in the trip file prevents a legitimate recovery from becoming a compliance problem. The rule should be reviewed after every major trip.
Prepare the traveler's one-page card
The principal needs a card with the day's schedule, the key phone numbers, and the one decision the assistant may need. Keep it to one page and update it when the plan changes. A card that duplicates the full itinerary is too long to use in a taxi or an airport lounge. The card should answer what is next and who to call.
Include the names of the people meeting the principal and the reason for each meeting. Add a short note about the local time zone and the expected weather only if it affects the plan. The card should be readable on a phone without zooming. A clean one-page format is more useful than a polished multi-page document.
Coordinate the home office while travel changes
A disruption affects more than the traveler. Meetings need to move, colleagues need to be told, and the assistant may need to cover a commitment in another time zone. Assign one person to own the home-office coordination so the traveler is not managing two conversations at once. That person should have access to the calendar and the contact list.
Send a short status note to the people whose meetings are affected, with the new time or the decision still pending. Do not wait until the trip is fully rebooked to communicate, because silence invites duplicate outreach. A clear note that says what is known and when the next update will come reduces anxiety. The traveler can then focus on the immediate problem.
Capture costs and approvals as you go
Disruption spending is easy to lose because it happens in a hurry. Record each change, the reason, the amount, and the approval reference while the details are fresh. Photograph receipts and attach them to the trip file rather than waiting for the expense cycle. A short log saves hours of reconstruction later.
Separate the cost of the original plan from the cost of the change so finance can see the delta. Note whether the airline, the hotel, or the company absorbed the cost. If a vendor failed to deliver, record the case number and the remedy offered. This record supports both reimbursement and a future negotiation.
Run a post-trip review within a week
Review the trip while the details are still fresh. Ask what disruption occurred, how quickly it was detected, what the assistant could change, and where the response stalled. Identify one process fix, such as a better connection buffer or a saved escalation number. A review that produces a list of ten fixes will produce none.
Update the trip file and the decision rights with what was learned. For related guidance, see our article on setting a first-thirty-minutes briefing routine and our executive support services. The U.S. Department of Transportation consumer guidance explains passenger rights that can affect rebooking options. Those rules describe the baseline the playbook should work within.
Key takeaways
- Define disruption by the commitment at risk, not by how dramatic the event feels.
- Keep one current trip file with confirmations, contacts, preferences, and offline access.
- Write decision rights for rebooking, including budget, class, and when approval is required.
- Give the traveler a one-page card and assign one person to coordinate the home office.
- Log changes and costs as they happen, then run a short post-trip review with one fix.