Last-minute executive travel disruption response: an evidence-based playbook

Deck: When a flight changes at the worst possible time, the support team should already know the executive's constraints, authority limits, safety contacts, and best alternative routes.

TL;DR

Treat a disruption as an itinerary recovery problem, not a flight-booking problem. Confirm the event, protect the executive's safety and time-critical commitment, build two or three viable paths, and send one recommendation with the decision required. Keep the original record, check airline and local passenger rights, and close the loop with hotels, ground transport, calendar owners, and expense records.

The evidence supports preparation. In December 2025, the U.S. Department of Transportation recorded 605,844 reporting-carrier flights, with 79.12% arriving on time, 0.53% cancelled, and 0.18% diverted. The global market was also operating close to full capacity in 2025: IATA reported an 83.6% passenger load factor. These figures do not predict one executive's flight, but they explain why a credible fallback plan matters.

Contents

• Methodology
• Key stats
• Key takeaways
• The response sequence
• Rerouting comparison
• Duty of care and passenger rights
• Executive preference handling
• Communication templates
• Limitations
• Sources
• FAQ

Methodology

This playbook combines current operational data and official guidance retrieved on August 1, 2026. The statistics use the source's own geography, period, population, and denominator. DOT and BTS data describe U.S. domestic scheduled service reported by covered carriers. FAA delay-cause data uses a different operational population and definition. IATA data covers scheduled domestic and international traffic for member and non-member airlines. GBTA data is a forecast or survey, not a flight reliability measure.

The practical recommendations are an interpretation of those sources for executive support teams. They are not legal advice, a guarantee of rebooking, or a substitute for an organization's travel-risk policy. Where rights vary by itinerary, operating carrier, ticket, or jurisdiction, check the applicable authority before spending on a self-reroute.

Key stats

Key takeaways

1. The first decision is not "Which flight is available?" It is "What must still happen, by when, and under what safety or authority constraints?"
2. Treat the airline's automatic rebooking as one option. Compare it with an alternate carrier, alternate airport, rail or ground transport, an overnight, and cancellation when each is feasible.
3. Keep duty of care separate from convenience. A cheaper route may be wrong if it creates an unsafe arrival, an impossible connection, or an unsupported overnight.
4. A preference profile should include priorities and tradeoffs: nonstop versus earliest arrival, cabin minimum, acceptable airports, ground transport, hotel standard, loyalty goals, spending ceiling, and who can approve exceptions.
5. Send the executive a recommendation. Include the facts, the proposed action, the cost, and one clear decision only when standing authority does not cover it.

The response sequence

1. Confirm the disruption

Check the airline or booking platform, flight number, operating carrier, airport, connection status, and the reason shown. Record the timestamp and preserve the original itinerary. Do not rely on an unverified text alert or a social post. Confirm whether the ticket is one reservation or separate tickets, because that changes the carrier's obligations and the risk of protecting the onward journey.

2. Define the hard constraint

Write down the next immovable commitment, its location, local start time, arrival buffer, and what can be done remotely. Check passport, visa, health, accessibility, security, and family or emergency constraints where relevant. For international travel, use the organization's risk process and official destination guidance. The U.S. Department of State's STEP program can send destination alerts and help an embassy contact the traveler or emergency contact, but it does not replace the employer's own duty-of-care process.

3. Build the recovery set

Search in this order:

• the airline's protected rebooking and any same-ticket options;
• an earlier or later flight on the same route;
• a different carrier or hub, if ticketing and baggage risks are acceptable;
• an alternate airport plus pre-cleared ground transport;
• an overnight with hotel, transport, calendar, and meeting updates;
• cancellation, refund, credit, or a remote substitute when the business purpose no longer survives.

For every option, capture departure and arrival in local time, connection margin, ticket status, fare rules, baggage treatment, airport transfer, hotel impact, ground cost, cancellation exposure, and the earliest point at which the executive must act.

4. Check authority before purchasing

