🕵️ Case Officer Intelligence
Go beyond authority-level data. Understand individual case officer behaviour — approval rates, decision speed, refusal patterns, and what they focus on. Intelligence your competitors don't have.
🔒 PlanningCore Exclusive — Deep Officer Behaviour AnalyticsKnown data gaps: our Idox scrape covers Gateshead, Sunderland, and Northumberland from late 2023 onwards. Newcastle Upon Tyne data is NOT in our corpus (the council's planning portal blocks IONOS shared-hosting IPs). If you're looking for a Newcastle case officer, their decisions won't appear here even if the officer name matches.
🕵️ Steve Davison · Bournemouth, Christchurch and Poole Council
📊 Application Type Breakdown
| Application Type | Total | Approved | Refused | Other | Approval Rate |
|---|---|---|---|---|---|
| Unknown | 44 | 0 | 0 | 44 |
⏱️ Decision Speed Distribution
📋 Decision History (44 most recent)
| Reference | Address | Type | Decision | Date | Days |
|---|---|---|---|---|---|
| Application No. P/26/04708/REG14 | — | — | — | ||
| Application No. P/26/04676/REG14 | — | — | — | ||
| Application No. P/26/04754/REG14 | — | — | — | ||
| Application No. P/26/04631/TTPO | — | Split | — | — | |
| Application No. P/26/03937/TCA | — | — | — | ||
| Application No. P/26/03992/TCA | — | — | — | ||
| Application No. P/26/04648/REG14 | — | — | — | ||
| Application No. P/26/03828/TCA | — | — | — | ||
| Application No. P/26/04384/TCA | — | — | — | ||
| Application No. P/26/04480/REG14 | — | — | — | ||
| Application No. P/26/04562/REG14 | — | — | — | ||
| Application No. P/26/04431/REG14 | — | — | — | ||
| Application No. P/26/04355/REG14 | — | — | — | ||
| Application No. P/26/04373/REG14 | — | — | — | ||
| Application No. P/26/04230/REG14 | — | — | — | ||
| Application No. P/26/04325/REG14 | — | — | — | ||
| Application No. P/26/03944/TTPO | — | Withdrawn | — | — | |
| Application No. P/26/04244/REG14 | — | — | — | ||
| Application No. P/26/04210/REG14 | — | — | — | ||
| Application No. P/26/04208/REG14 | — | — | — | ||
| Application No. P/26/04133/REG14 | — | — | — | ||
| Application No. P/26/04183/REG14 | — | — | — | ||
| Application No. P/26/04096/REG14 | — | — | — | ||
| Application No. P/26/04078/REG14 | — | — | — | ||
| Application No. P/26/04112/REG14 | — | — | — | ||
| Application No. P/26/04108/REG14 | — | — | — | ||
| Application No. P/26/04106/REG14 | — | — | — | ||
| Application No. P/26/04128/REG14 | — | — | — | ||
| Application No. P/26/02977/TCA | — | — | — | ||
| Application No. P/26/03981/REG14 | — | — | — | ||
| Application No. P/26/04025/REG14 | — | — | — | ||
| Application No. P/26/04012/REG14 | — | — | — | ||
| Application No. P/26/03927/REG14 | — | — | — | ||
| Application No. P/26/03948/REG14 | — | — | — | ||
| Application No. P/26/03923/REG14 | — | — | — | ||
| Application No. P/26/03906/REG14 | — | — | — | ||
| Application No. P/26/03902/REG14 | — | — | — | ||
| Application No. P/26/03919/REG14 | — | — | — | ||
| Application No. P/26/03820/REG14 | — | — | — | ||
| Application No. P/26/03814/REG14 | — | — | — | ||
| Application No. P/26/03847/REG14 | — | — | — | ||
| Application No. P/26/03845/REG14 | — | — | — | ||
| Application No. P/26/03841/REG14 | — | — | — | ||
| Application No. P/26/03863/REG14 | — | — | — |
🧠 Strategy Insight
Insufficient decision data to generate a strategy profile. As more applications are processed, the intelligence will become richer.
What Makes This Different
📊 Officer Approval Rates
See each officer's personal approval rate, not just the authority average. Know whether your officer approves 95% or 65% of applications.
PlanningCore Exclusive⏱️ Decision Speed Profile
Average days to decision per officer. Know if your officer is fast (under 8 weeks) or chronically slow — and plan your timeline accordingly.
Officer-level granularity🚫 Refusal Pattern Analysis
What does this officer refuse on most? Design? Highways? Amenity? Heritage? Know their focus areas and address them proactively.
Deep refusal analytics⚖️ Appeal Overturn Rate
How often are this officer's refusals overturned on appeal? A high overturn rate suggests the officer is too strict — useful for your appeal strategy.
Appeal data linked to officers🏛️ Committee vs Delegated Split
Does this officer usually decide under delegated powers, or do their cases end up at committee? Different preparation needed for each route.
Committee/delegated tracking🧠 Strategic Advice
Based on the officer's patterns, get tailored advice: what to emphasise in your planning statement, what issues to pre-empt, and how to frame your scheme.
AI-powered strategy layer📡 Data Pipeline
Officer intelligence is generated from planning application decision data. As more authorities are ingested into PlanningCore, officer profiles become richer and more accurate.
📊 Data sources & freshness
- planning_applications.case_officer (updated Daily ingest)
Live ingest from LPA portals (Idox + Civica + Northgate). Coverage varies by council — leading LPAs publish on every record, others publish only on committee reports. - Approval rate calculation
approvals / (approvals + refusals) per officer. Withdrawn and pending applications are excluded. - Date window
Stats reflect the entire decision history for the officer, not a rolling window. Recent volume changes can shift the averages.
About this tool: Case Officer Intelligence
Individual case officer profiling — approval rates, decision speed, refusal patterns, appeal overturn rates, and tailored submission strategy advice.
Use when you know which officer is assigned to your case, or to research officer behaviour in an authority before submitting. Deep officer behaviour analytics exclusive to PlanningCore.
Data-driven analysis of individual officer decision patterns
Use these tools to understand how your Local Planning Authority behaves — what they approve, what they refuse, how often appeals succeed, and what strategy gives you the best chance. This is behavioural intelligence, not just policy research.
Guidance to help you prepare — not formal planning advice. Check the current policy text and your council's local plan before relying on it.