Over 70 countries banned paraquat years ago. India's Union ban notification landed this week. The gap between those two dates isn't a coincidence of timing - it's how the system is actually built to work.

THE TARGET WAS PRE-EMPTIVE SAFETY. THE DATA SHOWS REACTIVE CONFIRMATION. The Insecticides Act, 1968 sets up a Registration Committee whose job, on paper, is to scrutinise an insecticide's formula and safety claims before it enters India's market - a pre-emptive hazard check.

That's the commitment. Look at what actually happened with paraquat: it stayed registered and in use for decades after other countries began banning it, through mounting self-harm and accidental death tolls, through three separate state governments independently deciding the national process wasn't moving fast enough and only now, in 2026, does the central ban arrive.

The target was pre-emptive assessment. The data shows the system moved only after harm had already accumulated at scale and states had already acted unilaterally. WHERE EXACTLY THE CHAIN BROKE It's tempting to call this "regulatory delay" and move on, but that phrase hides where the actual bottleneck sits.

The Registration Committee's process is built around efficacy and safety review at the point of initial registration - not automatic re-review triggered by accumulating real-world harm data. Once a chemical is registered, there's no statutory mechanism forcing periodic reassessment against new toxicological or mortality evidence; a ban requires a fresh recommendation process, effectively restarting bureaucratic scrutiny that the original registration should have front-loaded.

That's the specific gap: India's framework is strong on pre-market registration, weak on post-market monitoring that could catch a chemical like paraquat once real-world data - 70+ countries' worth of it - started accumulating against it.

State governments filled that gap the only way they could: acting on their own jurisdiction over agriculture to impose local bans, effectively doing the post-market hazard reassessment the central framework wasn't structured to do automatically.

Kerala, Telangana and Andhra Pradesh's bans weren't just precursors to the central decision - they were evidence that the accountability for catching this harm had shifted downward to states, because the central mechanism had no automatic trigger to catch it itself.

WHAT ACTUALLY MOVED THE CENTRE Credit where it's due: the ban did eventually happen and medical advocacy - specifically groups like Doctors Against Paraquat presenting clinical mortality data directly to the Expert Committee - appears to have been the actual mechanism that broke the logjam, not any automatic regulatory trigger.

That's worth naming precisely, because it tells you what actually works in this system: sustained, evidence-based, external pressure on the Registration Committee's discretionary review process, not the process reviewing itself.

For the exam, the sharper diagnosis isn't "India banned a dangerous chemical" - it's recognising that the Insecticides Act, 1968's architecture has no built-in post-market surveillance trigger, which means every future hazardous agrochemical will likely follow this same path: registration, accumulating harm, state-level bans, advocacy pressure and only then a central ban - unless the framework itself is amended to include periodic mandatory reassessment.