A vehicle recall is a statutory obligation now, not a PR decision
Recall used to be a voluntary industry practice managed by the communications team. It is now a defined statutory process under the Motor Vehicles Act with its own trigger, timeline and reporting duty — and several manufacturers are still running it as if it were optional.
For most of the Indian automotive industry's history, a recall was a voluntary act — a manufacturer decided a defect warranted a fix, communicated with owners, and managed the process largely on its own terms, with no statutory trigger forcing the decision or the timeline. That changed with the statutory recall provisions under the Motor Vehicles Act and the associated CMVR rules, and the shift has not fully landed inside every manufacturer's compliance function.
What actually changed
The statutory framework does three things a voluntary regime did not:
It defines the trigger objectively. A defect that poses a threat to road safety, the environment, or the driver or occupants creates a recall obligation, assessed against defined criteria rather than left entirely to manufacturer discretion. This matters because it removes the option to characterise a known defect pattern as a "customer advisory" or "goodwill campaign" indefinitely once it meets the statutory threshold.
It creates a reporting duty to the government, not just a duty to notify affected owners. Manufacturers are expected to inform the appropriate authority of defect patterns meeting the threshold, which changes the internal escalation calculus — this is no longer purely a decision the manufacturer's own legal and communications functions control end to end.
It attaches consequences for non-compliance, including the possibility of the authority directing a recall where a manufacturer has not initiated one voluntarily despite evidence meeting the threshold.
Why this still gets treated as a communications decision internally
In most manufacturers we have worked with, the process for deciding whether a defect pattern warrants a recall still sits primarily with product quality and customer service functions, with legal and regulatory affairs consulted rather than owning the trigger assessment. That made sense under a voluntary regime. Under a statutory one, the trigger assessment is a compliance determination with a defined legal standard, not a business judgement about brand risk versus fix cost.
The practical risk this creates: a defect pattern gets tracked as a warranty and quality issue, discussed in terms of unit cost and customer sentiment, and the statutory threshold question — does this now meet the definition requiring recall and reporting — is never explicitly asked by someone accountable for answering it against the legal standard rather than the commercial one.
What a statutory-grade recall process requires
A defined, evidenced threshold assessment, run by someone accountable to the legal standard, triggered automatically once a defect pattern crosses defined severity or frequency criteria in warranty or field data — not discretionarily elevated by whoever happens to notice.
Documented reasoning for every "not yet a recall" decision. If a pattern is assessed and determined not to meet the threshold, that determination and its basis should be recorded contemporaneously. Retrospective reconstruction of "why we decided not to recall in March" during a later investigation is a weak position to be in.
A reporting workflow to the authority, separate from and in addition to the owner communication workflow. These are two different obligations with two different audiences and, in some cases, different timing considerations. Treating them as one combined process risks the authority notification being an afterthought to the more visible owner communication campaign.
Supplier-level defect tracking that rolls up to the same threshold assessment. A defect originating in a bought-out component still creates the OEM's recall obligation. Component-level quality data needs to feed the same threshold process as vehicle-level data, not sit in a separate supplier quality system that the recall assessment never queries.
The read-across for component suppliers
Tier-one and tier-two suppliers are not directly subject to the OEM's recall obligation, but they are very much inside its evidentiary chain. An OEM investigating whether a defect pattern meets the statutory threshold needs supplier field-failure data promptly and in a usable form. Suppliers who cannot produce that quickly — because their own quality data is not organised for it — become the bottleneck in an OEM's statutory timeline, and increasingly, that bottleneck shows up in supplier scorecards and contract terms.
The shift in one sentence
Recall has moved from a discretionary brand-management decision to a compliance obligation with an objective trigger, a government reporting duty, and a paper trail that needs to exist before, not after, a regulator asks for it. Manufacturers still running the assessment as a quality-and-communications judgement call are one significant defect pattern away from discovering the difference the hard way.
Written by Rohit Menon, Principal Regulatory Analyst
Part of the team that builds and maintains the Regulens obligation library and platform. If you disagree with something here, we would genuinely like to hear it — get in touch.