Drafted pre-application submissions and what officers read

England has no statutory duty to provide pre-application advice. A council offers it because it chooses to, charges for it under its general power to charge for discretionary services, and can withdraw or ration it when staffing gets tight. That single fact explains most of what frustrates architects about the service: the variable turnaround, the hedged wording, the officer who will not be drawn on the one question you asked.

Write the submission on that understanding and you get more out of it.

No statutory duty, and what follows from that

Scotland and Wales both impose statutory pre-application obligations for certain categories of development, with prescribed consultation and prescribed content. England does not. National guidance encourages early engagement, local plans encourage it, and some authorities operate well-resourced schemes with named officers and committed timescales. None of that creates an entitlement.

The practical consequences are worth stating plainly. The officer is not obliged to answer every question. Consultees are usually not engaged unless you have paid for a service tier that includes them. The advice is given without prejudice to the authority's formal decision and cannot bind the committee, because an authority cannot fetter its discretion in advance.

It is still worth doing on anything beyond the simplest householder scheme. Advice that identifies the policy obstacle, the validation documents and the consultee you had not thought about saves more than it costs, and the comparison between a standard enquiry and a formal agreement is set out in pre-application advice or a planning performance agreement.

What a pre-application request should contain

An officer with a stack of enquiries and a two-week target reads the submission once. Make the material self-explanatory.

• A site location plan with the red line drawn as it will be on the application, and a note of any land in different ownership.
• Site photographs, including the context in both directions along the street and the relationship to the nearest neighbours.
• A short written description with the numbers: units and mix, gross internal floorspace, storeys, parking spaces, site area in hectares.
• Sketch massing, a block plan and at least one section through the site showing levels and the relationship to neighbours.
• The planning history, with references and outcomes, including refusals and appeals.
• The constraints you have already identified, with the source, so the officer corrects or adds rather than starts from scratch.
• A numbered list of specific questions.

That last item does the work. An enquiry that ends "we would welcome your comments" produces comments. An enquiry with six numbered questions produces six answers, or an explanation of why one cannot be answered, which is itself information.

Questions that get a useful answer

Officers can answer questions about policy, process and evidence. Those are the ones to ask.

1. Is the principle of this use on this site acceptable under the adopted plan, and if not, which policy is the obstacle?
2. Which documents on your local validation list will apply to an application of this description?
3. At this scale, would you expect a Transport Assessment or a Transport Statement?
4. Is the harm to the conservation area in your view less than substantial, and roughly where in that spectrum does it sit?
5. What affordable housing tenure split and percentage would you seek, and which policy sets it?
6. Are there site-specific constraints in your records, such as a drainage asset, an archaeological alert area or a recent enforcement history, that are not on the public mapping?
7. Which consultees will you engage, and are there any you would advise approaching directly before submission?

Question six repays the fee on its own more often than people expect. Councils hold information that never reaches a published layer.

Questions that get a holding answer

Anything that asks the officer to pre-judge the decision will come back hedged, and rightly so.

"Will this be approved" cannot be answered. "What will the committee think" cannot be answered, because the officer does not know who will be on it or what the objection pattern will be. "Can you confirm highways have no objection" cannot be answered unless highways has been consulted, which at most fee tiers it has not. "Is the design acceptable" produces a paragraph of generalities, because design is assessed against the scheme as submitted.

Reframe each of them. Instead of asking whether the design is acceptable, ask which elements of the design the officer considers would attract an objection under the named local policy, and what would address it. That question has an answer.

The weight pre-application advice carries later

Pre-application advice is a material consideration of limited weight. It does not bind the authority, and a scheme built exactly to the advice can still be refused, usually because a consultee or a neighbour raised something the officer had not anticipated.

Where it does bite is on consistency. An authority that gives written advice, receives an application that follows it, and then refuses on the very point it advised on is exposed at appeal, and inconsistency of that kind has featured in costs applications. That only works if you have the advice in writing with a date and an officer name.

Ask for the advice in writing. Where a meeting happens, send your own note of what was agreed within two days and ask for confirmation or correction. A note that goes uncorrected is evidence.

Where a draft saves unbilled time, and where it does not

Writing the narrative part of a pre-application submission is unbilled work for most practices, and it is the part a structured draft handles well: the site and context description, the planning history summary, the policy list, the constraints schedule, the description of development. Those are assembly tasks with a known shape.

What a draft cannot do is the judgement. It cannot tell you which of three massing options the officer will prefer, it cannot read the street, and it cannot decide what to concede. The limits are the same ones set out in where site judgement cannot be drafted in a design statement, and they apply with more force at pre-application stage because the questions you ask determine what you get back.

A sensible division of labour is to let the draft assemble the factual sections and write the questions yourself. Where the draft inserts a "[TO BE CONFIRMED]" flag against a missing site fact, resolve it before the enquiry goes in, because an officer who spots an unverified assertion will discount the rest. That tension between structure and evidence is covered in what drafts get right about structure and wrong about evidence.

Recording the advice given

Build a single record per enquiry: the submission as sent, the fee receipt, the written advice, the meeting note, the officer's name, and the date. Keep it with the application file, because you will be quoting from it in the planning statement and possibly in an appeal two years later.

Then write the application to answer the advice explicitly. A short section in the supporting statement that quotes each piece of advice and states what the scheme does about it tells the case officer that the process worked, and it tells an inspector the same thing.

If you are assembling pre-application material and want structured first drafts of the supporting sections, see PlanScope pricing for the one free report, pay per report and Professional options.

This is general guidance, not legal advice. Check the position with your local planning authority or a qualified professional before relying on it. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.