Be honest. Do you discourage ad hoc bus bookings? The one-off trips? The “can she just get the bus home today?” requests from a family who don’t normally use it? The occasional seat needed at short notice?
The whole thing is such a hassle to arrange that the path of least resistance is to make it difficult, and let most of these requests fall away. Afterall, we’re talking about students’ safety here…
On the surface that looks like sensible self-protection: the office is busy enough without chasing one-off seats. But it’s worth looking at what that “no” actually costs, because for most schools it’s considerably more than the yes would.
An ad hoc booking is, by its nature, the most admin-heavy transaction in school transport. A regular booking is made once and runs all term. A one-off has to be handled individually, from scratch, every single time.
When a parent asks for a one-off seat, someone has to check whether there’s space on that specific bus on that specific day. Confirm the child is allowed on that route. Make sure the driver or bus monitor knows to expect an extra passenger. Often, work out whether and how to charge for it. And do all of that at short notice, because ad hoc requests by definition don’t come with much warning.
Done by hand, that’s a genuine interruption, and it arrives unpredictably. So it’s completely understandable that schools come to dread these requests and design their processes, consciously or not, to minimise them. The rational response to “every one of these costs me twenty minutes I don’t have” is to receive as few of them as possible.
The trouble is that minimising the requests doesn’t just save the admin. It throws away everything the requests were worth.
Three things leak away every time a school turns an ad hoc request into too much hassle to bother with.
Revenue, directly. If the school charges for transport, every refused or discouraged one-off trip is a fare not collected. Individually these are small. Across a school year, across every family who might occasionally have used a spare seat, they add up to a real sum, money that was available, that families were willing to pay, and that simply went uncollected because taking it was more effort than it was worth. The seat on the bus was empty either way. The only question was whether the school got paid for it.
Goodwill. The families making these requests aren’t trying to be difficult. They’re dealing with the ordinary chaos of working life, a late meeting, a changed arrangement, a child invited to a friend’s house. When the school makes that easy, it’s a small but real moment of the service working. When the school makes it difficult, it’s a small moment of friction, and in a fee-paying setting, those moments accumulate into an impression of how responsive the school is. Flexibility is something parents notice and remember.
Capacity you’ve already paid for. The bus is running anyway. The empty seat costs the same as a full one. Discouraging ad hoc use means running buses with spare capacity that could have been used, by families who wanted it, generating revenue that would have covered part of the cost of the route. Refusing the booking doesn’t save the cost of the seat. It just guarantees the seat earns nothing.
So the “no” isn’t actually saving money. It’s spending it, subtly, in the form of revenue not taken and capacity not used, to avoid an administrative task. When you put it that way, it’s a strange trade: the school is paying, in foregone income, for the privilege of doing less admin.
The reason schools say no is the admin and safeguarding, not the trip itself. So the question isn’t really “should we allow ad hoc bookings?” It’s “how do we make an ad hoc booking cost us nothing to approve and safe?”
And that’s a solvable problem, because almost everything that makes an ad hoc booking laborious is a check that doesn’t actually need a human to perform it.
Is there a seat? That’s a live capacity question the system already knows the answer to. Is the child allowed on that route? That’s a rule the school has already set. Does the driver know? The register updates itself the moment the booking is made. Should it be charged, and how? That can be handled at the point of booking too.
Put those together and the ad hoc booking becomes self-service. In Vectare, the parent books the one-off seat themselves in the app, but only when there’s genuinely space, within the rules the school has already defined, with any charge applied automatically. The office isn’t involved at all. The twenty-minute interruption becomes a transaction the school never has to touch.
What’s interesting is what happens next. When schools remove the admin cost of ad hoc trips, they usually find ad hoc usage goes up, because the thing that was suppressing it was never lack of demand, it was the friction. More families use spare seats, more often. The school captures the revenue and the goodwill it was previously turning away, and it does so with less work than it took to say no.
Discouraging one-off bus bookings feels like protecting your team’s time. In practice it’s paying for that time with foregone revenue, unused capacity and small daily knocks to how responsive your school feels to parents.
The reason to say no was always the admin. Take the admin out, let the booking check and charge and confirm itself, and there’s no longer a reason to say no. You get to say yes more often, to families who’ll thank you for it, while your office does less than it did when the answer was no.
This is one of the efficiency gains we cover in our practical guide, including how ad hoc bookings can run without the office touching them.
Get the guide: The Complete Guide to Efficient School Transport With Vectare
Or book a demo and see it running on your own routes.
