Vineyard Pest Identification Records: Documenting What You Found Before You Sprayed

By VitiScribe Editorial·July 19, 2025·Updated September 26, 2025

Spray programs without pest identification documentation are classified as calendar-based by CDFA auditors. That classification matters for sustainable winegrowing certifications, for crop insurance claim support, and for demonstrating that your program meets the IPM standards that are increasingly expected by premium winery buyers.

The distinction between IPM and calendar spraying isn't just philosophy. It's a documented difference in when and why you applied a pesticide. Calendar spraying happens because the date says it's time. IPM spraying happens because you found something that crossed a threshold.

Your pest identification record is the evidence that you were practicing IPM.

TL;DR

Spray programs without pest identification documentation are classified as calendar-based by CDFA auditors -- the classification affects sustainable winegrowing certifications, crop insurance claims, and winery buyer program requirements
"14 mites per leaf" is a pest ID record; "mites present" is a note -- only the quantified observation connects to your threshold and justifies or fails to justify the treatment decision
Life stage documentation affects product choice: spirotetramat for mealybug is most effective against first-instar crawlers; UC IPM's leafhopper threshold is expressed in third-instar nymph counts, not adults -- recording adults without noting the relevant life stage doesn't accurately document threshold-based decision making
A photo of infected shoots with visible powdery mildew sporulation, dated and georeferenced to a block, is stronger IPM evidence than a written count alone -- and is essentially unanswerable documentation in a dispute with an adjuster or certifier
VitiScribe links scouting observations to subsequent spray events for the same block, creating the documented decision chain between what was found and what was applied
Field photos attached to scouting records at time of observation are geotagged and timestamped automatically -- the photo becomes part of the scouting record, not a separate file to locate and attach later

What Pest ID Records Need to Include

A pest identification record that satisfies IPM documentation requirements includes:

Date and time of scouting. Contemporaneous documentation. Not "we scout regularly" but "on July 12 at 9 AM."

Block or site location. Specific to the block being scouted, not property-wide.

Observer name. Who conducted the scouting observation.

Pest or disease identified. The specific organism: not "mites" but "twospotted spider mite (Tetranychus urticae)" or at minimum "spider mites confirmed by characteristic webbing and stippling." Not "powdery mildew" without noting whether it was confirmed through visual examination of spore characteristics or assumed from symptom presentation.

Life stage or developmental status. For insects: adults, nymphs, larvae, eggs, or specific instar. For diseases: early sporulation, advanced colony, latent infection, or other relevant developmental status. Life stage affects both threshold assessment and product choice.

Population level or severity rating. A quantified observation: "14 mites per leaf" is a pest ID record. "Mites present" is a note. The quantified observation connects to your threshold and justifies or doesn't justify the treatment decision.

Plant tissue affected. Which plant part shows the symptom or pest: leaves, clusters, shoots, bark. Relevant for both damage assessment and product efficacy planning.

Vine growth stage at observation. The phenological context that connects the pest observation to the spray timing decision (see also the vineyard IPM phenology tracking guide).

Threshold comparison. Does the observed population or severity exceed your economic or action threshold for this pest? Your threshold is the decision point. Documenting that you compared your observation to the threshold, and what conclusion that comparison yielded, completes the IPM decision record.

Why Life Stage Documentation Matters

Life stage identification isn't always possible in field conditions without specialized training, but it matters more than many growers realize.

Insecticide efficacy varies dramatically by life stage. Organophosphates effective against adult leafhoppers are poor choices for egg management. Systemic insecticides like spirotetramat for mealybug are most effective against first-instar crawlers. Applying a product at the wrong life stage is a common reason for below-expected efficacy that shows up in post-spray scouting counts.

Threshold calculations may be stage-specific. UC IPM's economic threshold for grape leafhopper is expressed in terms of nymph counts at a specific instar (third instar), not adults. If your scouting record shows adult counts without noting that third-instar nymphs were what triggered the threshold, the record doesn't document threshold-based decision making accurately.

Product selection justification may depend on life stage. A grower who selects imidacloprid for mealybug management and documents that first-instar crawlers were the target population observed is making a defensible product choice. A grower who selects imidacloprid without documenting life stage observation may have chosen the wrong product for the wrong life stage.

Photo Documentation in Pest ID Records

Field photos attached to scouting records add evidential weight that written descriptions alone don't provide.

A photo of infected shoots with visible powdery mildew sporulation, dated and georeferenced to a specific block, is stronger evidence of the disease pressure that justified your spray decision than a written count alone.

For disputes with county agricultural commissioners, insurance adjusters, or certifiers about whether your spray program was justified, photo evidence attached to the scouting records that preceded each application is essentially unanswerable documentation.

VitiScribe's scouting records allow photo attachments at the time of the scouting observation. Photos are geotagged from the phone's location data and timestamped automatically. The photo becomes part of the scouting record, linked to the spray decision it supports.

Connecting Pest ID Records to Spray Decisions

The connection between what you found and what you decided to do with it is where pest identification records pay off as IPM documentation.

