What you will learn
- Why early detection matters for forest pests and diseases
- How observations, traps and surveys are recorded
- How outbreaks are mapped and their spread tracked
- How control actions are planned and checked
- Where surveillance ends and pest control science begins
What this project is
Forest pests and diseases spread. An insect outbreak in one stand, a fungal disease on one species, or an invasive plant in one valley can, left unchecked, affect a whole forest. Surveillance is the system that finds them early: field staff, contractors and researchers record observations, trap catches and survey results, with location and species, and the system maps them so patterns become visible. A single sick tree is a curiosity; a cluster of sick trees in one area is an outbreak that needs action.
Recording must be easy in the field, because observations happen during other work: a forester walking a stand, a harvest crew in a coupe, a survey team on a transect. A mobile tool with offline capture, species lists and photo attachment lets those observations be recorded at the time, with location, rather than written up later from memory. The system should also handle uncertainty: an observation may be a suspected pest, not a confirmed identification, and the record should say so, with confirmation by an expert where needed.
Core features
- Field observation recording with location, species, symptoms and photos, offline-capable
- Trap and survey management, with catches and results linked to locations and dates
- Outbreak mapping showing observations, confirmed cases and spread over time
- Identification workflow: suspected, confirmed and expert-reviewed statuses
- Control action tracking: what was done, where, when, and whether it worked
- Alerts for new outbreaks in new areas, and for spread beyond a defined boundary
How it is built
- Define the pests, diseases and host species to watch, with identification guidance for field staff
- Build field observation recording with offline capture, then outbreak mapping
- Add trap and survey management, then identification workflow
- Add control action tracking, then alerts for new and spreading outbreaks
- Pilot in one forest area for a season, checking that field observations reach the map reliably
Technology considerations
Identification is the hardest data problem. Field staff may recognise symptoms but not the exact pest, and misidentification leads to wrong control actions. The system should support a workflow from suspected to confirmed, with photos and expert review, rather than forcing a definite identification at the time of observation. Location data must be accurate enough to map spread: a record that only names a forest block is too vague to show whether an outbreak is spreading stand by stand.
Spread tracking needs time as well as space. An outbreak map that only shows current cases hides whether the outbreak is growing, stable or shrinking. The system should show observations over time, so managers can see the direction and speed of spread. Control action tracking closes the loop: an action recorded without a follow-up check cannot be judged, so every control action should have a planned check date and a result.
For the first version, run surveillance for one priority pest in one forest area for a season, with field observations, outbreak mapping and control follow-up recorded. Forest health teams judge the system on whether a new outbreak is mapped and acted on quickly. A system that does that for one pest, with suspected versus confirmed status handled honestly, proves the workflow before it covers every pest and disease.
Challenges to plan for
- Observations that are never recorded, because the tool is too slow or too complex in the field
- Misidentifications that lead to the wrong control action
- Outbreaks that are mapped but never acted on, because nobody owned the response
- Control actions with no follow-up, so nobody knows whether they worked
Who it is for, and its limits
This suits a forestry company, a forest health agency or a public forest authority. It fits forests where pests and diseases are a real risk and where early action can limit damage. It does not fit a small woodland with no pest history, and it is not a pest control service: it finds and tracks outbreaks, control itself is done by forest health professionals.
A surveillance system does not stop pests or diseases. It finds them early and tracks whether control works, which is what makes control effective rather than reactive. Costs vary with forest area and survey intensity, so confirm with a quote after the priority pests are defined.
Frequently asked questions
What should I record for an observation?
Location, host species, symptoms, photos where possible, and the date. An uncertain identification is recorded as suspected, with expert review to confirm it.
How are outbreaks mapped?
By plotting observations over time, distinguishing suspected and confirmed cases. The map shows where cases cluster and how the affected area changes, which guides where to act.
What triggers an alert?
A new outbreak in a new area, a confirmed case of a high-priority pest, or spread beyond a defined boundary. Alerts go to the forest health team, not to everyone, to avoid alert fatigue.
How do we know if control worked?
By follow-up surveys after the control action, compared with the outbreak map before it. An action without a follow-up check cannot be judged, so follow-ups are part of the workflow.
Can the public report pests?
Where the program allows it, yes, with location and photos. Public reports are triaged like staff observations, and confirmed reports feed the same outbreak map.