Key takeaways
- Start the clock when the office learns of the disruption, not when the airline confirms it.
- Define recovery as the first usable revised plan, including meeting and briefing changes.
- Separate waiting for information from deciding what to do, and measure both.
- Test one rebooking authority or alert channel on the next two disruptions.
Question and scope
This study asks how long an executive office takes to restore a workable plan after a travel disruption. The unit is one disruption, such as a canceled flight, a missed connection, or a last-minute schedule change. The review records the first notice, the revised itinerary, the briefings that had to change, and the time the executive could act again. It does not judge the airline or the travel provider.
Set the scope to one executive and a defined travel period, such as one quarter. Record the travel policy, the booking channels, and the people who can approve a change. If the approval threshold changes during the window, separate the periods. A narrow scope keeps the sample comparable and makes the recovery measure meaningful.
Record the purpose of the trip and the decisions that depend on it. A disruption to a conference speech has a different cost from a disruption to a routine internal visit. The review should note the purpose before measuring recovery. That context prevents a fast recovery from looking successful when the important meeting was lost.
What the sources establish
The Department of Transportation publishes air travel consumer reports that describe the frequency and causes of flight disruptions. BLS occupational data provides context on the executive assistant role but not a recovery benchmark. NIST guidance on contingency planning supports the idea of a tested response rather than an improvised one. The Small Business Administration's management guidance discusses written procedures. These sources explain why disruption planning matters but cannot supply a local recovery time.
The local measure should start when the office learns of the disruption, not when the flight is officially canceled. A delay between the first alert and the first action is often the largest recoverable gap. Record who saw the alert and who had authority to act. That detail separates a notification problem from a decision problem.
Ask whether the office has a written travel disruption procedure. If the procedure exists only in the assistant's experience, the review should say so. A written procedure can be tested and handed to a backup. The absence of one is itself a finding, especially for an executive who travels often.
Definitions and measures
Define the disruption as any event that makes the original travel plan unusable. Define the first usable revised plan as the point when the executive has a new itinerary, the affected meetings have a decision, and the briefings reflect the change. Define recovery time as the interval between the first notice and that point. Write the definitions down so two reviewers measure the same event the same way.
Measure the number of disruptions, the time to first notice, the time to a revised plan, the number of meetings changed, and the number of approvals required. Record the people involved and the channel used. A simple timeline is more useful than a single average, because it shows which step consumed the available margin. Record the time zone of each event so a late-night alert is not confused with a next-morning one.
Record the first action taken, not only the first message sent. An assistant may see the alert and wait for the executive to wake up, or may begin rebooking immediately. The gap between those behaviors is the real recovery margin. Note who had authority to act at that moment.
Sampling and collection
Collect every disruption in the travel period, including minor delays that required a schedule change but no rebooking. Include trips that were canceled before departure and trips that were changed while the executive was already away. Record the airline, the route, and the time zone. A complete list prevents the review from focusing only on the most dramatic events.
Ask the assistant and the executive to review the timeline separately, then compare. The assistant may remember the booking work, while the executive remembers the meetings that were lost. Both views are needed to define recovery. Where they disagree, keep both notes and mark the uncertainty.
Include disruptions that were resolved before the executive noticed, because those are the ones the process handled well. Also include disruptions that the executive resolved personally, because those show where the office lacks authority. The contrast is more useful than a list of problems. Ask the executive which of those personal fixes should have been handled by the office.
Analysis and reporting
Report recovery time by disruption type and by time of day. Separate a delay that happened before the trip from one that happened at the airport. Show the meetings that were moved, canceled, or replaced with a delegate. A disruption that was handled without losing a decision may be less costly than one that preserved the itinerary but delayed a board paper.
Rank the delays by consequence and choose one fix. The fix might be a travel approval threshold, a standing rebooking authority, or a single channel for alerts. Test it on the next two disruptions and compare the same timeline. Do not change the airline, the policy, and the approval rule at once.
Compare the recovery time with the travel policy's approval threshold. A low threshold may force a call to the executive for a small cost change, while a high threshold may let the assistant act quickly. The review should show which threshold applied and whether it helped. That link turns a travel finding into a policy decision.
Compare the recovery timeline with the number of people who had to approve a change. A disruption that required three approvals may have been slower than one that required none, even when the airline response was similar. Report the approval count beside the time. That comparison shows whether the delay sits in the travel market or in the office.
Limits and sources of error
The study cannot prove that a faster recovery produced a better outcome, because the value of the meeting and the executive's fatigue also matter. The first notice may be missing if the alert went to a personal phone. Report the gaps and avoid claiming a precise recovery time when the start is uncertain. A range is more honest than a false exactness.
Some disruptions are resolved by the traveler without involving the office, and those events may not appear in the record. A canceled trip may also remove the need to recover, which makes the sample look better. Note those cases and keep them separate from disruptions that required active recovery. The method should reward a clear record, not a perfect outcome.
Do not treat a long recovery as a failure if the airline offered no alternative. The review measures the office's response, not the airline's schedule. Separate the time spent waiting for information from the time spent deciding. That separation shows where the office can improve and where it cannot.
Review and next action
Choose one change, such as a pre-approved rebooking limit or a single alert channel that reaches the on-call assistant. Test it for one quarter and repeat the timeline. The [coverage plan](/blog/designing-an-executive-office-coverage-plan-for-planned-absences/) can name who has authority when the executive is in transit. Keep the old approval rule for trips that are already booked so the test does not strand a traveler.
Close the review when the office can show which disruptions were recovered quickly and which still depend on the executive's personal intervention. Keep the timeline with the travel policy so the next review starts from the same definitions. Share one lesson with the people who book travel. The goal is a calmer recovery, not a longer policy.
Write the revised procedure into the travel pack and the coverage plan. Give the assistant a clear limit and a named escalation contact. Review it after the next two trips rather than waiting for the annual policy cycle. A tested procedure is more useful than a longer document.
Test the revised procedure on a planned trip before relying on it during a real disruption. A tabletop review can miss the access and contact problems that appear when a flight is actually canceled. Record the test date and the people who took part. The next disruption will show whether the procedure is usable under pressure.
Sources
- Secretaries and Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Outlook Handbook.
- Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics.
- Executive Secretaries and Executive Administrative Assistants, O*NET OnLine.
- Business Formation Statistics, U.S. Census Bureau.
- Nonfarm Business Sector: Labor Productivity, Federal Reserve Economic Data.
- Productivity Statistics, OECD Data Explorer.
- World Development Indicators, World Bank DataBank.
- ILOSTAT Labour Statistics, International Labour Organization.
- 2024 Work Trend Index Annual Report, Microsoft and LinkedIn.
- The economic potential of generative AI, McKinsey Global Institute.
- Creating helpful, reliable, people first content, Google Search Central.
- Search Engine Optimization Starter Guide, Google Search Central.
- Dear Manager, You Are Holding Too Many Meetings, Harvard Business Review.
- DOT, Air Travel Consumer Reports.
- BLS, Secretaries and Administrative Assistants.
- NIST, Contingency Planning Guide.
- SBA, Manage your business.
Related research
Apply the research
Use the finding to frame one question for your own team: which support work is currently invisible, and who should own the next step? A scoped consultation can turn that question into a practical role. Write the question down before the meeting. Name the person who owns the next step.
Turn the finding into a support scope.
Bring the workflow that feels hardest to see. We will help define the role, the evidence it should maintain, and the decisions that stay with leadership.
Talk through the role