Validation failures caused by generic supporting statements
A supporting statement that could describe any site is the most common avoidable validation failure. The fix is mechanical: tie every section to this address, these constraints and these policies.
The quickest way to lose three weeks on a planning application is to submit a supporting statement that could describe any site in England. Validation officers see hundreds of these, and the tells are obvious: no site address in the body text, policy references from the wrong authority, a constraints section that lists what might apply rather than what does, and no engagement with the specific reason the local list asked for the document. Planning application validation failure on a statement is rarely about length or polish. It is about whether the document is about this site.
Validation is a procedural check, not a judgement on the merits. The officer is asking whether the submission contains what the national requirements and the authority's published local list require. That makes the failure both avoidable and irritating, because nothing about the scheme has been assessed at the point it is returned.
How validation works and who does it
The national requirements come from Article 7 of the Town and Country Planning (Development Management Procedure) (England) Order 2015: the correct form, the fee, the plans, the ownership certificate and agricultural holdings declaration, a design and access statement where one is required, and since 2024 a statement on whether the biodiversity gain condition applies.
On top of that sits the local list. Section 62 of the Town and Country Planning Act 1990 lets an authority require additional information, provided the requirement is published, reasonable having regard to the nature and scale of the development, and about a matter material to the application. The Planning Practice Guidance expects local lists to be published on the authority's website and reviewed at least every two years.
The check is usually done by a validation or technical support officer rather than the case officer. That matters more than people expect. The validation officer is working through a checklist and is not in a position to make a planning judgement about whether your heritage paragraph is good enough. If the list says a heritage statement is required and the document does not identify itself as one, it fails, even where the content is buried inside the planning statement.
Local list requirements beyond the national list
Local lists vary widely in length and in trigger thresholds. Common items include a heritage statement for anything affecting a designated or non-designated heritage asset, an arboricultural report where trees are within influencing distance, a flood risk assessment below the national threshold in critical drainage areas, a parking survey for conversions in controlled parking zones, and a land contamination desk study for any site with a potentially contaminative former use.
Two practical points. The trigger is what to check, not the document title, because the same requirement appears under different names across authorities. And where an item is listed but you believe it is not necessary for your scheme, say so in the covering letter with reasons, rather than staying silent and hoping. The guidance is clear that requirements must be reasonable and proportionate, and a reasoned explanation is easier for a validation officer to accept than a gap.
Browse the full list of report types if you are trying to work out which document a local list item corresponds to.
What makes a statement fail as not site specific
Here is the checklist a validation officer is effectively running, whether or not it is written down anywhere.
- Does the document name the application site, by address and where relevant by ordnance survey reference, in the body text and not only on the cover?
- Does the description of development match the application form exactly?
- Does it cite the adopted development plan for this authority, with policy numbers, rather than national policy alone?
- Does the constraints section state which designations apply to this site, and which were checked and found not to apply?
- Does it respond to the specific local list trigger that caused the document to be required?
- Does it reference the submitted drawings by number and revision?
A Planning Statement that fails several of those reads as a template regardless of how well written it is. The commonest single failure is the constraints section: a list of every designation in the national system, with none identified as present or absent on this site.
The second commonest is policy. Citing the National Planning Policy Framework without the local plan is not enough, because section 38(6) of the Planning and Compulsory Purchase Act 2004 makes the development plan the starting point. Cite the current edition of the Framework when you use it, since the policy structure has changed twice in recent years and copying paragraph numbers from an older document is an easy way to look careless.
What an invalid application costs in programme terms
The arithmetic is worse than most clients assume.
| Stage | Effect of invalidity |
|---|---|
| Determination clock | Does not start until the application is valid |
| Consultation | Publicity and statutory consultation cannot begin |
| Committee | Slot lost, next cycle typically a month later |
| Fee | May be returned, requiring resubmission rather than correction |
| Client relationship | The delay is visible and attributable |
In practice a returned application on a minor scheme costs two to four weeks before the eight week period even starts. On a major going to committee, the loss is usually a full cycle. None of that time buys anything.
Fixing a rejected document quickly
Work from the authority's own words. The validation email or letter will name the deficiency, and the fastest route is to answer it literally rather than rewriting the document.
Insert a site identification section at the front with the address, the site area, the description of development as applied for, and the drawing schedule. Add a constraints table that names each designation checked, the source checked, the date checked and the result. Add the local plan policy references with numbers and the plan's adoption date. Then add a short section headed to match the local list item, so the officer can find it without reading the whole document.
Resubmit with a covering note that maps each point raised to the page where it is now answered. Validation officers have a queue, and a submission they can clear in two minutes gets cleared.
Building a validation check into your own process
The structural fix is to separate drafting from checking. Whoever writes the statement should not be the person who ticks it against the local list, because the writer has already convinced themselves.
A workable process runs: download the current local list from the authority's website on the day of submission rather than relying on a saved copy, record the constraint checks with source and date as you do them, draft, then run an independent check against the list and against the six questions above.
This is also the honest limit of AI-assisted drafting, and it is worth naming plainly. A drafting tool can produce a well structured document quickly and can be grounded in national policy and local plan text, but it cannot know your site's constraints unless it is told or unless it checks a dataset. PlanScope handles that by checking the site against flood, heritage and designation data automatically and by inserting a [TO BE CONFIRMED] flag wherever a site fact is missing rather than filling the gap with something plausible. Those flags are the point: they are a list of what a human has to supply before submission, and a document that still carries them is not ready to go in.
For a second pair of eyes on a draft before submission, the professional directory is the route to a reviewer, and the pricing page sets out the tiers, including the Professional option for agents producing documents at volume.
Where authorities differ and why
Local list variation is not arbitrary. An authority with extensive conservation areas asks for heritage information at a lower threshold. An authority with widespread surface water flooding asks for drainage information below the national flood zone trigger. A university city with houses in multiple occupation pressure asks for parking surveys and amenity evidence that a rural district never requests.
Reading the local list against the authority's constraints tells you what it cares about, which is also a reasonable guide to what the case officer will focus on after validation. That is a better use of half an hour than reformatting a template.
PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. This is general guidance, not legal advice: check the current validation requirements with your local planning authority before relying on it.
Frequently asked questions
Can a council refuse to validate for something not on its local list?
The Planning Practice Guidance expects authorities to publish their local requirements and to keep them to matters that are reasonable and proportionate to the development. If an item is being requested that does not appear on the published list, raise it with the validation team in writing and ask which published requirement it corresponds to, before resubmitting.
How long does an invalid application delay a scheme?
On a minor application, usually two to four weeks before the eight week determination period even begins, because the clock does not start until the submission is valid. On a major going to planning committee, the practical loss is normally a full committee cycle, which in most authorities is a month. The delay buys nothing.
What makes a supporting statement site specific?
Naming the site address in the body text, matching the description of development to the application form, citing the adopted local plan policies by number, stating which designations apply and which were checked and found absent, referencing the submitted drawings by number and revision, and answering the specific local list requirement that triggered the document.
Do I still need a design and access statement?
It depends on the development. Article 9 of the Development Management Procedure Order requires one for major development and for certain development in conservation areas and World Heritage Sites, and separately for listed building consent applications. Check both the Order and the authority's local list, since some authorities ask for design information on smaller schemes as a local requirement.
Can an AI-drafted statement be validated?
There is no rule against how a document is produced. Whether it validates depends on whether it contains the required, site-specific content. Drafts that carry unresolved placeholders, generic constraint lists or policy references from the wrong authority fail for the same reasons a human template fails. Resolve every flagged gap and have the document reviewed before submission.
Sources and further reading
This article is general guidance about the planning system in England and, where stated, the rest of the UK. It is not legal or professional advice. Check your local planning authority’s validation requirements and take professional advice for your specific site.