Pre-application meeting: agenda and what to bring

A pre-application meeting is worth having when you have a specific question that changes the scheme, and worth skipping when you only want reassurance. Councils charge for the service under their general power to charge for discretionary services, they set their own fee bands, and the advice you get back is a material consideration of limited weight rather than a promise. Treat it as buying an hour of a planning officer's attention on your particular site, and prepare accordingly.

Self-builders get more from pre-application advice than anyone, because the questions that decide a one-off house are exactly the ones officers can answer: principle, access, drainage, design approach, and which reports will be needed.

Deciding whether it is worth it

Three situations where the answer is yes. The principle of development is uncertain, such as a plot outside a settlement boundary or a garden plot in a tight street. The site has a constraint you cannot resolve from the desk, such as a protected tree, a watercourse or a listed neighbour. Or the council's validation requirements are unclear and you want to know what must accompany the application.

Two situations where the answer is usually no. You have a straightforward extension inside permitted development limits, where a lawful development certificate answers the question properly. Or your design is not yet developed enough to describe, in which case you will pay for advice on a scheme that no longer exists by the time you apply.

Check what the fee band buys before booking. A written response only, a meeting on site, a meeting at the council offices and a follow-up letter are usually priced differently, and the difference between the cheapest and the next tier is often the difference between a paragraph and a conversation.

What to send in advance

The quality of the advice tracks the quality of the submission. Send material at least a week before the meeting, in one email, with a short covering note.

• A location plan at a standard scale with the application site edged red and any other land in your control edged blue.
• Existing drawings, or a measured survey where one exists, and a block plan showing the relationship to neighbours.
• Proposed drawings, even as sketches, with dimensions and a rough scale.
• Site photographs, including the views from neighbouring windows towards the site.
• The planning history of the site, with application references, including refusals.
• A note of constraints you already know about: trees, flood zone, conservation area, listed buildings nearby, access arrangements.
• Your list of questions, numbered.

That last item is the one applicants leave out and the one that turns the meeting into something useful. An officer who has your questions in advance can check the policies and the constraint layers before the meeting rather than during it.

An agenda that fits the hour

Most meetings run to about an hour, and the time goes quickly. This order works.

1. Site and proposal, described by you in five minutes, using the drawings.
2. The principle of development, and the policies that govern it.
3. Site-specific constraints and what each one requires as evidence.
4. Design, scale, materials and the relationship to neighbouring amenity.
5. Access, parking and drainage.
6. The documents the council will expect with the application, against its validation list.
7. Likely conditions, and any section 106 or Community Infrastructure Levy liability.
8. Whether the application would be decided by an officer or by committee.

Leave the design discussion in the middle rather than at the start. Officers who have already agreed the principle are more forthcoming about design than officers who are still working out whether the site is developable.

Questions that get useful answers

Ask questions an officer can answer from policy and experience.

Which policies in the adopted local plan apply to this proposal, and is there a supplementary planning document I should be working to. Would the principle of a dwelling on this plot be acceptable, and what would need to be demonstrated. What does your validation list require for a site with a watercourse across it. Would you expect a tree survey, and to what standard. Is there an approach to the roof form that would be more acceptable here. What conditions would you expect to impose. Is this likely to go to committee.

All of those produce something you can act on. Note the answers verbatim where you can, with the policy references.

Questions that do not

"Will it be approved?" cannot be answered, and asking it wastes the goodwill in the room. Neither can questions about what neighbours will say, what your land is worth, whether a covenant prevents development, or where the boundary legally sits. Those are matters for a solicitor, a surveyor or nobody at all.

Officers also cannot advise you on how to avoid a policy. A question phrased as "how do we get around the Green Belt point" gets a careful non-answer. The same question phrased as "what would the very special circumstances case have to show" gets an answer you can use.

Recording the advice and the weight it carries

Take your own notes and write them up within 24 hours, then send the summary to the officer and ask them to correct anything you have misunderstood. Do this even where a written response is included in the fee, because the written response often arrives weeks later and in less detail than the conversation.

Pre-application advice is given without prejudice to the formal decision. It does not bind the council, a different officer may handle the application, and a committee can take a different view. It still carries practical weight: a submission that shows how the scheme responds to the advice, point by point, is faster to determine and harder to refuse on grounds the officer previously raised.

Turning advice into a submission

Build the response into the documents rather than leaving it in an appendix. The cover letter structure for a planning submission has a natural place for a short section listing each piece of advice and what changed as a result.

Then reflect it in the substance. Policy points and the principle of development belong in the Planning Statement. Design, scale, materials and access points belong in the Design and Access Statement. Where the officer suggested speaking to neighbours before submitting, keep a record of what you did, using something like a neighbour consultation record.

An illustrative example of the value: a self-builder with a two-storey house design on a rural plot was told at pre-application that the principle was acceptable but the ridge height would be tested against the adjoining bungalow. Lowering the ridge by 600 millimetres before submission, and explaining that in the statement, took the point off the table. The alternative was a refusal, an appeal and a year.

PlanScope drafts those documents structured to UK planning policy, with a clear marker wherever a site fact needs to be supplied. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.

Enter your postcode to see which documents your council is likely to expect.

This is general guidance, not legal advice. Pre-application advice does not bind the council, so check the position with your local planning authority or a qualified professional before relying on it.