By Michael Kalam
Founder, UK Planning Gateway

Every senior architect, planner and Chartered Technician knows the message.

“Your application has been deemed invalid.”

Most of the time, that is not a design problem. It is not a question of planning merit, and it is rarely about professional judgement. It is administrative non-alignment: the submission pack does not match what that Local Planning Authority (LPA) expects at validation.

The consequences are real and routine: lost billable time, programme delay, client exposure, strained relationships with LPAs, and a quiet erosion of professional credibility.

Recent commentary from No5 Barristers’ Chambers is a useful reminder that validation is not a procedural nicety. In their “Solid foundations” series, they highlight the legal risk that arises when an authority treats an invalid application as valid, including the potential for challenge.

That legal dimension matters, but invalidation is not primarily a legal event.

It is an operational systems failure.

Why it happens so often

National application forms are standardised. Validation requirements are not.

LPAs can require additional information through their published “local list” of validation requirements, where it is reasonable to do so. In Wales, there is long-standing guidance on lists of validation requirements and the supporting information that may be needed for an application to be made valid.

In practice, that means each authority maintains its own working expectations, typically including:

 

• • local list documentation and guidance notes

• • supplementary triggers (often tied to heritage, highways, flood risk, ecology, BNG and other constraints)

• • specific document naming and packaging conventions

• • interpretation that evolves over time as policy, evidence standards and local capacity shift

The professional obligation is clear: applicants must comply with published requirements. The structural problem is also clear: there is no governing pre-submission standard that makes that compliance predictable across authorities.

So compliance is interpreted manually at the point of submission, often under time pressure, and often with avoidable ambiguity. That is where volatility enters the process.

The real cost of submission volatility

An invalid application does not simply “pause” a project. It resets timelines and creates follow-on friction:

 

• • validation clocks restart or extend

• • documents need rework and reissue

• • clients need an explanation, sometimes more than once

• • internal workflows lose sequence

• • uncertainty grows inside the LPA queue as the case re-enters the intake process

In many practices, an invalidation can easily consume an hour or more of corrective administration once you include identifying the issue, rechecking requirements, amending drawings or forms, renaming files, re-exporting PDFs, re-uploading, and documenting what changed.

The less visible cost is reputational. Repeated non-alignment with published requirements can shape how a practice is perceived within LPA teams. Invalidation is not a minor inconvenience. It is a preventable instability in a regulated process.

The missing layer: governing pre-submission standards

What the planning ecosystem lacks is a national pre-submission validation control layer. Something that sits before authority intake and makes “meets the published checklist” a controlled, auditable step, not a reactive scramble.

UK Planning Gateway is being built to operate as that layer: a structured way to align submission packs against published LPA validation requirements across England and Wales.

This is not about giving planning advice. It is not about second-guessing professional judgement. It is about governing preparation.

In practical terms, a pre-submission validation layer focuses on process controls such as:

 

• • aligning a submission pack to the authority’s published validation checklist and local list

• • surfacing likely trigger documents before upload, not after rejection

• • standardising file structure and naming conventions to match authority expectations

• • applying structured checks before files enter an LPA system

• • maintaining an audit trail of what was prepared, when, and against which published requirement set

The point is not to replace the professional. It is to remove avoidable volatility from a process that is meant to be regulated, repeatable and fair.

From administrative reaction to controlled submission

Historically, validation has been reactive:

Submit. Wait. Receive invalidation. Correct. Resubmit.

That sequence is not a standard. It is a failure mode that has become normalised.

Infrastructure changes the sequence by introducing pre-flight controls before intake. The objective is not speed for its own sake. It is predictability: predictable validation, predictable workflow sequencing, predictable professional standards.

National infrastructure, not a productivity tool

Planning submission systems are often treated as simple mailboxes. They move files from applicant to authority.

The harder problem is governing what goes into the mailbox.

A structured pre-submission layer is institutional in nature because it is built around published requirements, process traceability, and the accumulation of validation intelligence over time.

As validation data is captured and compared across authorities, patterns can become visible at a system level: recurring checklist misalignments, common trigger points, and avoidable friction at intake. That is the kind of insight that supports better standards, not just faster uploads.

First-time-right should be the baseline

Invalidation should not be normalised. It is a signal that the system has tolerated misalignment between published requirements and submission control.

A regulated planning process needs clear standards, structured compliance, and validation intelligence that improves repeatability.

First-time-right should not be aspirational. It should be the operational baseline. That baseline requires governance.