⏳ LAUNCH PRICING — 77% OFF · Professional £9/mo (was £39) Only 74 days left Lock in launch rate →

🗓 Submission Timing Intelligence

When is the best month — and weekday — to submit your planning application? Real approval-rate + decision-speed data from 25,848 dated decisions across UK LPAs.

📅 Monthly breakdown per LPA 🏆 Best / worst windows ⚡ Decision-speed by month 🌍 National baseline for context
🏛️ By LPA 🗓 Best LPAs by Month
Narrow by type All types Householder Full / Major Outline Reserved Matters Listed Building Conservation Area Prior Approval Lawful Development Change of Use

📊 Gateshead Council

Months below refer to when you submit, not when the decision lands. Each application is bucketed by its received_date month — but the approval rate measures the final outcome, whenever it landed (60-90 days later typically). The lag is already baked into the signal: "submit in December = 100% approval" already accounts for the fact that those decisions arrive in Feb/March. The month-by-month table below shows the lag explicitly so you can see the full cycle.

⏱ Decision speed by application type

How long different application types actually take at Gateshead Council. Householder apps are statutorily 8 weeks; full/major are 13 weeks — but the real numbers usually drift. This is what the data says, not what the statute says.
→ Fastest: Discharge Conditions (52 days). Slowest: Full / Major (93 days).

Application type Decisions Approval rate Avg days Range
Householder 40 100% 65 d (9 wk) 19–207 d Filter ▸
Full / Major 23 78.3% 93 d (13 wk) 51–210 d Filter ▸
Discharge Conditions 16 87.5% 52 d (7 wk) 3–194 d Filter ▸
Listed Building (low sample) 4 100% 80 d (11 wk) 56–104 d Filter ▸
Advertisement (low sample) 2 0% 86 d (12 wk) 56–115 d Filter ▸
Prior Approval (low sample) 1 100% 63 d (9 wk) 63–63 d Filter ▸
Change of Use (low sample) 1 100% 282 d (40 wk) 282–282 d ✕ clear

ⓘ Month-by-month stats above are filtered to Change of Use only. The table above always shows all types so you can compare.

📅 Month-by-month breakdown — full submit→decide cycle

Each row shows the complete journey for applications received in that month: how long they took, when the decision actually landed, and what % were approved. The approval rate already accounts for everything that happens between submission and decision — the lag is part of the signal.

Submit month Decisions Approval rate Median lag Decision typically lands in Range

Read across each row: submit in [month] → wait [median lag] → decision lands in [target month] → outcome [approval rate]. The approval rate is the final outcome of the whole cycle, not a snapshot.

🗓 Day-of-week patterns

Day receivedDecisionsApproval rateAvg days
⚖️ Why timing matters less than they pretend: A planning decision should be made on its substantive merits, not the season. But officers have queues, committees have schedules, and consultees go on holiday. The data is a guide to operational friction, not policy friction. If your scheme is sound, time it to land in their best window. If it's borderline, give yourself every advantage.
📊 Data sources & freshness

Timing is a tactical edge, not strategic justification. Use alongside the constraint check + pattern fingerprint to make the case strong on substance, then time it to land well.

  • planning_applications.received_date (updated Daily ingest)
    25,848 dated decisions where both received_date and decision_type are known. Approval = approved/granted/permit. Sample size gating: months with fewer than 8 decisions excluded from best/worst recommendation.
  • Day-of-week patterns
    Reflects when applicants choose to submit, which may correlate with applicant type (Monday = professional consultants; Friday = end-of-week DIY submissions). Causality is correlative not causal.
  • Decision-time outliers
    Months showing 200+ day averages are flagged — they reflect older PINS-appeal-derived rows where determinations stretched over many months. Read the Jan/Feb/Nov/Dec numbers (largest samples) as the reliable benchmark.
Ask Planning Agent
🧭Guide me