IPM Scouting Records for Vineyards: Log Pest Pressure Before You Spray
Vineyards with documented scouting programs qualify for reduced pesticide use certifications in California. That's one benefit. The more immediate one: documented scouting records are what separate an IPM program from a calendar spray program in the eyes of a DPR auditor, and they're what let you spray less without spraying blind.
TL;DR
- Scouting records don't appear on DPR pesticide use reports (those cover only applications) but they directly affect DPR audit outcomes -- applications preceded by documented threshold-level observations are clearly defensible as IPM-based decisions; applications with no scouting records look calendar-based and draw more scrutiny
- Every scouting event record requires 10 specific fields: date/time, block, pest identity (specific species not generic), life stage, count using standardized method, sample size, scout identity, vine growth stage, weather conditions, and threshold comparison (above/at/below)
- UC IPM leafhopper threshold for most wine grape varieties is 15-20 nymphs per leaf; spider mite records should capture predatory mite counts alongside pest mite counts, because the predator-to-prey ratio is as important as absolute pest density
- A threshold breach with no documented response is not a valid IPM record -- both "above threshold, treated" and "above threshold, decision to monitor before treating due to [reason]" are valid; silence is not
- VitiScribe connects scouting records to spray decisions in a visible sequence: the scouting record that triggered a spray and the spray event that responded to it appear chronologically linked in the block history
- Post-treatment scouting records linked to the preceding spray event close the efficacy measurement loop -- pre-treatment counts, spray event, post-treatment counts form the documented evidence that the application achieved its intended result
IPM scouting records for vineyard management link observed pest pressure directly to spray decisions. Scouting data triggers economic threshold alerts so you spray only when pest pressure justifies it, not because the calendar says it's spray day.
What to Record During an IPM Scouting Event
The Essential Scouting Record Fields
Every scouting event needs a record that can stand on its own and link to any resulting spray decision. Required fields:
- Date and time of scouting event
- Block observed, with GPS block reference
- Pest(s) scouted, be specific (grape leafhopper, not just "leafhopper")
- Life stage observed, eggs, nymphs, adults, eggs/cluster, etc.
- Count or incidence, pest density per sample unit using standardized methods
- Sample size, number of leaves, shoots, clusters, or traps inspected
- Scout identity, who conducted the observation
- Growth stage of vines at time of scouting
- Weather conditions, temperature, cloud cover, wind
- Comparison to economic threshold, above, at, or below threshold
Standardized Counting Methods by Pest
Scouting records are only useful for comparison if you're counting the same thing the same way each time. Use standardized methods from UC IPM or your regional extension service:
Grape leafhopper: Count nymphs per leaf on the underside of 50 leaves per block, randomly selected from middle position of shoot.
Spider mites: Count motile mites per leaf on 25-50 leaves per block. Distinguish between pest mites (Pacific spider mite, Willamette mite) and predatory mites.
Powdery mildew: Count percentage of infected shoots and clusters. Standardized infection indices use percent incidence rather than raw counts.
Botrytis: Count clusters showing infection at standardized intervals from bloom through harvest.
Grape berry moth: Record pheromone trap catches per trap per week; also count infested clusters or shoots at appropriate phenological stages.
When your records use standardized methods, they're comparable across scouting events, across blocks, and across seasons.
How to Set Economic Thresholds for Vineyard Pests in VitiScribe
Economic thresholds are the action levels that trigger spray decisions. They're the core of IPM philosophy: you don't spray until pest pressure reaches a level where the cost of treatment is justified by the value of pest damage prevented.
For California wine grapes, UC IPM has published economic thresholds for most key pests. VitiScribe loads UC IPM threshold data as defaults that you can customize for your operation.
Loading Threshold Data
In VitiScribe, each pest in your IPM program has a threshold associated with the counting method you use. For leafhopper, the standard threshold for first-generation nymphs is 15-20 nymphs per leaf for most varieties, with lower thresholds for early-season pressure in wine grapes due to leaf stippling effects on wine quality.
Set your threshold values when you set up your IPM program. They can be adjusted as you accumulate your own scouting data and refine your understanding of your specific vineyard's pest dynamics.
Threshold Alerts
When you log a scouting event with pest counts above threshold, VitiScribe generates a threshold alert. The alert:
- Identifies the block and pest
- Shows the count vs. threshold
- Prompts you to record a spray decision response
- Remains visible until you log either a spray event or a documented decision not to spray
The documented spray decision, whether you sprayed or didn't, is the completion of the IPM decision record. "Above threshold, treated with [product] on [date]" and "above threshold, decision to monitor before treating due to [reason]" are both valid IPM records. What's not valid is a threshold breach with no documented response.
Does Scouting Data Affect Your DPR Pesticide Use Report?
Scouting records don't appear on your DPR pesticide use report, that report covers only actual applications. But scouting records affect your DPR audit outcome substantially.
When a DPR auditor reviews your spray records, they're evaluating whether applications were made appropriately. If your spray records show 12 applications and your scouting records show that 9 of those were preceded by documented threshold-level pest pressure, that's an IPM program. If your spray records show 12 applications and you have no scouting records, every application looks calendar-based, and auditors apply more scrutiny to calendar-based programs.
CDFA's sustainable pest management initiatives give favorable treatment to operations with documented scouting programs. Reduced audit scrutiny and eligibility for certification programs are both downstream benefits of solid scouting records.
Connecting Scouting Records to Spray Decisions
Generic farm apps do not link scouting records to spray decisions. VitiScribe closes that loop automatically.
When you log a spray event, you can attach it to a scouting record. The system shows you recent scouting data for the block as you're creating the spray event, making it easy to reference the observation that justified the treatment. That link is visible in your block history, the scouting record that triggered the spray and the spray event that responded to it appear in chronological sequence.
For post-treatment efficacy evaluation, the scouting record after the spray event links back to the spray record that preceded it. Pre-treatment counts, spray event, post-treatment counts, all visible as a connected sequence.
See the vineyard IPM tracking guide for how scouting integrates with the full IPM system, and the spray efficacy tracking guide for how post-treatment scouting closes the efficacy measurement loop.
See the integrated pest management wine grapes guide for the full IPM framework including economic threshold application, mandatory reportable pests, and sustainable certification record requirements.
Related Articles
FAQ
What should I record during an IPM scouting event in my vineyard?
Record the date and time, the block being scouted (with GPS block reference), the specific pest being counted, the life stage observed (eggs, nymphs, adults), the count or incidence using your standardized counting method, the number of samples taken (leaves, clusters, traps), the vine growth stage, weather conditions, and the scout's name. Most importantly, compare your count to the economic threshold and note whether the observation is above, at, or below the action level. That threshold comparison is what connects the scouting record to your spray decision documentation.
How do I set economic thresholds for vineyard pests in VitiScribe?
VitiScribe loads UC IPM economic threshold data as defaults for California wine grape pests. To customize thresholds for your operation, open the IPM settings for each pest in your program and enter your preferred action level using the same counting method as your scouting records. Thresholds can be set at the vineyard level or differentiated by block if you have blocks with different pressure history or quality tier. When you log a scouting event with counts above the threshold, the system automatically generates a threshold alert linked to that block and pest.
Does scouting data affect my DPR pesticide use report?
Scouting records don't appear on the annual DPR pesticide use report, which covers only actual pesticide applications. However, scouting records substantially affect how your spray records are evaluated during a DPR audit. Applications preceded by documented scouting observations and threshold comparisons are clearly defensible as IPM-based decisions. Applications with no supporting scouting records look calendar-based, which draws more scrutiny. CDFA's sustainable pest management programs also recognize documented scouting programs for certification eligibility and reduced audit frequency.
How do I document a no-spray decision when pest populations are below threshold?
A below-threshold observation should be logged as a scouting record with an explicit no-spray decision notation. The entry should include your count, the threshold value for comparison, and the basis for the no-spray decision: "15 leafhopper nymphs per leaf, threshold is 20 nymphs per leaf, decision to monitor -- below threshold." Over time, these documented no-spray decisions create the longitudinal record that shows your program is actually threshold-based, not just loosely calendar-based with scouting done after the fact. This documentation is specifically what Lodi Rules and CCOF certifiers look for when they review IPM records -- the absence of below-threshold no-spray records suggests the scouting was being done to justify a predetermined spray schedule rather than to drive the decision.
Can scouting records from multiple people in the same block be combined into a single weekly record?
No -- scouting records should identify the individual who conducted each observation, both for accountability and because different scouts may count slightly differently even with a standardized protocol. If multiple people scout the same block on the same day, log each scout's observations separately with their individual names. If you need a single block-level summary for reporting purposes, VitiScribe can aggregate individual scouting records for a block and date range into a summary report while preserving the individual records underneath. The individual records are what certifiers and auditors review; the summary is for your own program analysis.
What is IPM Scouting Records for Vineyards: Log Pest Pressure Before You Spray?
[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to IPM Scouting Records for Vineyards: Log Pest Pressure Before You Spray. Target 50-150 words.]
How much does IPM Scouting Records for Vineyards: Log Pest Pressure Before You Spray cost?
[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to IPM Scouting Records for Vineyards: Log Pest Pressure Before You Spray. Target 50-150 words.]
How does IPM Scouting Records for Vineyards: Log Pest Pressure Before You Spray work?
[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to IPM Scouting Records for Vineyards: Log Pest Pressure Before You Spray. Target 50-150 words.]
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
IPM scouting records that are disconnected from spray decisions tell only half the story -- the observation without the action. VitiScribe's connected scouting and spray record system links every threshold alert to the spray or no-spray decision that followed, creating the auditable decision chain that DPR auditors, certifiers, and winery buyers want to see. Try VitiScribe free and log your first connected scouting observation and spray decision today.