Routes on a real map, honestly described
Stops placed on a map with driving distances from a routing service, passengers allocated from the student register, and a live trip view whose position comes from the phone travelling with the vehicle. That last sentence is the important one.
The route list and the phone call to the driver
Route planning by memory produces a stop order that is nobody’s shortest path and a passenger list that lives in the conductor’s head. Planning on a map with real driving distances makes the order defensible, and allocating from the register means the list on the bus is the list in the office.
A typed route sheet with stop times
A per-bus passenger list on a clipboard
Vehicle document expiry dates in a diary
“Where is the bus?” answered by calling the driver
Transport, screen by screen
Each of these is a screen or a service in the module rather than a heading on a roadmap.
Routes built on a map
Stops with coordinates, pickup and drop times, and an explicit sequence. Distances and the drawn path come from a real driving-route service rather than a straight line between two pins, so a route’s length is the road’s length.
Passengers from the register
A student is allocated to a route, a stop and a shift — morning, evening or both — from the student record itself. The bus list and the roll are the same data.
A fleet with documents and dates
Vehicles with registration, capacity, type and assigned driver, plus insurance, fitness, permit, PUC and service dates recorded so an expiry is visible before it is a problem. Drivers carry a licence number and its expiry.
A live trip, and what it really is
A trip is started for a route and the vehicle’s position is written as it moves, drawing the path travelled and the stops already reached on a map the office watches. The position comes from the browser’s location on the device running the trip — a phone in the cab. That is a real live map; it is not fitted tracker hardware.
A tracker can post to it, with work
There is a position-ingest endpoint that takes a device id, coordinates and a timestamp, HMAC-signed against a secret you set — so a school that already owns trackers has somewhere to point them. It is not something you switch on from a screen: a vehicle’s location mode is written as “none” when the record is created and no field anywhere changes it, so enabling a device means that secret plus an edit in the database. Nothing ships with the product.
What the family can look up themselves
A student signs into the portal and finds their own route and code, their stop with its pickup and drop time, the shift they are on, the vehicle’s registration, model and capacity, and the driver’s name with a number that dials. A student with no allocation is told to contact the office rather than shown an empty screen.
The same row, read from somewhere else
The point of an ERP is not that it has a lot of modules. It is that a fee concession, an attendance shortfall and a report card are all reading one record. These are the places Transport touches.
Students
Allocation reads the student register, so a student who changes section or leaves does not linger on a bus list.
Reports
Routes with their vehicle, driver, contact number and stop count are one of the built-in report definitions, so the fleet sheet a school gets asked for comes out of the same records the map is drawn from.
Fees
Transport is billed as a fee head against the students allocated to it, so the transport charge sits in the same ledger as tuition.
What Transport does not do
Stated here rather than discovered in week three. If something you need is on this list, ask before you buy — it is a better conversation than the one after.
There is no GPS tracker in this product. The live map is real and the position is real, but it comes from a phone in the vehicle with the trip screen open. If the phone is off, the map is stale — and if the phone is not in the vehicle, the map is wrong.
The routing service is a public driving-directions API. It is a good distance and a good path; it is not a paid traffic-aware service and it does not predict arrival times under load.
Registration lookup calls a commercial vehicle-data API you supply a key for. It is not a government or RTO system integration, and with no key configured it returns sample details rather than an error — so treat a verified tick as “configured”, not as proof.
Document expiries are dates you record and can see. Nothing chases them, because there is no SMS or push pipeline to chase them with.
A delayed bus does not notify anybody. “Everyone on this route” is not an audience a notice can be addressed to — the scope exists in the schema and nothing resolves it — so reaching those families means naming the students, and they read it in the student portal rather than on a phone. The office phone is still the office phone.
Set your institution up on Elevate
Start on the free plan for up to 250 students. Paid plans begin at ₹1499 per month, billed to the institution.