Writing a pre-application enquiry that gets a usable answer

A pre-application enquiry is only worth the fee if it comes back with answers you can build on. The difference between a useful response and three paragraphs of policy quotation is almost entirely in how the submission is written: a numbered list of specific questions, enough drawn information to answer them, and your own policy analysis done first so the officer is reacting rather than starting from scratch.

Ask "is this acceptable in principle" and you will get "it depends on the detail". Ask six precise questions and you will usually get six answers.

What a pre-application response can and cannot do

Pre-application advice is a discretionary service, and councils charge for it under the general power to charge for discretionary services in the Local Government Act 2003. Fees are set locally and published in bands, usually by development type and scale.

The advice does not bind the authority. An officer cannot fetter the council's discretion or commit the decision-maker, and a committee is free to take a different view from the officer who gave the advice. There is no legitimate expectation created by a pre-application letter.

What the advice does give you is real. It tells you the officer's initial view, which policies they consider determinative, which consultees will be engaged, what evidence they will expect, and whether the scheme is likely to be delegated or reported to committee. On a marginal scheme that is the difference between a considered submission and a guess.

On larger proposals a planning performance agreement sets out a programme, the officer resource and a timetable, and is worth considering where the scheme will take months rather than weeks.

Structuring the submission around questions

Write the document backwards. Start with the questions you need answered, then supply only the material needed to answer them.

A structure that works looks like this: a one-paragraph summary of the proposal, a site description with the constraints identified, the relevant planning history with application references and dates, your policy analysis, the description of the proposal with the drawings listed, and then a numbered list of questions.

Put the questions on the first page as well as the last. Officers are busy and a list they can reply to line by line is far more likely to be answered line by line.

Keep the whole submission short. Twelve pages with six good questions gets a better response than forty pages with none, and the officer's time is finite regardless of what you paid.

Drawings to include at this stage

Enough to answer the questions and no more. Fully worked-up drawings at pre-application stage signal that you have already decided, which makes an officer less inclined to engage, and they waste fee income if the advice sends you back to the start.

A topographical survey is the one investment worth making before you ask anything. Levels drive the massing argument, the drainage argument and the amenity argument, and advice given on an assumed flat site is worthless when the site falls 2m across its width.

Include photographs from the viewpoints an officer would use, and a short context analysis showing the prevailing pattern of development, plot widths and building lines. Those two things frame the design conversation on your terms.

Policy analysis you should do first

Do the work rather than asking the officer to do it. Identify the adopted development plan documents and their dates, the policies you consider determinative, any relevant supplementary planning document, and any neighbourhood plan.

Then state your position. Set out which policies the scheme complies with and which are in tension, and explain how you say the balance falls. An officer who is asked to react to a reasoned position gives a reasoned answer. An officer who is asked an open question gives an open answer.

Relevant appeal decisions and nearby approvals are worth including where they bear directly on the issue, with references so the officer can check them. Present them as indicative of how the issue has been approached rather than as binding, because that is what they are.

Where the scheme relies on a fallback position, such as an existing permitted development right or an extant permission, set it out fully at this stage. Officers respond badly to a fallback argument that appears for the first time in the planning statement.

Asking about validation requirements early

This is the question people forget, and it is the one that saves the most time.

Ask directly which items from the local validation list the authority will expect, and ask for the answer in writing. Then ask a follow-up: what level of detail is proportionate for each. There is a large difference between a preliminary ecological appraisal and a full suite of protected species surveys, and between a drainage note and a modelled strategy.

Ask about the ecology programme specifically, because survey seasons are the most common cause of delay. If a bat emergence survey will be required, knowing that in October rather than in April moves the submission date by a year.

Ask about planning obligations and levy liability while you are at it. Whether the authority will seek a section 106 agreement, on what heads of terms, and whether the site is subject to a charging schedule, are all questions with financial answers that belong in the appraisal rather than in a surprise.

An illustrative example

A pre-application enquiry for nine dwellings on a former builder's yard. The submission ran to fourteen pages: site description, constraints plan, a planning history table with four references, three pages of policy analysis, sketch layout and street elevation, and eight numbered questions covering the principle, density, the relationship to two neighbouring gardens, access geometry, affordable housing, the validation list, ecology scope and whether committee or delegated. The response answered seven of the eight in order and the meeting dealt with the last. This example is illustrative rather than drawn from a specific case.

Recording the response for later use

Get everything in writing. Where advice is given at a meeting, write your own note immediately, send it to the officer and ask them to confirm or correct it. An unchallenged note is far better evidence than a recollection.

Keep the file: the submission, the written response, the meeting note, the confirmation, and a record of any subsequent phone conversations with dates. Officers move on, and a new case officer with no institutional memory is a routine hazard.

Where the advice changes, ask why in writing and record the answer. A change of view is legitimate, and an unexplained change of view is something you may want to refer to later.

Weight given to the advice at application stage

Quote the advice in the Planning Statement and show what you did about it. A submission that lists each piece of advice and the design response to it is easy for an officer to recommend and hard for an objector to attack.

Where you disagreed with the advice, say so and explain why, with evidence. Silently ignoring advice you asked for and paid for is the fastest way to a refusal, because the officer's report will say exactly that.

The same applies to the Design and Access Statement, which is the natural home for the design evolution narrative: what was shown at pre-application, what the officer said, and how the scheme changed.

Advice does not guarantee an outcome, and it should not be presented as if it did. What it does is remove most of the avoidable risk from a submission, and on a contested site that is usually worth several times the fee.

Browse the report types by category once the validation answer comes back, so the evidence base is scoped before you commission anything. 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.