Getting an AIS-140 certified device installed is the easy part. Keeping a fleet compliant month after month, across renewals, driver changes, and device faults, is where most of the actual work sits. This guide is built around the recurring monitoring cadence a fleet manager runs after installation, not a one-time checklist to work through once and file away.
KEY TAKEAWAYS
- Compliance isn’t a one-time install. Devices go offline, batteries degrade, and states update their whitelists, so ongoing checks matter as much as the initial setup.
- A device compliant at installation isn’t guaranteed to still be compliant eleven months later without someone checking in between, which is why this has to run on a calendar, not a one-time install log.
- A working checklist splits into daily, weekly, monthly, and renewal-cycle tasks, not one long list checked once a year.
- Documentation matters as much as the hardware. Auditors and RTOs ask for records, not just a working device.
- Most renewal delays trace back to small, unnoticed gaps rather than the device failing outright.
- Fleets running this as a routine, rather than a reaction to a failed renewal, spend far less time firefighting compliance issues.
In this guide, we cover the daily, weekly, and monthly checks that keep a fleet compliant, what to do in the run-up to renewal, the documentation RTOs actually ask for, and the gaps that most often cause delays.
The compliance check cycle at a glance
| Frequency | What to check |
| Daily | Active transmission status, overnight tamper or disconnection alerts, panic button test signals |
| Weekly | Device uptime and signal gaps, battery backup patterns, and new vehicles against install status |
| Monthly | Vehicle registry against Vahan, firmware versions, panic button incident logs |
| Before renewal | Device status recheck, state whitelist confirmation, certificate, and installation paperwork on file |
Why ongoing checks matter more than the initial install
A device that passed installation cleanly six months ago isn’t guaranteed to be compliant today. Batteries degrade. Wiring faults develop slowly and often keep a device transmitting right up until backup power finally runs out. States revise their whitelists, and a model that was approved when it went in can drop off that list without anyone at the fleet noticing.
Fitness certificate renewal in most states checks live device status against Vahan at the point of renewal, not at the point of installation. A gap that opened up in month three and went unnoticed shows up as a blocked renewal in month eleven, with no warning in between.
Daily checks
Confirm every vehicle scheduled to run that day shows an active, transmitting device status on the dashboard or the Vahan-linked backend. Check for tamper or disconnection alerts logged overnight and flag them for maintenance before the vehicle leaves the yard. Where the process includes a daily panic button test, verify the signal is reaching both the government server and the fleet’s own system, not just one of them.
Weekly checks
Pull a device uptime report across the fleet and flag any vehicle with recurring signal gaps, not just outright outages. Review battery backup alerts: a device that keeps switching to backup power during normal operation usually points to a wiring or main power issue, not a battery fault on its own. Cross-check any vehicles added to the fleet that week against device installation status. New vehicles are the most common gap in an otherwise compliant fleet.
Monthly checks
Audit the full vehicle registry against device status in Vahan, not just the internal dashboard. The two can drift apart if a sync issue goes unnoticed for a few weeks. Confirm firmware versions across the fleet and check whether the vendor has issued an update tied to a certification refresh. Review incident logs where the panic button was triggered, confirm each was closed out correctly on the government side, and keep a record for internal audit.
In the run-up to fitness certificate renewal
Start the device status check four to six weeks before renewal is due, not the week of it. A Vahan sync issue can take longer to resolve than expected, and four to six weeks gives enough room to fix it before the renewal date. Confirm the specific device model is still on the state’s current whitelist, since states update these lists, and a model approved at installation can drop off later. Keep the original Type Approval Certificate number and installation documentation on file. RTOs sometimes ask for this directly rather than accepting a vendor’s compliance letter alone.
Documentation to keep on hand
| Document | Why it’s asked for |
| Type Approval Certificate number | Proves the device passed ARAI or ICAT testing, needed if a state or auditor questions compliance |
| Installation date and vendor record | Establishes when the vehicle became compliant and who’s responsible for the install |
| State whitelisting confirmation | Shows the device is approved for that specific state, separate from central certification |
| Device fault and downtime log | Shows the fleet is actively monitoring compliance, not just installing and forgetting |
| Panic button incident log | Required in many states as part of emergency response record-keeping |
Common gaps that cause renewal delays
Most compliance problems fleet managers run into aren’t about the device failing outright. They’re about small gaps that go unnoticed until renewal.
A vehicle added mid-year without a device installed on day one is the most frequent gap. A device quietly running on battery backup for weeks because of a wiring fault is another, since it often keeps transmitting data right up until the battery finally dies, giving no obvious warning sign in the meantime. A device that was compliant at installation but has since dropped off a state’s updated whitelist can block renewal even though nothing about the vehicle or the device itself has changed.
Catching these during monthly checks, rather than at renewal, is the difference between a routine renewal and a delayed one. The cost of missing them isn’t just the delay itself. A blocked renewal takes a vehicle off the road until it clears, and a fleet running several vehicles through the same gap at once turns a paperwork issue into a capacity problem.
Where this checklist breaks down at scale
A single vehicle, this checklist is a five-minute daily habit. Across a fleet of fifty or a hundred, it turns into someone manually checking a dashboard, cross-referencing a spreadsheet against Vahan, and chasing down which vehicle’s battery alert from Tuesday never got followed up on. That manual load is only growing. India’s express logistics and courier industry was valued at close to $9 billion in FY25 and is projected to reach $18-22 billion by FY30, which means the fleets running this checklist today are, on average, going to be larger next year, not smaller. That’s usually where the gaps described above actually happen, not because nobody’s watching, but because nobody can watch fifty vehicles’ worth of alerts by hand every day and catch every one before it compounds.
How Intangles supports ongoing AIS-140 compliance
Running this checklist manually across a large fleet, spreadsheet by spreadsheet, is where most of the delays creep in. Intangles is a digital twin company serving the transportation and logistics industry across 18 countries, with more than 500,000 vehicles on its platform, and connects AIS-140 certified device data into a single dashboard, so device downtime, tamper alerts, and panic button events show up as they happen instead of surfacing during a manual audit weeks later.
The edge here is the same one that runs through the rest of the platform: the checks in this guide aren’t a separate workflow bolted onto compliance software. They’re the same predictive maintenance layer a fleet is already running for maintenance and route visibility, catching a wiring fault behind a battery backup alert the same way it catches an engine fault before it strands a vehicle on a route.
| What Intangles flags | Why it matters for compliance |
| Device downtime or signal gaps | Catches the kind of issue that would otherwise only show up at renewal |
| Battery backup usage patterns | Surfaces wiring faults before the backup battery itself fails |
| Panic button and emergency events | Keeps a running log for internal audit and state reporting |
| Vehicle registry drift | Flags new vehicles missing a device before they run a route uncovered |
Explore the platform or get in touch with our team to learn how Intangles’ fleet monitoring turns daily AIS-140 checks into an automated part of the dashboard instead of a manual routine.
KNOW MORE
Frequently Asked Questions
How often should I check the AIS-140 device status?
Daily for active transmission and alerts, weekly for uptime and battery patterns across the fleet, and monthly for a full registry audit against Vahan. Waiting until renewal to check is the most common reason renewals get delayed.
What documentation do RTOs actually ask for?
Most commonly, the Type Approval Certificate number, installation records, and proof that the device is on the state’s current whitelist. Some states also ask for panic button incident logs during audits.
Why would a compliant device suddenly cause a renewal delay?
The device itself may not have changed. A common cause is the specific model dropping off a state’s updated whitelist, or a Vahan sync issue that has nothing to do with the device’s physical condition.
Does a new vehicle need a device installed immediately?
Yes. A vehicle added to a fleet without a device from day one is one of the most common compliance gaps, since it can sit unnoticed until someone tries to renew its fitness certificate.
Can fleet software help with AIS-140 compliance tracking?
Yes. Platforms that pull AIS-140 device data into a single dashboard can flag downtime, battery issues, and incident events as they happen, rather than leaving a fleet manager to discover them during a manual audit.
We’re looking forward to meeting you