The default contract review
Two people sit down. The school says buses have been late. The contractor says they have not, or that traffic was bad, or that the school's expected times were never realistic. Neither side has anything but recollection. The meeting ends with a general commitment to do better and no measurable change.
This happens because the school has outsourced the operation and, with it, the data.
Four reports that change the meeting
You do not need a dashboard full of metrics. Four reports carry almost all of the useful signal.
1. Punctuality against expected arrival windows
For each stop on each route, the expected arrival window and the actual arrival, over a full month. What you are looking for is not the average — averages hide everything — but the distribution and the tail. A route that is on time 80% of the time and eleven minutes late the rest is a different problem from one that is consistently four minutes late.
Present it per route. A contractor with thirty vehicles almost always has three or four routes causing most of the complaints, and those are usually a scheduling problem rather than a driver problem. That is a fixable finding.
2. Speed violations by vehicle and by driver
Threshold crossings with location, peak speed and duration, attributed to both the vehicle and the driver assigned to that trip. Attribution to the driver is what makes this actionable: fleet-level speed data produces a defensive argument, while a per-driver profile produces a training conversation about two specific people.
Insist on knowing whether the threshold is evaluated on the device or on the server. Server-side evaluation at a coarse interval misses most short violations.
3. Boarding completeness
The percentage of expected boardings that produced an actual credential event, per route. This is partly a measure of the contractor and partly a measure of your own credential discipline, and separating the two is the useful exercise. A route at 99.6% has ordinary forgotten-card noise. A route at 91% has something structurally wrong — a reader positioned badly, an attendant who does not understand the process, or students being loaded through the wrong door.
4. Route deviation and unscheduled stops
Path departures beyond tolerance and stops at locations that are not on the route. Most deviations are innocent: roadworks, a diversion, traffic. The pattern is what matters. A vehicle that stops at the same off-route location every Tuesday is doing something that needs to be asked about.
How to run the meeting
Send the reports in advance. A contractor who sees the numbers for the first time in the room will spend the meeting disputing them rather than addressing them.
Lead with the routes, not the drivers. "These three routes are consistently outside the window — is the schedule wrong or is something else happening?" invites a diagnosis. "Your drivers are late" invites a defence.
Ask for a target rather than an apology. If punctuality on Route 7 is 74%, agree on what it should be next month and review it. A number that gets reviewed changes; a commitment to improve does not.
Bring the reports every cycle. The first meeting with data is uncomfortable. The fourth one is routine, and by then the numbers have usually moved.
The counterintuitive part
Contractors are frequently the party that benefits most.
An operator with no data is permanently exposed to accusations they cannot disprove. Every late arrival, every speeding complaint, every missed child becomes their fault by default because there is no evidence either way. Once tracking is in place, the ones who are actually performing well can prove it — and several of our contractor customers now bid for new school business specifically on the strength of arriving with a tracking and attendance platform already running.
The conversation stops being about blame and becomes about operations. That is a better relationship, not a worse one.
Tags
- contractors
- reporting
- operations
