Guest Transport at Exhibitions and Conferences: Flow, Roles and Contingencies

What decides how a conference or exhibition transport programme feels on the ground is not the size of the fleet. It is whether four things were settled in advance: which vehicle each guest tier gets, where the car actually stops, who is authorised to decide when something goes wrong, and what paperwork the on-site team keeps. Planning answers "how many cars"; execution answers "is the right car in the right place at the right time". Different people own each, and each fails in a different way.

1. Tier the guest list before you allocate a single vehicle

Tiering is a resourcing decision, not a courtesy. Within one event, VIPs, delegations and general attendees differ completely in vehicle type, flow and tolerance for waiting — mix them and every tier ends up dissatisfied. Confirm the tiered list seven days before the event, lock it 24 hours before arrival, and re-check it twice a day while flight schedules are still moving.

The last column is the one most often dropped. Vehicles can be swapped and greeting standards can be improvised, but once a confirmation deadline passes, every later step is spent catching up. The tiered list, the flight peaks and the stop-by-stop timetable are the only inputs execution has.

2. From the arrival gate to the kerb: routing and meet-and-greet standards

Arrivals levels are structurally awkward: many exits, a short pick-up lane, no long standing. So the flow has to separate people from vehicles — the car waits in the short-term parking zone, the driver or greeter meets the guest at the gate, and walks them across. Guests should never be left wheeling luggage around looking for a car.

• One day before: confirm flight number, terminal, gate number, baggage belt, party size and luggage count.
• Within 15 minutes of landing: dispatch posts "landed" in the group; the driver moves into the short-term parking zone.
• The name board is held at the first row of pillars or railing directly opposite the exit, facing outwards, at chest height, never blocking the passage.
• The board carries a name or group name plus a short event label — no full company name, no job title. Bilingual. One background colour per group for quick recognition.
• After meeting, the driver takes the luggage trolley and walks the shortest route that does not cross the vehicle lane, avoiding the second crowd in front of the baggage hall.
• Confirm name and headcount before opening the door; count luggage and photograph it; log the departure time to the group.

Holding a board looks like the simplest task on site and is the one that most often goes wrong. The more detail on the board, the more the guest is exposed; the higher it is held, the more it blocks the people behind. The only rule is: recognisable at a glance, without announcing who they are.

3. Four stops in one day: hotel, venue, dinner, departure

With four stops in a day, two tables do the work: a timeline and a vehicle-role chart. Every car is assigned exactly one role — shuttle (fixed departures sized to headcount), dedicated (tied to one guest or delegation, never reassigned), or floating (standby, temporary tasks only). Once roles are explicit, dispatch knows which car can be pulled.

The typical shape: shuttles run from hotels to the venue in the early morning; dedicated cars sit in their allocated bays through the day with drivers staying with the vehicle; a short hop covers venue to lunch; venue to dinner and dinner back to hotels are the two concentrated flows; next-day departures are timed to leave 2.5–3 hours before the flight. Build a 20–30 minute buffer between segments to absorb delay from the previous one — not to squeeze in another stop.

The real constraint is the last hundred metres. Parking around a venue is scarce at opening and closing, and coaches cannot queue at the door. Set a staging area 5–10 minutes away by road, with stewards walking guests from there to the entrance. The staging area must be fixed during the first site survey, not found on the day.

4. Standby discipline and the escalation order

Standby is not parking a car and waiting. When more than 20 vehicles are running at the same time, assign dedicated on-site operations staff; drivers stay within 15 minutes of their car, with meal breaks rotated by dispatch; drinking water, umbrellas and charging cables kept in the vehicle; phones charged and group messages visible. These details are what make a ten-minute response to an extra-vehicle request possible.

Most on-site chaos comes from nobody being willing to decide. Print this list on one page and give it to every on-site coordinator and driver before the event:

• Flight delay over 60 minutes: dispatch confirms the new landing time, holds or reassigns the driver; if the delay crosses a shuttle slot, fold the guest into the next departure. Owner: on-site coordinator.
• Extra vehicle: request goes to the on-site coordinator, who checks floating capacity first and then calls the pre-contracted reserve pool; answer within 10 minutes. Owner: dispatch lead.
• Vehicle swap (breakdown or a changed itinerary): driver reports to dispatch, dispatch sends a floating car, and the original driver stays to move the luggage — guests never move their own bags between cars. Owner: dispatch lead.
• Driver late or unreachable: if dispatch cannot make contact within 5 minutes, the backup driver is activated and the client is told immediately. Owner: operations manager.
• Headcount changes: the count on the ground governs; if it exceeds seating capacity, add a vehicle. No overloading under any circumstance.
• Closing congestion: switch to staged release, see the next section.

Every item needs a latest-decision time. Departure batches, for example, must be confirmed 60 minutes before the dinner ends, otherwise vehicles cannot arrive in time — and after that the only option is guests waiting at the door, which is the hardest cost to explain.

5. Staged release, bilingual communication and the paperwork that settles the invoice

When a thousand people leave at once, no single point can absorb the flow. Batch by destination plus flight or train time, not by seniority: cluster by direction, three to five guests per car; slice by time, one batch every 10–15 minutes; split by exit, coaches on one side and cars on the other. Print the batch sheet and post it at the registration desk and at every exit. To keep the dismissal smooth, beyond delegation vehicles and shuttle buses, VIP and media transfers should hold a proportional pool of standby vehicles. That reserve is what makes on-site adjustment possible, and in our experience it is well worth the cost for large conferences.

On language, put a bilingual driver or coordinator in every vehicle. Run two layers of groups: the master group carries instructions and timings only, the sub-group carries names and bay numbers. Thirty minutes before each pick-up, dispatch posts vehicle number, driver name, bay number and driver phone — this alone removes about half the people asking where their car is.

On-site reconciliation recognises four document types only: the dispatch sheet (time, stop, vehicle, driver), the guest sign-in or boarding signature, toll and parking receipts, and the exception log (written confirmation of added vehicles, swaps and delays). Dispatch collates them by vehicle number before the day closes and reconciles with the client within 24 hours. Chinese VAT invoices are available, split by project or cost centre. Reconciliation without an exception log always turns into a dispute.

If your event is within 30 days, send the tiered list, the flight peaks and the stop timetable first. We will return a workable vehicle timetable and standby roster within three working days, and size vehicle-days and stops from there. For multi-city itineraries, look at nationwide operations; for work alongside travel agencies and destination management companies, see OTA and DMC partnerships; for the overall approach, see conference and exhibition transport.