Why a tool cannot tell you your council's validation list

No drafting tool can tell you your council's local validation list, and any that claims to is guessing. There are around 300 local planning authorities in England, each publishing its own list of supporting documents, each revising it on its own timetable, and none of them publishing it as part of a consistent national dataset. The national requirements are fixed and knowable. The local list is an administrative document sitting on one council's website, in a format that council chose, changed when that council decides to change it.

That is a data problem rather than a modelling problem, and it is worth understanding because it tells you which parts of a scoping exercise you can delegate and which you cannot.

The national list and what it fixes

The Development Management Procedure Order 2015 sets the national validation requirements, and they apply identically everywhere: the form, the fee, the certificates, the plans needed to describe the development, a design and access statement where the Order requires one, and the biodiversity gain information.

A tool can be right about those, because they come from a statutory instrument that changes rarely and is published in one place. The same is true of the national policy framework and of the thresholds in national guidance.

Everything after that is local, and local means published by an authority rather than derived from a rule.

Why local lists differ between neighbouring authorities

Two councils sharing a boundary can ask for materially different document sets for the same scheme, and both can be acting reasonably. The differences come from real things.

Constraints, first. A council over a coalfield asks for a coal mining risk assessment as a matter of course. A London borough with a history of subsidence claims asks for a basement impact assessment on any below-ground work. An authority in a nutrient neutrality catchment asks for a nutrient budget calculation that its neighbour outside the catchment has no interest in.

Then local plan policy. A council with a policy requiring a specified level of on-site carbon reduction will ask for an energy statement at a lower threshold than one relying on Building Regulations alone.

Then supplementary planning documents. A householder design guide, a parking standards document, a shopfront guide: each tends to bring a corresponding submission requirement.

And finally validation practice, which is a matter of how the authority has staffed and organised its registration team, and which produces genuine variation in how strictly the same wording is applied.

How often local lists are revised

Unpredictably. The triggers are the adoption of a new local plan, the adoption of an SPD, the arrival of a new designation such as an Article 4 direction or an Air Quality Management Area, advice from a statutory consultee that changes what the authority needs, and periodic housekeeping.

National guidance makes the timing consequential, because a local list requirement can only be relied on if the list was published within the previous two years. A council whose list has aged past that point is in a weaker position, and applicants who know this ask the question.

What this means in practice: the list you used on a scheme six months ago may not be the list that applies now, even in the same authority. Checking is a task per project, not a task per client.

Where the current list actually lives

There is no single answer, which is the point. The list may be a standalone PDF on the council's planning pages, a page of expandable sections, an appendix to the adopted local plan, a table inside a validation guidance note, or a spreadsheet. Titles vary: local list, local validation requirements, validation checklist, information requirements.

The practical routine is set out in more detail in the piece on finding a local validation list and checking it is current, and the separate question of how to interpret the wording once you have it is covered in reading a council validation list properly.

Do not rely on a cached copy in your practice's server folder without checking the date on the council's site. That is the most common way a practice submits against a superseded list.

Thresholds inside local lists

The thresholds in a local list are where automation goes wrong most often, because they look national and are not.

A tool reading national policy will produce the left-hand column. Your council's registration officer is working from the right-hand column. The gap between them is the reason applications fail validation.

What a tool can usefully do instead

The honest division of labour looks like this.

A tool can identify site constraints from public datasets: flood zone, listed buildings and their grade, conservation area, SSSI, and the like. It can apply national thresholds for major development, transport assessment scale and flood risk. It can propose a starting document set from those constraints and thresholds, and it can draft the documents themselves against national policy and local plan text.

PlanScope's recommendation engine works exactly that way, flagging reports from the constraints it detects and from thresholds such as ten or more units for major development, 1,000m² of floorspace, and Flood Zone 2 or 3. Those are the thresholds PlanScope uses to flag reports, and a council's own validation list and national policy thresholds take precedence over them.

What no tool can do is read the current PDF on one of 300 council websites and tell you it is still the operative version. That check stays with you.

Using the list to scope the document set

1. Download the current local list and record the date it was published and the date you downloaded it.
2. Run the constraint check for the site and note every designation that appears.
3. Map each constraint and each scheme characteristic against the list's triggers, in a table you keep on the file.
4. Where a trigger is ambiguous, ask the case officer or the registration team in writing and keep the reply.
5. Decide which documents you are commissioning, which you are drafting and who reviews each one.
6. Where you are deliberately not submitting something the list mentions, write one line explaining why and put it in the covering letter.

Step six saves more time than the rest combined. A registration officer who can see that you considered an item and explained its absence will usually pick up the phone rather than reject the application.

The cost of getting this wrong is not abstract, and the position on the cost of failing validation and resubmitting sets out what a rejection actually costs in programme terms.

Keeping a record of the version you relied on

Keep the dated PDF, your mapping table, and any written confirmation from the authority, all in the project file rather than in an inbox. If the list changes during determination and an officer asks for something new, a dated copy of what applied at submission is the whole of your argument.

It also protects you professionally. A validation dispute six months later is much easier to handle when you can show what you read and when you read it.

Browse the 66 report types by category to see the document set PlanScope can draft, then check each one against your council's current local list. 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 position with your local planning authority or a qualified professional before relying on it.