Pre-app advice: what a council officer can and cannot promise

Pre-application advice carries no legal weight. An officer's written response is an opinion given without prejudice to the council's formal decision, and the pre-application advice weight an inspector will give it at appeal is close to nothing on its own. That does not make pre-app worthless. It makes the value sit somewhere other than where most applicants look for it: in the factual admissions, the policy list and the consultee positions you can extract and then evidence in your own submission.

Officers know this. Their standard caveat says so in the first paragraph. The skill is knowing what an officer is actually able to commit to, what they are only forecasting, and how to convert the second kind of statement into something that survives a change of case officer.

The status of written officer advice

Section 70 of the Town and Country Planning Act 1990 and section 38(6) of the Planning and Compulsory Purchase Act 2004 put the decision in the hands of the authority, determined against the development plan unless material considerations indicate otherwise. No officer can bind that decision in advance. Nor can they bind the planning committee, which is free to depart from an officer recommendation entirely.

So a written pre-app response is evidence of one professional's reading of policy on a given day. Where it helps is narrower and more useful than a promise:

• Confirmation of which development plan policies the council considers engaged, and which it does not.
• Confirmation of the validation requirements the council will apply to your description of development.
• A statement of the constraints the council has on record for the site, including anything its own records show that public datasets do not.
• The officer's view of the principal harms, which tells you where to spend the evidence budget.

The last one is the reason most consultants pay the fee. If the officer flags overlooking as the issue and says nothing about parking, you now know that a daylight and amenity case matters more than a parking survey. That is a scoping decision, and it is worth having in writing even though it binds nobody.

Why the caveat wording matters at appeal

Read the caveat rather than skipping it. Most councils use wording to the effect that advice is informal, given without prejudice, based on the information supplied, and does not constitute a decision. Some go further and state that advice expires after a fixed period or is superseded by any change in the development plan.

That expiry line matters. If you obtain advice, sit on it for eighteen months and submit into a newly adopted local plan, the response is not merely stale, the council has already told you it no longer applies. Inspectors treat officer advice as a material consideration of limited weight, and they weigh it less again where the applicant has not acted on it or where the policy background has moved.

Where advice does bite is in inconsistency. If a council granted a comparable scheme, told you in pre-app that your version was acceptable in principle, and then refused it on that very principle, you have a fairness argument to run and, in the right circumstances, a costs application. That is a narrow route and it depends on the advice being specific. Vague encouragement will not carry it.

Planning performance agreements on larger schemes

A planning performance agreement is a different instrument. It is a project management document between applicant and authority setting out the scope of work, the meetings, the officer time and the timetable through validation to decision. It does not buy a decision and it must not look as though it does.

What it buys is programme certainty and named people. For a scheme of any size, the value sits in three places: an agreed list of the technical documents the council will expect at validation, named officers across planning, highways, environmental health and urban design, and a date-stamped timetable that both sides have signed. Extensions of time under a PPA are agreed in advance rather than negotiated in the eighth week.

The trap is scope creep. A PPA that lists monthly meetings and no deliverables produces a large invoice and a thin file. Write deliverables into it: a written response after each meeting, a schedule of local validation requirements, and confirmation of whether the application is likely to go to committee. Our guide to how committee and delegated decisions are allocated sets out why that last point changes your programme by several weeks.

Getting statutory consultees into the room

The pre-app response you actually want is rarely from the planning officer alone. Highways, the lead local flood authority, the conservation officer and environmental health are the people who write the objections that get quoted in refusal reasons.

Councils vary in whether pre-app fees cover internal consultee input, and many charge separately for it. Ask before you pay. Then ask for the consultee comments to be passed on verbatim rather than summarised, because a summary loses the technical qualifier that tells you what evidence would satisfy them.

For heritage constraints the sequence works better in the other direction. Get the conservation officer's view of significance first, then design, then return to planning. Articles on using conservation area appraisals to justify a design explain why an appraisal quoted back at the officer usually lands harder than a general appeal to context.

External statutory consultees, the Environment Agency, Historic England, National Highways, run their own pre-application services with their own fees and timescales. They are outside the council's process and their response times are not the council's to promise.

Turning advice into an evidenced design change

An officer's comment becomes useful the moment you can point to a drawing that answers it. The pattern that works is a short table in the planning statement: the advice given, the date, the change made, the drawing number. It takes twenty minutes and it does two things. It shows the determining officer that the scheme in front of them is not the scheme that was criticised. And it protects you when the case officer changes between pre-app and determination, which happens more often than anyone plans for.

Do not overclaim. Writing that the council supported the scheme at pre-app when the letter said the principle appeared acceptable subject to design and highways will be checked, and the correction will appear in the officer report. Quote the sentence rather than characterising it.

Where the advice identifies a technical gap, name the document you are supplying against it. Linking each pre-app point to a named report from the 66 report types is a faster way to close out a validation list than writing more narrative.

When to skip pre-application entirely

Pre-app is not free, and for some applications it costs more than it returns. Skip it where the proposal is a straightforward householder application in an unconstrained location, where the fee approaches the application fee itself, or where you already hold a recent decision on a near-identical scheme on the same street.

Skip it also where speed is the constraint and the answer is already knowable. A response time of six to eight weeks is common for larger schemes, and you can lose a season waiting for confirmation of something the local plan already states plainly. Budget the pre-app fee alongside the application fee when you plan the cash flow, as set out in the guide to working out the planning fee you owe.

Use it where the answer is not knowable from the plan: departures, Green Belt cases, heritage balance, anything where the council's judgement of harm decides the outcome. That is where an officer's early view of harm changes what you build, which is the only kind of pre-app advice that pays for itself.

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.