Pest and Disease Surveillance Signals
Pest and disease surveillance signals help agricultural teams detect risk earlier, focus field checks, and connect observations to action. The strongest system combines field scouting, trap data, weather and crop conditions, satellite context, diagnostic confirmation, and clear response thresholds.
A signal is not the same as a confirmed outbreak. It is evidence that the risk, presence, or spread of a pest or disease may be changing. Used properly, signals help teams decide where to inspect, what to verify, and when to escalate.
This guide explains how to interpret pest and disease surveillance signals in an agriculture monitoring programme.
What are pest and disease surveillance signals?
Pest and disease surveillance signals are observations or measurements that may indicate a change in plant health risk.
They can come from:
- Field scouting: visible insects, eggs, larvae, lesions, wilting, abnormal growth, or plant damage
- Traps and samples: pheromone trap catches, spore traps, sticky cards, soil samples, or plant tissue
- Weather conditions: temperature, humidity, rainfall, leaf wetness, wind, and soil moisture
- Crop observations: changes in canopy colour, vigour, density, or growth stage
- Remote sensing: unusual vegetation patterns or persistent stress detected in satellite or aerial imagery
- Diagnostic results: laboratory identification or confirmation of a pest or pathogen
- Reports from growers and extension teams: structured observations from people working in or near fields
- Movement and pathway information: risk associated with plant material, produce, equipment, storage, or transport routes
A surveillance signal is an input to a decision, not proof by itself. A yellow patch in a field may reflect disease, water stress, nutrient deficiency, herbicide injury, or soil variation. Confirmation requires a suitable inspection or diagnostic process.
The International Plant Protection Convention describes surveillance as an official process for collecting and recording information about pest presence or absence through surveys, monitoring, or other procedures. Its ISPM 6 standard treats surveillance as a foundation for plant health decisions, including pest reporting, pest-free areas, pest risk analysis, and eradication.
Why surveillance signals matter in agriculture
Pests and diseases rarely appear as a complete, uniform event across an entire production area. They often begin in specific locations, hosts, crop stages, or environmental conditions.
That makes timing and location important.
A good surveillance system helps answer four operational questions:
- Where is risk increasing?
- Which crop, host, or production site is exposed?
- What evidence supports the signal?
- What action is justified now?
The answer may be a routine inspection, a targeted survey, sample collection, laboratory confirmation, treatment review, quarantine step, or continued observation.
Surveillance also supports more than immediate crop protection. The IPPC identifies plant pest surveillance as important for:
- Establishing and maintaining pest-free areas
- Supporting phytosanitary certification and trade
- Confirming pest status in an area
- Detecting new pests
- Defining the boundary of an affected area
- Tracking changes in pest populations
- Supporting eradication and management decisions
The value of a signal comes from what it changes. If nobody knows who must verify it or what happens after verification, the signal is only a notification.
The main types of pest and disease signals
1. Direct field signals
Direct field signals are observations made on plants, soil, traps, or surrounding habitat.
Examples include:
- A repeated increase in insects found during standard scouting
- Fresh feeding damage on a crop part associated with a known pest
- New lesions appearing across multiple plants
- Symptom clusters near field edges, irrigation points, storage areas, or transport routes
- Trap catches that continue across consecutive monitoring periods
- Sudden mortality in a crop block or nursery
Repeated and spatially connected observations deserve more attention than one isolated observation.
A field record should include the date, location, crop, variety if relevant, growth stage, observed symptom or pest, severity description, number of plants or traps checked, photographs, and the name of the observer.
2. Weather and environmental signals
Weather does not confirm a pest or disease. It can indicate that conditions may become more suitable for development, movement, infection, or spread.
Useful environmental variables may include:
- Temperature relative to the pest or pathogen’s known development range
- Rainfall and prolonged wetness
- Relative humidity
- Leaf wetness duration where relevant
- Wind direction and speed
- Soil moisture
- Irrigation patterns
- Flooding or standing water
- Crop canopy density
The correct interpretation depends on the target organism and crop. A weather pattern that raises concern for one disease may have little meaning for another.
Use weather as a trigger for targeted inspection, not as a substitute for inspection.
The World Meteorological Organization supports agricultural services that provide weather, climate, and related information to agricultural communities. In a surveillance workflow, this information becomes more useful when linked to crop stage, host distribution, field observations, and a defined decision rule.
3. Crop and satellite signals
Satellite imagery can identify unusual changes in vegetation or canopy condition across large areas. It is useful for prioritising field checks, especially where farms are dispersed or access is difficult.
Potential indicators include:
- A sudden decline in vegetation vigour
- A persistent difference between neighbouring fields
- Stress appearing in a consistent pattern
- A new cluster near a known risk area
- A change that remains visible across multiple observation dates
Remote sensing has limits. Cloud cover, mixed pixels, bare soil, crop rotation, irrigation differences, and natural variation can all create misleading patterns.
Satellite data can show where to look. It usually cannot identify the pest or disease on its own.
The most reliable workflow is a two-stage process:
- Use imagery to rank areas for inspection.
- Use field observations and diagnostics to explain the pattern.
The Agriculture Data field signals category for pest and disease monitoring can be used as a starting point for connecting these observations to a broader monitoring framework.
4. Diagnostic signals
A diagnostic result provides stronger evidence than an unverified visual observation, but its value depends on sample quality, chain of custody, method, and interpretation.
A useful diagnostic workflow records:
- Who collected the sample
- Where and when it was collected
- Which plant part or material was sampled
- How the sample was stored and transported
- Which test or identification method was used
- Whether the result is preliminary or confirmed
- Who reviewed or verified the result
A confirmed identification should update the map, risk assessment, and response plan.
Where a regulated or unfamiliar pest is suspected, local plant protection authorities or the relevant national plant protection organization should be consulted. The required reporting process varies by country and organism.
5. Movement and pathway signals
Pest and disease risk can change when plants, produce, soil, machinery, packaging, or other materials move between locations.
Pathway signals may include:
- A new production site receiving planting material from an affected area
- Equipment moving between fields without cleaning
- A pest appearing near a transport or consolidation point
- Symptoms found in a nursery or propagation facility
- A disease report linked to a shared water source
- An unusual finding near a border, port, market, or storage facility
ISPM 6 recognises that surveillance may cover growing plants, wild flora, plants and plant products in storage, and materials in transportation.
The location of a signal may reveal the pathway as well as the field risk.
How to turn signals into decisions
A practical surveillance system should use a clear chain:
| Stage | Key question | Useful record |
|---|---|---|
| Detect | What changed? | Observation, image, trap result, weather condition |
| Locate | Where is the signal? | Coordinates, field, block, host, pathway |
| Describe | What is the evidence? | Symptom, pest stage, severity, timing |
| Verify | Is the signal credible? | Repeat visit, sample, expert review, laboratory result |
| Assess | What is the likely risk? | Distribution, crop stage, conditions, movement |
| Act | What should happen now? | Inspect, isolate, notify, treat, survey, or monitor |
| Review | Did the action change the situation? | Follow-up visit, new map, updated status |
The system should distinguish at least three states:
- Suspected: evidence is incomplete or unverified
- Probable: several observations support the same explanation, but confirmation is pending
- Confirmed: an authorised diagnostic or verification process has established the finding
This distinction prevents a weak observation from becoming an official claim. It also keeps decision-makers aware of what is known, what is uncertain, and what must happen next.
Set thresholds before the signal arrives
A threshold is a pre-agreed condition that triggers a defined action. It may be based on:
- A trap result
- A number or proportion of affected plants
- The appearance of a defined symptom
- A confirmed laboratory result
- A weather and crop-stage combination
- Detection in a high-risk location
- Evidence of spread between sites
Thresholds should not be copied blindly from another crop or region. They depend on the pest, disease, host, crop value, production system, control options, and regulatory context.
FAO guidance on surveillance and early warning emphasises the importance of linking detection to preparedness, response, and communication. A threshold is useful only when the response, owner, and timeline are also defined.
Designing a reliable surveillance programme
Start with a specific purpose
Do not begin with a dashboard. Begin with the decision the programme must support.
Possible purposes include:
- Early detection of an exotic pest
- Routine monitoring of an established pest
- Delimiting the boundary of an outbreak
- Supporting a pest-free area
- Protecting a high-value crop or nursery
- Guiding integrated pest management
- Supporting trade documentation
- Prioritising field inspections
The purpose determines the target, sampling design, timing, data fields, and level of verification required.
Combine general and specific surveillance
ISPM 6 distinguishes between general surveillance and specific surveillance.
General surveillance gathers information from many sources. This may include growers, extension teams, researchers, consultants, public reports, trade publications, laboratories, and other plant health organisations.
Specific surveillance actively collects information about a pest or disease over a defined period. It may be designed as:
- A detection survey
- A delimiting survey
- A monitoring survey
A strong programme can use both. General surveillance broadens coverage. Specific surveys provide structured evidence for a defined question.
Build records that can be compared
If each scout records symptoms differently, the programme cannot reliably identify change.
Use standard fields for:
- Date and time
- Location and coordinate quality
- Crop and host
- Growth stage
- Pest or disease target
- Observation method
- Number inspected
- Number affected
- Symptom or pest stage
- Sample identifier
- Confidence level
- Follow-up action
- Reviewer and verification status
Consistency is what turns separate observations into a time series.
Technology: what helps and what does not
Digital tools can improve speed, traceability, mapping, and data sharing. FAO examples include eLocust systems, FAMEWS for fall armyworm, and SusaHamra for red palm weevil surveillance.
Useful capabilities include:
- Offline field data collection
- GPS and map display
- Photo capture
- Sample and case identifiers
- Validation rules
- Role-based review
- Laboratory result integration
- Time-series charts
- Alert routing
- Exportable records
Technology does not solve weak sampling, unclear case definitions, poor diagnostics, or missing response ownership.
Choose the simplest system that field teams can use correctly and consistently.
What should not be treated as a signal by itself?
Some observations are useful context but are too weak to support a pest or disease conclusion alone:
- One unexplained colour change in a field
- A single social media report with no location or image
- A weather forecast without crop or host information
- A satellite anomaly with no field verification
- A pest photograph without scale or identifying features
- A laboratory result with no sample history
- A dashboard alert with no explanation of the trigger
These observations should not be ignored. They should be labelled as leads requiring verification.
Frequently asked questions
What is the difference between monitoring and surveillance?
Monitoring usually refers to repeated observation of a condition over time. Surveillance is a broader, structured process that includes data collection, verification, analysis, reporting, and use in plant health decisions.
Can satellite imagery detect crop diseases?
Satellite imagery can identify patterns of crop stress that may be associated with disease. It generally cannot confirm the causal pest or pathogen without field observations, samples, or diagnostics.
How often should pest and disease surveillance be conducted?
Frequency depends on the target organism, crop growth stage, season, weather, production system, and purpose of the programme. A monitoring protocol should define visit frequency and the conditions that require additional checks.
Are trap catches proof of an outbreak?
No. Trap catches are evidence that a target organism may be present or moving through an area. Identification, trap performance, sampling coverage, and follow-up inspection all affect interpretation.
Who should verify a suspected regulated pest?
The responsible national plant protection organisation, plant health authority, or another authorised diagnostic service should verify suspected regulated pests. Requirements differ by country and pest.
What is the most important field data to record?
Record the location, date, host, observation method, symptom or pest description, number inspected, evidence collected, and next action. Without these fields, later verification and comparison become difficult.
Conclusion: make every signal actionable
Pest and disease surveillance works when it connects evidence to a decision. Field observations, weather, crop condition, satellite imagery, traps, laboratory results, and pathway information each provide part of the picture.
The goal is not to create more alerts. The goal is to create credible, traceable signals that help teams inspect earlier, verify faster, and respond with the right level of action.
For more agriculture monitoring analysis, explore the Insights section and review the pest and disease field signals. Use them to build a surveillance workflow with defined targets, consistent records, verification steps, and named response owners.
Authoritative sources
- International Plant Protection Convention, ISPM 6: Surveillance
- IPPC and FAO, Plant Pest Surveillance Guide
- FAO, Early warning systems for plant health
- FAO, Transboundary Plant Pests and Diseases
- World Meteorological Organization, Agricultural Services
- USDA APHIS, Plant Pests and Diseases
Slug: pest-disease-surveillance-signals