The File on Your Desk Carries Someone Else's EMI

When Compliance Itself Becomes the Injury Picture the

file: a small truck operator, one vehicle, a loan he is still repaying, weeks off the road because his VLTD failed to sync with the VAHAN portal - not because he broke a rule, but because the portal broke on him. The officer reviewing his fitness certificate has two paths and neither is free.

The Actual Dilemma, Not a Simulated One

Path one: enforce VLTD and BS-VI compliance to the letter. This protects real public goods - road safety through vehicle tracking, air quality through emissions standards - and treats every operator equally under the law, which is itself a form of fairness.

But over 80% of India's trucking fleet is owned by operators running one to five vehicles, with no capital buffer. For them, strict enforcement during a portal outage they did not cause does not enforce compliance - it enforces bankruptcy.

Path two: relax enforcement for operators caught in technical failures beyond their control. This protects livelihoods and freight continuity for an industry carrying 70% of the country's goods. But it also risks becoming a permanent loophole, undermining the very safety and environmental standards VLTD and BS-VI were built to secure and treating similarly situated operators unequally depending on which official happens to review their file.

Why Neither Extreme Survives Contact With the Facts

The temptation is to resolve this as "rules versus compassion"

• but that framing hides the real distinction. Not every compliance failure is the same kind of failure. An operator who never installed a VLTD is not in the same ethical position as one who installed it correctly and was stranded by a VAHAN server outage the government itself has acknowledged. Treating both as identical failures to comply is not neutrality; it is a refusal to look closely enough to see the actual difference between negligence and misfortune.

The Resolution That Actually Resolves Something

The honest answer is not "enforce strictly" or "relax broadly"

• it is a phased, means-tested distinction built into how compliance itself is judged. Where a technical failure is demonstrably the system's fault - a portal outage, an integration glitch - the burden of proof and the cost of delay should shift to the government, not the operator: automatic compliance grace periods, not case-by-case discretion an operator has to beg for. Where genuine non-compliance exists, enforcement should proceed, but calibrated to fleet size - a single-truck operator facing a first violation is not the same enforcement priority as a large fleet ignoring the rules repeatedly. This costs something real: it is administratively harder than a blanket rule in either direction and it will occasionally let a genuine bad actor slip through misclassified as a technical victim. That cost is worth paying, because the alternative - a single enforcement standard blind to whether the failure was the operator's or the state's - quietly punishes the most vulnerable operators for infrastructure failures they had no power to prevent, which is not enforcement of the law. It is abdication of the state's own responsibility, relabeled as someone else's fault.