Use the written travel policy and the executive's delegation limits. If the assistant may rebook within a stated amount, act and log the reason. If the choice exceeds that limit, send a recommendation with the exact approval required. Do not place speculative nonrefundable tickets on separate carriers without recording the financial and missed-connection risk.

5. Update the network around the flight

Change the calendar block, meeting owner notice, hotel arrival, ground transport, airport transfer, traveler profile, expense record, and emergency contact path. If the executive is already in transit, send the new confirmation where it can be reached offline. Keep one version of the itinerary and note who owns each follow-up.

6. Close the incident

Confirm the executive arrived, the meeting or remote substitute was handled, and any overnight support was safe and usable. Save receipts, refund or credit references, and the reason for the decision. Add the route, carrier, airport, and preference lesson to the playbook. A disruption log should track event type, response time, outcome, spend, and whether the current authority or preference rule was adequate. It should not copy sensitive message content unnecessarily.

Rerouting comparison

Duty of care and passenger rights

ISO 31030:2021 frames organizational travel risk management as a cycle of policy, threat and hazard identification, risk assessment, prevention, mitigation, and review. Apply that structure to disruption response. Before travel, define who monitors, who can approve spend, who receives safety alerts, and how the traveler is contacted. During a disruption, separate a normal service failure from a safety or security event and escalate the latter immediately.

Passenger rights depend on the journey. In the United States, the DOT airline cancellation and delay dashboard records the customer-service commitments airlines make for controllable disruptions. Those commitments are not the same as a universal promise that every airline will provide a hotel, meal, or alternate-carrier ticket for every delay. Preserve the reason code and check the carrier's current commitment before promising reimbursement.

For journeys covered by EU Regulation 261/2004, official EU guidance describes a choice among reimbursement, return, or rerouting after cancellation, plus assistance in qualifying situations. It also distinguishes extraordinary circumstances from issues within the carrier's control. Do not tell a traveler to buy a replacement ticket and assume reimbursement. First document what the carrier offered and what the applicable rule says.

Safety comes before schedule. An airport closure, civil unrest, medical issue, severe weather, or security concern is an escalation event. Use official government alerts, the organization's emergency plan, the travel insurer or assistance provider, and local emergency services as appropriate. A remote EA can coordinate the response, but should not improvise medical, legal, or security advice.

Executive preference handling

The preference profile should answer questions that become expensive during a disruption:

• Is earliest safe arrival more important than nonstop service, loyalty status, or cabin preference?
• Which alternate airports and ground transfers are acceptable?
• What is the minimum hotel standard for an unexpected overnight?
• May the assistant buy a refundable placeholder, a new carrier, or a separate ticket?
• What spend can be approved without contact, and how long may the assistant wait for a reply?
• Who should be informed if the executive is unreachable?
• What accessibility, medical, dietary, family, or privacy needs must be protected?

Review the profile after every meaningful incident. A preference is not a guess about what the executive likes. It is a documented rule with a fallback and an exception path. For example: "Choose the earliest safe arrival; preserve nonstop travel when arrival remains within the meeting buffer; an alternate airport is acceptable only with pre-cleared car service; assistant may spend up to X without approval."

Communication templates

Executive message

The 7:10 a.m. flight from New York to Chicago was cancelled at 5:42 a.m. I held the 8:25 a.m. nonstop, arriving 10:05 a.m., which keeps the 11:30 meeting. The fare is refundable and within your travel authority. I have moved the car and updated the hotel. Reply "keep" if you want me to ticket it; otherwise I will use the airline's 12:40 p.m. protected option.

Meeting owner message

The executive's flight was cancelled. The current recovery plan arrives at 10:05 a.m. local time, so the 11:30 meeting remains feasible. I will confirm again after ticketing. If the connection fails, the fallback is a video call from the airport or a reschedule at [time].

Incident note

Record the event, source and timestamp, original and new itinerary, options considered, authority used, spend, rights or credits checked, people notified, arrival confirmation, and the preference or policy change to make before the next trip.

Limitations

