The Validation Queue: What Happens When Software Looks at Your Extension First

You upload the drawings at half eleven at night, pay the fee, and get the automatic acknowledgement. A week or so later an email lands: your householder application has been validated.

Most people read that word as "a person has looked at this". Increasingly it means a person has looked at whatever the software flagged. That is the quiet shift in English planning departments, and it is worth understanding before you are the one refreshing the portal every morning.

First, what validation actually is

Validation is the bureaucracy that happens before the argument. Long before a case officer weighs up whether your two-storey rear extension will block next door's kitchen light, somebody has to confirm you sent the right things: the form, the location plan with a properly closed red line, the block plan, existing and proposed elevations, the ownership certificate, the correct fee band, a design and access statement if one is triggered, and whatever else your council's local list demands.

It is a tick-box exercise. Which is exactly why it is the part councils have been keenest to hand to software. Ticking boxes is expensive when a human does it, and it is tedious, and it is the stage where applications sit in a pile for three weeks because someone is on annual leave.

What the kit genuinely checks

Be clear-eyed here: the systems doing the rounds are mostly not making planning judgements. They are doing clerical work at scale.

• Completeness and naming. Does every document on the local list exist, and is it titled the way the council's system expects?
• Geometry of the red line. Is the boundary drawn as a closed shape? Does the stated site area roughly match the polygon? Does that area fall into the fee band you paid for?
• Site context lookups. Does the address match a known property? Does the GIS layer put it in a conservation area, a flood zone, or under an Article 4 direction that removes permitted development rights?
• Cross-checks against the form. Does the description of development match what is described in the plans, and does the number of units on the drawings match the number on the application?
• Duplicate and anomaly spotting. Has this exact application been submitted before? Is the site boundary suspiciously large for a householder scheme?

Some authorities go further and use tools that parse drawings directly, measuring dimensions and comparing them with the figures typed into the form. Those tools are improving, but they are not reliable enough to be the last word, and most councils know it.

What none of this does is decide whether the extension is acceptable. Design quality, neighbour amenity, the character of the street, heritage harm, highway safety, the planning balance — that is judgement, and judgement sits with a named officer, a delegated report, and occasionally a planning committee. Some councils are now trialling AI to draft those reports too. That is a different risk, because the report is the reasoning, and a human still has to own every line of it.

Where the money leaves a trail

If you want to know what your council is running, you generally can. Start with the committee papers behind the digital strategy, then look for a contracts register entry, a published contract on Contracts Finder or Find a Tender if it cleared the threshold, and any data protection impact assessment. Councils are encouraged but not compelled to publish an Algorithmic Transparency Recording Standard entry for tools that touch decisions — central government departments must, local ones mostly haven't.

A freedom of information request asking which software is used at validation, what it checks, and whether any application has been refused or bounced on its output alone will usually get you an answer within the statutory window. Ask specifically about the validation stage; broad questions about "AI in planning" tend to come back as a glossy paragraph about innovation.

The bits that should make you pause

Validation sounds harmless, and mostly it is. But there are edges.

GIS layers are not gospel. Conservation area boundaries in some authorities are digitised from old paper maps and are quietly wrong by a few metres. An Article 4 direction that exists in policy but not in the dataset will not be picked up by anything automated.

Bouncing is a form of power. An application declared invalid stops the clock. If software is over-eager about a missing document that was in fact attached, you lose weeks. Ask for the specific local-list requirement you supposedly failed, in writing, with a reference.

Language and format. Tools that read supporting statements favour clean, well-formatted, standard-English documents. That disadvantages people writing their own application at the kitchen table, and anyone whose first language isn't English.

Historic patterns. Where machine learning creeps in, it learns from past decisions — and past decisions reflect past biases about which areas get extensions approved and which get scrutiny. Postcode effects are real in planning long before any algorithm arrives; software can amplify them by making them faster.

A short checklist for applicants

1. Keep timestamped copies of everything you uploaded. Screenshot the confirmation page.
2. If you are bounced, ask in writing which specific validation requirement was not met, and who or what made that call.
3. Ask whether any part of the assessment was automated, and request a human re-check. UK GDPR Article 22 gives you rights around decisions taken solely by automated means; validation is a murkier area than the decision itself, which is why you ask rather than assume.
4. Get the case officer's name and read the delegated report when it appears — it is a public document.
5. If you are refused and the reasoning reads generically, say so at appeal. The Planning Inspectorate is still a human process, for now.

If you are the neighbour

You have less direct leverage at validation, but not none. When an application appears, read the officer's report rather than just the consultation page, and ask the council whether the site was flagged for conservation area, flood risk or an Article 4 direction. Errors in those layers affect what gets built next to you, not just what gets approved.

The bottom line

No council in the country is having an algorithm decide whether your loft conversion gets consent. What is happening is subtler and more mundane: software is deciding whether your application gets into the queue, how fast, and with what label attached. That is administrative power dressed as admin — and it is worth knowing who holds it, and asking.