Running an Airport Shuttle Contract for a Hotel: Scheduling, Manifests, and No-Shows
- By Booking Tool
- September 14, 2026
A hotel shuttle contract is one of the most attractive pieces of business in ground transportation. The volume is predictable, the revenue recurs without a sales cycle, and the route rarely changes. That predictability is exactly why so many operators underestimate it.
The margin on these contracts does not disappear in one dramatic loss. It leaks. It leaks in half-empty 4:30 a.m. loops that nobody needed, in monthly invoices the hotel disputes because your passenger counts do not match theirs, and in the no-show charges you quietly absorb because proving them costs more than eating them. Operators who hold hotel accounts for five and ten years are not better drivers. They run three things as systems rather than as daily improvisation: the schedule, the manifest, and the no-show policy.
Build the Schedule Around the Guest Curve, Not the Fleet
Most shuttle schedules are built backward. An operator looks at the vehicles and drivers available, divides the day into shifts, and publishes a headway that fits the roster. The hotel’s guests then have to live with it.
Start at the other end. Ask the property for ninety days of arrival and departure timestamps, then overlay the airport’s flight banks. Nearly every airport has two or three concentrated arrival windows and a heavy morning departure push, and hotel demand mirrors them with a predictable lag. You will typically find that 60 to 70 percent of your runs cluster into four or five hours of the day.
That shape tells you which service model to run in each block. During peak windows, a fixed loop with a tight headway of fifteen or twenty minutes moves the most people per driver hour and requires no dispatch decisions. During shoulder and overnight periods, a fixed loop is a money pit, and on-demand service triggered by a guest request or a tracked flight arrival is far cheaper. Many contracts benefit from a hybrid: scheduled loops from 5 a.m. to 10 a.m. and 3 p.m. to 11 p.m., request-based service otherwise.
Two details are worth negotiating into the contract before you sign. First, define the service standard in measurable terms, such as a maximum guest wait of twenty minutes during posted hours, rather than vague language about prompt service. Second, agree on terminal pickup points in writing. At multi-terminal airports, a driver circling to find a guest who walked to the wrong curb destroys your headway and your on-time numbers. Nesting specific curb zones and door numbers under each terminal as sub-points keeps drivers and guests looking at the same instruction.
Treat the Manifest as Contract Insurance
The manifest is the single document that determines whether your monthly invoice gets paid without an argument. Treat it accordingly.
A usable airport shuttle manifest carries more than names and times. It should include the guest name and confirmation or room number, party size, bag count, flight number and terminal, the scheduled pickup window, any mobility or child seat requirements, and a free-text note field drivers actually use. Bag count matters more than operators expect. A run booked for eleven passengers that arrives with twenty-six checked bags is a run that leaves people standing on the curb.
Paper manifests printed at shift start are already obsolete by the second run. Flights move, guests cancel, and the front desk adds two late requests. A live manifest that the driver, the dispatcher, and the hotel’s front desk can all see removes the phone calls that eat your dispatcher’s day.
The billing consequence is the part operators discover too late. Hotel contracts are usually invoiced per run, per passenger, or on a monthly minimum with overage. Every one of those structures is only as defensible as your passenger records. When a driver confirms each pickup and drop with a timestamp, you are not producing a schedule anymore. You are producing an audit trail, and audit trails end invoice disputes in one email instead of three meetings.
Define No-Shows Before They Happen, Not After
No-shows are inevitable on hotel airport work, and they are the most common source of friction in the relationship. The fix is contractual language written before the first run.
Spell out the wait rule precisely: how long the vehicle holds at the hotel entrance, how long it holds at the airport curb, and what happens to a guest whose flight lands two hours late. Ten minutes at the hotel and fifteen at the curb are common starting points. Then answer the question that actually matters, which is who pays. A no-show may be billable to the hotel, waived once per guest, or absorbed by you under a monthly cap. Any of those can work. What does not work is leaving it undefined and negotiating it monthly.
Two practices make the policy enforceable. Capture a reason code at the moment of the no-show rather than reconstructing it later, separating guest no-shows from flight delays, cancellations made at the desk, and dispatch errors on your side. And track inbound flights automatically so a delayed arrival reschedules instead of burning a run. Real-time flight status routinely converts a third or more of apparent no-shows into simple retimed pickups.
Then send the summary to the hotel every month, unprompted. Nothing changes a general manager’s posture faster than a one-page report showing on-time percentage, total passengers moved, and no-shows broken out by cause. It reframes the conversation from a complaint about your service into a shared operational problem.
The Takeaway
Hotel shuttle contracts are renewed on documentation as much as on driving. Build the schedule from the property’s actual demand curve, keep a live manifest detailed enough to defend an invoice, and define no-shows in writing before the first one occurs. Do those three things and the account becomes what it looked like on paper: steady, predictable, and profitable.
Booking Tool’s shuttle module was built for exactly this kind of contract work, with fixed-loop and on-demand scheduling, nested terminal sub-points, live manifests, and no-show tracking in one system. Request a demo to see how it fits your hotel accounts.
