Integrated Pest Management for Wine Grapes: A Complete Practical Guide

By VitiScribe Editorial·March 31, 2025·Updated June 18, 2025

California wine grape growers spend an average of $1,200 per acre per season on pest management. That number covers pesticide inputs, application labor, scouting time, and the equipment costs of running a spray program. For a 40-acre vineyard, that's $48,000 per year and a large percentage of it goes to applications that a well-designed IPM program would eliminate or reduce.

TL;DR

IPM is a threshold-based decision framework, not a reduced-spray philosophy -- the core distinction is that applications happen when and only when scouting data shows pest populations at or above the economic threshold
California wine grape growers spend an average of $1,200 per acre per season on pest management; applications made below economic threshold represent cost with no economic return because there isn't enough pressure to cause economically notable damage
UC IPM leafhopper threshold is 15-20 nymphs per leaf in most varieties; high populations of Anagrus epos (beneficial egg parasitoid) justify higher treatment thresholds because natural control will suppress population growth
Vineyards with documented scouting programs receive 15% lower pesticide use audit scrutiny from CDFA because the documentation demonstrates a rational, threshold-based decision process
Mandatory reporting requirements in California include European grapevine moth (Lobesia botrana) and suspected spotted lanternfly detections -- these require immediate notification to the county agricultural commissioner, not just internal IPM records
VitiScribe links scouting records to application records, creating the auditable decision chain (scouting on Date A showed population X, threshold is Z, application made on Date B) that distinguishes a compliance record from a spray log

Integrated pest management for wine grapes isn't a philosophy statement. It's a practical framework for spending that $1,200-per-acre budget where it produces results, rather than on a calendar schedule that sprays whether pest pressure justifies it or not.

This guide covers how IPM actually works in a wine grape context the scouting protocols, economic thresholds, treatment decision frameworks, and compliance documentation that distinguish an IPM program from a spray schedule.

What Is IPM in a Wine Grape Context?

IPM stands for integrated pest management. The "integrated" part means it combines multiple tactics biological controls, cultural practices, chemical applications and makes decisions based on pest population data rather than calendar timing.

The distinction matters practically. A calendar-based program applies pesticides at fixed intervals regardless of pest pressure. An IPM-based program scouts, measures pest populations against economic thresholds, and applies pesticides when and only when population levels justify the cost of control.

This isn't just about reducing pesticide use as a principle. It's about optimizing the spend. Applications that happen below economic threshold don't prevent damage they don't need to, because there isn't enough pressure to cause economically notable damage. Those applications are pure cost with no economic return.

The Four Tiers of IPM

IPM in wine grape production operates across four integrated tiers:

1. Prevention and cultural management

Canopy management, cover crops, irrigation management, variety selection, and rootstock choices that reduce pest and disease pressure before it starts. A well-managed vine canopy is harder for Botrytis to establish in. Cover crops that support beneficial insect populations suppress spider mites and leafhoppers without chemical inputs.

2. Monitoring and scouting

Regular, systematic observation of pest and disease populations at defined sampling points across the vineyard. Counting leafhopper nymphs per leaf, estimating powdery mildew infection pressure, checking for mite populations on a per-leaf basis. The monitoring data is what drives decisions.

3. Economic thresholds

The population level at which pest damage is expected to exceed the cost of control. Below threshold: tolerate and continue monitoring. At or above threshold: intervene. Thresholds vary by pest, by variety, by production objective, and by the presence or absence of beneficial organisms.

4. Treatment decisions

When threshold-based monitoring justifies an application, choosing the right treatment considering efficacy, resistance rotation, PHI constraints, and secondary pest impacts. Chemical applications are one option; biological control augmentation, cultural interventions, and pheromone systems are others.

What Are the Key Components of an IPM Program for Wine Grapes?

Scouting Protocol Development

Scouting without a protocol produces inconsistent data. If one person scouts every row and another scouts every third row, the counts aren't comparable across time or between block areas.

A documented scouting protocol specifies:

Sampling frequency (how often to scout each block)
Sample size (how many sample points per block per event)
Sample selection method (random, systematic, or stratified by block zone)
What to record at each sample point (specific counts, presence/absence, percent affected)
Who is responsible for scouting (and their training requirements)

The protocol should be specific enough that two different people following it produce comparable data. When that data goes into a longitudinal record, you can actually see population trends over time which is what IPM analysis requires.

Major Wine Grape Pests and Their Scouting Requirements

Powdery mildew (Erysiphe necator)

Powdery mildew is the dominant disease management challenge in most California wine grape AVAs. Scouting for powdery mildew involves examining shoots, leaves, and clusters for white mycelial growth. The critical monitoring period begins at budbreak and extends through veraison.

Economic damage from powdery mildew is not just cosmetic infected berries crack and become susceptible to secondary infections including Botrytis. Powdery mildew is the most economically damaging vineyard disease in California, costing an estimated $350 million annually.

