The Executive Assistant Travel Playbook

June 13, 2026 · 8 min read · Black Swan Editorial

A senior executive assistant manages 200+ ground-travel touchpoints per year for a busy executive. Each one has the same five failure modes: wrong vehicle, wrong time, wrong driver, wrong route, wrong handoff. This playbook is the checklist that stops them from happening. The EAs who use a version of this never make the news for the wrong reason.

Pre-trip: 72 hours out

Confirm the full itinerary with the executive: flight number, terminal, hotel, meeting addresses with floor numbers, dinner reservations with phone numbers. Cross-check time zones for every leg, especially red-eyes and trans-continental flights where the calendar date shifts in transit.

Book ground transportation for every leg, not just airport runs. Hotel-to-meeting, meeting-to-meeting, meeting-to-dinner, dinner-to-hotel, hotel-to-airport. Each one is a separate booking with a separate vehicle, chauffeur, and confirmation. Use a single chauffeur operator across cities so you have one phone number for problems.

Pre-trip: 24 hours out

Re-confirm flight times. Airlines change them quietly. The dispatch system at your chauffeur operator should be tracking the flight automatically, but a manual re-check protects against integration gaps.

Brief the chauffeur via dispatch: any specific vehicle preferences (sedan vs SUV based on weather, luggage, or guest count), arrival protocol (curbside vs inside terminal meet-and-greet), and the executive's preferred conversation level (minimal, professional, none). The chauffeur should know all this before pulling up.

In-flight: real-time coordination

Push notifications on flight status to your phone, not just the executive's. Most major airlines have an API your travel-management platform integrates with. A 4-hour delay at 2am in Atlanta is your problem to solve at 11pm in Dallas, not the executive's problem to discover at the gate.

When a delay or cancellation hits, your chauffeur operator is the second call after the airline. Dispatch rebooks the chauffeur for the new arrival time and notifies you when the rebook is confirmed. Total elapsed time should be 10 to 15 minutes from delay notification to chauffeur rebook complete.

On the ground: meet-and-greet protocols

For international arrivals, FBO arrivals, and first-time-in-city executives, always book inside-terminal meet-and-greet. The chauffeur waits at baggage claim with a printed name placard or branded tablet, takes the bags, and walks the executive to the vehicle. Curbside-only pickup is for repeat business travelers in their home city.

For executives traveling with bodyguards, brief the chauffeur on the protection protocol before arrival. Where the principal sits, where the protection sits, vehicle approach pattern, primary and secondary egress routes. The chauffeur should know the playbook from the security lead, not from improvisation.

Multi-city coordination

Use one operator across every city the executive visits. Multiple operators means multiple booking systems, multiple invoices, multiple SLAs, and multiple potential points of failure when something goes wrong at 11pm in a city you have never been to. One operator with national coverage solves this by design.

Black Swan operates with one phone number, one account manager, and one booking system across 18 US cities. The vehicle in Cincinnati matches the vehicle in Los Angeles. The chauffeur in Atlanta has been vetted to the same standard as the one in Dallas. Consistency is the entire point.

Billing and reporting

Consolidated monthly invoicing with per-traveller and per-cost-centre coding. Receipts auto-generated and synced to your AP system (Concur, Expensify, or direct ERP integration). No more chauffeur tip-and-tap reimbursements to chase down 30 days later.

Quarterly utilisation reports: which routes were taken, which vehicle classes used, which chauffeurs assigned, on-time performance, and any service incidents. This is the data the finance team uses at renewal and the executive uses to know whether the program is working.

Escalation: the 3am scenario

When something fails at 3am (vehicle no-show, chauffeur sick, executive misses connection), you need one phone number that answers live. A real chauffeur operator has 24/7 dispatch staffed by humans who can see every vehicle, every reservation, and every chauffeur status in real time.

Voicemail at 3am is the wrong answer. So is "we will call you back when the office opens." If your operator does not have live 24/7 dispatch, you do not have an operator for the executive you serve.

Frequently asked