Managing Multi City Business Travel: One Process, Many Markets

How do you coordinate ground transport across cities?

Coordinate ground transport across cities by standardizing the process that travelers and finance see, letting delivery stay local, and tiering cities by volume. One booking route, one confirmation format, one escalation path and one invoice format matter more than having identical vehicles everywhere.

Most national programs start as a patchwork: a trusted car company at headquarters, a different provider in each branch city and rideshare everywhere else. Each relationship has its own booking method, invoice and standard, so travelers relearn the process in every city.

• Map current suppliers, booking methods and invoice formats by city
• Decide what is standard and what may vary
• Tier cities by trip volume
• Write one booking and escalation process and one set of tier definitions
• Agree reporting by city and cost center
• Review quarterly and adjust the tiers

What should business travel ground transportation standardize?

Business travel ground transportation should standardize what travelers and finance see: how to book, who to call, what a confirmation contains, which vehicle tiers exist and how invoices are referenced. It should leave local what has to vary: available vehicles, airport pickup rules and local licensing.

Write the local differences down. A traveler landing in an unfamiliar city should know where to meet the driver and what vehicle to expect.

• Standard: one booking route and one escalation contact
• Standard: a confirmation with driver and vehicle details
• Standard: tier definitions, noting where a market cannot meet them
• Standard: one invoice format with PO, cost-center or matter references
• Standard: shared reporting fields for every market
• Local: which vehicles are available in each city
• Local: airport pickup zones and staging rules
• Local: licensing and permit requirements

How do you tier cities by volume?

Tier cities by trip volume: core cities with steady volume can justify a standing arrangement, secondary cities with occasional trips run on demand within the same framework, and one-off cities are booked as needed under the standard process.

Illustrative arithmetic: a company sees 150 trips a month across two core cities, 30 a month across six secondary cities and a handful elsewhere. About 80 percent of trips are in the two core cities, so that is where standing terms, service reviews and tailored airport plans belong. The long tail needs a simple, reliable process more than a bespoke arrangement. These are example numbers for the method.

How do you plan itineraries that cross several cities?

Plan a multi-city itinerary as one connected plan rather than a set of separate bookings: store the full itinerary in one place, share it with every local contact, and build buffers at each handoff, where one city's delay becomes the next city's problem.

Illustrative example: a two-day roadshow starts with a 7:00 a.m. pickup in City A, flies to City B for afternoon meetings, then drives 90 minutes to City C for dinner. The City B pickup depends on the flight, and the City C arrival depends on how long the last City B meeting runs. Put flight monitoring on the City B pickup, agree how long the driver can wait after the final meeting, and send City C an expected-arrival update rather than a fixed time.

Take extra care with the first trip into a new market, where the details have not yet been proven.

What changes when a business trip crosses state lines by road?

When a road trip crosses state lines in a vehicle designed or used to carry more than 8 people including the driver for compensation, it is interstate passenger transportation under federal rules: the operator must hold a USDOT number and the driver falls under federal hours-of-service limits. Sedans and most SUVs sit below that threshold and are governed mainly by state and local rules.

Hours matter on long city-to-city legs. For passenger-carrying commercial vehicles, a driver may not drive more than 10 hours, or drive after 15 hours on duty, following 8 consecutive hours off duty (49 CFR 395.5). A van that drives a team between cities after a full day of meetings may need a second driver, or the leg may be better as a flight or train.

Ask which operator will run each interstate leg and for its USDOT number. FMCSA uses that number to track a company's safety information from audits, inspections and crash investigations, so it is the right key for any check your risk team wants to run.

How do billing and reporting work across markets?

Across markets, billing should arrive in one format with the same references, and reports should break spend and issues down by city and cost center. Consolidated invoicing is most valuable in multi-city programs and also hardest to deliver, so treat it as a program option to scope, not an assumption.

Ask exactly how local operator charges are aggregated, how long they take to reach the invoice, and how disputes about a trip in another city are resolved. Use the city-level reports to decide where a standing arrangement is justified.