Ground transportation is usually the last line to be scoped on an event budget and the first thing guests complain about. That is not a coincidence: it is the only supplier whose product is consumed while the guest is alone, tired, and unable to do anything about it.
The good news is that it is almost entirely a planning problem. Here is what makes a brief quotable and what to expect back.
What a real quote needs from you
- The agenda with times — not the theme, the actual clock. A keynote at 09:00 changes the vehicle count more than the guest count does.
- The hotel list, with approximate room blocks per property. Three hotels is a different loop from one.
- Arrival and departure flights, or at least the arrival windows. "Sunday" is not a window; "Sunday, 14:00–19:00, mostly AUS" is.
- The venue, and whether you have its traffic and load-in plan. In Austin, whether you are at Palmer rather than downtown changes everything, because it puts the river in the middle.
- The interval you want to promise delegates — every ten minutes, every twenty — and whether it must hold at peak or only on average.
- Who cannot be pooled: keynote speakers, the board, sponsors bringing clients.
If a supplier quotes a vehicle count from headcount alone, they are guessing. Vehicle count comes out of loop length, dwell time and promised interval — headcount only tells you the vehicle size.
How a shuttle loop is actually sized
A loop is a frequency machine. Take the round-trip drive time, add dwell at each stop, and divide by the interval you promised. Four vehicles on a twenty-minute loop deliver a five-minute headway; three deliver seven; two deliver ten and collapse the moment one is delayed.
That arithmetic is why the river crossing to the Palmer Events Center matters so much in Austin. It adds only a few minutes to the map distance and considerably more to the afternoon reality, and a loop sized on the map quietly stops meeting its promise by mid-morning.
Loops should also be thickened rather than run flat: heavier before the keynote and at the close, thinner mid-morning. A flat loop is a loop that is over-supplied for six hours and under-supplied for two.
Separate the executive layer. Always.
Pooling a keynote speaker into a delegate loop is how a session starts twenty minutes late. The speaker, the board, and the sponsor hosting clients need dedicated assignments with a named chauffeur and flight tracking on both ends.
It is a small proportion of the spend and effectively all of the risk. If the budget forces a choice, cut frequency on the delegate loop before you pool the people whose absence stops the programme.
The five questions worth asking a supplier
- How will you size the loop, and what interval will you commit to at peak rather than on average?
- Who is my single point of contact on the day, and what happens when they are unreachable?
- Which of these markets do you operate directly, and which do you deliver through partners? (An honest answer to this is a very good sign.)
- How is billing structured — consolidated to the program, or per ride?
- What is your plan for the departure wave, specifically?
Billing that a finance team will accept
Guests of a hospitality program should never be asked for a card. Billing consolidates to the host, with reporting that a travel manager can reconcile — not a shoebox of individual receipts assembled after the fact.
Agree that structure before the program runs. Retrofitting consolidated billing onto a week of individual bookings is unpleasant for everyone and usually loses somebody's expense claim.