A pest ID record that's stored separately from your spray log doesn't demonstrate the IPM decision process. A pest ID record linked to the specific spray event it justified creates a readable IPM narrative: "On July 12, we observed 14 twospotted spider mites per leaf and confirmed predatory mite populations at 2 per leaf (7:1 prey-to-predator ratio). Threshold at that ratio is considered crossed. On July 14, Block 3 was treated with bifenazate."

That linked record demonstrates:

Observation was made before the spray
Population was quantified, not estimated
Natural enemy population was assessed
The decision to spray was made after threshold comparison, not on a calendar
The product and timing were appropriate for the pest and life stage observed

This is what IPM documentation looks like. And it's what CDFA auditors and certifiers mean when they say spray records should demonstrate IPM practice rather than calendar spraying.

Building a Pest ID Protocol for Your Operation

For a small-to-mid-size vineyard operation, a practical pest ID protocol doesn't require elaborate equipment or formal training. It does require:

Systematic coverage. Walk each block in a consistent pattern at regular intervals during high-risk windows. Don't selectively scout areas that look good. The statistical value of your observation depends on covering the full block, not cherry-picking representative locations.

Consistent counting methodology. For each pest, establish a consistent sample size: number of leaves per vine, number of vines per sampling point, number of sampling points per block. Consistency allows comparison across dates and seasons.

A field tool for threshold reference. UC IPM published thresholds for all major California wine grape pests and diseases are available through UC ANR. Having access to these thresholds in the field, on your phone, means you can document the threshold comparison at the time of the scouting observation rather than from memory later.

Real-time record entry. Entering the pest ID record in the field at the time of observation rather than reconstructing it later ensures accuracy in both the data and the timestamp.

Frequently Asked Questions

What pest information should I record before making a spray decision in my vineyard?

Before logging a spray decision, your scouting record should include: date and location of the observation, the observer's name, the pest species or disease identified with life stage or developmental status, a quantified population count or severity score, the vine growth stage at observation, and a comparison of the observed count against the applicable economic or action threshold. This documentation creates the decision chain that demonstrates IPM practice rather than calendar spraying.

How does VitiScribe link pest ID records to spray event justification?

When you log a scouting observation in VitiScribe, the observation is stored on the block's record timeline with a timestamp and location tag. When you subsequently log a spray event for the same block, VitiScribe links the most recent scouting observation as the justification record for the application. The spray record includes a reference to the scouting observation that preceded it, creating a documented decision chain between what you found and what you applied.

Can I attach field photos to pest identification records in VitiScribe?

Yes. VitiScribe's mobile scouting record entry includes photo attachment functionality. Photos taken from the field are geotagged and timestamped automatically and attached to the scouting observation record. These photos provide visual evidence of the pest pressure that justified your spray decision, which is valuable for insurance claim documentation, certifier review, and any dispute about whether your spray program was justified by observed conditions.

What should a pest identification record show when a decision is made NOT to spray based on scouting results?

A below-threshold scouting observation that results in a decision not to spray is some of the most valuable IPM documentation you can maintain. The record should document: the pest species observed, the quantified population count, the applicable economic threshold value, and the explicit conclusion that the observation was below threshold and did not justify an application. This "no-spray" scouting record demonstrates that your program is genuinely threshold-based -- that you considered applying and chose not to because conditions didn't warrant it. For certifiers like CCOF, SIP Certified, and Lodi Rules, below-threshold no-spray records are direct evidence of IPM practice and are more compelling than spray records alone.

What is Vineyard Pest Identification Records: Documenting What You Found Before You Sprayed?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Vineyard Pest Identification Records: Documenting What You Found Before You Sprayed. Target 50-150 words.]

How much does Vineyard Pest Identification Records: Documenting What You Found Before You Sprayed cost?

How does Vineyard Pest Identification Records: Documenting What You Found Before You Sprayed work?

What are the benefits of Vineyard Pest Identification Records: Documenting What You Found Before You Sprayed?

Who needs Vineyard Pest Identification Records: Documenting What You Found Before You Sprayed?

How long does Vineyard Pest Identification Records: Documenting What You Found Before You Sprayed take?

What should I look for when choosing Vineyard Pest Identification Records: Documenting What You Found Before You Sprayed?

Is Vineyard Pest Identification Records: Documenting What You Found Before You Sprayed worth it?

Sources

UC IPM Program
UC ANR Viticulture Research
California Department of Food and Agriculture (CDFA)
FRAC (Fungicide Resistance Action Committee)
American Vineyard Foundation

Get Started with VitiScribe

"14 mites per leaf" is a pest ID record that connects to your threshold and justifies the treatment decision; "mites present" is a note that doesn't -- and CDFA auditors and certifiers know the difference when they review your program. VitiScribe's scouting module captures species-level pest identification, life stage, quantified population counts, and threshold comparisons, then links each observation to the spray event it justified or the no-spray decision it supported. Try VitiScribe free and log your first threshold-documented pest identification record today.