Editing a draft to match a local validation checklist

A local validation checklist is the list of documents a particular authority requires on top of the national requirements, and it is the reason an application prepared perfectly well for one council gets returned by the next. Editing a drafted document set to match it is a mechanical exercise, but it has to be done against the current published list, because the items change and the version saved on your server from the last job is probably out of date.

Two thirds of validation failures are administrative rather than technical. A missing certificate, a plan without a scale bar, a document named in a way the authority's system rejects.

Finding the current local list

Authorities must publish their local list, and Planning Practice Guidance expects it to be reviewed regularly, generally at least every two years. Find the published version with its date on the council's own website rather than working from a copy.

Two checks are worth making every time. Is the list in date, and does the authority operate different lists for different application types. Many do, with separate requirements for householder, minor, major and listed building consent applications, and the householder list is often much shorter than people assume.

Where the list is more than two years old, that is a fair point to make if the authority later insists on an item that is no longer justified. The requirement has to be reasonable, and relevant to the application in question.

Mapping each requirement to a document

Build a two-column table before touching the drafts. Left column, every item on the national and local lists. Right column, the document in your set that answers it, with its filename.

The mapping exposes three things quickly. Items with no document, which is the obvious gap. Documents with no item, which are either useful additions or clutter. And items answered by half of a document, which is the difficult case.

That third case is where most editing time goes. An authority asking separately for a sustainability statement and an energy statement will not accept one document labelled as both, even where the content covers everything. Split it, retitle each part, and cross-reference. Where a Planning Statement covers policy compliance and the local list also asks for a separate affordable housing statement, the affordable housing content has to come out into its own file.

Thresholds inside the local list

Local lists are full of conditional requirements. A tree survey where trees are within a stated distance of the works. A transport statement above a floorspace figure. A daylight assessment where a scheme exceeds a given height or sits within a set distance of residential windows.

Read the trigger, not the heading. A requirement that reads "where the site is within 250 metres of a watercourse" needs measuring rather than guessing, and the measurement should be recorded so you can justify the answer later.

Thresholds also interact with national requirements. A Design and Access Statement is required nationally for major development and for certain applications in designated areas, and the local list may add categories on top. Satisfy both.

Naming and formatting so the file is accepted

This is the dull part that causes the delays. Most authorities publish a document naming convention, and their systems reject or mislabel files that do not follow it.

Five rules cover almost every authority.

1. Name each file for what it is, using the authority's own terminology from the local list.
2. Include the drawing number and revision in the filename for every drawing.
3. Submit one document per file rather than a merged bundle, unless the authority asks for a bundle.
4. Keep each file inside the portal's size limit, and check the current limit rather than assuming.
5. Use a consistent scale bar and north point on every plan, and never submit a drawing marked as not to scale where a scale is required.

Drawings are the usual casualty. A location plan at the wrong scale, or a site plan showing the red line around the building rather than around the whole application site including the access, is a same-day rejection at most councils.

Explaining why a listed document is not needed

You are allowed to say a requirement does not apply. Do it properly, in writing, in a short covering letter rather than by silence.

State the item, state why it is not engaged, and give the evidence. "The local list requires an arboricultural impact assessment where works fall within the root protection area of a tree over 150 mm in diameter. The nearest such tree is 14 metres from the proposed foundations, as shown on drawing 104 rev B, so no assessment is submitted."

Silence gets the application returned. A reasoned explanation gets a phone call at worst. Validation officers are generally willing to accept a justified omission and generally unwilling to chase an applicant who has simply left something out.

Pre-validation enquiries that save a week

Several authorities offer an informal document check before submission, sometimes free, sometimes as part of a pre-application service. Where it exists, use it.

Where it does not, an email to the validation team listing your proposed document schedule and asking whether anything is missing usually gets an answer within a week. That costs less than a return, because a returned application loses its place in the queue entirely and the fee has to be re-paid in some systems.

Ask specifically about the items you have omitted and the reasons, rather than sending a generic list.

Keep the reply. If the application is later returned for an item the validation team told you was not needed, the email settles it in one exchange rather than three.

Keeping a reusable checklist per authority

Build a file per authority and keep it current. Record the local list version and date, the naming convention, the portal quirks, the validation officer's preferences and anything that went wrong last time.

Review it at the start of each job rather than trusting it. Lists change, and an authority that merged with a neighbour will often have two inherited lists running in parallel for a period.

The file pays for itself on the second application to the same council. It pays for itself twice over when a colleague picks up a job in an area they have never worked in and finds the quirks already written down.

An AI-assisted draft gives you the content quickly. Matching it to a specific authority's list is judgement work: deciding which requirements are engaged, splitting documents, writing the justification for omissions. PlanScope drafts are structured to UK planning policy and flag where site facts are missing, and they still need that local mapping done by someone who has read the council's list.

Where a document needs a qualified author, the reviewers in the professional directory are the route to sign-off, and the pricing page sets out what a draft costs before that step.

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.