How Executive Assistants Should Book Multi-City Airport Transfers

Every transfer booking should carry the same brief: flight number (not just arrival time — the number is what enables tracking), terminal if known, pickup style (inside meet with name board versus curbside), vehicle class, the traveler's mobile number, and the destination with any building- or entrance-level detail. Add the executive's preferences once to the account profile — temperature, conversation, water, preferred seat — so they follow automatically.

The confirmation protocol matters as much as the brief. Require written confirmation at booking, reconfirmation the day before with chauffeur name and mobile number, and an on-location message at pickup time. And agree on the failure path in advance: who the traveler calls if they cannot find the car, and who dispatch calls if the traveler is unreachable. Two minutes of protocol eliminates ninety percent of transfer-day anxiety.

Each major market has one rule that matters most. New York: match the airport to the destination, and prefer an inside meet at JFK's international terminals — the JFK to Midtown Manhattan transfer is the workhorse booking. Los Angeles: build traffic buffers into everything and book fixed-price legs like the LAX to Beverly Hills car service early, because LAX's pickup logistics punish improvisation.

The Bay Area: confirm which of three airports the flight actually uses before booking the SFO to downtown San Francisco transfer — SFO, SJC, and OAK serve different corridors. Chicago: O'Hare is far from the Loop and weather-exposed, so the O'Hare to Chicago Loop car service should be booked with generous winter buffers. Washington: the Dulles to Washington D.C. transfer is a genuine 27-mile leg — never assume Dulles is close to anything.

Roadshow-style weeks — fly, meet, fly again — produce transfer chains: airport-to-meeting, meeting-to-airport, sometimes twice a day. Book the entire chain with one provider and label each leg against the flight it feeds, so a delay on the morning flight automatically cascades into the afternoon pickup adjustments. A provider holding the whole itinerary can rebalance; five separate vendors cannot.

Cross-market chains are where consolidation shows its value most. A Boston-to-Dallas-to-Miami week runs through the BOS to Downtown Boston car service, the DFW to Downtown Dallas transfer, and the Miami Airport to Brickell transfer — three cities, one account, one thread. You can view all U.S. airport transfer routes to price each leg while building the itinerary.

Before the trip: the full itinerary in one document, all flight numbers, hotel addresses, any VIP-handling notes, and the escalation contacts on both sides. Flag anything unusual — oversized luggage, a second passenger joining mid-leg, a stop to add. Providers plan vehicles and chauffeurs the night before; information that arrives at pickup time arrives too late to help.

The day before each leg, confirm three things: the flight number still matches the ticket (schedule changes are silent killers), the pickup style and location, and the chauffeur's name and mobile number delivered to the traveler's phone. If the executive's plans shifted — earlier flight, different terminal, colleague added — this is the moment the change costs nothing.

Parallel travel — three principals, three cities, same week — is where spreadsheet-and-app booking collapses. The consolidated pattern scales cleanly: one itinerary document per traveler, one account covering all of them, and a dispatch desk that knows the travelers by name. Vehicle assignments stay consistent, preferences follow each profile, and the assistant tracks one confirmation thread instead of nine.

For group arrivals — a deal team converging on one city from four origins — coordinate pickups by flight, not by person. Four tracked pickups delivering to one hotel beats one van waiting for the last delayed arrival, and a provider running point-to-point transfer legs under a single account can stage them without the assistant refereeing arrival order.

The rule of thumb: fixed point-to-point transfers for airport legs and single-destination moves; hourly chauffeur service when the day holds three or more stops, uncertain timing, or a schedule likely to reshuffle in the executive's hands. Hourly keeps the vehicle and chauffeur with the traveler, so a meeting that runs forty minutes long is absorbed rather than renegotiated.

Cost logic follows the same line. Two point-to-point legs usually beat two hours of hourly; five short hops across a city do not. When in doubt, describe the day to the provider and ask them to price both structures — a good account manager will recommend the cheaper configuration, because keeping the program is worth more than one inflated day.

The compact version, one week out: itinerary and flight numbers sent; vehicle classes confirmed; pickup styles set per airport; traveler profiles current; escalation contacts exchanged. Day before each leg: flight number re-verified; chauffeur name and mobile delivered to the traveler; destination details (building, entrance, host) confirmed; weather and traffic flagged if relevant. Day of: on-location confirmation received before wheels-down.

Run against a consolidated account, the checklist takes minutes per trip and removes the transfer leg from the list of things that can go wrong. If you are still selecting the provider itself, start with our travel manager's checklist for selecting a chauffeur partner, and browse BNG's worldwide airport transfer service coverage. To set up a multi-city program with one account and 24/7 dispatch, contact BNG Worldwide Chauffeur Services at +1 (650) 240-2666, toll free +1 (855) 515-4666, or info@bnglimo.com.