Every child accounted for, on and off the bus
Routes, stops, drivers and nannies managed together — with boarding and alighting scanned, a live manifest per trip, and a handover that is logged rather than assumed.
What usually goes wrong
- The bus list is printed each morning and out of date by the afternoon.
- Nobody can say with certainty whether a child boarded, only that they were expected to.
- At dismissal, release depends on the gate staff recognising the adult collecting.
What this module does
Routes, stops and staff together
Buses, drivers, nannies, routes and stops managed as one structure rather than four lists.
Board and alight scanning
Each child scanned on and off, producing a live manifest per trip instead of a headcount from memory.
Authorised collection
Who may collect a child is recorded, checked at release, and logged — so handover is evidenced rather than assumed.
Exceptions surfaced
A child who did not board, or alighted at the wrong stop, raises an alert while it can still be acted on.
Why this fits UAE schools
UAE school transport covers long routes across an emirate in high heat, often with a nanny alongside the driver. The manifest and handover model reflects that staffing rather than a driver-only assumption.
How it runs day to day
- 1
Routes and stops are defined
Each route carries its stops, timings, vehicle and assigned staff, so the plan exists somewhere other than the transport supervisor’s memory.
- 2
Students are assigned
A student belongs to a route and a stop, with their guardians and authorised collectors attached.
- 3
Boarding is recorded
On and off the bus, per student, per journey. This is the record that answers the only question that ever really matters.
- 4
Exceptions are flagged live
A student who did not board when expected is visible now, not at the point a parent calls the school.
- 5
Parents are notified
Boarding and arrival notifications go to the family, which removes most of the calls the transport office fields daily.
- 6
The journey is reconciled
Who boarded, who did not, and who is still on the vehicle — a closed loop rather than a headcount someone hopes was right.
The cases that usually break things
Any system handles the straightforward path. These are the situations that decide whether it survives a real school year.
A student is on the bus who should not be
The mismatch against the assigned route is flagged, rather than being discovered when the child gets off somewhere unexpected.
A parent collects from school instead today
A one-off change is recorded against the journey, so the absence from the bus is expected rather than treated as a missing child.
A student does not board at the end of day
This is the case the whole module exists for. It surfaces immediately, while the student is still on site and findable.
Someone unauthorised tries to collect
Authorised collectors are held against the student, so the check does not depend on a driver recognising a face.
The route changes for roadworks
Stops and timings update against the route, and families on it are notified from the same change.
A sibling pair travels on different routes
Assignment is per student, not per family, because assuming siblings travel together is how one of them gets missed.
Frequently asked questions
What if a child is not on their usual bus?
The exception is flagged at boarding time rather than discovered at the stop, and the parent notification is recorded.
Does the driver need special hardware?
Scanning runs on a standard phone. The route and manifest are on the same device.
How is pickup and drop-off handled at the gate?
Release is checked against the authorised collector list and logged, so there is a record of who took which child and when.
What hardware does boarding need?
Scanning runs on ordinary handheld devices rather than requiring fixed equipment installed on every vehicle, which keeps the cost proportionate to what it delivers.
Can parents see where the bus is?
Boarding and arrival notifications are the core of what families actually want, and they are generated from the same journey record staff use.
How are temporary route changes handled?
A student can be assigned to a different route or stop for a defined period, so a temporary arrangement does not become a permanent data error.
Does it link to attendance?
Yes. A student who did not board in the morning is a useful early signal, and boarding data sits alongside the attendance record rather than separate from it.
Related modules
Parent Portal & Communication
Attendance, reports, notices, consent forms and direct messaging in a single portal — instea…
Reports & Analytics
Attendance trends, academic progress and operational data across every campus — with schedul…
Behaviour & Wellbeing
Behaviour, rewards, concerns and pastoral notes in one record — so a picture builds across t…