Almost every local planning authority in England requires a tree survey where a proposal affects trees, but the exact trigger is set locally in each council's validation list rather than by a single national rule. That is why the answer to "does my council need one?" genuinely differs from one authority to the next — and why checking your own council, not a generic checklist, is the only reliable approach.
Why there is no single national answer
There is no national statutory rule that says "a BS5837 tree survey is required." BS5837:2012 is itself only a British Standard — a set of recommendations, not law. The compulsion comes from a different place: Local Validation Lists, the checklists each LPA uses to decide whether an application is complete enough to register. Central government sets a national baseline through Planning Practice Guidance, but the arboricultural detail is a local overlay. Councils add their own triggers, and those triggers are worded differently authority to authority.
The near-universal test is whether a proposal is on or near trees, or likely to affect them. Guildford Borough Council's wording is representative: arboricultural information is required where "there are trees on or overhanging the site" or "the work will impact trees" — explicitly including driveways, patios, drains and utilities, and including neighbouring trees whose root protection areas extend into the site.
That last point catches people out. The root protection area is calculated as a radius of 12 times the tree's stem diameter, so a mature tree just over the boundary can throw an RPA several metres into your site. If your works fall inside it, you are "affecting" that tree even though you never touch it — and the survey requirement bites.
For the full picture of what documents that requirement covers, see our tree survey for planning guide and the BS5837 survey explainer.
Three different sources of compulsion
It helps to separate the reasons a tree can force paperwork on you, because they operate independently:
| Source | What it does | Where it comes from |
|---|---|---|
| Local validation requirement | LPA won't register the application without the arboricultural documents its checklist demands | The council's Local Validation List |
| Planning condition | Permission granted subject to conditions requiring a detailed method statement, TPP or supervision | The decision notice |
| Statutory tree protection | Works to a TPO or conservation-area tree need separate written consent or notice, backed by criminal law | Town and Country Planning Act 1990, 2012 Regulations |
A survey can be triggered by any one of these — or all three at once on the same site. The validation requirement is what most people mean by "does my council require a tree survey", but a Tree Preservation Order applies regardless of whether you are making a planning application at all.
What actually varies between councils
The requirement is set locally, so it really does differ LPA to LPA. The main variables:
- Trigger wording and distance thresholds — some councils spell out exactly how close works must be to a tree before a survey is triggered; others use a broad "likely to affect trees" test. There is no universal numeric distance.
- How much detail is wanted upfront — some LPAs want a full arboricultural impact assessment plus tree protection plan at validation; others accept a survey and impact assessment at submission and condition the arboricultural method statement for later.
- Local TPO density and conservation area coverage — areas with many Tree Preservation Orders or extensive conservation areas add a statutory layer on top of the validation requirement.
- Ancient woodland and veteran trees — where these are present, national policy raises the bar considerably, expecting enhanced buffers (a minimum 15 m from ancient woodland) and treating them as irreplaceable habitat.
- Tree officer strictness — how rigorously the requirement is applied, and how hard the officer negotiates on layout, varies with the individual authority.
Documented examples of council variation
These published documents show how differently authorities set out their rules:
| Council | What they publish |
|---|---|
| Guildford BC | Requires AIA, method statement and tree protection plan where trees are on, overhanging, or impacted by the site; references BS5837:2012 directly |
| Epsom & Ewell BC | "Applications Validation Requirements" list specifying when arboricultural information is needed |
| Stockton-on-Tees BC | Combined National and Local Validation Checklist with its own arboriculture triggers |
| Bradford Council | Maintains a "Local Validation List" setting the level and type of information required |
| West Lindsey DC | Publishes standalone "Tree Survey – Guidance Notes" for applicants |
| Welwyn Hatfield | Publishes "BS5837 Tree Surveys & Development" FAQ guidance |
The pattern is consistent: the national baseline is common, but the arboricultural specifics are a local decision — right down to whether the council publishes a dedicated tree-survey guidance note or buries the requirement in a general validation list.
A worked example: same extension, two councils
Imagine the same rear extension proposal, with a Category B tree just inside the boundary, submitted to two different authorities. Council A's validation list demands a full survey, AIA and tree protection plan before it will validate — so the application sits unregistered until all three are supplied. Council B's list asks only for a survey and impact assessment at submission, and conditions the detailed method statement for discharge after permission. Same trees, same standard, materially different paperwork and timing at the front end. Neither council is wrong; they have simply written their local overlay differently. This is exactly why reading your authority's list, rather than assuming, saves weeks.
How to check your own authority's requirement
- Find the validation list. Search your council's planning pages for its "Local Validation List" or "Local Validation Requirements" document. Many also publish separate tree survey guidance notes.
- Read the trees / arboriculture section. Look for the trigger wording and whether it names specific documents (survey, AIA, TPP, method statement) and any distance threshold.
- Check for TPOs and conservation areas. These are separate, statutory protections that apply regardless of the validation list. Use our Tree Preservation Order check guide to confirm whether your trees are protected.
- When in doubt, ask for pre-application advice. If your site has trees on or near it, an LPA will almost always want arboricultural information, so commissioning a survey early de-risks validation.
You can also compare how tree requirements land in specific places on our per-council pages — for example Leeds, Manchester, Bristol, Lambeth and Nottingham — all linked from the tree surveys hub. Because PlanWatch tracks live planning activity across hundreds of UK local planning authorities, you can watch how tree and arboricultural conditions are being applied on real, comparable applications in your area — useful context for what your own council is likely to expect before you spend a penny on consultants.
Note on Scotland and Wales
This guide is England-centric. Wales, Scotland (under the Town and Country Planning (Scotland) Act 1997) and Northern Ireland run parallel-but-distinct statutory regimes for tree protection and validation. BS5837:2012 itself is a UK-wide British Standard, so the technical survey methodology is the same across nations, but the compulsion mechanics and validation lists differ — check your national and local guidance.
The bottom line
If your proposal is on or near trees, assume you will need a survey and confirm the specifics against your council's validation list. Missing arboricultural documents are the single most common reason tree-affected applications are invalidated. To understand what the full package involves and what it costs, start with our tree survey for planning guide and cost breakdown, or read up on the root protection area that usually drives the whole requirement.