Vineyard manager documenting IPM reporting data for CDFA compliance on digital device in wine grape field
CDFA vineyard IPM reporting requirements demand accurate pest monitoring documentation.

Vineyard IPM Reporting for CDFA: What to Submit and When

By VitiScribe Editorial··Updated October 27, 2025

CDFA increased IPM reporting enforcement in wine grape regions by 22% in 2025. That's not a coincidence it follows years of expanding IPM program requirements, a more structured compliance expectation, and broader recognition in the regulatory community that documented IPM programs produce measurable environmental benefits that justify enforcement investment.

If you're growing wine grapes in California, IPM reporting requirements touch your operation even if you've never thought of your spray program in IPM terms. The question isn't whether CDFA's IPM framework applies it's whether your records satisfy what the framework requires.

This guide covers what California vineyards must report to CDFA, when reports are due, and how VitiScribe generates CDFA-compliant IPM reports automatically from your existing spray and scouting records.

TL;DR

  • CDFA increased IPM reporting enforcement in wine grape regions by 22% in 2025 -- operations with inconsistent records, late filings, or discrepancies between PUR reports and application records are the primary targets of this enforcement increase
  • Monthly PUR reports must be filed with the county agricultural commissioner by the 10th of the following month; late filings incur penalties of up to $5,000 per unreported application -- January applications are due February 10, with no growing-season exceptions
  • CDFA's IPM framework expects documented plans including monitoring and scouting descriptions, economic thresholds, evidence that treatments were triggered by monitoring data, non-chemical management practices, and resistance management documentation -- beyond the PUR filing that most growers focus on
  • Operations with consistent, accurate PUR records generated directly from application data rather than manually compiled are less likely to receive targeted compliance attention; manual compilation at end-of-month introduces the transcription errors and field gaps that attract additional scrutiny
  • County-level variation matters: Napa, Sonoma, and San Luis Obispo county agricultural commissioners have active IPM program frameworks that interact with state requirements -- check with your county about specific local obligations beyond the baseline PUR requirement
  • VitiScribe generates California PUR reports with one export operation, auto-populates county/section/township/range location formats, and updates reporting templates automatically when CDFA requirements change

What IPM Data Must California Vineyards Report to CDFA?

CDFA's integrated pest management reporting requirements for commercial agricultural operations fall under California's IPM Act and associated regulations. Wine grape operations generally fall into the commercial agriculture category and have corresponding obligations.

Pesticide Use Reporting as IPM Documentation

The California Pesticide Use Reporting (PUR) system is the foundational layer of CDFA's IPM data collection. Every commercial pesticide application must be reported monthly to your county agricultural commissioner, who aggregates data for CDFA's statewide system.

PUR data includes:

  • Pesticide product and active ingredient
  • Amount applied
  • Date of application
  • Site (section/township/range or other location description)
  • Commodity treated
  • Application method
  • Certified applicator information

This is the data that goes into CDFA's statewide pesticide use database. When CDFA analyzes IPM adoption trends in wine grape regions, they're working from this data.

IPM Program Documentation

Beyond PUR reporting, CDFA's IPM program framework expects that commercial operations have documented IPM plans that include:

  • Description of monitoring and scouting activities
  • Economic thresholds used for treatment decisions
  • Documentation showing treatments were triggered by monitoring data
  • Evidence of non-chemical management practices being used alongside chemical controls
  • Records showing resistance management considerations

The documentation expectation here is more about your compliance posture than a strict annual filing. Operations that are part of county or regional IPM programs, or that receive CDFA funding for IPM activities, have more specific reporting obligations.

County-Level Variation

IPM reporting obligations can vary by county. Some California wine grape counties participate in CDFA-supported IPM programs with more specific documentation requirements, while others have only the baseline PUR obligation. The Napa, Sonoma, and San Luis Obispo county agricultural commissioners' offices have active IPM program frameworks that interact with state requirements.

Checking with your county agricultural commissioner about specific local IPM reporting requirements is the most reliable way to understand what applies to your operation.

