Agriculture & Future Food Systems · Article
Monitoring, Thresholds and Timing
Turn comparable crop observations into a justified decision, keeping sampled abundance, injury and predicted development distinct.
Preparation and related reading
Shared Foundations
Related articles
This article helps you
- State the organism, sampled unit and observation effort.
- Separate trap catches from infestation and crop injury.
- Interpret an action threshold within its crop and regional scope.
- Use development models and outcome records without treating them as guarantees.
A rising count needs a clear meaning
Flying-insect catches increase while leaf inspections show little change. Those records need not contradict each other: a trap samples certain moving adults, while the leaf assessment observes another population or stage. Before deciding that damage has increased, state what each count represents.
Monitoring follows an identified question about the crop. Record organism identity, date, location, crop stage, sampled unit and effort. A result without its sampling basis is difficult to compare with an earlier one.
The diagnostic article explains identification and competing causes. Here we connect monitoring with supported action criteria and timing, rather than prescribing a treatment from every finding.
Keep sampling effort and denominators visible
A count of affected leaves needs the number examined, the scoring criterion and the sampling arrangement. A count per plant or per area answers another question. Sampling more material can raise the raw count without increasing the affected proportion.
In a hypothetical record, 6 affected leaves out of 30 is 20%; 12 out of 60 is also 20%. Those proportions use a consistent criterion but do not by themselves establish whole-crop infestation, statistical equivalence or an action threshold.
Retain the distribution across the crop, not only a convenient average. Sampling position, stage and conditions can influence observations. A comparable method and traceable record help distinguish an apparent trend from changed observation effort.
Trap catches are evidence of a sampled process
Sticky traps can help detect activity or changes in flying-adult catches. Their placement and attraction influence what is caught. Damaging immature stages on the plant may not be measured by the same device.
Natural enemies can also appear on traps, so identification matters. A total number of insects should not be treated as a total number of crop pests. Plant observations and the relevant stage remain necessary for interpretation.
More catches can reflect movement or a changed sampling setting as well as a changing population. This does not make traps useless; it means their results need an appropriate question and supporting observations. Trap catches are not automatically either a crop census or effective control.
A threshold supports a particular decision
An action threshold is a supported level of pest abundance or injury at which management is justified in the relevant system. Its interpretation can depend on crop value, damage consequences, method cost, delay before a method works and adverse effects.
Crop, cultivar, stage, harvest timing, region and conditions affect how much injury can be tolerated. A threshold from ornamental nursery guidance should not be copied as a numerical rule for food crops. Some crop problems also lack a well-established quantitative threshold.
Use an applicable guideline or qualified advice and retain its scope. The European Commission’s IPM framework similarly calls for monitoring and, where feasible, appropriate thresholds. That general principle does not create a local number or replace product-specific and national requirements.
Timing follows the target’s development
A management method may act on a particular life stage. Finding the organism is therefore different from identifying the period when a supported method can work. Calendar dates can shift with conditions and location.
Degree-day models accumulate time-temperature indices to estimate development using a named model, its thresholds and a biological starting event often called a biofix. Units, calculation conventions and stage targets must match the fitted model.
The crop-development article provides the shared thermal-time reasoning. For a pest, the species and model need their own validation. A calculated total is an estimate to check against observations, not a guaranteed emergence date or a generic spray schedule.
A decision needs a follow-up observation
Record the evidence, applicable criterion, chosen action or reason for waiting, and the stage being targeted. Later, assess the relevant crop outcome and adverse effects using a suitable observation method. An intervention is not successful merely because it was completed.
Changed counts after an action can also reflect weather, sampling or population movement. A causal effectiveness claim requires an appropriate comparison. Preserve the limits of an uncontrolled before-and-after record.
The next articles compare methods and explain resistance. Monitoring connects them into a traceable process: identify the problem, obtain comparable evidence, make a justified decision and assess what happened.
From comparable evidence to a checked decision
Read the diagram as text
Monitoring evidence and an applicable criterion support a decision whose outcome needs another observation.
Parts
- Comparable evidence
- Identity, unit, effort and stage
- Justified decision
- Applicable criterion and method timing
- Follow-up observation
- Crop consequence and adverse effects
Connections
- Comparable evidence → Justified decision: apply relevant guidance
- Justified decision → Follow-up observation: assess the result
Worked examples
Compare fractions rather than raw affected counts
Using the same criterion, hypothetical sample A has 6 affected leaves out of 30 and B has 12 out of 60.
- A fraction: 6/30×100=20%.
- B fraction: 12/60×100=20%.
- Retain sampling arrangement and dates; neither fraction provides an action threshold or proves a population trend.
The observed fractions are equal even though the raw affected count doubled. Wider inference needs the sampling design.
Interpret catches and leaf observations
Flying-adult catches increase while the assessed immature-stage infestation on leaves appears unchanged.
- Check identification, placement and trapping effort.
- Keep the adult catch and leaf assessment as different measured processes.
- Use the crop-specific decision criterion and further evidence before inferring injury.
The records may both be valid. Increased adult catches do not automatically establish increased damaging stages or justify a specific intervention.
Check your understanding
Does doubling the affected count necessarily double the affected proportion?
Show answer and reasoning
No.
The denominator and sampling effort may also change.
Can a threshold for one crop and market be applied universally?
Show answer and reasoning
No.
Its scope includes the crop, stage, conditions, consequences and available methods.
Does a degree-day estimate guarantee the exact day a pest stage appears?
Show answer and reasoning
No.
The model and starting event require relevant validation and observed checks.
Key ideas
- Record the sampled unit, identity, effort and crop stage.
- Interpret traps and plant inspections by what they measure.
- Use applicable thresholds without inventing operating numbers.
- Assess outcomes and retain the decision’s evidence.
References
Sources supporting the explanations and examples in this article.
University of California Agriculture and Natural Resources, Statewide IPM Program3 sources
- Establishing Action ThresholdsUniversity of California Agriculture and Natural Resources, Statewide IPM ProgramTeaching resource
- Monitoring with Sticky TrapsUniversity of California Agriculture and Natural Resources, Statewide IPM ProgramTeaching resource
- Degree-Days: About Degree-DaysUniversity of California Agriculture and Natural Resources, Statewide IPM ProgramTeaching resource
- Integrated Pest Management (IPM)European Commission, Directorate-General for Health and Food SafetyReference guide