September 13, 2024 by Frank Burns
How to Plan a Conference Shuttle That Actually Works
Delegate shuttles fail in predictable ways: everyone arrives at once, the forecourt jams, the loop is too slow, and by day two people are catching rideshares and expensing them. Nearly all of it is solvable at the planning stage.
Loop frequency beats vehicle size
The instinct is to book one large coach. For a shuttle, frequency usually matters more than capacity. Delegates judge a shuttle by how long they wait, not by how many seats it has. Two smaller vehicles on a 15-minute loop feel dramatically better than one large coach on a 30-minute loop carrying the same total number.
Work out your loop time honestly — including boarding, traffic and forecourt access, not just the driving — then decide how many vehicles you need to hit the headway you want.
Cluster the hotels
Six pick-up points is a slow loop. Two or three hotel clusters, each within a short walk of several properties, is far more efficient and barely less convenient. Delegates will walk three minutes to a known corner. They will not tolerate a 40-minute loop.
Plan for the peaks, not the average
Conference demand is not evenly spread. There is a heavy inbound surge before the opening session, a lighter midday flow, and a sharp outbound peak at close — often the worst of the day, because everyone leaves at once and everyone is tired.
A shuttle sized for the average will fail at both ends. The usual answer is to add capacity for the two peak windows and run a reduced service in between, rather than paying for peak capacity all day.
Check the venue forecourt before you finalise
Large venues often have designated coach bays separate from the main entrance, limited simultaneous capacity, or restrictions during other events. Find out how many vehicles can set down at once. If the answer is one, your loop design has to reflect that, or your vehicles will queue on the street.
Tell delegates where to stand
Obvious, routinely skipped. A shuttle that runs perfectly and that nobody can find is a failed shuttle. Publish the pick-up point, the frequency and the first and last service in the delegate pack and on signage at the hotel, and brief the venue's front-of-house so they can direct people.
The last service is the one people remember
Evening functions run late and finish untidily. Set a clearly communicated final departure, and consider a second later service rather than holding one vehicle indefinitely — a coach waiting for stragglers is expensive standby, and it strands the punctual majority.
What to give your operator
Delegate numbers, and how they split across hotels.
Session times, including any offsite dinner or partner programme.
The venue's coach access arrangements and bay capacity.
Target headway — how long a delegate should ever wait.
Accessibility requirements, at enquiry rather than on the day.
Frequently asked questions
How many vehicles do we need for a conference shuttle?
It comes from loop time and target headway rather than from delegate numbers alone. Calculate the round trip including boarding, then divide by the wait you are willing to accept.
Is it cheaper to run scheduled transfers than a continuous loop?
Usually yes, if your programme has clear start and finish times. A continuous loop costs more but suits programmes where delegates come and go.
Should the shuttle run during sessions?
Often a reduced service is enough mid-programme, with full capacity restored for the peaks. It is one of the easiest places to take cost out.
Who briefs the drivers on the venue?
The operator should, but give them the venue's access details in writing. Drivers arriving without bay information is a common cause of first-morning delays.
