Ground Transport for Corporate Team Meetings and Offsites

A company offsite has a published agenda and an unpublished one. The published agenda is the sessions. The unpublished one is the movement between them — and it is the unpublished agenda that decides whether the first session starts on time, whether the dinner runs late, and whether the people who flew furthest spend their first evening in a car park.

Start from the manifest, not the agenda

The instinct is to build transport around the programme: sessions at nine, lunch at one, dinner at seven. That works for the middle of the event and fails at both ends, because arrivals and departures are not something you control. They are a distribution.

Ask your organiser for the arrivals manifest first — every attendee, flight number, airport and scheduled landing time. Sort it. What almost always emerges is that eighty per cent of people land inside three or four clusters, and the remaining twenty per cent are scattered across eighteen hours. Those are two completely different transport problems and they need two different answers.

Band the arrivals

For the clusters, band them. Rather than a car per arriving passenger, set meet windows — say every forty-five minutes through the busy afternoon — and assign a vehicle sized to the number of people landing inside each one. A greeter holds the meeting point, passengers gather, and the vehicle leaves when the window closes or when it is full.

The saving is significant, and not only financial. Twelve people arriving inside forty-five minutes is one van and one chauffeur rather than eight saloons and eight chauffeurs competing for the same kerb space. The hotel receives one arrival rather than eight, which its front desk will also thank you for.

For the scattered twenty per cent, individual transfers are correct. Trying to force a solo arrival at 02:40 into a shared band produces a senior person waiting alone in a terminal, which is exactly the impression an offsite is supposed to avoid.

Band the clusters. Book the outliers individually. Do not try to make one policy cover both.

Shuttle loops: headway, not timetable

Where the hotel and the venue are separate, the instinct is a timetable. A published headway works better. “A vehicle every twelve minutes from the hotel entrance between 08:00 and 09:30” is easier for attendees to act on than six specific departure times they have to remember, and far more forgiving when one person is slow to the lobby.

Size the headway to the walk. If the venue is eight minutes away, a twelve-minute headway with two vehicles means nobody waits more than twelve minutes and the loop is continuous. If it is thirty minutes away, you need more vehicles or a longer headway, and you should decide which before the day rather than during it.

• Publish the headway in the joining instructions and on a sign in the lobby.
• Marshal the pickup point — one person with a clipboard prevents most of the confusion.
• Run the loop for thirty minutes past the session start. Somebody is always late, and a stranded latecomer becomes a complaint.
• For the evening return, increase capacity. Everyone leaves at once.

Hold the vehicles. Do not release them

This is the single most valuable decision in the whole programme, and it is the one most often cut for cost. When a vehicle drops a group and is released, getting it back takes twenty to forty minutes. That is precisely the twenty to forty minutes your session overran by, and the two delays compound rather than cancel.

Held vehicles look more expensive on the quote and are almost always cheaper on the day, because the alternative is either a delayed dinner reservation for eighty people or a scramble of ad-hoc rides at whatever the market rate happens to be at six in the evening.

For executive groups moving between meetings, our hourly chauffeur hire is the right structure: the vehicle and chauffeur stay with the group for a block of hours and the itinerary can change without anything being re-quoted.

One coordinator, not five dispatchers

On a multi-city programme — a roadshow, a regional leadership tour, an incentive trip with several legs — the temptation is to use a good local operator in each city. The problem is not their quality. It is that a change in the second city has to be relayed to four other companies, and one of them will not get it.

A single coordinator holding the whole manifest means a schedule change is reflected everywhere at once, and your organiser has one number to call rather than a directory. Where we do not garage our own vehicles we dispatch through vetted operators in the LWD and LAI networks, but the coordination stays with us and so does the accountability.

Our roadshow service and conference programmes are both built this way.

Pick the vehicle for what happens inside it

Vehicle choice for an offsite is usually made on headcount. It should be made on what the passengers need to do during the journey.

The full range and capacities are on the fleet page, with passenger and luggage figures stated separately for each class — because they are not the same number.

Plan the failure, not just the schedule

Every offsite has one session that, if it overruns, breaks the rest of the day. Identify it in advance. Then decide three things before the day rather than during it.

1. Who decides. When the schedule slips, who has the authority to hold the coach or leave without the stragglers? It should be your organiser, never the chauffeur.
2. What gets cut. Agree in advance which stop is dropped if time runs short.
3. Where the contingency vehicle sits. One spare vehicle staged near the critical session costs very little and saves the evening surprisingly often.

And build the departure day properly. Offsites fail at the end more often than at the beginning, because everyone treats departures as simpler than arrivals. They are not — they are the same distribution problem, with a hard deadline attached and a room full of people checking out at the same moment.

What actually drives the cost

Offsite transport budgets are usually built by multiplying a headcount by a per-person transfer price. That number is almost always wrong, because the cost of a programme is driven by vehicle-hours and by how concentrated the movement is — not by how many people attend.

Two events with identical headcounts can differ by a factor of three. A hundred people arriving into one airport across four hours, staying in one hotel, walking to a venue next door, is a cheap programme. A hundred people arriving into three airports across two days, split across four hotels, with a venue thirty minutes out of town and a dinner somewhere else again, is an expensive one. The headcount is the same number in both.

The practical consequence is that the cheapest lever available to you is usually not negotiating the rate. It is telling people to book flights inside a suggested window, and putting everyone in one hotel. Both of those decisions are made by your organiser weeks before anyone talks to a transport company, and both move the number far more than anything we can do afterwards.

The transport budget is largely decided by the travel policy and the hotel choice, not by the transport quote.

What to send us when you enquire

A team-meeting enquiry is quoted much faster and much more accurately with these in hand. None of it needs to be final.

• Dates, city, and the hotel and venue addresses.
• Headcount, and the arrivals manifest if you have it — even a draft.
• Which airports people are flying into.
• The agenda, so we can see where the movement sits.
• Any VIP or board-level attendees needing separate arrangements.
• Whether you need billing by cost centre or department.

Send it to the desk and we will come back with a manifest and a rate rather than a per-journey price list. For a single executive transfer, the online booking form is faster.