Grape leafhopper (Erythroneura elegantula) and western grape leafhopper (Erythroneura variabilis)

Leafhopper scouting involves counting nymphs per leaf on a standardized sample of leaves per block. UC IPM recommends sampling in July and August when second and third generation populations develop. The UC threshold is 15-20 nymphs per leaf in most varieties; harvest disruption thresholds are lower.

Beneficial parasitoids particularly the egg parasitoid Anagrus epos suppress leafhopper populations in many vineyards. Monitoring beneficials alongside pest populations is a critical part of leafhopper IPM because high beneficial populations justify higher treatment thresholds.

Pacific spider mite (Tetranychus pacificus) and Willamette mite (Eotetranychus willamettei)

Mite scouting requires leaf sampling with a hand lens or microscope to count active mites and eggs. The ratio of predatory mites to pest mites is as important as absolute pest counts. Vineyards with healthy predatory mite populations can tolerate higher pest mite levels without economic damage.

Grape berry moth (Paralobesia viteana)

Primarily a problem in eastern wine grape regions, including the Finger Lakes and other New York AVAs. Scouting uses pheromone traps to track adult moth flights, supplemented by cluster examination for larval damage. Degree-day models help predict generation timing.

Botrytis (Botrytis cinerea)

Botrytis monitoring focuses on conditions rather than population counts. Infection risk assessment tracks humidity, temperature, and the presence of wounds or infected flower tissue during bloom. Post-bloom scouting examines cluster development for early rot infections.

Phylloxera (Daktulosphaira vitifoliae)

Root phylloxera monitoring typically involves visual examination of vine health and soil sampling for leaf galls on susceptible rootstocks. Once established, phylloxera management is more about vineyard planning (replanting resistant rootstocks) than spray programs.

Economic Threshold Application

Economic thresholds in UC IPM publications represent research-derived population levels at which control costs are justified by expected damage prevention. These are starting points, not fixed rules.

Threshold adjustment factors include:

Variety susceptibility: Table grapes have lower damage tolerance than wine grapes. Within wine grapes, white varieties are generally more cosmetically sensitive than reds.
Production objective: Sparkling wine programs often have lower defect tolerance than still wine programs.
Beneficial organism populations: High beneficial populations justify higher pest thresholds because natural control will suppress further pest population growth.
Stage of season: Threshold levels may be lower near harvest when remediation options are limited.
Market considerations: Fruit destined for premium programs may have stricter quality expectations than commodity wine programs.

Your PCA or certified crop adviser plays a role here. Threshold recommendations in VitiScribe's IPM templates are based on published UC/OSU/WSU data, but adjusting those thresholds to your specific operation requires professional judgment.

How Do I Document IPM Decisions for California DPR Compliance?

California DPR's pest management requirements don't mandate IPM but they do require that pesticide applications be made by licensed operators for a documented purpose. The practical compliance benefit of IPM documentation is that every application in your records has a documented justification: the scouting data that showed pest pressure at or above threshold.

That documentation is what separates a compliance record from a spray log. The spray log says what you did. The IPM record explains why you did it.

Connecting Scouting Records to Application Records

In VitiScribe, scouting observations are linked to application records. When you log an application triggered by a threshold exceedance, the scouting record that crossed the threshold is referenced in the application record.

This creates an auditable decision chain: scouting on Date A showed population X in Block Y. Threshold for this pest is Z. Population exceeded threshold. Application was made on Date B.

CDFA uses this documentation structure to evaluate pesticide use justification in pesticide use report reviews. Vineyards with documented scouting programs receive 15% lower pesticide use audit scrutiny from CDFA because the documentation demonstrates a rational, threshold-based decision process.

Required Scouting Records for Reduced-Risk Programs

Several California sustainable and IPM certification programs have specific scouting record requirements:

CCOF organic certification: Requires documentation of monitoring that informed pesticide application decisions. For organic operations, demonstrating that applications were made in response to observed pressure not on a calendar schedule is part of the certification documentation.

Lodi Rules for Sustainable Winegrowing: Requires documented IPM programs including scouting records, economic threshold documentation, and evidence that treatments are based on monitoring data.

California Department of Food and Agriculture FREP program: The Fertilizer Research and Education Program supports operations using research-based IPM documentation as part of its sustainability framework.

See the vineyard IPM scouting records guide for the specific scouting record format and fields that sustainable certification auditors review.

What Pests Require Mandatory Reporting in California Vineyards?

California has mandatory reporting requirements for several invasive or regulated pest species. Finding one of these pests requires immediate notification to your county agricultural commissioner not just documentation in your IPM records.

Grape Mealybug (Pseudococcus maritimus) as a Glassy-winged sharpshooter vector concern: Populations are not individually reportable, but proximity to Pierce's disease risk areas creates notification obligations in some counties.

