A tree survey rejected at validation means your application was never registered because the council's checklist required arboricultural information it did not receive — it is not a refusal, there is nothing to appeal, and the fix is to supply the missing or corrected documents and resubmit, usually without losing your fee.
This is one of the most common and most frustrating ways a planning application stalls, and it is almost entirely recoverable if you understand what actually happened. Here is the full picture and a step-by-step route back.
Rejected at validation is not the same as refused
The single most important thing to grasp: validation is a completeness check, not a decision. When you submit, the local planning authority (LPA) checks your application against national and local validation requirements before it is formally registered. If the checklist demands arboricultural documents and they are absent or inadequate, the application is deemed invalid — returned to you, never assessed on its merits.
That means:
- There is no appeal — you cannot appeal a non-validation, because no decision was made.
- Your fee is usually held or refunded, because the application was never registered.
- The route forward is simply to fix the gap and resubmit.
So the emotional sting ("rejected!") is worse than the reality. You are at the start line, not the finish. Contrast this with a refusal, which comes after validation and assessment, does carry appeal rights, and puts a negative decision on the planning history of the site. A validation bounce leaves no such mark.
Why tree surveys are the classic validation failure
Councils set their own local validation lists, and nearly all of them require arboricultural information wherever a proposal is on or near trees or likely to affect trees. The trigger is deliberately broad. A representative council wording requires a survey where "there are trees on or overhanging the site" or "the work will impact trees" — and that explicitly includes driveways, patios, drains and utility runs, and neighbouring trees whose root protection areas extend into your site.
The usual reasons a tree survey gets bounced at validation:
| # | Failure mode | What the officer actually saw |
|---|---|---|
| 1 | No survey at all | Trees on/near the site, no arboricultural document — the number-one cause |
| 2 | Survey but no impact assessment | A bare tree schedule with no assessment of your proposed layout against the trees |
| 3 | Off-site trees ignored | A neighbour's tree whose roots or canopy reach into the site was not surveyed |
| 4 | Not to BS5837:2012 | An informal condition report rather than a survey following the expected standard |
| 5 | No tree protection plan | Where the local list demands a TPP at submission and it is absent |
| 6 | Protected status missed | A TPO or conservation-area tree not identified in the report |
| 7 | Unqualified author | A report the tree officer will not give weight to |
Note the mechanism: BS5837 is a British Standard — recommendations, not law. It becomes compulsory here purely because your LPA has adopted it in its validation list. That is why the requirement varies council to council and why the fix always starts with your specific council's list.
A worked example
An applicant submits for a rear extension and a widened driveway. There is a sycamore in the garden and an oak just over the neighbour's fence. They commission a one-page "tree report" from a general contractor that lists the two trees and says both are "healthy." The validation officer invalidates the application within a fortnight for three reasons: the report is not to BS5837:2012, it gives no tree categories (A/B/C/U) and no calculated root protection areas, and it contains no impact assessment showing whether the extension foundations and the impermeable driveway fall inside either tree's RPA. The neighbour's oak is barely mentioned. The applicant re-instructs a qualified arboriculturist, who produces a proper survey plus an arboricultural impact assessment — confirming the driveway sits within the oak's RPA and specifying a no-dig permeable build-up in a method statement. The resubmission validates first time, and no second fee is charged.
Step-by-step: how to recover
Step 1 — Read the invalidation letter closely
The LPA's correspondence states exactly which documents are missing and gives a deadline (often around 21–28 days) to supply them before the application is treated as withdrawn. This letter is your specification. Do not guess at what is wanted — it is written down.
Step 2 — Pull your council's local validation list
Every council publishes a validation checklist. Find the arboricultural / trees section and read the precise trigger and the exact documents required at submission — some want only a survey and impact assessment to validate; others also want a tree protection plan and a preliminary method statement. This tells you whether you need one document or three. Our which LPAs require a tree survey guide explains how to find and read it.
Step 3 — Commission the right documents from a qualified arboriculturist
Instruct a suitably qualified and experienced arboriculturist to produce what the list requires — typically a BS5837 tree survey plus an arboricultural impact assessment, and a tree protection plan if your council wants one upfront. Reports from an Arboricultural Association Registered Consultant or an ICF chartered arboriculturist carry the most weight with a tree officer. A straightforward site is often surveyable year-round and turned around in roughly one to two weeks — a survey does not need leaf-on. See find a tree surveyor and likely costs.
Step 4 — Check off-site and protected trees explicitly
Two things get missed and cause a second rejection:
- Neighbouring trees — make sure any tree whose root protection area (12 × stem diameter) reaches into your site is included, whether or not you own it.
- TPO / conservation area status — run a TPO check so any protection is stated in the report, not discovered later. This is also a criminal-law matter in its own right: consent to touch a protected tree is separate from planning permission.
Step 5 — Resubmit within the deadline
Provide the documents to the validation officer named in your letter, within the stated period. Because the application was never registered, you are completing it, not starting a fresh one — the fee normally carries over.
The one time it is worth pushing back
Occasionally a council flags trees where none are genuinely affected — for example the works are nowhere near any tree or RPA. You can put that case in writing to the validation officer, ideally with a short supporting note from an arboriculturist confirming no tree is within influencing distance. But be realistic: if any tree is affected — including a neighbour's — supplying the survey is faster and cheaper than a protracted argument, and it de-risks the determination that follows.
Requirements are set locally — check your own council
Because validation is a local overlay on the national baseline, what got you invalidated in one district might have sailed through in another, and vice versa. The exact trigger wording, the distance thresholds, whether a full impact assessment and tree protection plan are demanded upfront, and how strict the tree officer is in practice all vary by authority — as does the local density of TPOs and conservation areas. That is precisely why generic advice only takes you so far and the invalidation letter plus your own council's list are the real specification.
PlanWatch tracks live tree-related planning activity per authority, so you can see how your council handles tree matters on real applications near you before you resubmit. Compare how different LPAs behave — for instance Leeds, Manchester, Bristol and Nottingham — or check your own area from the hub. This guidance is England-centric; Scotland, Wales and Northern Ireland operate parallel but distinct tree-protection regimes, though BS5837:2012 applies UK-wide.
Avoid the repeat rejection
The applicants who get stuck are the ones who resubmit a second incomplete package. Before you resend, confirm three things: the report follows BS5837:2012, it includes an impact assessment of your actual layout (not just a tree list), and it covers every affected tree including off-site ones. Get those right and validation is a formality.
Where to go next
- Understand the requirement in full: Tree Surveys for Planning.
- Know what a compliant report contains: What a BS5837 Tree Survey Includes.
- Householder-specific triggers: Tree Survey for a Householder Application.
- Once permission is granted with tree conditions: How to Discharge an Arboricultural Planning Condition.
- Check protection before you build: TPO check.