Chandigarh Suspends Uber and Rapido Over Driver Insurance: State Aggregator Rules Now Decide Your Platform's Cover

On 9 September 2026, The Tribune reported that the Chandigarh Administration had suspended the aggregator licences of Uber India Systems and Rapido (Roppen Transportation Services) for six months. The order was passed under Rule 17 of the Chandigarh Administration Motor Vehicles Aggregators Rules, 2025, and the grounds cited were failure to comply with the Rules on driver health insurance and term insurance, driver training, and notified fares.

The two suspensions complete a sequence. Ola was suspended in June 2026 and InDrive in August 2026, so with Uber and Rapido off the road until around March 2027, all four of the major ride-hailing apps are out of the Union Territory. The Tribune reported that Bharat Taxi is the only platform still operating.

Insurance is not the only ground in the order, but it is the one that should worry platforms outside Chandigarh. Fares and training are operational fixes a platform can usually make quickly. A driver insurance stack that does not match a state's text takes a placement cycle to fix, needs underwriter appetite, and has to be evidenced on paper before a transport authority will accept it. A licence can now be lost on that ground.

The suspension is a licensing action against the platform entity, not a claim dispute. No accident had to happen and no insurer had to decline anything. The gap between the cover bought and the cover a state rule describes was enough.

The most useful detail in The Tribune's report is how Rapido's programme was assessed. Insurance for its bike-taxi captains was limited to accidental death and injury. The Chandigarh Rules require driver health and term insurance, and an accident-only programme does not answer either requirement.

That distinction matters because accident-only cover is the default shape of most gig programmes in India. A group personal accident policy pays on death, permanent disablement and sometimes accident medical expenses, but only when an accident is the cause. It does not pay for a hospitalisation caused by illness, and it does not pay a death benefit when a driver dies of a heart attack or an infection. Health insurance and term life exist precisely to cover those events. A regulator that names health and term cover is asking for protection against the ordinary health risks of a working population, not just road risk.

Rapido also sought to rely on the Centre's Motor Vehicle Aggregator Guidelines 2025 (MVAG 2025) instead of the UT's own Rules. Chandigarh did not accept that position. Whatever the comparison between the two texts on a given requirement, the administration treated its own notified Rules as the binding standard for a licence it issues. For a platform, the practical reading is simple: central guidelines are a reference point, and the state or UT that issues the licence sets the floor it will enforce.

This corpus has tracked state aggregator regimes as they diverge. The Uttar Pradesh rules attach conditions to a platform-held operating licence. Tamil Nadu's doubling of gig accident cover added a state benefit that platforms must coordinate with their own group personal accident programme. Maharashtra's draft delivery rules would turn insurance into a transport permit condition.

Chandigarh adds something none of those posts could show: enforcement. It is the first case in this series where a regulator has taken a licence away from the largest platforms, with insurance named in the grounds. Three consequences follow for programme design.

1. The binding text is the licensing authority's own rules. A programme designed to satisfy MVAG 2025 alone may be short in any state whose rules ask for more or ask differently.
2. Cover type matters, not just cover amount. Rapido's licence was not suspended over a low sum insured. It was suspended, in part, because the type of cover was wrong.
3. The test is applied per licensed entity, per jurisdiction. A national programme that is adequate in one state can be inadequate in a neighbouring jurisdiction.

The effect is that a platform's insurance programme is now a licensing asset. Its design should start from the strictest text among the jurisdictions where the platform holds or seeks a licence, not from the central guidelines.

Read across the Chandigarh grounds and the Bharat Taxi benchmark, a driver programme that would withstand a state review has three core layers, plus the motor and liability covers the platform already carries.

Driver health cover

A group health insurance policy for active drivers, written on a hospitalisation basis for illness and injury alike. The design questions are who counts as an active driver, whether the family is included, and how cover starts and stops as drivers join, go idle and leave. Bharat Taxi's package, reported by Dynamite News, includes Rs 5 lakh of family health cover, which signals that at least one operator in the market treats family health cover as standard.