How Often Must Vineyard Operators Submit IPM Reports to CDFA?

The timing of IPM-related reporting varies by report type.

Monthly PUR Reports

Pesticide use reports must be filed monthly with your county agricultural commissioner. The filing deadline is the 10th of the month following the reporting month so January applications are due by February 10.

This monthly cycle applies to all commercial pesticide applications, regardless of whether your operation has a formal IPM program. If you applied a pesticide in April, the PUR report for those applications is due to your county by May 10.

Late filings incur penalties. California can fine operations up to $5,000 per unreported application for late or missing PUR reports. Automated reporting systems that generate PUR data directly from your application records eliminate the risk of missed filings.

Annual IPM Program Documentation

For operations participating in formal CDFA IPM programs or county-level programs with documentation requirements, annual reporting typically follows the calendar or growing season year. Annual reports generally cover the previous year's scouting data, threshold-based treatment decisions, and outcomes.

CDFA's Pest Management Alliance Grants and related programs that fund IPM development have specific annual reporting requirements for grant recipients. If your operation has received CDFA IPM grant funding, your specific reporting obligations are defined in your grant agreement.

On-Demand CDFA Records Requests

Beyond scheduled reporting, CDFA and county agricultural commissioners can request IPM documentation as part of compliance reviews and audits at any time during the three-year record retention period. These requests require producing records promptly.

Operations with digital records in VitiScribe can respond to records requests immediately pulling the requested data and generating a formatted report in minutes. Operations with paper records must locate, organize, and potentially copy physical documents, a process that can take days and still produce incomplete results.

How Does VitiScribe Generate CDFA-Compliant IPM Reports?

No competitor auto-formats IPM reports for CDFA submission. VitiScribe growers generate CDFA reports with one click.

PUR Report Generation

VitiScribe's DPR/PUR export function generates pesticide use report data in the format required by California county agricultural commissioners. The export includes:

  • All required PUR fields populated from your application records
  • Location data formatted to county/section/township/range requirements
  • Product registration numbers from the product database
  • Application method codes in CDFA-required format
  • Applicator information

The export is ready to submit. You don't reformat, re-enter, or manually compile data. The application records you've been logging throughout the month become the monthly PUR report with one export operation.

IPM Program Documentation Reports

For IPM program documentation beyond PUR, VitiScribe generates reports that capture your scouting history, threshold data, and treatment decisions in a format appropriate for CDFA program review:

Scouting and monitoring report: Documents all scouting observations by block, date, and pest, with counts and notes. Shows the monitoring frequency your program maintains.

Threshold and treatment decision report: For each spray event triggered by threshold data, shows the scouting observation that crossed the threshold, the threshold value, and the treatment decision. This is the core IPM documentation that shows treatments were data-driven.

Resistance management report: Shows FRAC code rotation across your spray history, documenting that resistance management was implemented.

Non-chemical practice documentation: Records of cultural practices, biological control deployments, cover crop management, and other non-chemical IPM components.

CDFA Reporting Template Updates

CDFA reporting templates update automatically when state requirements change so you never use an outdated form. California's regulatory environment evolves, and reporting requirements for IPM programs have been updated several times in recent years as the state's IPM framework has matured.

VitiScribe's reporting templates stay current with California requirements. When CDFA updates a required format or field, the change propagates to VitiScribe's export functions. You don't have to monitor regulatory changes to know whether your report format is current the system handles that.

Connecting PUR Records to CDFA Analysis

CDFA uses PUR data to analyze pesticide use trends in wine grape regions, evaluate IPM adoption rates, and target compliance resources. When your PUR records are accurate and complete generated directly from your application data rather than manually compiled you're contributing clean data to this system.

Operations with consistent, accurate PUR records are less likely to receive targeted compliance attention from CDFA because clean records don't raise questions. Operations with inconsistent records, late filings, or discrepancies between PUR reports and application records attract exactly the kind of additional scrutiny that has driven the 22% increase in IPM enforcement.

