Turning a pre-application response into a drafted statement

A pre-application response is the best outline you will ever get for your planning statement, and the mistake is to treat it as a letter rather than a brief. Work through it once and split every sentence into four categories: information you must submit, design changes the officer wants, points where they say the principle is acceptable, and points where they say the proposal conflicts with policy. Those four categories become four different sections of your submission, and the last one is the one the statement exists to answer.

Do this before you ask anyone to draft anything, because the split determines the structure.

What a pre-application response contains

Most English authorities use a similar format for a written pre-application response, charged under their own published fee schedule. Pre-application advice is discretionary in England, so the level of detail varies, and what you get for the fee should be set out in the council's published service description.

The usual sections are a description of what you asked about, a summary of the site and its constraints, the policies the officer considers relevant, the officer's assessment, a list of the information they expect with an application, and a conclusion.

Read the caveats at the end. They will say the advice is officer opinion, that it does not bind the authority, and that the decision will be taken on the application as submitted. Those statements are accurate and they do not make the advice worthless. They do mean you cannot cite the letter as a promise.

Separating advice from requirement

Four categories, and mixing them up is what produces a statement that argues with the wrong things.

Information requirements. Sentences beginning "the application will need to be accompanied by". These are validation matters and they are non-negotiable in practice. Cross-check each against the council's current published local validation list, because the two occasionally differ.

Design advice. Sentences beginning "I would suggest" or "the scheme would be improved by". These are recommendations. You can follow them, follow them partly, or decline with a reason, and the statement should say which you did.

In-principle views. Sentences saying the use, the principle of a dwelling in this location or the general scale is acceptable. Record these carefully and quote them accurately, because they are the part of the advice with the most value and the part most often overstated.

Policy objections. Sentences identifying conflict with a named policy. Each one needs a dedicated answer in the statement, with either evidence that the conflict does not arise or an argument that other considerations outweigh it.

Highlight the letter in four colours if it helps. It is a five-minute task that saves a redraft.

Structuring the statement around the officer's concerns

Use the officer's own framing. Officers reading an application they advised on look for their points, and a statement organised around the policy chapters of the local plan makes them hunt.

The arrangement that works:

1. A short description of the proposal and the site, factual.
2. The planning history, including the pre-application reference and date.
3. A table responding to the pre-application advice, point by point.
4. The policy assessment, addressing each identified conflict in the order the officer raised them.
5. The supporting evidence, with a list of what is submitted and what each document answers.
6. A short conclusion on the planning balance.

Section three is the one that changes how the application is received. Three columns. The officer's comment, quoted or closely summarised. Your response. And where in the submission it is addressed, by document and drawing number.

A Planning Statement built that way is shorter than a generic one and does more work, because every paragraph is answering something a named person actually wrote.

Evidence the response asked for

List the documents the officer asked for and check each against three things: the validation list, whether the document needs a specialist author, and whether a survey season constrains it.

That third check is the one that wrecks self-build programmes. Ecology surveys have windows. Bat emergence surveys run in the warmer months, great crested newt survey has a defined spring window, and a response received in October asking for a newt survey means a submission in the summer rather than at Christmas. Find that out on the day you read the letter, not in three months.

Where a document needs a licensed or competent professional, the officer's request is telling you to appoint someone rather than to write something. Ecology surveys requiring a licensed ecologist, contamination reports prepared to the relevant British Standard by a suitably qualified person, and fire statements needing fire engineering competence all fall into that category, and a drafted document is a starting point for that professional rather than a substitute for them.

Where the advice has been overtaken

Pre-application advice ages, and the older it is the more carefully you check it.

Three things go out of date. Policy references, where a new local plan has been adopted or the national framework has been re-issued, which it has more than once in recent years. Regulatory requirements, such as the biodiversity gain information now required with most applications and the exemptions that apply to smaller self-build schemes, whose criteria should be checked against the current guidance. And the constraints themselves, since an Article 4 direction or a new designation can arrive between advice and application.

Where a policy reference in the letter no longer exists, do not repeat it. Cite the current policy that replaced it, and note in your response table that the advice referred to the earlier version. That reads as competence rather than as a correction of the officer.

Where a whole strand of the advice is superseded, consider whether a short follow-up email to the same officer is worth the time. Often it is, and it is free.

Recording the changes you made

Keep a schedule of amendments, and submit it. Each row: what the officer said, what changed, which drawing revision shows it.

This does three things. It proves you engaged rather than ignoring the advice. It gives the case officer a checklist rather than a comparison exercise across two sets of drawings. And it protects you where you declined a suggestion, because a documented reason is a position, while silence looks like an oversight.

Where the design change also affects the Design and Access Statement, make the same points there rather than leaving the two documents to disagree.

What weight the response carries at determination

Less than applicants hope and more than officers admit.

Formally, the decision is taken under section 70 of the Town and Country Planning Act 1990 and section 38(6) of the Planning and Compulsory Purchase Act 2004, on the development plan and material considerations as they stand at the date of decision. The pre-application advice is a consideration, not a commitment, and the authority is entitled to reach a different view. A different officer may handle the application. A committee is not bound by an officer's earlier view at all.

Practically, an application that follows clear pre-application advice is quicker to assess, easier to recommend and harder to object to. Where you have departed from the advice, say so prominently and give the reason. Officers respond badly to discovering a departure themselves.

And do not quote the advice as though it settles the matter. A statement asserting that the council has already agreed something the letter did not quite say is the fastest way to lose an officer's goodwill.

The same discipline applies before the meeting as after it, and the piece on using a draft to prepare for a pre-application meeting covers that half. When the draft comes back, review it for the specific errors listed in factual errors to look for in a drafted planning document before it goes anywhere near the council.

PlanScope can produce an AI-assisted draft Planning Statement structured around the points in your pre-application response. Reports should be reviewed before submission, and PlanScope does not guarantee planning approval. For specialist technical reports, qualified professional input may be required. Enter your postcode on PlanScope to see which documents your scheme is likely to need. This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional before relying on it.