School Bus GPS Tracking Checklist: AIS-140, Safety and Procurement

What the AIS-140 mandate means for school buses

The starting point of any school bus GPS tracking checklist is the law. Rule 125H of the Central Motor Vehicles Rules requires public service vehicles to be fitted with a vehicle location tracking (VLT) device and one or more emergency buttons conforming to AIS-140, the standard published by ARAI and notified by MoRTH. As notified, the rule excludes two-wheelers, three-wheelers, e-rickshaws and transport vehicles that do not need a permit. MoRTH made fitment mandatory for new public service vehicles registered from 1 January 2019 and left compliance dates for older vehicles to state and UT governments, which enforce the rule and decide empanelment, backend registration and penalties.

Does it cover school buses?

Buses hired from a transport operator normally run under a permit and fall inside the rule. Institution-owned buses are categorised differently in some states, and several states have extended VLT and panic-button requirements to them through school-bus safety rules. Either way, confirm the current position with your RTO or state transport department before you buy anything.

What "AIS-140 compliant" actually requires

• A type-approved VLT device (ask for the ARAI or other test-agency approval certificate), typically with GPS plus NavIC/IRNSS support.
• Emergency (panic) buttons wired to the device, so a press sends the location and an alert to the configured backend.
• Location data pushed to the state's designated backend as well as to your own school platform.
• Registration of the device against the vehicle on the state portal and, in many states, a fitment certificate for the RTO file.

Read our AIS-140 GPS tracker guide for the device side and the VLT device explainer for how backends and reporting intervals work.

The school bus GPS tracking checklist at a glance

Print this table and tick items off as you go. Each stage has an owner so nothing sits between departments.

The rest of this guide expands each block, so you can turn the table into a tender document or an internal SOP.

Panic buttons, over-speed and driver behaviour monitoring

Panic buttons

• Fit at least one button within reach of the driver and one within reach of the attendant or the passenger area; add more on longer buses.
• Decide who receives the alert: the school transport desk, the principal's office and, where the state backend is live, the emergency response centre as notified by your state.
• Test every button weekly and log the result. A button nobody has pressed for six months is a button you cannot trust.

Over-speed

Set the over-speed threshold on the platform to match the speed governor setting and the bus speed limit that applies in your state (Delhi, for example, sets 40 km/h for buses; other states have their own figures, so check locally). Route the alert to the transport manager in real time and to a daily exception report for management.

Driver behaviour

Modern trackers carry an accelerometer, so harsh braking, harsh acceleration, sharp cornering, long idling and route deviation can be scored per driver. Use the scores for coaching first and discipline second, and review them with drivers monthly. As an example, GPSBULL's AIS-140-4G (model TRP-4G) includes an accelerometer, gyroscope, over-speed alerts and SOS support, and its GBULL CLOUD platform produces driver-behaviour reports. See the panic button device page for wiring and placement options.

Route and geofence setup, plus speed governors

Routes and geofences

1. Map every route with named stops and expected pick-up and drop times.
2. Draw a geofence around the school campus, each stop cluster and any no-go zones such as highways or unsafe roads.
3. Enable alerts for route deviation, unscheduled stops longer than a few minutes, arrival at school after the bell and movement outside operating hours.
4. Assign each bus a route, driver and attendant on the platform so reports are meaningful.

Speed governors

Speed governors are a separate requirement from GPS but belong on the same checklist. State rules and school-bus safety guidelines generally require a tamper-resistant governor on school buses; Delhi Traffic Police, for example, lists speed governors as mandatory for buses and trucks with a 40 km/h limit, but the figure and the paperwork vary by state, so confirm locally. Governors that regulate fuel supply, such as GPSBULL's GBULL-SLD100 (pulse line) and BG-SLD200 (OBD-II), are one option; whichever you fit, ask the installer for a fitment certificate, because the RTO may want to see it at fitness time. Our speed governor page explains the two types, and the school bus GPS tracker page shows how tracker and governor work together.

Staff training and communicating with parents

Train the people, not just the platform

• Transport manager: daily dashboard review, alert triage, monthly reports to management.
• Drivers and attendants: what the panic button does, when to press it, how to report a device fault.
• Front office: how to answer "where is the bus?" by looking it up rather than phoning the driver.
• Everyone: a one-page SOP for panic alerts, breakdowns, route deviation and device-offline events.

Communicating with parents

Share the parent app or live link with clear expectations: bus ETA and stop-arrival notifications, not a live video feed. Explain what data is collected, who can see it and how long it is stored. Publish the transport desk number and the escalation path. A short demo at the start of term usually reduces daily "where is the bus" calls. Platforms built for commercial fleets, such as the one described on our fleet management system page, typically expose open APIs so ETA feeds can be integrated into a school's own parent app.

Tender and procurement: questions to ask vendors

Ask for written answers to these questions in every tender or quotation:

1. Is the device AIS-140 type-approved? Ask for the TAC number and verify it with the test agency. (GPSBULL's TRP-4G, for instance, carries ARAI TAC AS9026.)
2. Is the maker empanelled with, or the device registered on, our state's VLTD backend? Who does the portal registration, and is it included?
3. 4G or 2G? Prefer 4G LTE with an embedded dual-network SIM so connectivity does not depend on one operator over the device's life.
4. Housing and power: IP-rated enclosure, 12/24 V support, and tamper alerts if the unit is unplugged or opened.
5. Panic buttons: how many are included, how they are wired, and how they are tested after installation.
6. Platform: live tracking, history, geofences, alerts, driver behaviour, reports, parent app or API, and who owns the data if we change vendors.
7. Subscription: what the annual charge covers (SIM, platform, support) and what happens on non-renewal.
8. Warranty: length, exclusions, replacement turnaround, and whether a loaner unit is provided.
9. Support: 24/7 device support, remote configuration, spare-part availability, and who to call during a 6 AM route.
10. Track record: devices deployed, years in business, and a reference school of similar size.

Prices vary widely depending on device class, subscription model and volume, so compare total cost over three to five years rather than unit price alone. Manufacturers that design and build in India can usually document certifications and support processes directly rather than through a reseller. See choosing a GPS tracker manufacturer in India and the 4G AIS-140 device page.

RTO paperwork, warranty and 24/7 support

Paperwork to keep on file

• Device invoice, type-approval certificate copy and fitment certificates (VLT device and speed governor).
• Confirmation that the device is registered and mapped to the vehicle on the state VLTD backend (some states use the VAHAN portal for this), where your state requires it.
• Permit, fitness certificate, insurance and PUC; inspectors may check the tracker alongside these.
• Panic-button test log and device-uptime report, useful in school audits and RTO inspections.

Warranty and support

Prefer a warranty that covers device replacement and a support desk that works when your buses do: early mornings, weekends and exam days. GPSBULL, for example, runs 24/7 device support in addition to office hours. Book a review of the whole checklist before every academic year: firmware and configuration updates, SIM and subscription renewals, geofences for new routes and refresher training for new drivers.

Finally, rules and enforcement timelines change. Check the state transport department's website or your RTO once a year and update your checklist. More guides are in our guides library.

Frequently asked questions

Related products & solutions

More guides

Official sources & further reading

• PIB / MoRTH - Vehicle Location Tracking Devices and Emergency Buttons Mandatory for all New Public Service Vehicles Registered After 1st January 2019
• PIB / MoRTH - GPS Tracking System for Vehicles (Rule 125H / AIS-140)
• Delhi Traffic Police - Safety Guidelines (school buses, speed governors)