School transport is the part of a school that operates furthest from the office and carries the most risk. A bus leaves at 5.40am with forty children on it, travels roads nobody in the administration block can see, and comes back. Most days nothing happens, which is exactly why the record-keeping tends to slide.
The things that go wrong in school transport go wrong quietly: an insurance certificate that lapsed, a route that grew by three stops without anyone recosting it, a learner billed for a service they stopped using in January. This guide is about keeping those visible.
Routes and stops as records, not memory
In a lot of schools the route lives in the driver's head. That works until the driver is unwell, and then a replacement is guessing at pick-up points while parents phone the office.
A route should exist as a record: an ordered list of stops, with times, assigned to a vehicle, with the learners who use each stop attached to it. Once it exists in that form several things become possible — a replacement driver can run it, the office can answer “where is the bus” without phoning anyone, and you can see that the eastern route has twelve learners while the northern route has forty-one.
Assigning learners properly
The link between learner and stop is what makes everything downstream work: the register on the bus, the billing, the parent notification. Keep it current. A learner who changes stop mid-term and is not updated will be looked for at the wrong place, and that is the failure mode nobody wants to explain.
Transport billing is where money leaks
Transport is usually billed as a separate votehead, often at different rates for different routes or for one-way versus return. That is more variation than a fee structure normally carries, and it is where quiet losses accumulate:
- Learners who stopped using the bus but are still billed — which becomes a refund argument.
- Learners who use the bus but were never added — which is simply lost income.
- Term-time changes that nobody prorates.
- Siblings on different routes charged at one rate.
- Exemptions granted verbally and never recorded.
The fix is unglamorous: transport billing should be generated from the route assignment, not maintained as a separate list. If the two are kept apart, they drift within a term. Exemptions should be recorded against the learner with a reason, so the decision survives the person who made it. See the budgeting guide for how transport sits in the wider votehead picture.
The vehicle file
Every vehicle should have a file that somebody checks on a schedule rather than when a problem appears. What belongs in it:
| Record | Why it matters |
|---|---|
| Insurance and expiry date | The lapse you discover after an incident is the expensive one |
| Inspection and compliance documents | Needed on demand; painful to reconstruct |
| Speed governor records | Part of the compliance file for school vehicles |
| Service history and mileage | Distinguishes a due service from a surprise breakdown |
| Fuelling records | Consumption per vehicle is one of the clearest early signals of a problem |
| Driver assignment | Who was on which vehicle, when |
Expiry dates are the ones to automate. Insurance and inspection dates should generate a reminder well before they lapse, because the alternative is finding out at a roadblock — or worse, after an incident.
What to tell parents, and when
Transport generates more parent anxiety per message than anything else a school sends, so precision matters more than volume:
- Boarding and alighting — a short confirmation when a child gets on and off. This single message removes most transport calls.
- Delays — proactively. A parent told the bus is twenty minutes late is calm; a parent who works it out is not.
- Route or stop changes — in writing, ahead of time, naming the learner and the new stop.
- Billing changes — when a learner joins or leaves the service, so the invoice is never a surprise.
What not to do is send live tracking to parents as a substitute for notification. A map a parent has to interpret at 6am is not reassurance. Send the sentence; keep the map for the office. The parent communication guide covers which channel each of these belongs on.
How Mzizi handles it
Mzizi holds bus stops, routes, vehicles and trips as records, with learners assigned to routes so that the register, the billing and the parent notification all come from the same assignment. The vehicle file covers insurance, inspection, speed governor records, servicing, fuelling and mileage. Transport charges post to the learner's account alongside tuition rather than sitting in a separate spreadsheet, and exemptions are recorded against the learner. MziziGo extends the same records to tracking and parent notifications on the journey itself.
Transport is also covered step by step in our help centre guide to transport routes.