Transport that refuses to overfill a bus

Seat capacity is a limit, not a note

Every school knows how many children its buses seat. Very few schools have a system that refuses the allocation which exceeds it. The number lives in a register; the allocation happens at a counter, in August, under pressure from a parent who lives on the route.

So the first thing to fix is not tracking. It is that capacity should be enforced where the allocation is made. When the route is full, the answer should be a waitlist, not a judgement call — and the waitlist should be visible enough that the school can add a stop or a vehicle instead of quietly adding a child.

The fleet is a set of expiry dates

A bus is legal to run only while a stack of documents is current. Each of them expires on its own date, and none of them announce themselves.

• Registration certificate for each vehicle, with the record kept against the vehicle rather than in a folder.
• Insurance, the expiry a school least wants to discover after an incident rather than before one.
• Permit and fitness certificate, both dated, both routinely discovered expired at a checkpoint.
• Pollution Under Control (PUC) certificate, which is short-dated and therefore comes round again well before the others do.
• Driver and attendant licences, which expire per person and not per vehicle — a detail that makes a purely vehicle-shaped register incomplete.

The mechanism is unglamorous: hold the dates as data, alert before they pass, and make somebody accountable for the alert. A calendar reminder in one person's phone is not a system; it is that person.

Be honest about what live tracking is

Parents want to know where the bus is. That expectation is reasonable and it is also the place where school-transport software most often oversells.

A position on a map comes from a device on the vehicle reporting its location — a tracker the school buys and fits, or an app on a crew member's phone. Software displays and interprets that stream; it does not create it. If no device is reporting, the honest interface says so.

Who got on, and when

The record that actually matters after an incident is not the route map. It is whether a specific child boarded a specific bus at a specific stop, and who recorded it.

1. Capture at the door, by the attendant, on the trip — not reconstructed in the office that evening from memory.
2. Make the log append-only. A boarding record that can be edited afterwards is a record that answers no question it was created to answer.
3. Give the crew the narrowest possible access. A driver or attendant needs their trip and their boarding list. They do not need the student directory, guardian phone numbers or fee records, and giving them a general staff login to solve a capture problem is a data-protection decision made by accident.
4. Reconcile with attendance, do not replace it. Boarding the bus is not the same fact as being present in class, and merging them hides the case you most want to see: the child who boarded and never arrived.

How this works in Vidyapeeth360

Route allocation is refused above the configured seat capacity — the request becomes a waitlist entry rather than a silent overfill, so the decision to add a stop, a trip or a vehicle is made deliberately. Transport is billed as its own fee head rather than folded into tuition, which keeps the tax treatment and the income reporting separate and correct.

The fleet and crew registers hold expiry dates for registration, insurance, permit, pollution and fitness certificates and for driver and attendant licences, and raise alerts before they pass. What the platform does not do is certify anything about a vehicle: the dates are yours, the documents are yours, and the alert is a reminder, not an approval.

Where a school supplies a compatible location input, trips show a live position with an explicit live-or-stale badge, so a parent is never shown an old reading as a current one. Boarding is captured on the trip and the log is append-only. Drivers and attendants get a deliberately minimal login — their trips, their boarding capture and their assigned tasks, with no student directory and no fees — and those logins exist only when a school explicitly links a crew record to a user account.

Everything else is ordinary record-keeping: routes and stops in transport management, the recurring charge in transport fees, and the child's arrival still recorded through student attendance rather than inferred from a bus.