.jpg)
In March 2025, the EPA formally issued its bilingual pesticide labeling policy under the Pesticide Registration Improvement Act of 2022, known as PRIA 5. The law requires Spanish translations for key sections of end-use pesticide product labels on a rolling schedule that began in December 2025 and extends through 2030.
Translations must appear either directly on the product container or through a hyperlink or scannable QR code that gives users immediate access. EPA is providing step-by-step instructions to help companies report compliance through its MyPeST platform, a web-based system that replaces the Pesticide Submission Portal and gives registrants a transparent dashboard for tracking application statuses and managing bilingual labeling compliance.
Here is where most operators stop reading and where the actual operational risk begins. Spanish is the primary language for most American farmworkers, this effort advances environmental justice by making health and safety information on pesticide labels more accessible, fostering better understanding and compliance with label instructions.
That's the regulatory intent. But for pest control operators managing commercial accounts, the practical implication is different: your technicians are applying products in the field and logging application data, product name, EPA registration number, concentration, target pest, method of application. That documentation is what ties your service record to the label version in effect at the time of application.
If the product label has been updated under PRIA 5 and your field documentation doesn't reflect the current label version consistently, you have a compliance gap. Not on paper, in your service records.
And in an audit whether that's an AIB, SQF or BRC third-party audit for a food processing client, or a Vigilance Sanitaria inspection for a healthcare facility, that gap is exactly what auditors look for.
The next implementation deadline of December 29, 2026, which applies to EPA-registered antimicrobial and non-agricultural products with a DANGER signal word, is quickly approaching. Product labels must comply by December 29, 2026. Registrants with these products must also update MyPeST to report compliance by January 30, 2027.
What this rolling schedule means in practice is that the label for a product your technicians are applying today may look different from the label for the same product six months from now. That's not unusual in regulatory compliance, but it creates a specific documentation challenge: how do you ensure that every technician, on every service, is logging product information that corresponds to the current, compliant label version?
When field documentation lives across disconnected tools, a field app here, a spreadsheet there, the answer is: you don't, you hope.
The operators who get ahead of this aren't checking labels manually before every service. They're using platforms that standardize product application logging across every technician and every visit: EPA registration numbers captured automatically, product details recorded consistently, application records timestamped and exportable at any moment.
That's the difference between documentation that survives an audit and documentation that creates one.
Regardless of what software you use, here is what your team needs to be capturing on every service visit to stay ahead of PRIA 5 compliance requirements:
All label updates will be submitted and managed through EPA's MyPeST digital platform, marking the advent of dual "linguistic and digital" oversight. That phrase is worth sitting with. The EPA now has a digital trail of what every compliant label should say and when it should say it. The gap between what the label says and what your service record shows is no longer a gray area. It's a verifiable discrepancy.
Commercial clients, particularly those operating under food safety certifications like AIB International, SQF or BRC Global Standards, already request service documentation that meets this standard. As PRIA 5 continues rolling out through 2026 and into 2030, the expectation will expand from certified facilities to broader commercial accounts.
The operators who build consistent, standardized field documentation now are the ones who won't be scrambling when a client's auditor asks for three years of service records and product application logs in a single afternoon.
Rupipest standardizes product application logging across every technician and every visit, EPA registration numbers, products, concentrations and application areas captured consistently, regardless of who performed the service or which site they visited. Every record is timestamped, organized by client and exportable for any audit request, at any time, without manual compilation.
When PRIA 5 compliance becomes part of a commercial client's audit checklist, your documentation will already be ready.
.jpg)
.jpg)
.png)