Term life and personal accident

A group term life policy pays a death benefit whatever the cause. A group personal accident policy pays on accidental death and disablement, including permanent partial disablement, which drives frequency in a two-wheeler fleet. Bharat Taxi's reported package pairs its health cover with Rs 5 lakh of personal accident, for a total of Rs 10 lakh. Rapido's experience shows that personal accident on its own does not satisfy a rule that names term insurance. The two covers do different jobs and both belong in the stack.

Around those layers sit the supporting covers:

• Motor third-party cover on every vehicle on the platform, verified at onboarding and at each renewal, since the statutory cover attaches to the vehicle rather than to the platform.
• Public and platform liability for claims made against the aggregator itself.
• A scheme-basis attachment so that driver churn does not create unnamed, uncovered drivers between monthly declarations.

None of these covers is new to the Indian market. What is new is that a state can test the shape of the whole stack, and pull the licence if a layer is missing.

The public reporting on the Chandigarh order does not give the sums insured the UT Rules prescribe, and this post does not guess them. The practical approach is to get the notified text, extract every insurance requirement into a schedule, and build the programme to that schedule line by line.

A workable extraction lists, for each requirement:

1. The rule number and the exact wording, including whether the requirement is for health, term, accident or a combination.
2. Who must be covered: drivers only, drivers and family, or a defined class of active drivers.
3. Any minimum sum insured, waiting period limit or exclusion restriction.
4. Who must hold the policy: the licensed aggregator, the fleet operator, or the driver.
5. What evidence the authority expects, and when.

Where the text is silent on an amount, the Bharat Taxi package gives a market reference point of Rs 10 lakh per driver, split between personal accident and family health cover. It is a reference, not a legal minimum. Platforms should also expect a regulator to compare their stack with what a competitor operating in the same territory offers, and a Rs 10 lakh benchmark sitting next to an accident-only programme is not a comparison a platform wants to defend.

Buying the right cover is half the job. A licence review is decided on documents, and many platforms cannot produce the right ones quickly. Build an evidence pack per licensed entity and per jurisdiction, and keep it current.

• Policy schedules and wordings for each layer, showing the licensed aggregator entity as the policyholder or named insured, and the insured class defined in terms that match the rule.
• A certificate of insurance per layer, issued by the insurer and naming the jurisdiction, the policy period and the insured class. Group-level certificates in a parent company's name do not prove cover for a subsidiary that holds the licence.
• A rule-to-policy map that lists each insurance requirement in the state or UT rules and cites the policy section that answers it. This is the document a reviewing officer actually reads.
• Monthly enrolment data showing that every active driver in the jurisdiction was within the insured class for the month, reconciled against the platform's driver roster.
• Claims and grievance data, where the rules or the authority ask for it, showing that claims are being intimated and paid.

When the authority issues a notice, the response should go back with this pack attached, not with a statement that cover is in place. And where a platform disagrees with a state's reading of its rules, as Rapido did in relying on MVAG 2025, the safer course is to bring the programme up to the state's reading while the argument is pursued. The cost of an additional health and term layer for a policy year is small next to six months off the road.

The Chandigarh order was made against ride-hailing platforms, but the lesson travels to any business whose licence comes from a state transport authority. Bike taxis, last-mile delivery, quick commerce and intercity logistics aggregators are all inside or moving into state licensing regimes, as the Uttar Pradesh and Maharashtra developments show.

A short action list for the next renewal or the next licence application:

1. Pull every notified aggregator rule in the states and UTs where the platform operates or plans to operate, and extract the insurance requirements into one table.
2. Gap-test the current programme against the strictest text, by cover type first and amount second. Accident-only programmes should be the first item reviewed.
3. Add group health and group term layers where they are missing, structured by jurisdiction so the cover can be evidenced state by state.
4. Align named insureds with licensed entities, so each licence holder can produce its own schedules and certificates.
5. Assign ownership. Someone in compliance, not only in HR or partner operations, should own the rule-to-policy map and refresh it whenever a state amends its rules.