Pre-application advice

General guidance, not advice. This guide explains how UK planning law works in general terms. It is not legal or planning advice for your specific site, and the law changes over time and differs between England and Wales. Check the current rules with your local planning authority or a qualified planning professional before you act.

Pre-application advice (usually shortened to "pre app" or "pre-app") is a non-binding view from a local planning authority (LPA) planning officer on whether your proposal is acceptable in principle, usually treated as confidential, given to you before you submit a formal planning application. You pay the council a fee, send a sketch and a short description, and an officer writes back - or meets you - with their initial reading of the scheme: which policies bite, what the likely concerns are, and whether they think it would be approved.

It is not a decision, and it does not guarantee consent. It is an early read - the same judgement the officer would later apply, but delivered before you commit the application fee, the design time, and the waiting period. The National Planning Policy Framework (NPPF) sets this out at policy DM1, "Preparing development proposals", and treats early engagement as central to good decision-making. Planning Policy Wales (PPW) has no dedicated pre-application section - the Welsh pre-app process is set out in the Development Management Manual - though PPW does stress early engagement in its design and placemaking chapter.

What is pre-application advice?

Pre-application advice is a discretionary service offered by most local planning authorities in England and Wales. You ask the council to look at an emerging proposal and tell you, informally, how it would be likely to be determined. The output is usually a short written response from a planning officer, sometimes a meeting, and - for larger schemes - a more structured officer report.

A typical pre-app response covers:

• whether the principle of the development is acceptable
• which local and national policies apply, and which weigh against you
• what concerns neighbours, town or parish councils, and statutory consultees are likely to raise
• what changes would make the scheme more likely to succeed

Crucially, it is non-binding. The NPPF (August 2026) expects pre-application engagement on major proposals under policy DM1(1)(a), and DM1(2) goes further than the previous Framework: pre-application engagement "may also be required" where proposals raise complex planning matters, so the old rule of thumb that a council could never insist on it no longer holds. The officer's view remains their honest reading at the time, not a promise about how the application will be determined.

Why do it - the benefits

Policy DM1(1)(a) of the NPPF says proposals for major development should be informed by early engagement with neighbours and the local community, the local planning authority, statutory consultees, infrastructure providers, registered providers of social housing and other relevant bodies, "to identify and seek to resolve key planning matters prior to the submission of a planning application." That engagement should be proportionate to the nature of the proposal and to those likely to be affected by it. The more issues resolved before submission, the greater the benefit on both sides: authorities can issue timely decisions, and applicants avoid unnecessary delays and costs.

In practical terms, the benefits are:

• Testing the principle before you pay. The biggest cost in a refused application is usually the lost application fee plus redesign time, not the refusal itself. Pre-app tells you if the principle is viable before you spend either.
• Surfacing officer concerns early. You learn which policies the officer will weigh against you while you can still change the scheme - set-back, height, materials, unit mix, parking layout.
• Improving the scheme. Officers often suggest concrete tweaks that move a borderline proposal into approval territory, which is cheaper to do before you submit than after a refusal.
• Flagging a likely refusal. If the officer's read is "I can't support this," you can reframe - for example to a different application type - reconsider the site, or walk away before the application fee is spent.
• Faster formal decisions. DM1 frames pre-app as the way key planning matters get resolved before submission, so the contentious issues are already narrowed by the time the application lands.

DM1(1)(a) makes a related point by naming the bodies involved: bringing statutory consultees and infrastructure providers (highways, environment, heritage, utilities) into pre-app discussions lets the fundamental questions about whether a development is acceptable in principle be considered in parallel, rather than serially once the application is lodged.

What does pre-app advice cost?

There is no single national fee. Each LPA sets its own pre-application charging schedule, so the cost varies by council and by scheme type. As a realistic picture across England and Wales:

• Householder schemes (extensions, alterations, a single new dwelling) are often around £100-£300, though some councils provide a basic householder pre-app free of charge.
• Minor residential and small commercial (a few units, a change of use) typically runs into the low hundreds of pounds.
• Major schemes (10 or more dwellings, large commercial, or 1,000 sqm+ of floorspace) are charged at much higher rates - often £1,000-£5,000 or more depending on scale - and usually include a meeting and a structured officer response.

Some councils offer a tiered service (written-only, meeting, or a full officer panel). Some waive the fee for particular categories, such as certain householder or community proposals. Check your council's planning pages for the current charging schedule - it changes, and the same council often charges very different amounts for written-only versus meeting pre-app.

The fee is the council's charge for officer time. It is not a deposit on the application, it is not offset against the later application fee, and it is usually non-refundable - though whether any refund is available depends on the council's own terms. It buys a view, not a decision.

What to bring to a pre-app

The point of pre-app is to get a useful reading, so you need to give the officer enough to form a judgement. Policy DM1(1)(b) of the NPPF expects a major proposal to be accompanied by a concise planning statement covering how it is consistent with the development plan and national decision-making policies, the outcome of pre-application engagement and how the scheme changed in response, and any planning obligations proposed. Smaller schemes need only "the minimum necessary information requirements to enable a decision" (DM1(2)), so it is worth discussing what the council needs as early as possible. A typical pre-app submission includes:

