Pesticide Drift Complaint Systems Need Exposure-Resolution Accountability, Not Intake Counts Alone
Pesticide drift complaint systems are often summarized by complaint intake, calls, or incident reports, but those counts do not show whether exposure was medically triaged, investigated, classified, enforced, repaired, or prevented from recurring. This conceptual synthesis combines EPA drift guidance and incident-reporting routes, NPIC public-health reporting guidance, EPA spray-drift models and labeling notices, SENSOR-based peer-reviewed drift illness evidence, California and Washington pesticide illness surveillance, and EPA dicamba incident reporting. It contributes an exposure-resolution accountability chain that separates report intake, health triage, site evidence, exposure classification, regulatory finding, corrective action, surveillance coding, and recurrence prevention. The conclusion is that pesticide drift systems should publish complaint intake as an early signal and reserve resolution language for evidence that exposure, health, regulatory, and prevention stages were closed.
Introduction
Pesticide drift is not only a nuisance metric. EPA defines drift as movement of pesticide dust or droplets through the air away from the target site, and NPIC guidance treats drift as a route that can affect people, crops, animals, and property [[cite:epaDriftIntro,npicDrift]].
A complaint count is therefore an alert signal, not a resolution measure. Reporting guidance sends affected people through poison centers, medical care, state regulators, and EPA incident routes, while surveillance studies show that reported cases are only part of the underlying exposure landscape [[cite:epaIncidents,npicIncident,lee2011]].
Method
The study mode is conceptual synthesis. Six AlexandrAI graph searches found no direct prior drift-complaint accountability item. External research prioritized EPA, NPIC, state surveillance, Federal Register, and peer-reviewed SENSOR evidence.
Each source was coded by complaint-system stage: drift prevention, public intake, health triage, evidence collection, exposure classification, regulatory finding, corrective action, surveillance coding, and recurrence prevention. The synthesis applies a weakest-stage rule to prevent intake counts from being described as resolved exposure risk.
Results
The first result is that drift systems must route three different needs: immediate health advice, regulatory investigation, and public surveillance. EPA and NPIC reporting routes recognize that these are not the same record, while California and Washington surveillance materials show the need for case review and classification [[cite:epaIncidents,npicIncident,cdprIllness,cdphReport,waDoh]].
The second result is that prevention evidence and incident evidence should not be collapsed. EPA drift guidance, AgDRIFT modeling, and spray-drift label work can reduce expected off-target movement, but incident reports and dicamba experience show that field complaints can remain incomplete, contested, or underreported [[cite:epaReduceDrift,epaAgdrift,fedregSprayDrift,epaDicamba]].
Discussion
An exposure-resolution chain does not require public release of private medical or farm records. It requires public stage labels: intake received, health triaged, site evidence collected, exposure classified, regulatory decision made, corrective action issued, recurrence check complete.
The chain also resolves a common conflict. Regulators may hesitate to overstate unconfirmed complaints, while affected residents may see complaint intake as proof of exposure. A staged ledger allows both views to be represented without pretending that intake, confirmation, and resolution are one event.
Limitations
This synthesis does not adjudicate any pesticide product, application event, or state enforcement action.
Complaint systems differ by jurisdiction; the model should be mapped to local statutes, reporting obligations, and privacy rules before implementation.
Conclusion
Pesticide drift complaint systems need exposure-resolution accountability, not intake counts alone. Public reporting should show where each case stands in the health, evidence, regulatory, and prevention chain.
The most useful dashboard would publish aggregate stage counts, time to triage, time to classification, evidence completeness, enforcement or corrective-action status, and recurrence signals without exposing protected health or farm details [[cite:cdprIllness,waDoh,epaDicamba]].