Council pre-application meetings: preparing for the officer call

A pre-application meeting planning officer discussion is worth what you put into it. Send a red line, three sketches and a vague question and you will get a paragraph of policy quotations back. Send a properly framed set of drawings with six specific questions and you will usually get an officer telling you which part of your scheme will be argued about and what would fix it.

Pre-application advice is discretionary and most councils charge for it, using a published fee scale by development type. The advice is given without prejudice to any later decision, so it binds nobody. It is still the most useful hour you will spend on a self-build project.

What a paid pre-app usually includes

Councils package the service differently, and the difference matters when you choose a band. The common tiers are written advice only, written advice plus a meeting or call, and written advice plus a site visit.

For most single-dwelling and conversion schemes the meeting tier is the right one. Written advice on its own arrives as a formal letter that answers the question you asked rather than the question you should have asked, and the value of the call is that the officer can tell you where the real difficulty lies.

Check three things on the council's pre-app page before you pay. What the fee includes, and whether it covers one round of comment or two. The stated turnaround, which is commonly four to six weeks from a valid request. And whether the fee is deducted from any later application fee, which some authorities do for smaller schemes.

Also check whether the service is being run at all. Several authorities have suspended or restricted pre-app for certain scales, and the page is not always current.

What to send before the meeting

The officer will read your submission the day before. Assume 20 minutes of preparation, and write for that.

• A location plan with the red line and the blue line for any other land you control.
• An existing site plan with levels, boundary treatments and every tree that is more than incidental.
• Photographs of the site and of the relationship with each neighbour, taken from positions marked on a plan.
• A sketch proposal with dimensions and heights, even where the design is not resolved. An officer cannot advise on a scheme with no size.
• The planning history, by application reference, including refusals and appeals.
• One page of text saying what you propose, which policies you think apply, and what you are asking.

That last page is the part most people skip, and it is what turns a meeting into a useful one. Set out your own view of the policy position and the officer will correct it, which is far more informative than an open question.

Where the site has an obvious constraint, do the basic checking yourself first. Flood zone, conservation area, listed building, tree preservation order, article 4 direction. The 66 report types index shows which documents each constraint usually triggers, and knowing that before the meeting lets you ask about scope rather than about existence.

Questions worth asking on the call

1. Is the principle of this development acceptable in policy terms, and which policies of the adopted plan decide it?
2. Which parts of the proposal would you expect a case officer to resist, and what change would remove that concern?
3. Which documents will the validation list require for an application of this description?
4. Which consultees will be asked, and is there anything they will want that I should commission now?
5. Would this be determined under delegated powers or go to committee, and what would push it to committee?
6. Are there obligations or levy liabilities I should be budgeting for?

Ask the second question early. Officers answer it candidly when the conversation is advisory, and the answer is the one you will act on. The fourth question is the one that saves seasons, because ecological survey windows and traffic count restrictions do not move for your programme.

If the scheme is design-sensitive, ask whether the authority runs a design review panel and whether a referral is expected. Our note on design codes and design review panels covers how those responses are weighed.

Taking notes and confirming the advice

Write your own note within 24 hours, while the phrasing is still fresh. Record what you asked, what the officer said, and anything they said they would check.

Then send it to the officer with a short covering line asking them to correct anything you have recorded wrongly. Most will reply, and the reply is worth more than your own note because it is the council's record. Where formal written advice follows, compare it against your note and query any difference immediately rather than at submission.

Two things to keep in proportion. Officer advice does not bind the council and cannot bind a committee, so treat it as a well-informed prediction rather than a commitment. And officers change. Advice given by one officer is not automatically owned by their successor, which is one reason to have it in writing.

Pre-application correspondence can also end up in the public domain later, so write as though a neighbour will read it.

Where a site visit changes the advice

Desk advice on a photograph is advice on a photograph. The things that change once an officer stands on the site are consistent: ground levels and how much of a proposed building will actually be visible, the condition and value of boundary vegetation, the real relationship to the nearest windows, the width and visibility at the access, and whether the street has a rhythm the scheme is breaking.

Pay for the visit where levels vary across the plot, where the site is in a conservation area or National Landscape, where mature trees are close to the footprint, or where access is onto a road with poor visibility. The national landscape tests applied in designated areas are almost always better discussed on site than in an office.

Walk the site with the officer rather than presenting at them. Bring a tape and a levels drawing.

Turning the advice into your submission

Pre-app advice is evidence, and the point of paying for it is to use it in the application.

In the Planning Statement, set out the advice received by reference and date, then list each point and say what the submitted scheme does about it. Where you have followed the advice, say so plainly. Where you have not, give the reason. Officers deal with a great many applications that ignore their own pre-app advice without explanation, and an application that engages with it reads as a serious one.

Do the same with the document schedule. If the officer named four supporting documents, submit four, and say in the covering letter which advice each answers. That single move removes most validation friction, and the local validation list will confirm whether anything further is needed.

Enter your postcode on PlanScope to see which reports your site is likely to need, then take that list into the meeting and ask the officer to correct it.

This is general guidance and 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.