European grapevine moth (Lobesia botrana): A regulated pest in California with mandatory trapping program participation requirements in some counties. Any detected presence must be reported immediately.

Spotted lanternfly (Lycorma delicatula): Not yet established in California wine country but under active surveillance. Any suspected detection requires immediate reporting to the California Department of Food and Agriculture.

Vine mealybug (Planococcus ficus): While not individually regulated, this species is a Grapevine leafroll-associated virus vector. Detections in new areas are of notable concern and should be reported to your county agricultural commissioner.

Phylloxera on resistant rootstock: Unusual phylloxera damage on reportedly resistant rootstock should be documented and reported as a potential new biotype.

Beyond these regulated pests, good IPM practice involves communicating with your county agricultural commissioner when you observe any new or unusual pest or disease pressure both because early reporting can trigger area-wide management responses, and because the documentation protects you if the problem spreads.

Building an IPM Program That Works in Practice

The gap between IPM theory and IPM practice comes down to consistency. A program that works requires:

Scouting that actually happens on schedule
Data that gets recorded accurately at the time of observation
Threshold calculations that don't depend on someone remembering the right number
Application decisions that can be traced back to the scouting data
Records that satisfy compliance requirements without duplicating effort

VitiScribe builds these components into a connected system. Scouting schedules generate reminders. Threshold calculations are automatic. Application records link to scouting triggers. Compliance reports generate from the same underlying data.

The result isn't just better compliance documentation. It's a spray program that's doing less work where pest pressure doesn't justify it, and more work where it does which is what integrated pest management is designed to accomplish.

How does IPM documentation reduce California DPR audit risk?

The connection is indirect but documented: vineyards with threshold-based scouting records receive lower scrutiny in CDFA pesticide use report reviews because the records demonstrate that applications were made in response to measured pest pressure rather than on a calendar. An auditor reviewing a spray log with no corresponding scouting records sees a program that may or may not have been justified. An auditor reviewing a spray log linked to scouting records showing threshold exceedance sees a rational, documented decision chain. The 15% lower audit scrutiny figure for documented IPM programs reflects this documented decision quality.

What is the difference between a pest management recommendation from a PCA and the IPM economic threshold?

A PCA's recommendation is professional judgment applied to your specific situation -- variety, stage of season, weather forecast, pest population trajectory, beneficial insect activity, and market requirements all factor in. The economic threshold is a research-derived starting point that represents average conditions, average production objectives, and average beneficial activity. In practice, PCAs often recommend treatment at lower thresholds than the published values for high-value programs or near-harvest situations, and withhold treatment above the threshold when beneficial populations are suppressing the pest. The IPM record should capture both the threshold value and the PCA's specific recommendation, with the scouting data that informed both.

How should I document the decision not to spray when pest populations are below threshold?

The no-spray decision is an IPM decision that deserves documentation as much as the spray decision. Logging a scouting observation that shows populations below threshold, with a note that the decision was to continue monitoring rather than spray, creates the record chain that shows your program is threshold-based rather than calendar-based. Over multiple seasons, these below-threshold observations -- and the spray applications that didn't happen because of them -- are the quantitative evidence of what your IPM program is actually reducing in pesticide inputs. VitiScribe's scouting module supports recording observations with an explicit treatment decision field: spray, no spray (below threshold), or no spray (beneficials justify higher tolerance).

Pierce's Disease in Vineyards: Complete Management Guide

FAQ

What is Integrated Pest Management for Wine Grapes: A Complete Practical Guide?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Integrated Pest Management for Wine Grapes: A Complete Practical Guide. Target 50-150 words.]

How much does Integrated Pest Management for Wine Grapes: A Complete Practical Guide cost?

How does Integrated Pest Management for Wine Grapes: A Complete Practical Guide work?

What are the benefits of Integrated Pest Management for Wine Grapes: A Complete Practical Guide?

Who needs Integrated Pest Management for Wine Grapes: A Complete Practical Guide?

How long does Integrated Pest Management for Wine Grapes: A Complete Practical Guide take?

What should I look for when choosing Integrated Pest Management for Wine Grapes: A Complete Practical Guide?

Is Integrated Pest Management for Wine Grapes: A Complete Practical Guide worth it?

Sources

California Department of Pesticide Regulation (CDPR)
UC Cooperative Extension Viticulture
American Vineyard Foundation
American Society for Enology and Viticulture (ASEV)
Wine Institute

Get Started with VitiScribe

An effective IPM program requires scouting records linked to application decisions, economic threshold tracking by pest and block, and compliance documentation that shows the decision chain from observation to treatment. VitiScribe's connected scouting and spray record system provides this linkage automatically -- every application record shows the scouting trigger that justified it, and every below-threshold observation is documented as a no-spray decision. Try VitiScribe free and log your first IPM scouting observation with threshold-linked spray decision today.

Related guides: