Pre-application advice: what to ask for and what you get

Pre-application advice is worth buying when you ask the right questions, and close to worthless when you ask whether the scheme is acceptable. The response is an officer's opinion, not a decision, and it binds nobody. What it can give you, reliably, is a written list of the documents the council will expect on validation, the policies it will apply, and the two or three points it will push back on. Those three things are what shorten a determination period, and they are what you should be asking for by name.

What pre-application advice is, in law

There is no statutory right to it. Local authorities provide the service under their general power to charge for discretionary services, and each sets its own fee bands, service levels and turnaround times.

National guidance encourages early engagement and treats it as a way of improving the quality of applications and reducing determination times. It also makes clear that any view given is officer advice, given without prejudice to the formal decision, and that it cannot bind the authority or its members.

For major schemes, a planning performance agreement puts the arrangement on a project footing, with an agreed programme, named officers, meeting dates and an extended determination period. Those are worth having on anything with a long consultee list.

What the fee buys

Fee bands are published, usually scaled from householder through minor to major, with higher tiers including a meeting and sometimes a site visit. The turnaround is commonly four to six weeks for smaller schemes and longer for majors.

The output is a written response. Its quality varies more than the fee does, which is why the input you supply matters so much. An officer given a site location plan and a one-line description will produce a paragraph of generalities. An officer given drawings, a constraints plan and six numbered questions will answer the questions.

Statutory consultees run their own pre-application services separately, and several charge. Where a scheme engages the highway authority, the Environment Agency, the lead local flood authority or the conservation officer, ask the council which of those it will consult at pre-application stage, and whether you need to approach them directly.

The package to submit

Send enough for an officer to form a view, and no more.

• A site location plan with the red line as you intend to apply.
• Existing and proposed plans, elevations and a site section, even if they are early.
• A short constraints summary: designations, flood zone, trees, listed buildings nearby, access.
• A description of development in the words you intend to use on the application form.
• Numbered questions, ideally no more than eight.
• Any relevant planning history for the site, with references.

Leave out the visualisations and the marketing narrative. They shift the conversation towards impressions and away from the answers you are paying for.

Questions that get useful answers

Replace the open question with specific ones.

1. Which development plan policies will you apply to this proposal, by number?
2. Which documents on your local validation list will this application require?
3. Do you require a transport statement, an ecology survey or a heritage statement, and at what scope?
4. What parking standard applies, and what cycle parking provision will be sought?
5. Is the scheme community infrastructure levy liable, and at what rate?
6. What affordable housing or financial contributions will be sought, under which policy?
7. Which statutory consultees will you consult, and are there known constraints from any of them?
8. Given the drawings, what are the two or three design points you would want changed before submission?

Each of those has a checkable answer. An officer who cannot answer the second and third is telling you something useful in itself.

The validation list is the prize

For an architect or agent, the single highest-value output is written confirmation of the documents needed for validation.

Local validation lists differ between neighbouring authorities and are updated. Getting the list confirmed for your specific scheme removes the most common cause of delay, which is an application invalidated three weeks after submission for a report nobody expected.

Keep the response. If the application is later held up for a document the pre-application advice did not mention, you have a written basis for asking why. And where the answer confirms that a technical report is needed, you can commission it during the pre-application period rather than after submission, which is often the difference between a decision in eight weeks and a decision in sixteen. The 66 report types show what each of those documents covers.

One habit is worth adopting on every enquiry. Ask the officer to confirm, in the response, the date on which the advice was given and the version of the development plan it was based on. Plans get adopted, supplementary documents get replaced, and advice that was sound in March can be out of date by the autumn. Where a scheme sits still for a year between pre-application and submission, go back and ask whether anything has changed rather than submitting on the strength of the old letter.

Confidentiality and disclosure

Assume the advice may become public. Councils hold pre-application correspondence and it can be requested under freedom of information and environmental information legislation. Authorities will consider commercial confidentiality, and some will withhold on that basis for a period, but a request for confidentiality is not a guarantee.

Two practical consequences follow. Do not put anything in the submission you would not want an objector to read, including your view of the site's weaknesses or your fallback position. And where a site assembly or a land transaction is sensitive, ask the authority in writing how it handles confidentiality before you submit.

Using the advice afterwards

Respond to it in the application rather than filing it.

The most effective move is a short table in the Planning Statement listing each point raised at pre-application, what you did about it, and where in the submission the response sits. Officers read that first, and it converts your fee into a shorter case officer report.

Where you disagree with a point, say so and explain why, with the policy reasoning. Silently ignoring advice is the option that guarantees the point reappears as a reason for refusal.

Pre-application advice carries limited weight at appeal, since it is not a decision. It is not irrelevant either. Where a council advised that a design approach was acceptable and then refused on that same point without an explanation for the change, the inconsistency is worth raising, and a costs application on unreasonable behaviour is at least arguable. Keep the correspondence, dated, with the officer's name.

A well-run pre-application also tells you when to stop. If the officer's view is that the principle conflicts with an up-to-date plan policy and there is no material consideration to outweigh it, the honest reading is that the scheme needs to change rather than that the argument needs to be better. A Design and Access Statement that documents how the design responded to that advice is far stronger than one written as though the conversation never happened.

This is general guidance rather than legal advice. Fees, service levels and validation lists differ between authorities, so check the position with your local planning authority 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.