Threshold-Based Spray Decisions in Vineyard IPM

By VitiScribe Editorial·March 17, 2025·Updated June 10, 2025

Economic thresholds reduce average spray applications by 2-4 per season compared to calendar programs -- that reduction comes from applications that would have been made on a calendar schedule but weren't justified by actual pest pressure when monitoring was conducted. Threshold-based decisions documented in VitiScribe provide an audit trail for IPM program justification that calendar records simply can't provide.

If you've been asked by a sustainable certification auditor "why did you spray on this date?" and your honest answer is "because it had been 14 days," you understand the gap between calendar spraying and threshold-based IPM. This guide explains how to make the transition.

TL;DR

Economic thresholds reduce average spray applications by 2-4 per season compared to calendar programs; the reduction comes from applications that weren't justified by actual pest pressure when monitoring was conducted -- not from applications that were genuinely needed
Economic threshold for western grape leafhopper is 15-20 nymphs per leaf for first generation and 20-25 per leaf for second generation (UC IPM); spider mite threshold is typically 5-10 mobile pest mites per leaf with predatory mites below 1-2 per leaf; grape berry moth timing follows degree day accumulation from biofix rather than population-based thresholds
Powdery mildew and botrytis don't have standard population-based economic thresholds -- they're managed preventively because the cost of waiting for visible symptoms far exceeds the cost of prevention; the "threshold" is effectively 0-day visible symptoms
No-spray scouting records -- "July 19 -- 8 nymphs/leaf, below threshold of 20 -- no application" -- are as important to document as spray-triggering observations; they demonstrate genuine threshold-based management rather than calendar spraying for sustainable certifiers and CDFA auditors
The spray record should reference the scouting observation that triggered it: "Applied per July 19 scouting showing 24 nymphs/leaf average (exceeds 20 nymph threshold)" -- this creates the documented decision chain that auditors look for
VitiScribe links scouting observations directly to spray records, so the connection between what was found and what was applied is documented in the record structure rather than requiring manual cross-referencing

What an Economic Threshold Is

An economic threshold (ET) is the pest population level at which the cost of control is less than the value of the damage the pest will cause if left unmanaged. Below the threshold, the pest is present but the economic damage from not spraying is less than the cost of the application. Above the threshold, spray -- the damage will exceed the control cost.

This is deliberately an economic concept, not just a biological one. You're not trying to eliminate every pest from your vineyard -- you're managing pest populations below the level where they cause unacceptable economic damage.

Economic injury level vs. economic threshold: These are related but distinct. The economic injury level (EIL) is the population density that causes economic damage. The economic threshold is set somewhat below the EIL to allow time to apply controls before population growth crosses the injury level. You spray at the threshold so that population growth doesn't carry you past the EIL before control takes effect.

Established Economic Thresholds for Vineyard Pests

These thresholds come from university research and are the current guidance from Cooperative Extension programs. Thresholds should be calibrated to your region and variety -- your PCA is the best local source.

Western grape leafhopper (Erythroneura elegantula):

First generation (late May-June): 15-20 nymphs per leaf at 5-10 leaves per sample site
Second generation (July-August): 20-25 nymphs per leaf
Third generation adults: damage potential at harvest, but control efficacy against adults is low -- threshold sprays are generally not recommended at this stage
Source: UC IPM guidelines

Variegated grape leafhopper (Erythroneura variabilis):

Similar thresholds to western grape leafhopper; confirm with local extension if both species are present

Spider mites (Tetranychus urticae, Panonychus ulmi):

Pest mites per leaf: intervention justified when pest mite numbers substantially exceed predatory mite numbers and the ratio is worsening
A rule of thumb used in many California programs: when mobile pest mites exceed 5-10 per leaf AND predatory mites are below 1-2 per leaf, biological control is failing and intervention is warranted
Note: thresholds vary by vine vigor, growth stage, and whether leafburn symptoms are developing

Grape berry moth (Paralobesia viteana):

Trap-based thresholds: generally, spray at each generation if local GBM populations are historically notable
Some programs use cumulative trap captures as a threshold indicator
Degree day timing (100-150 DD50 from biofix for each generation) is more useful than population-based thresholds for GBM

Powdery mildew:

Flag shoot incidence at early season: 1% or more of buds showing flag shoot symptoms indicates high overwintering inoculum and warrants escalated early-season program intensity
In-season: there is no standard economic threshold for powdery mildew -- it's managed preventively because the cost of waiting for visible infections to reach a "threshold" far exceeds the cost of prevention

Documenting Threshold-Based Decisions in VitiScribe

The documentation challenge with threshold-based decisions is showing the connection between what you observed and what you decided.

For spray applications triggered by threshold exceedance:

Your scouting record (entered before or concurrent with the spray record) should show:

