Guide
Ash dieback surveys: classification, prioritisation and delivery
Ash dieback turned tree management from a maintenance activity into a network-scale liability programme. This guide covers the classification scale, how classes translate into works priorities, and how to run a survey across thousands of trees without losing the audit trail.

What you are actually assessing
Ash dieback — Hymenoscyphus fraxineus — kills the tree progressively from the crown down. The practical consequence for asset managers is not just tree loss, but brittleness: affected ash sheds limbs and fails at the base with far less warning than a healthy tree, and often outside storm conditions.
A survey therefore records two separate things. The first is the extent of infection, expressed as crown decline. The second is the structural condition of the tree — basal decay, cavities, included unions, lean — which is what usually determines whether it needs work now.
The four-class scale
UK practice has converged on a four-class scale based on the proportion of the crown lost against what the tree would be expected to carry in full leaf:
- Class 1 — under 25% crown decline. Healthy or early infection. Monitor on the normal cycle.
- Class 2 — 25% to 50% decline. Established infection, tree still substantially functional. Re-inspect within 12 months.
- Class 3 — 50% to 75% decline. Significant decline, deadwood accumulating, structural risk rising. Works usually required where a target is present.
- Class 4 — over 75% decline or dead. Brittle and unpredictable. Treated as a priority in high-occupancy zones.
The classes describe the tree, not the risk. A Class 4 ash standing in the middle of an inaccessible woodland is a habitat feature; a Class 3 ash overhanging a live carriageway is an urgent works item. Class must always be combined with the target.
Survey timing
Crown decline can only be assessed properly in full leaf, so the useful survey window in the UK runs from roughly June to September. Winter surveys can confirm dead trees and find lesions, but a class assigned outside the leafed season is not defensible.
This compresses the programme. A network-scale ash survey has, in practice, a four-month annual delivery window — which is why survey throughput per surveyor-day, rather than report quality, is usually the binding constraint.
From class to works priority
The output that funds the next stage is a prioritised works schedule, not a list of classes. Most programmes map to something like:
- Priority 1 — immediate or within weeks: Class 3 or 4 with an occupied target directly below or within falling distance.
- Priority 2 — within the current season: Class 3 with a target, or Class 4 with intermittent exposure.
- Priority 3 — within the programme year: declining trees where the target is minor or seasonal.
- Monitor — retain and re-inspect, including trees showing possible tolerance.
Whatever scheme you use, apply one scheme. Where several contractors survey adjacent sections using their own priority language, the client cannot produce a single ranked programme without a manual reconciliation exercise that costs more than the surveys.
Delivering at network scale
The difficulties on a large ash programme are logistical rather than arboricultural:
- Thousands of assets have to be inspected inside a four-month window, often under traffic management.
- Every tree needs a stable reference that survives across years and contractors.
- Photographic evidence must attach to a specific inspection, not just to the tree.
- Progress has to be visible to the client mid-season, not delivered as a spreadsheet in October.
- Exports must land in the client's own spatial format without rekeying.
These are the points at which spreadsheet-based delivery breaks down — not because teams are careless, but because the volume exceeds what manual reconciliation can absorb. Our National Highways case study walks through how one programme handled it, and the tree safety inspection guide covers what each record needs to contain.
Run your ash programme inside the survey window.
Arbrium is GIS-native and built for high-volume field survey — stable asset references, offline capture, evidence attached to the inspection, and exports in your client's format.
