The bus is at Stop 3. The parent already knows. Live, on the parent app.

How parents track the school bus today

It is 7:38 a.m. The mother of a Class 3 student is standing at her colony gate, waiting. The bus was supposed to arrive at 7:35. There is no horn. She does not know if the bus has already left school, if it is stuck at the bypass railway crossing, if a tyre has gone flat, or if it is sitting two stops away because two siblings did not come down on time. She has called the school office once — the receptionist said "on the way". She has called again at 7:42. Same answer. By 7:45 she is on a separate WhatsApp group with three other mothers from the colony comparing notes.

At the school office, the receptionist has answered five "where is the bus" calls in 20 minutes, and "on the way" is genuinely all she knows. The transport in-charge is in his cubicle trying to remember if the late bus is the one whose brakes were checked yesterday or a different one. He has no screen that says "Bus 4 is at Stop 3, the driver pinged 90 seconds ago, your stop is four minutes away". So he hopes for the best and shouts at the dispatcher to make calls.

Live bus tracking is the single thing that ends this morning. Inside Inkwelly's Transport module, the same app a parent already uses for fees and report cards now shows their child's bus moving on a map. The next stop has a name. The arrival time keeps updating. The school office watches every running bus on one screen. The driver runs the route from the phone in his pocket. Three different views of the same morning, and the morning works.

How live tracking actually works on a Tuesday morning

At 6:30 a.m. the driver opens the Inkwelly Driver app on the phone clipped to his bus dashboard. The app shows today's trips assigned to him — a morning pickup, an afternoon drop, both. He taps Start Trip when the bus pulls out of school. From that moment the phone's GPS pings every few seconds and the trace is streamed to Inkwelly's servers in Mumbai.

A hundred parents on that route open the parent app between 6:30 and 7:30. The Transport tab shows their child's bus moving on a live map, the current stop the bus has just left, the next stop coming up, the planned arrival at their child's stop, and the live arrival time updating as the bus actually moves. As stops are completed, the stop list updates. When the bus is two stops away from the child's pickup point, the WhatsApp alert goes out automatically.

The transport in-charge opens his admin screen with a cup of tea. Every trip running today is listed — the bus, the driver, the planned start time, the actual start time, the current location, how many children are on board, any deviation from the route. He can filter by date, route, vehicle, driver, direction (morning or drop), or trip status (planned, started, on the way, completed, cancelled). One screen, the whole fleet.

When the driver reaches each stop, he taps to mark each child boarded, absent or no-show — that becomes the day's transport attendance, automatically. If the bus deviates from the route because the road is dug up, the in-charge sees the deviation on the admin map and calls the driver before any parent has a chance to wonder.

Walkthrough — four screens that replace the 7:30 a.m. phone calls

“Mere paas pehle subah 7:30 se 9 baje tak parent calls aate the. "Bus kaha hai, bus kaha hai". Ab Inkwelly ke baad woh sab bandh ho gaya. Parents khud app pe dekh lete hain. Mera receptionist 2 ghante apna actual kaam kar paati hai — admission enquiries, fee receipts, parent meetings.”

Five real moments live tracking is built for

1. The 7:42 a.m. call from a worried mother. Old way: the mother calls the office, the receptionist says "on the way". Inkwelly way: the mother opens the parent app, sees the bus is at Stop 3, sees her stop is four minutes away, and waits. No phone call is made. The receptionist's morning is freed.

2. The flat tyre at Stop 5. The driver tapped Start Trip at 6:42 a.m. The bus reached Stop 4 on time, then deviated from the route to a tyre repair shop. The in-charge sees the route deviation flag on the fleet view and calls the driver. Driver reports the puncture. In-charge updates trip notes, sends an automatic delay message to parents of stops 5 to 9, and dispatches the spare bus. Parents are informed before they pick up the phone to ask.

3. The principal's 8:35 a.m. ops review. The principal walks in. The fleet view shows five buses completed, one still on the way (8 minutes late), zero cancelled. Yesterday's full trip log is one click away. Last seven days' on-time percentage per route is one click further. There is no "let me check and tell you".

4. The substitute bus on Tuesday. Bus 4 is at the workshop. The in-charge swaps Bus 12 onto Route 4 in the morning. The Driver app on Bus 12's phone now shows Route 4 — same stops, same children, same timings. Parents continue to see live tracking on the parent app for their child's bus. They do not even know a swap happened. The school's transport reliability looks effortless.

5. End-of-month operations review. The in-charge pulls the trips report for the month — average start delay per route, average end delay per route, cancellations by reason, deviations by route, top three routes by complaint count. Decisions are made: re-time Route 7 (consistently six minutes late), train Driver Suresh on speed control (three alerts last month), drop Vendor B's Bus 14 (two breakdowns in 30 days). Numbers, not opinions.

See live bus tracking on a real school's fleet

On the demo we will show you a real school's live trips screen, the parent app for one student, and the Driver app for one driver — the full loop end to end. 25 minutes. No sales pitch.

Limits, safety and the small print

Where the GPS comes from. The default and recommended source is the driver's Android phone running the Inkwelly Driver app. This works for every Indian school regardless of fleet size. Schools that already own vehicle-mounted GPS trackers (some State RTOs require these on contract carriages) can plug those in alongside the Driver app source. We have an integration guide — ask for it.

No-signal stretches. The Driver app caches the route, stop list and child list offline. GPS pings queue on the device when out of signal range and sync the moment connectivity returns. The parent app shows the last-known location with a "last seen X minutes ago" label so families are never confused about staleness. We have tested this in Tier-3 outskirts, hostel-route mountain passes and railway underpasses without data loss.

The driver's phone. Any Android 8 or newer phone with 3 GB RAM runs the Driver app for a 12-hour shift on a single charge. A ₹8,000 device works. The school can issue the phone or pay an allowance to use the driver's own.

Privacy. Live GPS traces are visible only to the assigned parent for their child's bus, and only during active trips. Other parents do not see other children's buses. The transport in-charge, principal and accountant (for billing context) see the full fleet. GPS traces are kept for 30 days by default and purged automatically afterwards. The Driver app switches GPS off when no trip is active — drivers are never tracked outside trip hours.

Multi-language families. The parent app and the in-trip alerts are available in English and Hindi today. A parent who picks Hindi gets Hindi-language arrival messages, in Latin digits the way the rest of the product works. Tamil, Marathi and Bengali are on the road map.

Auditability. Every trip, every status change, every cancellation, every deviation, every attendance mark is recorded with the user, the timestamp and (where it applies) the GPS location. Records can be exported per route, per driver, per bus, per term. Auditors at board affiliation reviews and RTO inspections see live data, not screenshots.