The statistics above are not a forecast for an individual flight, executive, airline, or route. DOT and BTS cover specific U.S. reporting carriers and domestic operations. FAA's weather statistic uses a broader operational population and an older six-year period. IATA's load factor describes filled capacity, not disruption probability. GBTA's forecast and survey describe business travel markets and policy practice, not outcomes for a particular company. Passenger-rights rules differ by itinerary and can change. Recheck live airline, government, and destination guidance before acting.

Sources

Sources were retrieved August 1, 2026. Publication or data period is stated where it materially affects interpretation.

1. U.S. Department of Transportation, Air Travel Consumer Report for December 2025, published January 2026. U.S. domestic reporting-carrier flight records, on-time, cancellation, diversion, and delay-cause fields.
2. U.S. Bureau of Transportation Statistics, Airline On-Time Statistics and Delay Causes, current dashboard. U.S. large-air-carrier domestic on-time definitions and cause allocation.
3. Federal Aviation Administration, Weather Delay FAQ, current page; OPSNET data for June 2017 to May 2023. System-impacting delays over 15 minutes.
4. Federal Aviation Administration, general statements on delay causes, current page; 2024 delay-cause shares. National aviation delay context.
5. U.S. Department of Transportation, Airline Cancellation and Delay Dashboard, updated September 11, 2025. Airline customer-service commitments for controllable disruptions.
6. IATA, 2025 full-year passenger market performance, published January 29, 2026. Global scheduled domestic and international traffic, RPK, ASK, and passenger load factor.
7. Global Business Travel Association, 2025 Business Travel Index forecast, published 2025. Global business travel spending forecast.
8. GBTA and ALTOUR, State of Corporate Travel Policies 2025, published 2026. Online survey of 168 U.S. and Canadian corporate travel managers conducted November 19 to December 10, 2025.
9. ISO 31030:2021, Travel risk management, published September 2021 and current ISO listing. Guidance for organizational travel-risk policy and response.
10. U.S. Department of State, Smart Traveler Enrollment Program, current official guidance. Alerts and emergency contact support for U.S. travelers abroad.
11. European Union, air passenger rights, current official guidance. Reimbursement, rerouting, assistance, and extraordinary-circumstance rules under applicable EU protections.

FAQ

What should an executive assistant do first when a flight is cancelled?

Confirm the disruption through the airline or booking platform, identify the next immovable commitment, preserve the original itinerary, and build a small set of viable recovery options. Check authority before buying and send the executive one recommendation rather than an unfiltered list.

Should an EA always accept the airline's automatic rebooking?

No. Treat it as the first option to evaluate. Compare its arrival time, connection margin, ticket protection, airport, cabin, baggage, cost, and impact on the executive's commitment with other permitted routes.

Who is responsible for duty of care during a travel disruption?

The organization retains responsibility for its travel-risk program. The EA may monitor, coordinate, communicate, and document within delegated authority. Safety, medical, legal, and security issues should follow the organization's escalation plan and qualified assistance channels.

Can an executive assistant book a different airline?

Only when the travel policy and delegation limit allow it, or after the executive approves it. A different airline can improve arrival time, but it can also create separate-ticket, baggage, refund, and missed-connection risk. Record that tradeoff before ticketing.

What belongs in an executive travel disruption playbook?

Include monitoring ownership, authority limits, regular routes and alternate airports, acceptable carriers and hotels, ground transport contacts, emergency contacts, communication templates, passenger-rights checks, expense and refund procedures, and a post-incident review method.

How should an EA use the executive's travel preferences during a disruption?

Use preferences as ranked rules with explicit exceptions. Record the preferred tradeoff, such as earliest safe arrival versus nonstop service, the approved spend, acceptable airports and hotels, and the point at which the assistant must ask for a decision.

Related research and next step

For the operating model behind this playbook, read the research brief on distributed executive travel coordination. For the broader booking and monitoring workflow, see executive travel coordination. For preference-profile setup, read executive travel preferences.

If your executive needs someone to monitor itineraries, handle changes, and keep the rest of the day aligned, review our travel logistics support.