How to Automate California Pesticide Use Reporting from Your Vineyard Spray Logs

If you farm in California, pesticide use reporting is not optional. Every restricted pesticide application -- which covers most of what goes on in a Napa or Sonoma vineyard -- has to be reported to your county Agricultural Commissioner within 7 days of application. For most operations, that means someone on your team is manually transferring spray log data into CalAgPermits, the state's online submission portal, week after week.

It is exactly the kind of work that sounds manageable until you are doing it across 200 acres, multiple blocks, and a 12-month spray program. Then it becomes a significant time sink.

This post covers what PUR reporting requires, how CalAgPermits works, and how Sentinel's direct integration with CalAgPermits eliminates the manual double-entry step entirely.

What California Pesticide Use Reporting Actually Requires

California's Department of Pesticide Regulation (DPR) mandates Pesticide Use Reports for any application of a restricted material. In vineyard operations, that typically includes fungicides, herbicides, and most insecticides -- effectively everything except basic sulfur applications in some counties.

For each application, your submitted report must include:

• Operator and site identification (county, township/range/section, or GPS coordinates)
• Product name and EPA registration number
• Amount applied and application method
• Treated acreage
• Commodity (in our case, grapes)
• Date and time of application
• Pest(s) targeted
• Any applicable permit number

That is a lot of fields to fill in manually for every spray event. A vineyard doing 15-20 applications per year across multiple blocks can have dozens of individual PUR entries to submit. The 7-day filing window adds urgency -- you cannot let submissions accumulate.

The Manual Workflow Most Vineyards Are Using Today

The typical workflow looks something like this:

1. Field crew completes a spray, records the application in a paper log or spray app
2. At week's end, an office staff member reviews the spray records
3. They log into CalAgPermits and manually key in each application -- product, rate, acreage, block location, dates
4. Repeat for every application that week

If your spray records are in one system (or on paper) and CalAgPermits is a separate portal, there is no connection between them. Every submission is a manual re-entry of data you already recorded in the field.

This is where errors happen. Acreage entered incorrectly. Product names that don't match the registered DPR product exactly. Blocks that are described differently in your spray log versus your compliance submission. County inspectors review these reports -- inconsistencies create follow-up questions you don't want.

How CalAgPermits Works

CalAgPermits is California DPR's statewide reporting system, administered through county Agricultural Commissioners. Growers and Pest Control Advisors with a county permit submit their use reports through this portal, either manually via the web interface or through a machine-to-machine integration for operators and software vendors who support it.

The system stores all submitted reports and makes them available to county staff for review and enforcement. Reports are also used by DPR for statewide pesticide use statistics and environmental monitoring.

The manual web interface works fine for small operations. For anyone managing 50+ acres with a meaningful spray program, the volume of individual submissions makes the portal a time drain.

How Sentinel's CalAgPermits Integration Works

Sentinel's vineyard management platform records spray applications as work orders tied to specific blocks -- and as of early April 2026, Sentinel can submit those records directly to CalAgPermits on your behalf.

The workflow with Sentinel looks like this:

1. Field crew records the spray application in Sentinel (product, rate, blocks treated, date/time, crew)
2. Sentinel validates the application data against DPR's registered product database
3. When the report period closes, Sentinel packages the applications into properly formatted PUR submissions
4. Submissions are sent directly to CalAgPermits through the integration -- no manual portal entry required

Because Sentinel already knows your block boundaries, acreage, and GPS coordinates from the vineyard mapping layer, the location data in your PUR submissions is consistent and accurate. The same GPS coordinates that define your vine-by-vine records drive your compliance submissions.

This matters for two reasons. First, it eliminates transcription errors -- the product name, rate, and treated acreage in your PUR submission come directly from the spray work order, not from a human typing the same data a second time. Second, it creates a full audit trail: every PUR submission is linked to the original work order, the specific blocks treated, and the individual vines in those blocks.

Spray History as a Vineyard Asset

The compliance angle is the immediate value -- automating PUR submissions saves real administrative time and reduces the risk of filing errors. But the larger opportunity is what happens to your spray data once it is in Sentinel.

Because Sentinel records spray applications at the block level (and optionally at the vine level for targeted applications like roguing), your spray history becomes queryable vineyard data. You can ask: which blocks received Movento in 2024? How many times did Block 7 get treated for powdery mildew last season? What is the total fungicide load per acre across your estate year over year?

Those questions are nearly impossible to answer from a stack of paper logs or a CalAgPermits history view. They are straightforward in Sentinel because every spray application is tagged to your map, not just filed in a compliance system.

For operations thinking about certification programs, sustainability benchmarks, or buyer transparency requirements, that queryable spray history is increasingly valuable -- and it is built automatically as a byproduct of doing your compliance correctly.

The Practical Upshot

California's PUR reporting requirements are not going away, and the volume of required filings only increases as operations grow. The question is whether compliance is a manual task that consumes administrative capacity each week, or a workflow that runs automatically in the background.

Sentinel's CalAgPermits integration is in production. If your operation is currently managing PUR submissions by hand, it is worth seeing what the automated workflow looks like.

Schedule a demo here to see how Sentinel handles spray logging, PUR submission, and vine-level compliance records in a single platform.