• a location plan with a red-line site boundary on an Ordnance Survey base
• a site plan showing the existing layout and the proposed works
• basic drawings or a sketch - enough to show scale, height, and the relationship to boundaries and neighbouring properties
• a short written description of the proposed use, the floorspace, and the number of units
• a note of known constraints - listed building, conservation area, Article 4 direction, Tree Preservation Orders, flood zone, green belt - and any material considerations you are already aware of
• for non-householder schemes, an outline of any phasing or timing you have in mind

You do not need a full planning application pack. The smaller the scheme, the lighter the ask - a sketch and a location plan is often enough for a householder pre-app, and councils will usually tell you on request what they need for your scheme type. Giving too little produces a vague response; giving a finished, detailed pack can be wasted if the principle itself is the question.

The limits of pre-application advice

Pre-app is genuinely useful, but it has hard limits you should understand before paying:

• It is non-binding. The officer's view is not a determination - the officer's reading at pre-app stage is not a promise about how the application will later be determined. Note that under DM1(2) engagement may be required for proposals raising complex planning matters, a change from the previous Framework.
• The officer may not determine the application. Pre-app responses are often written by one officer; the application may later be allocated to a different one, or sent to planning committee for a decision by elected members.
• Committee can still refuse. Schemes that officers spoke favourably of at pre-app are sometimes refused by committee, particularly on contentious or high-profile sites where local opposition is organised.
• It does not guarantee consent. A positive pre-app is a strong signal, not a warranty. New objections, a neighbour campaign, or a changed local plan can shift the outcome between pre-app and decision.
• It is only as good as what you submit. If you hold back information, the officer's reading is limited by that - and they will usually say so in the response.

When pre-app is worth it (and when it isn't)

Pre-app earns its fee where the principle is genuinely uncertain. It adds less where the answer is already obvious.

Worth it:

• Contentious sites - green belt, conservation area, listed building, protected open space. The policy edge is exactly where an officer's early read saves the most time and money.
• Major schemes. The pre-app fee is small relative to the design and application cost, and the NPPF's early-engagement expectation at policy DM1(1) applies specifically to major development.
• Policy-edge cases - proposals that turn on a material-consideration judgement, or on whether the benefits would be substantially outweighed by adverse effects under NPPF policy S4 or S5. An officer view tells you which way the balance is likely to fall before you commit.
• Anything neighbours will object to. Pre-app surfaces the likely objections while you can still respond to them in the scheme, rather than after they have become formal representations.

Probably not worth it:

• Straightforward householder extensions that clearly meet the council's design guide. The principle is obvious; the fee is better spent on the application itself.
• Permitted development. If the work is within permitted development rights, or a lawful development certificate would cover it, you don't need the council's view on principle - you need certainty on the PD rules, which is a different question.
• Schemes you already know are policy-compliant. If the site is allocated and the proposal matches the allocation, pre-app adds little beyond confirmation.

How England and Wales differ

The two nations frame pre-app slightly differently, though the practical experience - fee, output, non-binding status - is much the same.

England. The NPPF (August 2026) deals with pre-application engagement at policy DM1, in Chapter 3 on decision-making procedure. It expects early engagement on major development and pre-application discussion where proposals raise complex planning matters. Most English LPAs run a charged pre-app service with a published fee schedule.

Wales. Planning Policy Wales (Edition 12) does not have a stand-alone pre-application section. The Welsh pre-app process is set out in the Development Management Manual, not in PPW. Paragraph 3.2 of PPW sits in the design and placemaking chapter and concerns design-stage engagement with the public and other stakeholders - part of PPW's placemaking ways of working - rather than the LPA pre-app advice service. Welsh LPAs offer broadly similar charged pre-app services to their English counterparts, and the non-binding status is identical.

In both jurisdictions the takeaway is the same: pre-app is an optional, charged, non-binding early read that exists to de-risk your application before you commit to it.

A first read - GapSense screening

If the value of pre-app is an early read on policy risk, you can get a comparable first read before - or instead of - paying the council.

A GapSense screening takes your site (a postcode, a grid reference, or a drawn red-line boundary) and assesses it against the local plan and the relevant national framework - the NPPF for England, PPW for Wales. You get a structured view of the policy risks on your site: which policies support the principle, which constrain it, and where the judgement is likely to land. It is the same kind of "acceptable in principle?" question a pre-app officer would answer.

Use it to decide whether a paid pre-app is worth the fee. If the screening surfaces a hard policy conflict, you may not need to pay the council to tell you the same thing - you can reframe or drop the site first. If the screening shows the principle is viable, a pre-app then becomes a more targeted conversation: you arrive already knowing the policy landscape, so the officer's time goes on the fine judgement calls rather than on explaining the basics.

For larger or more contentious schemes, the two work well in sequence - a screening to map the risks, then a paid pre-app to test the officer's view on the points that remain open. For smaller or clearer schemes, a screening alone may be enough to decide whether to apply at all.

Disclaimer: this guide is general information, not legal or planning advice, and reading it does not create any professional relationship. Planning law and national policy change, and vary between England and Wales. Always confirm the current position with the relevant legislation, your local planning authority, or a qualified planning consultant before making a decision.

Sources: the National Planning Policy Framework (August 2026), Chapter 3 (Decision-making), policy DM1 on preparing development proposals and pre-application engagement; Planning Policy Wales (Edition 12), paragraph 3.2 (design and placemaking); and the Welsh Development Management Manual, which sets out the Welsh pre-app process. Pre-application services and charges are set individually by each local planning authority in England and Wales. Limits reflect the consolidated policy as at August 2026; always check the live national policy and your council's current pre-app scheme.