Routes accumulate, they do not get pruned
A school route gets created because a cluster of families needs it. Over the following years the intake shifts, siblings graduate, families move, and the cluster thins out. Nobody removes the route, because removing a route means telling specific families their bus is being cancelled and nobody wants that conversation without a reason.
So the fleet grows a tail of under-used services. In most fleets we survey, two or three routes are running at under 40% of seat capacity, and often one of them is nearly parallel to another.
Why it stays invisible
Because seat utilisation is not measured. Schools know how many students are allocated to each route, which is a very different number from how many actually travel.
Allocation is set at admission and rarely revised. A student allocated to Route 7 who has been getting a lift from a parent for eight months is still on the Route 7 list. Utilisation based on allocation shows a healthy route; utilisation based on boarding events shows an empty bus.
Credential-based attendance produces the second number, which is the one that matters.
The analysis
Take a full term of boarding data. For each route, on each trip, count actual boardings against seat capacity. Then look at three things.
Mean occupancy per route. Sort ascending. Anything under 45% is a candidate for consolidation. Anything over 95% is a candidate for a split or a larger vehicle, and is also a safety issue if students are standing.
Occupancy by day of week. Some routes are viable on three days and empty on two. That is a candidate for a reduced-frequency service rather than cancellation, which is a much easier conversation with families.
Geographic overlap between low-occupancy routes. Plot the stops of your under-used routes on one map. Two routes at 35% whose stops are within a few hundred metres of each other are one route at 70% with a slightly longer journey time. This is the finding that saves a vehicle.
What the saving looks like
A consolidated route removes one vehicle from the fleet. Depending on your contract that is the vehicle charge, the driver, the attendant and the fuel — in most Indian school contracts a meaningful annual figure per vehicle.
Whether that saving is material depends entirely on your contract and your fleet, which is exactly why the analysis is worth doing before the argument is had. A board being asked to approve a tracking platform tends to respond better to occupancy data from its own routes than to a vendor's general claims.
Doing it without upsetting families
Consolidation fails on communication rather than on analysis.
Lead with journey time, not with cost. The honest framing is that the merged route adds four to seven minutes for some families. Say that number. A parent told the truth about a seven-minute change usually accepts it; a parent who discovers it themselves does not.
Show the occupancy data. Parents understand an empty bus. "This vehicle has been running with eleven of forty-five seats used" is a reason, and reasons are what defuse objections.
Give a term of notice, and implement at a term boundary. Nobody's routine should change mid-term.
Protect the youngest. If the merged route pushes the earliest pick-up before a threshold you are comfortable with for primary-age students, do not merge it. Some routes should stay under-used, and that is a legitimate decision made with data rather than in the absence of it.
The reverse finding matters too
The same analysis finds the over-loaded routes, and those are the ones with a safety dimension. A route at 105% occupancy has students standing or sharing seats, which is worth knowing before an inspection tells you.
Under-used routes cost money. Over-used routes cost more than money. Both are invisible until boardings are counted rather than allocations.
Tags
- utilisation
- route optimisation
- cost
