Routes and stops, vehicles and drivers, and a boarding record that answers the question a worried parent is actually asking.
Book a demoA parent rings at half past four because the bus has not arrived. The office knows which route the child is on, probably, and phones the driver, who is driving. Nobody can say whether the child boarded at all.
Meanwhile transport fees are tracked on a list that is separate from the fee ledger, so a family who changed route in October is billed for the old one until somebody notices.
When boarding is recorded and the route is attached to the student, both questions answer themselves.
Grouped by the job it does rather than listed as one long set of features.
Ordered stops with assigned vehicles, so a route is a defined thing rather than a driver's habit.
Vehicle records, driver assignment, documents and maintenance history in one place.
Who boarded which vehicle and when, so the question a parent asks at half past four has an answer.
Families told about departure or arrival. Available message channels vary by country, so confirm yours with us.
Transport charges that follow the student's route and change when the route does, billed through the same fee structure.
Who is assigned to each route today, printable for the driver and current rather than from last term.
A full route with a queue, and a promotion to a seat that updates the passenger list and the fee together.
Service history, insurance and fitness expiry visible before it lapses rather than when it is checked.
Which routes are full, which are running near-empty, and what each is costing.
The child who did not board. The bus left, the parent is waiting, and nobody can say whether the child was on it. That is the only question that matters and most systems cannot answer it.
The route change nobody billed. A family moves house in October and switches route. The fee keeps charging for the old one because the two lists are separate.
The driver document that expired. Insurance or fitness lapsed three weeks ago. Without an expiry date attached, that is found by an inspection rather than by the office.
The passenger list from last term. The driver has a printed sheet that predates two admissions and one withdrawal, so the headcount never matches.
These are the cases worth testing in a demo. Bring the messiest one you have.
The same records, presented differently depending on the job.
Defines routes, assigns vehicles and drivers, manages waitlists and tracks maintenance.
See their child's route and stop, and are told about the trip rather than phoning to ask.
Answers the parent who rings, because boarding and route assignment are visible rather than with the driver.
Route utilisation and cost, which is what decides whether a route survives next year.
A route is assigned to the student record, so transport is part of who the child is rather than a separate list somebody maintains. A withdrawal takes them off the passenger list without anybody remembering to.
Transport fees bill through the same fee structure as tuition, so a family gets one bill and the accounts see one collection. Route costs post to accounting against the right head.
That is why a route change in October is a single edit rather than three.
The parts of the institution this touches most.
The parent who rang, the route that changed, the list the driver was carrying. That is the test worth running.
Book a demo