For guidance on what scouting documentation CDFA expects alongside PUR records, see vineyard IPM record keeping what to track. For how VitiScribe handles the full California compliance framework, see California DPR reporting.


Frequently Asked Questions

What is the monthly deadline for California PUR report filing?

Pesticide use reports must be filed with the county agricultural commissioner by the 10th of the month following the reporting month. Applications made in May are due by June 10. Applications in November are due by December 10. This cycle applies throughout the year including during harvest -- there are no growing-season exceptions to the monthly filing deadline. CDFA can fine operations up to $5,000 per unreported application for late or missing PUR filings. VitiScribe's automated PUR report generation compiles all applications from the prior month and sends a filing reminder with the pre-built report on the first of each month.

Does CDFA's IPM reporting requirement apply to small vineyard operations?

Yes. CDFA's IPM framework and PUR reporting requirements apply to commercial pesticide applications regardless of operation size. A 10-acre estate vineyard applying restricted-use or general-use pesticides commercially has the same monthly PUR filing obligation as a 500-acre corporate operation. What varies is the complexity of what's being reported, not whether reporting is required. Small operations sometimes assume lower enforcement attention, but CDFA audit triggers include PUR data anomalies that can be identified from the state database without regard to operation size.

What happens if my scouting records and PUR reports tell different stories to a CDFA auditor?

A discrepancy between scouting records and PUR reports -- for example, PUR records showing spray applications during periods when scouting records show zero pest activity -- is exactly the kind of inconsistency that triggers additional CDFA scrutiny. Auditors reviewing your records look for a coherent story: monitoring data shows pest pressure building, the spray decision follows, and the PUR record documents the application that resulted. If the PUR records show applications during periods when no scouting was logged, the application looks calendar-based rather than threshold-based. The most defensible program is one where scouting frequency, threshold comparisons, and spray timing all align in a way that tells the same story across all three record types.

What is Vineyard IPM Reporting for CDFA: What to Submit and When?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Vineyard IPM Reporting for CDFA: What to Submit and When. Target 50-150 words.]

How much does Vineyard IPM Reporting for CDFA: What to Submit and When cost?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Vineyard IPM Reporting for CDFA: What to Submit and When. Target 50-150 words.]

How does Vineyard IPM Reporting for CDFA: What to Submit and When work?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Vineyard IPM Reporting for CDFA: What to Submit and When. Target 50-150 words.]

What are the benefits of Vineyard IPM Reporting for CDFA: What to Submit and When?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Vineyard IPM Reporting for CDFA: What to Submit and When. Target 50-150 words.]

Who needs Vineyard IPM Reporting for CDFA: What to Submit and When?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Vineyard IPM Reporting for CDFA: What to Submit and When. Target 50-150 words.]

How long does Vineyard IPM Reporting for CDFA: What to Submit and When take?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Vineyard IPM Reporting for CDFA: What to Submit and When. Target 50-150 words.]

What should I look for when choosing Vineyard IPM Reporting for CDFA: What to Submit and When?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Vineyard IPM Reporting for CDFA: What to Submit and When. Target 50-150 words.]

Is Vineyard IPM Reporting for CDFA: What to Submit and When worth it?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Vineyard IPM Reporting for CDFA: What to Submit and When. Target 50-150 words.]

Sources

  • California Department of Food and Agriculture (CDFA)
  • California Department of Pesticide Regulation (CDPR)
  • UC IPM Program
  • UC Cooperative Extension Viticulture
  • American Vineyard Foundation

Get Started with VitiScribe

CDFA's 22% increase in IPM enforcement targets operations where PUR records don't align with documented monitoring data -- and manual monthly report compilation introduces the transcription errors and field gaps that attract that scrutiny. VitiScribe generates CDFA-compliant PUR reports directly from application records with one export, sends monthly filing reminders, and keeps reporting templates current when California requirements change. Try VitiScribe free and eliminate your manual PUR compilation workflow today.


Related guides:

Related Articles

VitiScribe | purpose-built tools for your operation.