Every safe stop. Every speed alert. On the principal's screen, in real time.

How most Indian schools think about bus safety today

The principal mentions safety at every parent-teacher meeting. The school's brochure has a section on safety, complete with the words "GPS", "speed governor" and "trained drivers". On the day of the CBSE affiliation review, the file with all the safety paperwork is presented to the inspector and ticked off. And then the school year resumes, and safety becomes invisible — a thing that exists in folders, on certificates, in slogans, but not in any real-time signal anyone can see. When something does go wrong — a driver speeds, a bus deviates from the route, a stop is skipped because the driver was running late — the school finds out the way it always does: a parent complains, a class teacher reports an upset child, a police officer calls.

This is not a complaint about Indian schools. It is the structural reality of a system where safety is documented but not measured. The CBSE School Bus Safety Guidelines, the Motor Vehicles Act, the POCSO Act 2012 — each of these expects active safeguarding, not passive paperwork. But without a system that turns safety into live signals, the principal's commitment lives in conversation; the in-charge's plans live in his diary; the driver's behaviour lives in his memory. Three layers, none connected to each other. Something will eventually fall through.

Inkwelly's geofencing and safety workspace is the live signal layer Indian schools have been missing. The school perimeter is a geofence — every entry and exit of every bus is logged. Each stop is a geofence — every arrival and departure is timestamped. Speed limits are set per route; crossing them fires an alert in seconds. Route plans are drawn once; deviating from them flags the bus on the in-charge's screen the moment it happens. Safety stops being a slogan and becomes a screen the principal can actually look at.

How safety alerts actually work in Inkwelly

Open Transport → Safety. The dashboard shows four kinds of geofences and three kinds of alerts. The school perimeter — a geofence around the school gate, with an entry alert when a bus arrives and an exit alert when it leaves. The principal sees the time of every gate event, the bus, the driver, the route. Each stop — a small geofence around the stop, with arrival and departure events that match against the planned timing. Restricted areas — a railway crossing where buses must crawl, a school zone where the speed limit is 25 km/h, a markets road where the route should never deviate during peak hours.

Speed alerts fire when the bus crosses the school's set speed limit — typically 40 km/h on city roads, 25 km/h in school and residential zones, set per route. The alert lands on the in-charge's WhatsApp within seconds, with the bus, the driver, the speed, and the GPS location at the moment of the alert. Patterns build up over a term — a driver who fires three speed alerts a week becomes visible on the safety dashboard, and the in-charge plans a coaching session before parents start to notice.

Route deviation flags fire when the bus exits the planned route geofence. The in-charge sees the deviation on the live fleet view and can call the driver immediately. Ninety percent of deviations are innocuous — a road dug up, a tyre puncture, a sudden traffic jam. The driver explains, the in-charge updates the trip notes, parents on stops yet to be visited get an automatic delay alert. The remaining ten percent — a driver taking a personal detour, a vendor's bus running an unauthorised side trip — are caught, addressed, and a pattern over time becomes the school's safety conversation, not a parent's complaint.

Walkthrough — four screens the principal opens for the safety review

“Pehle hum bus safety ke baare mein bas baat karte the. Brochure mein likhte the. Inspection ke pehle file taiyaar karte the. Ab Inkwelly har bus ki har trip ka data deta hai — speed alerts, route deviations, stop arrivals. Ek driver ne pehle 3 speed alerts mein license renewal pe note mil gaya. Ab woh raftaar mein nahi chalata. Safety ek system ban gayi hai, ek slogan nahi.”

Five real moments safety alerts is built for

1. The Wednesday morning speed alert. The driver of Bus 4 hits 47 km/h on the bypass at 7:08 a.m. The school's speed limit on that stretch is 40 km/h. A WhatsApp lands on the in-charge's phone within seconds. The in-charge calls the driver, asks him to slow down, and notes the alert against the driver's profile. By Friday's safety review, the driver's alert count for the week is the highest in the fleet — the in-charge schedules a coaching session for the following Monday.

