Parents ask three questions: which bus, where is it, and did my child board. A transport module should answer all three — and nothing else about other children.
Route clarity first
Before live tracking, get the static data right: the route, the ordered stops, the timings, the assigned vehicle and driver. Most 'where is the bus' calls are really 'what time does it reach my stop'.
Boarding confirmation
A trip record per route and day, with boarding marked at the stop, lets the school confirm attendance on the bus and notify parents of exceptions.
Live position — honestly
Live tracking needs a GPS source: a device in the vehicle or a provider's API. A platform should be GPS-ready — map, routes and parent view built in — and show live positions only when a real provider is connected. Simulated dots presented as live are a trust problem.
Privacy by default
- A parent sees one bus: the one assigned to their child.
- Driver phone numbers are shared by policy, not by default.
- Transport managers see the fleet; principals see their school's routes.
MANEXA's transport module is built this way: fleet, routes, riders, trips and reminders now; live location when you connect a GPS provider; and a parent view limited to their child's vehicle.