Building an internal review checklist for submissions

The applications that fail at validation almost never fail on planning judgement. They fail because the red line on the location plan excludes the access strip, because the area schedule says 148 m2 and the floor plans add up to 152 m2, or because nobody ticked Certificate B when the land is in joint names. Those are process failures, and process failures are fixed with a checklist rather than with more experience.

A practice that submits more than a handful of applications a year should have one written down, used every time, and signed.

Why a checklist beats a careful read

A careful read is a single pass by a person who already knows what the document is meant to say, which is precisely the condition under which the eye skips over an error. A checklist forces a different mode: item by item, against the drawing rather than against memory.

The discipline comes from aviation and surgery rather than from planning, and the finding in both fields is the same. Checklists catch the routine omissions that experienced people make when tired or busy. They do not catch design errors, and they are not a substitute for someone who understands the scheme.

Keep it short enough to be used. A 90-item list gets ticked without being read. Thirty items that actually fail sometimes is a working document.

The factual checks that happen every time

These are the items a validation officer checks, and every one of them has stopped an application somewhere.

• The site address, postcode and any unit or plot numbering match across the form, the drawings and the statements
• The red line includes everything the development needs, including access, visibility splays and any land for drainage or bin storage, and the blue line covers other land in the applicant's control
• The location plan is at a recognised scale with a north point and a scale bar, and the site is edged red on an up to date base
• The correct ownership certificate is signed, with notice served on any other owner and the agricultural holdings declaration completed
• Existing and proposed floor areas are stated on one consistent basis, with the basis named
• Drawing numbers and revisions listed in the covering schedule match the drawings actually uploaded
• The application type, description of development and fee category agree with each other

The drawing schedule item is worth its own line in the procedure. More applications are delayed by a missing revision letter than by anything in the planning statement.

The policy checks and who does them

Policy checking is a different skill and usually a different person. The reviewer confirms that the development plan cited is the adopted one, that the policy numbers quoted exist in that version, and that any national policy reference matches the current edition rather than the one in an old template.

That last point has bitten a lot of practices recently. The National Planning Policy Framework was reissued in December 2024 with renumbered paragraphs and again on 17 August 2026 with policy-coded chapters, so a citation copied from a two year old statement is now wrong on its face. Open the current Framework and check the reference you are about to publish.

The same applies to drafts produced with AI assistance. A Planning Statement generated from a structured brief will cite policy confidently, and confident citation is exactly what needs verifying. Treat every policy reference in a draft as unverified until someone has opened the source.

Consistency checks across the document set

This is where most practices lose time, because the error is invisible in any single document and obvious when two are put side by side.

Check that the unit count, storey heights, floor areas, parking numbers and materials described in the design and access statement match the drawings. Check that the planning statement describes the same scheme as the form. Check that any specialist report was written against the current drawing revision rather than the one issued three weeks earlier, which is the single most common source of contradiction in a submission.

A Design and Access Statement is particularly prone to this because it is often drafted early and not revisited after the design changes. Date it, version it, and reissue it when the scheme moves.

Where a draft carries a placeholder, deal with it. Structured drafting tools insert flags such as "[TO BE CONFIRMED]" where site-specific facts are missing, which is a safeguard rather than a defect, and the checklist item is simply that no flag survives into the submitted document.

Validation checks against the local list

Every authority publishes a local list of requirements in addition to the national ones, and the lists differ enough that a practice working across three boroughs needs three versions of this section.

Download the current local list for the authority, not the one saved last year, and work down it. Note the items that apply only above a threshold, because that is where the arguments happen: a tree survey required where any tree within a stated distance is affected, a drainage assessment above a site area, a heritage statement where the site is within a set distance of a listed building.

Where you think an item does not apply, record why in the covering letter rather than leaving the officer to guess. That one habit prevents a large share of invalidation notices.

Recording sign off and who gave it

The record matters for two reasons: it tells you who to ask when a question arrives six months later, and it tells you where the procedure failed when something goes wrong.

Keep it simple. A single sheet per application listing each checklist section, the initials of the person who completed it, the date, and the drawing revision current at that moment. Store it with the submission rather than in a separate quality folder nobody opens.

For report types where a licensed or competent professional is legally required, the record should name that person and the basis of their competence. A biodiversity net gain assessment under the Environment Act 2021, a protected species survey requiring a licensed ecologist, a fire statement under the Building Safety Act 2022 framework: in each case the question of who signed is the question the council will ask. Reviewers who take on that sign-off role are listed in the professional directory.

Reviewing the checklist after a refusal

Treat every invalidation and every refusal as data about the procedure rather than only about the scheme.

After each one, ask whether a checklist item would have caught it. If yes, find out why the item was ticked. If no, consider adding one, then delete an item that has never failed to keep the list at a usable length. Do this quarterly rather than after every bad day.

And keep the list in one place that everyone edits, rather than in a personal folder. A checklist that exists in four versions is four different procedures.

For practices producing several submissions a month, the economics of the review time are worth looking at alongside PlanScope pricing, since drafting time and review time trade off against each other rather than adding up.

This is general guidance, not legal advice. Check validation requirements with your local planning authority before relying on any list.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.