2026-10-17 · Conference Dispatch

How Should On-Site Conference Transport Be Dispatched in Shanghai? Vehicle Leads, Communication Lines and Last-Minute Changes

Conference transport rarely fails on the road. It fails in the few minutes when people and vehicles cannot find each other: registration says the vehicle is at the entrance while the guest is at the side door, the drop-off has changed and the driver of the third vehicle has not heard, an extra run is added and hotel concierge was never told. That confusion has little to do with how many vehicles are booked and a great deal to do with how the site is organised. Six questions and answers set out the on-site structure: whether each vehicle needs a lead, where the dispatch desk sits, how to make a pickup point describable, how to push a change to everyone, how to allocate vehicles across several hotels, and which four sheets to keep. General organisation method only; your event plan and venue conditions govern the detail.

1. Vehicle Leads and the Dispatch Desk

Q1: Does conference transport need a vehicle lead?

Yes, and it is worth more than an extra vehicle. A vehicle lead is not a new job title but one named person on each vehicle, usually a colleague from the events or requesting department. Four duties: count passengers before departure and after arrival and report any gap at once; relay instructions from the dispatch desk to driver and passengers so information does not stop inside the vehicle; handle small requests, such as a guest needing to stop briefly or divert, by judging whether it fits the route and then reporting; and record actual departure time, headcount and exceptions on the trip sheet. Without a lead, the driver is driving, coordinating and absorbing requests at the same time, and the things that fail are the most basic ones: numbers and time. The lead does not need an approval chain, only a clear limit: may reorder boarding and decide whether to wait five minutes, may not change the destination or the settlement basis.

Q2: Where should the on-site dispatch desk sit, and how should it run?

It does not need a desk, but it needs a fixed place and one person. Put it near the registration desk or in a corner of the hotel lobby where arrivals can be seen and attendees can find it; where venues are spread out, keep one at the main venue and a named contact at each main hotel, connected by a single agreed channel such as radios, a dedicated group or a phone line. What sits on the desk is concrete: the day list of vehicles and drivers, each vehicle task and time, the attendee grouping list, standby vehicle and driver contacts, and a floor plan with drop-off points marked. The operating rule is equally simple: all changes enter the desk and leave from the desk, so the organiser, the event agency and the hotel are not each briefing drivers with a different version. One person and one phone beats five people giving instructions.

2. Finding People: Pickup Points and Markers

Q3: What should be done when a guest cannot find the vehicle, or the driver cannot find the guest?

This happens at almost every large event, and calling around at the moment is the weakest response; design is the answer. Make the pickup point describable: not the hotel entrance but which door, which side, and what landmark is beside it, ideally with a photograph in the registration pack. Give the vehicle a visible marker: a meeting sign or uniform board at the front stating the event and destination, so guests recognise it without asking vehicle by vehicle. Give the driver a finding list: for station or airport pickups, the flight or train, the name and a contact number, plus an agreed rule for how long to wait, whom to call and when to withdraw, so nobody waits indefinitely or leaves early. For VIPs, station one person at the pickup point purely to guide and confirm; that cost is far below twenty minutes of a guest standing at the kerb.

3. Passing On Last-Minute Changes

Q4: How should last-minute changes and extra vehicles be communicated?

The damage comes less from the change than from some people knowing and others not. Design three levels. First, desk to vehicle lead and driver: one sentence stating what changes (time, place, headcount), with a request to acknowledge; no acknowledgement means not received, so follow up. Second, lead to passengers: announce at the next stop or before departure and post the same change in the attendee group, with both messages identical so the spoken and written versions do not diverge. Third, desk to venue and hotel: a changed drop-off must be passed on, or the vehicle arrives where nobody is waiting and the gate is not open. Extra vehicles follow the same logic: confirm the vehicle and driver are available first, then publish the new timing. Reversing that order produces an announcement with no vehicle behind it. Keep a timeline of changes so a review can see which step was slow.

Q5: How should vehicles be allocated when guests stay in several hotels?

When accommodation is spread out, allocate by departure time and headcount rather than by dividing vehicles evenly. Build one table: guests per hotel, earliest and latest departure needs, travel time to the venue, and whether a dedicated run is required. Then apply three rules. The main hotel comes first, holding most vehicles and the standby, because numbers are concentrated and late additions are likely. Secondary hotels run a fixed timetable of two or three round trips instead of on-demand departures, which cuts empty running. Distant hotels are assessed separately: if the morning journey exceeds forty minutes, depart earlier or move guests to the main hotel rather than spending their time in a vehicle. One detail is often missed: departure times should be worked back from the required arrival minus travel time minus buffer, not set identically for every hotel, or the near hotel arrives half an hour early and the far one ten minutes late.

4. On-Site Records and Close-Out

Q6: What records should be kept on site?

On-site records are not for blaming anyone; they serve three purposes: reconciling the day, settling the invoice, and improving the next event. Four sheets are enough. A vehicle and driver check-in sheet: plate, driver, arrival time and contact, confirming who is on duty. A run sheet: planned time, actual departure, headcount on arrival and exception notes for each trip, which is the core of any review. A change log: time, what changed, who was notified and whether it was acknowledged, which shows whether the information chain held. A cost acknowledgement sheet: overtime, extra runs and additional vehicles signed by both coordinators on the spot, so month-end does not become an argument. Each can be a single page, and the discipline that matters is filling them during the shift and handing them in the same day rather than reconstructing from memory afterwards. Reconcile them line by line against the invoice and differences surface immediately.