Published October 22, 2026
A travel change is rarely one change. A meeting moves, a flight is rebooked, a hotel is adjusted, a ground transfer is reordered, and the calendar invitations are updated. If those actions live in separate threads, the traveler arrives with a document that no longer matches the plan.
One record per trip prevents that. It holds the approved itinerary, each change event, the approval, the cost consequence, and the current documents.
Table of contents
- Open the record before the first change
- Separate preference from policy
- Record each change event
- Handle cost and approval
- Reissue and verify documents
- Close the trip with a reconciliation
- Sources
- Frequently Asked Questions
Open the record before the first change
The record starts with the approved itinerary:
- traveler and purpose
- origin, destination, and dates
- flight, hotel, and ground transport confirmations
- passport, visa, and entry requirements that apply
- traveler preferences that affect booking
- approver and budget
- emergency contact and duty-of-care owner
Store the confirmation numbers and links, not screenshots of every email. A single source of truth is easier to update than a folder of forwarded messages.
Separate preference from policy
A traveler may prefer an aisle seat, a later flight, or a particular hotel. A policy may require a refundable fare, a preferred hotel rate, or a minimum connection time. Record both, but label them differently.
When a change conflicts with policy, the assistant routes the exception to the approver. The assistant should not decide that an exception is reasonable, even when the traveler is senior. Write the requested exception, the policy line, the cost, and the recommendation if asked.
Record each change event
Use one row per material change:
| Field | Example |
|---|---|
| Change ID | TR-218-C2 |
| Requested by | Traveler |
| Received time | 2026-10-22 08:14 ET |
| Original segment | UA 412, Oct 27, 08:00 |
| New segment | UA 588, Oct 27, 11:20 |
| Reason category | Meeting moved |
| Approval | Owner, 08:40 ET |
| Cost delta | $145 |
| Documents reissued | Boarding pass, calendar, ground transfer |
A reason category helps later reviews without forcing a narrative. Common categories: meeting change, weather, airline schedule, illness, family emergency, and booking error.
Handle cost and approval
Record the cost delta before confirming the change when the fare rules allow it. If the change must be made immediately to preserve the trip, record the reason and reconcile the cost afterward.
Do not hide a cost in a later expense report. A change fee, fare difference, or extra hotel night should appear in the trip record and the reconciliation. Finance can then match the charge to an approved event.
The assistant may contact the airline, hotel, or travel management company. The assistant should not approve an exception, upgrade, or personal extension without the named approver.
Reissue and verify documents
After a change, verify:
- the traveler's current itinerary matches the record
- the calendar holds the new times with the correct time zones
- the hotel and ground transfer reflect the new arrival
- any visa or entry requirement still works with the new dates
- the traveler received the updated confirmation
- the emergency contact knows the change if the trip is international
A change is not complete when the booking is updated. It is complete when the traveler can act on the new plan.
Close the trip with a reconciliation
At the end of the trip, compare the final itinerary with the approved one and list every change, approval, and cost. Attach the receipts. This record supports expense review and answers future questions about why a trip cost more than planned.
The O*NET executive administrative assistant profile includes arranging travel and coordinating schedules as core tasks. A change log is a practical expression of that duty, not extra bureaucracy.
Sources
- O*NET OnLine: Executive Administrative Assistants
- U.S. Department of State: Travel Advisories
- U.S. Department of Labor: Hiring
- NIST Privacy Framework
Frequently Asked Questions
Who approves a travel exception?
The named approver in the travel policy or the trip record. Seniority is not approval. If the approver is unavailable, the written backup decides.
Should the assistant rebook before approval?
Only when the fare rules or safety require immediate action and the policy allows it. Record the reason and notify the approver as soon as possible.
What belongs in the final reconciliation?
The approved itinerary, each change, the approval, the cost delta, and the receipts. Keep it with the trip record, not in a personal folder.
Review cadence
Reconcile the record within 24 hours of return. Compare the original brief, the changes, the approvals, and the final cost. Note which change could have been prevented by a better buffer or a clearer decision rule. Share the finding with the travel owner and update the next brief.
A good travel record separates the change the principal requested from the change the carrier imposed. The first is a preference; the second is a service event. Keeping them apart makes the cost review fair and helps the next brief set realistic buffers. Record the distinction even when the final itinerary is the same.