2. The October route deviation. Bus 7 exits the planned route 380 metres on a Tuesday morning. The in-charge sees the flag on the live fleet view, calls the driver. Driver reports a tyre puncture. The in-charge updates trip notes, sends an automatic delay alert to parents of stops 5 to 9, dispatches the spare bus. The trip closes 18 minutes late instead of an hour late, and parents are informed before any of them call.

3. The school-perimeter audit at term-end. The CBSE affiliation reviewer asks for evidence that buses are leaving school on time and arriving back. The in-charge exports the school-perimeter event log for the term — every entry, every exit, every bus, every driver, with timestamps. The reviewer sees clean data, on-time percentages per route, and the school's safety culture documented in numbers. The review passes without a follow-up.

4. The off-hours movement alert. A vendor's bus moves at 8:42 p.m. on a Saturday — well outside scheduled trip hours. Inkwelly's off-hours alert fires. The in-charge calls the vendor. Vendor explains the bus was being moved to a workshop. Inkwelly logs the explanation, ties it to the alert, and the audit picture is intact. If the explanation had not been satisfactory, the school would have caught a misuse before it became a complaint.

5. The stop-skip flag. The driver of Bus 12 passes within 50 metres of Stop 4 without entering the geofence — the bus did not actually stop. The in-charge gets a flag in real time. He calls the driver, who explains he saw no children at the stop and did not want to delay the route. The in-charge updates the policy: drivers must wait at every stop for the planned 90 seconds, even if they see no children, because some children may run from inside the colony to catch the bus. The driver acknowledges. The pattern stops repeating because it is now visible.

See your school's bus safety as a live screen, in 30 minutes

Bring a list of two or three of your routes and the speed limits you would like applied. On the demo we will draw the school perimeter and the stops as geofences inside Inkwelly while you watch — you will see exactly what live alerts look like for one of your buses before you sign anything.

Limits, safety and the small print

Geofence shapes. School perimeter geofences are custom polygons drawn on a city map (Indian school campuses are rarely circles). Stop geofences default to a 60-metre circle around the boarding point and can be adjusted per stop. Restricted areas are drawn manually for railway crossings, school zones, narrow market streets and other school-specific concerns.

Speed limit configuration. Per route, with a default applied across the fleet. The defaults match what the CBSE School Bus Safety Guidelines suggest — 40 km/h on city roads, 25 km/h in school zones and residential areas. The in-charge can override per route or per stretch.

Alert routing. Speed alerts and route deviations go to the in-charge by default. The principal can opt in to receive critical alerts (severe speed violations, repeated deviations on the same trip). Parents do not receive raw safety alerts; they receive sanitised delay messages where the deviation will affect their child's stop timing.

Privacy. GPS traces during trips are visible to the assigned parent for their child's bus only and only during active trips. Safety alerts are visible to the transport in-charge, the principal and (briefly during a verified inspection) the inspector. Drivers and conductors see only their own performance tab; they do not see other drivers' alerts.

Data residency. All Inkwelly data — GPS traces, geofence definitions, alert logs — is stored on servers in Mumbai, encrypted at rest, handled the way the DPDP Act 2023 expects. Safety alert records are kept for the full session and exportable for board affiliation reviews.

Hardware. No special GPS hardware is needed. Inkwelly's safety alerts run on the same Driver app GPS that powers live tracking. Schools that already own vehicle-mounted GPS trackers can connect those as an additional source.

False alerts. GPS occasionally drifts in dense city signals (multi-storey buildings can scatter the satellite reading). Inkwelly's alert engine smooths short-duration drifts so a single one-second spike does not fire an alert. Sustained anomalies (longer than 8 seconds) fire. The threshold is configurable per school.

Audit readiness. Every safety alert, every geofence creation or edit, every driver acknowledgement is logged with user, timestamp and GPS coordinate. The audit is exportable per route, per driver, per term. Auditors at CBSE affiliation reviews and police inquiries see live data, not screenshots.