Planning readiness: what needs to be nailed down before you submit

People preparing to submit a planning application usually worry about the wrong stage of the process. They worry about whether the design is good enough, which is a real question but a slow-burning one. What actually derails applications in the first few weeks is duller than that: a missing document, a drawing that doesn't match the form, a report that was scoped for a different site than the one being applied for.

Validation and assessment are two different tests, and it's worth understanding the difference before you submit anything.

Validation is not assessment

Validation is an administrative check: does this application contain everything the local list says it must, in the right format, for this type of proposal. It happens before a planning officer ever forms a view on the design. An application that fails validation isn't refused — it's returned, or the clock doesn't start, which in practice is the same delay with less clarity about why.

Assessment is the actual judgement on the merits — whether the scheme is acceptable in planning terms. You want to reach assessment on the first attempt, with a case that's been thought through, rather than losing weeks to a validation bounce that had nothing to do with the design at all.

Check the local validation list, not a generic one

Every local planning authority publishes its own local validation requirements alongside the national minimum list, and they genuinely differ — one authority wants a full arboricultural impact assessment for any tree within influencing distance, another only above a stated threshold; some want a construction management plan submitted at application stage, others only as a condition. Read the specific authority's current list rather than assuming last time's requirements still apply, even if it's the same authority as your last project — lists are updated.

Drawings that agree with each other

This sounds too basic to cause real problems, and yet it's one of the most common validation and assessment issues: the site plan, the floor plans, the elevations and the application form describing slightly different things. A ridge height that doesn't match between the elevation and the section. A parking count on the form that doesn't match what's drawn. A red line boundary that doesn't match the title.

Before submission, cross-check every number that appears more than once across the drawing set and the form. It's a mechanical task, not a design one, and it's the kind of thing that's easy to miss when you've been looking at the same drawings for months and easy to catch with fresh eyes.

Pre-application advice — addressed, not just received

If you've had pre-application advice, the officer's report or letter will usually flag specific concerns. Submitting without visibly responding to each one is a common way to convert a fixable pre-app comment into a formal objection. Where you've disagreed with a piece of advice, say why in the supporting statement rather than silently ignoring it — a reasoned disagreement reads very differently to an officer than an unexplained one.

Neighbour consultation, realistically

Statutory neighbour notification will happen regardless, but it costs little to talk to immediate neighbours before they receive a site notice, particularly on anything with overlooking, boundary proximity or construction access implications. This doesn't stop a genuine objection, but it does reduce the number of objections that are really about not having been told, which are avoidable and which still take an officer's time to read and weigh.

The supporting documents worth scoping properly

Which of these apply depends entirely on the site, but each is commonly required, and each is commonly scoped too narrowly or requested too late to be ready for submission:

• Design and Access Statement — required above certain thresholds, and its content requirements differ by authority
• Flood Risk Assessment — required in Flood Zones 2 and 3, and sometimes in Zone 1 with critical drainage issues
• Arboricultural Impact Assessment / tree survey — required where trees are on or near the site, scoped to BS5837
• Heritage Statement — required near listed buildings or in a conservation area, even if the proposal itself isn't listed
• Ecology report — increasingly requested where habitat, protected species or biodiversity net gain requirements apply
• Transport statement or parking survey — required above certain unit or floor area thresholds, or on constrained access
• Sustainability or energy statement — required by a growing number of authorities regardless of scheme size

Each of these has its own lead time — a tree survey can only be done at certain times of year for full accuracy, an ecology survey may need a specific season for a protected species check — so working out which apply is a task for the start of the design process, not the week before submission.

Conditions you can predict

Look at recent approvals for similar schemes at the same authority and read the conditions attached, not just the decision. Materials samples, construction hours, surface water drainage details, landscaping schemes and contaminated land conditions recur constantly for certain site types. Where you can reasonably anticipate a condition, addressing it in the application itself — rather than leaving it to be imposed and discharged later — can genuinely speed up the pre-construction programme.

A short list to work through before you submit

• Checked this authority's current local validation list, not a remembered or generic one
• Cross-checked every repeated dimension across drawings and the application form
• Addressed every point raised in any pre-application advice, in writing
• Spoken to immediate neighbours ahead of formal notification
• Confirmed which supporting reports apply to this site and that each has been scoped and commissioned with enough lead time
• Reviewed conditions on comparable recent approvals at this authority
• Confirmed the red line matches the title and includes everything the scheme depends on, including the access