AIS-140 covers a wide range of vehicle types, but the mandate does not sit the same way on all of them. A school bus, a goods truck, and an app-based cab all need a certified device, yet who monitors that data, what extra rules stack on top of it, and how hard enforcement bites varies by category. This guide breaks the mandate down by vehicle type rather than treating it as one flat rule.
KEY TAKEAWAYS
- The core AIS-140 device requirement stays the same across categories, but several vehicle types carry extra rules on top of the base standard.
- School buses face the strictest additional requirements of any category, driven by Supreme Court directives and MoRTH’s School Bus Policy rather than AIS-140 itself.
- Two-wheelers, three-wheelers, and e-rickshaws are exempt under the central rule, though a few states have issued their own notifications covering commercial three-wheelers.
- Taxi aggregators carry platform-level risk for non-compliant vehicles in their network, on top of whatever the individual vehicle owner faces.
- A private vehicle sits outside AIS-140 entirely until it starts running under a transport permit, at which point the mandate applies in full.
- Goods carriers see enforcement concentrate at interstate checkposts more than at any other single point, since these vehicles cross state lines far more often than local buses or cabs.
In this guide, we cover how AIS-140 applies to buses, school transport, taxis, goods carriers, employee transport, and ambulances, which categories are exempt, and what to check before choosing a device for a specific vehicle type.
AIS-140 compliance by vehicle category
| Category | Core device requirement | What sits on top |
| Buses | Yes | Fitness renewal and route permit are tied closely to device status |
| School Buses | Yes | Attendant-accessible panic button, parent and school access, School Bus Policy rules |
| Taxis and cabs | Yes | Aggregator-level consequences for non-compliant vehicles |
| Good carries | Yes | Heavier scrutiny at interstate checkposts |
| Employee transport | Yes | Same enforcement as public transport despite private passengers |
| Ambulances | Yes | No extra layer beyond the base requirement |
| Two/three-wheelers, e-rickshaws | Exempt centrally | A few states extend rules to commercial three-wheelers |
| Private vehicles | Exempt | Applies fully once operated under a transport permit |
Why category matters when you’re planning a rollout
A fleet owner buying one AIS-140 device for every vehicle on the roster usually assumes the installation is identical across the board. It isn’t. The hardware and the certification process stay constant, but what happens after installation, who gets access to the data, what documentation an auditor asks for, where enforcement actually shows up, changes from one category to the next. A logistics company running trucks across three states has a different risk profile than a school running four buses inside one city, even though both bought the same class of certified device.
Getting this wrong shows up later rather than at the time of purchase. A school transport operator who installs a standard device without checking the attendant-access requirement finds the gap during an audit, not during installation. A fleet that assumes its three-wheelers are exempt everywhere finds out otherwise the day a state notification changes that.
Buses
Stage carriages, contract carriages, and both intercity and intracity buses, public and private, fall under AIS-140 without exception. This is also the category the Supreme Court singled out in May 2026, when it noted that fewer than one percent of public service vehicles nationwide had the mandated tracking device installed, and directed states to withhold fitness certificates until installation shows up on Vahan. A bus operator who lets a device go offline for even a few weeks risks that same renewal block.
School buses and institutional transport
School transport carries the heaviest set of add-on requirements in the entire AIS-140 framework, and none of that extra weight comes from AIS-140 itself. It comes from Supreme Court directives on student safety and from MoRTH’s School Bus Policy, both of which layer additional obligations on top of the base standard.
In practice, this usually means the panic button has to be reachable by the bus attendant as well as the driver, not just the driver alone. Real-time tracking access typically needs to reach school management, and in a number of state implementations, parents get access too. A school that treats this as a standard install, without building in attendant and parent-facing access, tends to find the gap during an audit rather than before one.
Non-compliance here carries a specific consequence: the school bus permit can be suspended on its own, and education authorities can separately act against the school running the vehicle.
Taxis and app-based cabs
Taxis, rental cars, and corporate cab fleets operating under a transport permit fall under AIS-140, including vehicles running through ride-hailing platforms. The category-specific risk here sits as much with the aggregator as with the individual owner. A state transport authority can issue a show-cause notice to an aggregator or restrict a non-compliant vehicle at the platform level, separate from any fine or permit action taken against the vehicle itself.
For an aggregator running thousands of vehicles, this turns a handful of non-compliant cars into platform-wide scrutiny rather than an isolated problem confined to a few owners.
Good carriers and logistics vehicles
Trucks and logistics vehicles carry the same core requirement as every other category, but enforcement risk concentrates differently. Goods vehicles cross state lines far more often than a local bus or cab does, so interstate checkposts and highway patrol stops end up being where non-compliance actually surfaces, often triggering the same permit suspension and fine structure that applies to any other flagged vehicle. A truck that stayed compliant in its home state can face real scrutiny the moment it crosses into a state running tighter roadside enforcement.
Employee transport
Corporate and institutional employee transport, office cabs, and shuttle services fall under the same mandate as taxis and buses. Fleet operators running their own employee transport sometimes assume this category draws lighter scrutiny than public-facing transport, which is not a safe assumption. Fitness certificate and permit checks apply the same way here, regardless of who is riding.
Ambulances and emergency vehicles
Ambulances and emergency response vehicles fall under AIS-140 given their public service role. The reasoning mirrors buses and taxis: real-time location and a working emergency alert path matter as much for the ambulance’s own safety monitoring as they do for the patient inside it.
Two-wheelers, three-wheelers, and e-rickshaws
Rule 125H of the Central Motor Vehicles Rules, 1989 exempts two-wheelers, three-wheelers, and e-rickshaws from the device requirement under the central rule. This is one of the more commonly misread points in the mandate, since some fleet operators assume every commercial vehicle needs a device without exception.
That exemption is not absolute in every state. A few states have issued their own notifications extending the device requirement to commercial three-wheelers, so an operator running an auto-rickshaw fleet should confirm the current position with their State Transport Authority rather than assuming the central exemption holds unchanged everywhere.
Private, non-commercial vehicles
A car registered and used for personal purposes, with no transport permit attached, sits outside AIS-140 entirely. The moment that same vehicle starts operating under a transport permit, as a taxi, a delivery vehicle, or any hire-and-reward use, the mandate applies in full. This distinction matters most for owner-operators who shift a vehicle between personal and commercial use, since the obligation follows the permit rather than the vehicle’s original registration category.
What this means for choosing a device and a platform
A device that clears central certification will pass regardless of vehicle category. What differs is the operational layer sitting on top of it. A school bus operator needs a system built to extend visibility to an attendant, school management, and possibly parents. A logistics fleet crossing state lines cares more about consistent recognition at interstate checkposts than about parent-facing access. Buying a device without accounting for these category-specific needs tends to surface as a gap only once the vehicle is already on the road.
This is also where fleets running mixed categories, a few buses alongside a goods segment, run into the most friction. Two categories, two sets of extra obligations, and a device or platform that was only built to handle one of them.
The gap that shows up after installation
A certified device answers one question well: is this vehicle where it says it is, and can it call for help? It has nothing to say about whether a school’s attendant can actually see the panic button status, whether a goods fleet’s interstate paperwork will hold up at a checkpost in a neighbouring state, or whether an aggregator’s non-compliant vehicles are quietly building up platform-level risk. Those gaps sit outside the device itself, and they are exactly where category-specific obligations get missed, the same way a mechanical fault gets missed without predictive health monitoring watching for it.
How Intangles supports fleets across vehicle categories
Intangles is a digital twin company serving the transportation and logistics industry across 18 countries, with more than 500,000 vehicles running on its platform. Its AIS-140 (IRNSS) certified device, InGenious, connects through the vehicle’s OBD port and streams data into InRoute, the same platform behind fuel monitoring, driving behaviour monitoring, and vehicle health tracking. It works across 30-plus OEM brands, including Volvo, Kenworth, Peterbilt, Freightliner, Mack, International, Western Star, Scania, and Mercedes-Benz.
Because the underlying platform sits behind the same certified device regardless of category, a fleet running buses alongside goods vehicles does not need two separate systems to handle two separate sets of obligations. A school transport operator extending tracking access to school management and a logistics fleet monitoring vehicles across state lines both run on the same base install, configured differently around the common fleet management challenges each category actually runs into.
| Capability | What it does |
| Compliance | AIS-140 (IRNSS) certified, State RTO approved, registers directly to Vahan |
| Multi-stakeholder access | Extends tracking visibility to attendants, school management, or dispatchers, depending on the category |
| Predictive health | Flag mechanical faults before they turn into a roadside breakdown |
| Fleet reporting | Turns the same certified feed into route, idle time, and utilisation data through operations automation |
Explore the platform or get in touch with our team to learn how Intangles’ predictive health monitoring adapts a single certified device to the compliance needs of every vehicle category in a mixed fleet.
KNOW MORE
Frequently Asked Questions
Do all commercial vehicles need the same AIS-140 device?
The core technical requirement is identical, but several categories, such as school buses and taxi aggregator fleets, especially carry extra operational or reporting obligations on top of the base standard.
Are two-wheelers or auto-rickshaws exempt from AIS-140?
Under the central rule, yes. Rule 125H exempts two-wheelers, three-wheelers, and e-rickshaws. A few states have issued their own notifications covering commercial three-wheelers, so it’s worth checking locally rather than assuming a blanket exemption.
What extra requirements apply specifically to school buses?
Beyond the standard device rules, school buses typically need the panic button reachable by both the driver and an attendant, with real-time tracking access extended to school management and, in many states, to parents as well.
Does a private car need an AIS-140 device?
No, not while it stays registered and used for personal, non-commercial purposes. The requirement applies the moment the vehicle starts operating under a transport permit.
Are taxi aggregators penalised differently from individual vehicle owners?
Yes. Beyond the usual fitness certificate and permit consequences for the vehicle itself, state transport authorities can issue show-cause notices or platform-level restrictions to the aggregator over non-compliant vehicles in its network.
We’re looking forward to meeting you