Date of monitoring
Block and number of sample sites
Monitoring method
Count per sample unit (nymphs per leaf, mites per leaf, etc.)
Average across sample sites
Comparison to established threshold
Decision: "Threshold exceeded. Apply Delegate for leafhopper second generation."

Your spray record should reference the scouting observation:

All standard compliance fields (product, rate, block, date, weather, applicator)
IPM rationale note: "Applied per July 19 scouting showing 24 nymphs/leaf average (exceeds 20 nymph threshold)"

For monitoring decisions that don't trigger a spray:

These "no-spray" decisions are equally important to document, because they're the evidence that you're managing by threshold rather than calendar. A scouting record showing "July 19 -- 8 nymphs/leaf, below threshold of 20 -- no application" demonstrates that you checked and made a conscious decision not to spray. That's what IPM looks like in practice, and that's what sustainable certification auditors want to see.

In VitiScribe's scouting module, no-spray decisions are documented with the same fields as spray-triggering observations. The decision and rationale are captured in the scouting record. For more on what a complete pest identification record needs to include, see vineyard IPM pest id records. See scouting records in VitiScribe.

Integrating Thresholds with Your Spray Calendar

Some vineyard managers misunderstand threshold-based IPM as meaning "don't spray until you see a problem." That's not the correct interpretation for diseases like powdery mildew and botrytis where preventive applications are essential and waiting for visible symptoms means you're already behind.

A better framework:

Preventive management for diseases: Apply fungicides preventively based on conditions that create infection risk (temperature, humidity, growth stage) rather than waiting for visible symptoms. The "threshold" for powdery mildew is effectively 0-day visible symptoms -- you spray before you see anything because post-infection symptoms indicate your program already has gaps.

Threshold-based management for insect pests: Leafhoppers, spider mites, and most insect pests have established population-based economic thresholds that you use to decide whether to spray at each monitoring event.

Degree day-based management for timing-sensitive pests: Grape berry moth and mealybug have life stage timing (based on degree day accumulation) that drives application timing regardless of population threshold. You spray at the threshold degree day accumulation because that's when the pest is most vulnerable, not because you've counted a specific number of insects.

Your spray records should reflect this distinction. Fungicide applications are connected to weather conditions and disease pressure indicators. Insecticide applications for leafhoppers and mites are connected to monitoring counts and threshold comparisons. GBM applications are connected to degree day accumulation from biofix.

Frequently Asked Questions

What is an economic threshold in vineyard IPM?

An economic threshold is the pest population level at which the economic benefit of applying a control measure equals the cost of that measure. Below the threshold, the pest is present but controlling it would cost more than the damage it would cause -- so you don't spray. Above the threshold, the expected damage exceeds the control cost -- so you do spray. Economic thresholds are established through research that quantifies the relationship between pest population density and crop damage value. In vineyards, UC Cooperative Extension (California), OSU Extension (Oregon), WSU Extension (Washington), and Cornell (New York) are the primary sources for regionally calibrated economic thresholds.

How do I know when to spray based on scouting data in my vineyard?

For leafhopper management, count nymphs per leaf at 10-25 leaves per block from 3-5 representative locations. Average across all samples. Compare the average to the regional economic threshold (15-20 nymphs/leaf for western grape leafhopper first generation in California). If average exceeds threshold, apply an insecticide. If average is below threshold, document the count and continue monitoring in 7-14 days. For spider mites, compare pest mite count to predatory mite count per leaf. If predators are keeping pace with pests and the ratio is stable or improving, withhold treatment. If pest numbers are rising substantially faster than predators, apply a selective miticide.

How does VitiScribe help me document threshold-based spray decisions?

VitiScribe's scouting module allows you to enter monitoring observations with pest identification, count per sample unit, average across samples, and a comparison to the established threshold for that pest. The scouting record can include a decision field: "Threshold exceeded -- applying Altacor" or "Below threshold -- continuing monitoring." When you create a spray record following a threshold-exceeding scouting observation, you can link the scouting record to the spray record, creating a documented connection between the observation that triggered the application and the application itself. At audit time, this connection is exactly what sustainable certification programs require to verify that spray decisions were threshold-based rather than calendar-based.

How should a threshold-based leafhopper spray decision be recorded differently from a preventive disease spray?

A leafhopper threshold exceedance record documents the specific count (24 nymphs/leaf average), the threshold it was compared against (20 nymphs/leaf for second generation), and the explicit conclusion that the threshold was exceeded. The spray record then references this observation. A preventive powdery mildew application, by contrast, documents the conditions that created infection risk -- vine growth stage (bloom), recent weather conditions (warm temperatures, moderate morning humidity), and spray interval relative to the last application -- rather than a population count. Both are defensible IPM documentation; they document different types of spray triggers that apply to different categories of pest management.