Stop Staffing Your Shuttle by Guesswork

Most independent hotel shuttles run on a fixed loop: every 30 minutes, on the hour and the half, whether there's a guest waiting or not. It's simple to communicate and it's usually wrong. At 6am on a cruise-day Saturday, that 30-minute loop can't keep up — guests are stacking up at the curb with a boarding time to make. At 2pm on a Tuesday, the driver is making an empty round trip because the schedule said so, not because anyone needed it.

That mismatch is a staffing cost hiding as a service standard. Every empty loop is paid driver time with no guest on board. Every overwhelmed peak is a guest who's now late, annoyed, or both — and telling other people about it in a review.

The fix is scheduling around actual bookings instead of a fixed clock. When shuttle requests come through a real booking system — see the cruise-shuttle numbers in an earlier post — the hotel can see demand building hours or days ahead. A cruise-day Saturday with eleven bookings by 6am looks nothing like a quiet Tuesday, and staffing should reflect that difference instead of running the identical loop on both.

This isn't about adding a second van. Most properties don't need more shuttle capacity — they need to deploy the capacity they have against where the demand actually is. A driver who knows there are three airport runs backed up between 7 and 8am can sequence them efficiently. A driver running a fixed loop with no visibility into demand can't do anything but follow the clock and hope.

If your shuttle schedule was set once, years ago, and hasn't moved since, it's optimized for an average day that may not exist anymore. The properties getting real revenue and real guest satisfaction out of their shuttle are the ones scheduling against demand they can actually see — not a loop that was easy to print on a lobby sign.