If fixing planning was easy, it would have been done already

Planning submission looks like a solved problem until you have to do it properly.

From the outside, it’s uploading drawings, filling out fields, paying a fee, and clicking submit. From the inside, it’s a compliance gate that has to satisfy statutory requirements, local validation checklists, public transparency, and professional liability at the same time.

That’s why it still feels heavier than it should. The job of a planning submission system is not just to collect information. It has to produce a record a local authority can validate, register, consult on, and determine, without creating holes you discover later.

UK Planning Gateway exists because we think that can be done with far less friction for professionals, without pretending the underlying system is simple.

Planning is a system, not a form

A planning application isn’t “data entry”. It’s the point where multiple parts of the planning system collide.

There are legal and procedural rules about what must be on the public record. There are national expectations, then local policy and validation checklists that turn those expectations into practical requirements. Case officers need information in a form they can assess and defend. Neighbours need documents they can read. Applicants and agents need a clear audit trail, because planning is one of the few admin processes where a missing certificate or a wrong plan can derail weeks of programme.

If you simplify the surface without respecting those constraints, you don’t get a cleaner process. You get a submission that looks fine until it hits validation, then comes back with a list of issues that were predictable on day one.

Why “digitising paperwork” hit a ceiling

Most digital submission work has been framed as moving paper online. That does help, but it caps out quickly.

If the workflow still makes professionals re-enter known information, interpret local validation rules themselves, and only discover missing items after submission, the time cost stays where it has always been. It just becomes browser-based admin.

You see the symptoms everywhere. Avoidable invalidations. “Please resubmit” emails. Plans named five different ways across the same project. A location plan that’s technically there, but not to the scale the council’s checklist expects. Certificates ticked incorrectly. Fee issues discovered after the file has sat in a queue.

The gap isn’t effort. It’s early feedback. A modern system should catch repeat problems before the application leaves the building.

The constraint people avoid saying out loud

Planning submission systems are usually designed around institutional needs first.

That isn’t a moral failing. It’s what happens when you build around statutory process, procurement, and risk. But it does have knock-on effects for practices and agents.

Admin time gets pushed onto applicants and professionals because it doesn’t show up neatly on an authority budget line. Validation becomes a downstream policing step rather than an upstream quality step. User experience rarely gets measured as an outcome, partly because choice is limited in a statutory environment.

This is a big reason change is slow. In most software markets, bad UX loses users. In planning, users often just endure it.

What actually makes submission faster without lowering standards

Real improvement rarely comes from prettier pages or longer help text. It comes from removing ambiguity and preventing rework.

That usually looks like:

• catching common omissions before submission, not after
• prompting against local checklist rules where they are specific (without bluffing)
• producing consistent outputs that officers can rely on, including clearer document sets, naming, and metadata
• keeping a clean audit trail, so professionals can prove what was submitted and when

This is what “professional-first” means in practice. Not skipping requirements, but reducing the time wasted on avoidable loops.

Reform that survives contact with reality looks boring, on purpose

There’s a type of “reform” that sounds great in a pitch deck and falls apart in real submissions. It treats planning like a neglected web form, then assumes the fix is mostly a better interface.

Planning is complex for reasons that aren’t going away: public accountability, legal challenge risk, local discretion, and policy nuance. The job isn’t to deny that reality. The job is to make the submission process behave like modern infrastructure while staying legible to the planning system it serves.

If a platform can reduce invalidation risk, reduce duplication, and make the record more consistent, it’s doing the right kind of work, even if the changes look unglamorous.

Takeaway

Planning submission is hard because the underlying job is hard. It sits on statutory process, local interpretation, professional liability, and public record requirements.

The route to “better” is not wishful simplification. It’s prevention before submission, local checklist awareness, consistent outputs, and a defensible audit trail.

Frequently asked questions

Why do planning applications get invalidated so often?

Most invalidations come down to missing documents, incorrect plans, incomplete certificates, or mismatches with the council’s validation checklist. The frustrating bit is that many of these issues are predictable at upload if the workflow checks for them early. See our guide on planning application invalidation.

Are planning validation requirements the same everywhere?

No. There is national guidance, but local planning authorities publish their own validation checklists and local requirements. Professionals get caught when a “standard” document set doesn’t meet a specific council checklist. See our page on local validation requirements.

What does “professional-first submission” mean?

It means designing around professional workflows: reuse of known data, predictable document sets, consistent naming, and validation checks before submission rather than after.

Does making submission easier mean lowering standards?

It shouldn’t. The best systems reduce rework while keeping the public record complete, consistent, and defensible for officers, consultees and applicants.

What is the biggest time-waster in planning submissions?

Rework after submission. Invalidation cycles, clarification requests, and chasing missing items that could have been flagged before the application went in.

Is there a way to reduce invalidation risk without slowing down?

Yes. Upfront checks and local checklist awareness are faster than “find out later” fixes. A good Planning Portal alternative should reduce those loops, not create new ones.