Identify the real minimum connection
Check the airport's published minimum connection time and the airline's own rule for the itinerary. The two are not always the same, and a tight connection may be legal on paper and unrealistic in practice. Add the time needed to deplane, change terminals, and clear any required check. A connection that works without bags may fail with a checked bag.
Look at the historical on-time performance for the inbound flight, not only the schedule. A flight that regularly arrives late makes a tight connection fragile even when the airline sells it. Record the source and the date of the performance data. The executive should see the risk, not just the connection time.
Check whether the itinerary is on one ticket or separate tickets. A protected connection gives the airline more responsibility when a delay occurs, while separate tickets can leave the executive stranded. The difference changes the advice and the fallback plan. Record the ticket structure before recommending a change.
Check whether the airport requires a bus, a train, or a long walk between terminals. A connection that looks short on a map can be longer in practice. Add the time for the slowest likely path, not the fastest. The executive should see the assumption behind the estimate.
Check the airline's protected itinerary
Confirm that the connection is protected under the airline's rules and that the baggage is checked through to the final destination. A tight connection with a re-checked bag is a different risk. Ask the airline or the travel management company to document the protection. Do not assume that one booking reference means one protected itinerary.
Review the change and cancellation rules for the fare. A flexible fare may make a tight connection acceptable because the cost of a missed flight is lower. A restrictive fare may make the same connection a poor choice. The executive should know the trade-off before the ticket is issued.
Check the executive's status and the lounge or fast-track options. Status can improve rebooking, but it does not make a connection physically possible. Use the benefits as a recovery aid, not as a substitute for a realistic schedule. The plan should work for a traveler without special status.
Ask the airline to confirm the connection in writing if the itinerary is complex. A verbal assurance is difficult to use when a delay occurs. Keep the confirmation with the travel record. The written note also helps the travel management company act quickly.
Build the ground plan from the arrival gate
Write the plan from the arrival gate to the next departure, including the terminal transfer, the security check, and the walk time. Use the airport map rather than a generic estimate. A plan that starts at the airport entrance misses the most variable part of the connection. The walk time should be recorded from the actual gate, not the terminal entrance.
Identify the backup flights and the last flight of the day. If the connection fails, the executive needs a specific alternative, not a general instruction to call the airline. Record the backup flight numbers, the seats available, and the rebooking contact. A backup that is already full is not a backup.
Name the ground contact who can help if the connection becomes impossible. That may be the travel management company, a local host, or the executive assistant. The contact should know the itinerary and the authority to rebook within the approved limit. A phone number without context is not a plan.
Include the time to clear immigration or customs when the route requires it. A domestic connection rule does not apply to an international arrival. The plan should name the documents the executive needs at each step. A missing document can turn a tight connection into a missed one.
Prepare the executive's decision options
Give the executive a short choice: keep the tight connection with the backup plan, move to an earlier flight, or add a buffer and arrive later. State the cost, the time impact, and the risk for each option. Do not bury the recommendation in a long itinerary. The executive should be able to decide in one read.
Explain what happens if the connection is missed. Will the airline rebook automatically, or must the executive call? Is there a hotel or a ground transfer included? The answer should be specific to the ticket and the airline. A vague assurance that it will work out is not useful.
Record the executive's choice and the date. If the choice is to keep the tight connection, note the accepted risk and the backup plan. If the choice is to change, confirm the new itinerary and cancel the old one. The record protects the assistant when the trip is reviewed later.
Put the recommendation first and the alternatives second. The executive may not have time to read a long comparison. State the cost and the risk in one line each. If the recommendation is to change the ticket, say who will make the change and by when.
Record the plan and the triggers
Write the itinerary in the travel file with the connection time, the backup flights, the ground contact, and the executive's decision. Include the trigger for activating the backup, such as a delay over a set number of minutes. A plan without a trigger tends to be used too late. The trigger should be a delay or a gate change that the office can observe.
Send the executive a one-page summary before departure. Put the first flight, the connection, the backup, and the contact at the top. Keep the detailed itinerary in the file. The summary should be readable on a phone in a taxi.
Review the trip after it ends. Did the connection work? Was the backup needed? Was the ground contact reachable? Record the answer and update the travel policy if a pattern appears. A tight connection is a test of the plan, not only of the airline.
Send the summary to the travel management company as well as the executive. The company may need to act before the executive calls. Keep the same version in both places. A plan that exists only on the executive's phone is not shared.
Related resources
Read also: executive travel disruption research and executive office coverage plan.
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