What planning officers actually do
A planning officer's role includes:
Officers don't 'want to refuse' applications—they're assessing against policy. A well-presented, policy-compliant application makes their job easier and gets approved faster.
- Validate applications: Check all required documents and fees are submitted
- Consult neighbours and statutory consultees: Send notifications, gather comments from highways, ecology, heritage officers
- Site visits: Visit the site to assess impact, context, and verify drawings
- Policy assessment: Check the proposal against local plan policies, NPPF, and material considerations
- Write recommendation report: Document assessment with reasoning and recommend approval (with conditions) or refusal (with reasons)
- Make decision or present to committee: Most applications decided by officers under delegated powers; contentious/major cases go to planning committee
The development plan test (the foundation of every decision)
The NPPF states that planning law requires applications to be determined in accordance with the development plan unless material considerations indicate otherwise.
This means officers start with: Does this proposal comply with adopted local plan policies? If yes, it's usually approved. If no, are there material considerations that outweigh policy conflict?
The development plan includes: Local plan (core strategy, site allocations, development management policies), Neighbourhood plans (where adopted), and Supplementary Planning Documents (SPDs) for specific topics (design, heritage, parking, etc.).
Material considerations include: The NPPF, Planning Practice Guidance, recent appeal decisions, site-specific circumstances, and updated policy context.
The site visit (what officers look for)
Every planning application gets a site visit (or multiple visits for complex applications). Officers assess:
Site visits are often brief (15–30 minutes). Officers can't enter neighbouring properties without permission, so they assess from public vantage points and your site.
- Site context: What's the character of the area? How does the site relate to neighbours?
- Impact on neighbours: Would the proposal overshadow, overlook, or create overbearing impact?
- Visual impact: How would it look from the street, public viewpoints, and neighbouring properties?
- Accuracy of drawings: Do the submitted plans match reality?
- Trees and landscaping: Are there protected trees? Would they be affected?
- Access and parking: Is access safe? Is parking adequate?
Want to see your application through an officer's eyes before submitting?
Use PlanWiser's Mock Application tool to submit your proposal and get an AI-powered assessment that mimics how a planning officer would evaluate it—policy compliance, amenity impact, conditions, and approval likelihood.
Try it nowDelegated decisions vs planning committee
Most applications (90%+ in many councils) are decided by officers under delegated powers, not by planning committee.
Delegated decisions: Officer makes the decision based on their assessment and recommendation report. Faster (typically decided within 8 weeks), less political, more policy-focused.
Planning committee decisions: Elected councillors make the decision after hearing the officer's recommendation, applicant statement (3 minutes), objector statements (3 minutes), and debate. Slower (can take 10–16 weeks), more political, can overturn officer recommendations.
What triggers committee referral? Major applications (10+ dwellings, large commercial), significant public interest (high number of objections/support), councillor call-in (local councillor requests committee consideration), or officer recommendation conflicts with policy presumption.
For most householder applications and small extensions, you'll get an officer decision. This is often better—officers are trained professionals applying policy objectively.
How to work effectively with planning officers
Best practices for good officer relationships:
Officers are often overworked (50–100+ live applications per officer in busy councils). Making their job easier improves your chances.
- Submit complete, clear applications—officers appreciate applications they can validate quickly
- Provide a short planning statement (1–3 pages) explaining how you meet policy—saves officers time and shows you've done your homework
- Respond quickly to officer queries—if they ask for more information, provide it within 48 hours if possible
- Be professional and factual—officers are applying policy, not making personal judgments
- Consider pre-application advice—meeting the officer before applying can identify issues early (£200–£600 for pre-app)
- Accept reasonable conditions—if officer suggests conditions to make the application acceptable, agreeing can secure approval
What officer reports contain (and how to read them)
Officer reports (available on the planning register after decision) typically include:
Reading officer reports for similar nearby applications is one of the best ways to understand how your council applies policy. You can see exactly what issues mattered and how they were resolved.
- Site description and planning history
- Summary of the proposal
- Relevant planning policies (local plan, NPPF)
- Consultation responses (neighbours, highways, ecology, heritage)
- Officer assessment of policy compliance
- Assessment of material considerations (amenity, design, parking, etc.)
- Recommendation (approve with conditions, or refuse with reasons)
- Recommended conditions (if approval) or refusal reasons (if refusal)
Want to see how your council assesses applications in your area?
Use PlanWiser's Property Checker to search planning decisions for your address and nearby properties—read the officer reports to understand what your council approves and refuses.
Try it nowCommon applicant mistakes that frustrate officers
These mistakes slow down applications or lead to refusal:
- Submitting invalid applications (missing documents, wrong fees)—delays validation by 2–4 weeks
- Not responding to officer requests for information—officer may refuse for lack of information
- Submitting obviously non-policy-compliant proposals without justification—wastes officer time and guarantees refusal
- Pressuring officers for 'yes' before assessment is complete—officers can't pre-determine applications
- Treating officers as adversaries—they're assessing against policy, not making personal judgments
Step-by-step: working with your planning officer
Follow this workflow for best results:
- Step 1: Before applying, read officer reports for similar nearby applications (use PlanWiser's Property Checker to find them)
- Step 2: Consider pre-application advice to meet your case officer early (£200–£600)
- Step 3: Submit complete application with clear drawings and short planning statement
- Step 4: Monitor the planning register for consultee responses and neighbour comments
- Step 5: Respond promptly to any officer queries or requests for more information
- Step 6: If officer raises concerns, consider amendments or conditions rather than fighting
- Step 7: Accept the decision professionally—if refused, you can appeal or revise and resubmit