📅 2026-11-02 · Event Dispersal

Why the Last Hour of an Annual Event Stalls — and What Admins Should Schedule Six Weeks Ahead

What employees remember about an annual event is rarely the programme. It is the ride home. A late start can be absorbed; a chaotic dispersal cannot — people crowd the lobby, cannot find their vehicle, board the wrong one, and wait in the cold for half an hour. The next morning the internal chat is full of it. The cause is not a shortage of vehicles. It is treating dispersal as something that happens by itself once the event ends. Dispersal is a project with its own peak minutes, bottlenecks and owner. Admins who get it right start six weeks out: they size the demand, calculate the fleet, and match people to vehicles on site. This article follows a countdown from T-6 weeks to T+1 day, with the questions to ask, the arithmetic to use and the documents to keep. Event transport options are described in corporate event transport, vehicle classes in business vehicle fleet, and fixed commuter routes in employee shuttle service.

1. Why dispersal always jams: three flows in the same five minutes

Q1: Where exactly does dispersal jam, and why do extra vehicles not fix it?

Three points, each amplifying the others. First, the doorway: a hotel lobby usually has one exit to the driveway, so several hundred people converge on the same lifts, revolving door and canopy while vehicles queue for space. Second, identification: lighting is low and people find their vehicle from memory, so one vehicle parked in the wrong place pushes ten others to move. Third, splitting: self-driving, taxi, shuttle and chauffeur pick-ups all use one door. None of these depends on fleet size; they depend on order. The fix is to stagger departure times by twenty minutes, split the pick-up area into two or three points, and put every vehicle against a named group of passengers. Done six weeks ahead, that beats ten extra vehicles hired on the day.

2. T-6 weeks: size three numbers before asking for a quote

Q2: Which three numbers should be sized six weeks out?

Travel mode split, departure time distribution, and alcohol arrangement. Travel mode decides whether a return trip is needed at all: how many drive themselves, live within walking distance, or need transport. Add one column to the sign-up form — do you need a return seat — and you will get about eighty per cent accuracy. Departure distribution decides how many waves to run: the actual exit is not a single moment but a forty-minute slope after the raffle and the group photo, so ask the host when the last collective item ends and place waves on that slope. Alcohol decides the boundary between driver and designated driver: if the event serves alcohol, those who drove themselves need another plan, and without asking early someone will ask you on the night for a lift. With these three numbers in hand, the remaining four weeks can be calculated rather than guessed.

3. T-4 weeks: fleet size is not headcount divided by seats

Q3: How should the fleet be calculated without over-hiring or leaving people behind?

Work backwards from waves times realistic load, never headcount divided by seats. Define waves first: early leavers at ten to twenty per cent, the main peak at sixty to seventy, and the tail at ten to twenty. Then set realistic load: five to six passengers in a seven-seat business van, about eighty per cent of capacity in a mid-size coach, ninety per cent in a large coach. Never plan at full capacity, because plus-ones, prizes and luggage always take seats. For a three-hundred-person event, roughly thirty per cent leave by themselves; of the remaining two hundred and ten, the main peak is about one hundred and forty, which at six per passenger means twenty-four van trips, run in three waves. Eighteen to twenty vehicles plus two spares moves faster than thirty stacked at the door. Then calculate trips rather than vehicles: a vehicle running two waves needs empty return time plus a twenty-minute buffer, or the second wave leaves late.

4. T-2 weeks: pick-up points, vehicle cards and driver briefing

Q4: How do you match people to vehicles on site so nobody boards the wrong one?

Three items, all required: a vehicle card, a wave sheet and a sign holder. Number cards by wave and vehicle — A-03, B-07 — print them A4 and laminate, with the number on one side and the destination plus stops on the other, fixed to the right side of the door. A number alone is useless, because nobody knows which route it belongs to. Send the wave sheet to department chats a day ahead: which wave, which pick-up point, which vehicle, one line per person. Put a sign holder at every door, either the driver or an admin contact, so people look for a card rather than a name being shouted over a microphone. Add one coordinator per pick-up point with the full sheet and a radio, able to pull the next vehicle forward when one fills. With all three in place wrong boarding almost disappears; with cards but no wave sheet, people still queue at the door asking which vehicle goes to Pudong.

5. T-1 week and event day: arrival, dispersal and last bus

Q5: How should event day be timed, and when should the last bus leave?

Three segments with a buffer in each. Arrival: work back forty minutes from registration, send the first vehicles an hour early and the rest in ten-minute batches, dropping passengers and leaving immediately rather than holding bays. Dispersal: start ten minutes before the last collective item, hold the first wave at the door, then release the main peak one vehicle every five minutes, leaving when full rather than waiting. Agree with the host on one announcement — Line A at the west gate, Line B at the south gate, leave when full — which works better than printed directions. Last bus is where incidents happen: keep two vehicles to the end, one at the main hall door and one at the lobby, departing thirty minutes after final clearance, with someone sweeping the hall, washrooms and cloakroom. The last bus does not leave when full; it checks names against the list and radios if anyone is missing. It feels fussy, and it is the only reliable way to avoid leaving someone behind.

6. T+1: settlement, review and four documents

Q6: What should be settled and reviewed afterwards, and which documents kept?

Four documents: trip sheets (one per run, with plate, driver, start and end time, start and end mileage, passenger count and a signature), the wave sheet (which vehicle ran which waves, actual departure and arrival), an exception log (late arrival, breakdown, replacement vehicle, extra passengers, complaints, with the resolution), and the settlement statement (by vehicle and by wave, with runs, mileage, waiting time and overtime or cross-midnight periods). Settlement rules belong in the contract: when waiting starts, whether overtime is billed by half hour or hour, and whether a cross-midnight trip belongs to the previous or the next day. The review asks three questions only: which wave jammed, which vehicle ran empty most, which pick-up point was busiest. The answers improve next year’s sizing sheet directly — cut a vehicle from the emptiest route, release the busiest wave ten minutes earlier, add a pick-up point at the busiest door. Keep the four-part set: contract with amendments, statement, invoice and trip sheets. Accounting treatment and deductibility follow your finance lead and the competent tax authority.