💡 Submission Timing works best inside your planning journey — open or create your case there and your documents and site data fill this in for you.

🗓 Submission Timing Intelligence

When is the best month — and weekday — to submit your planning application? Real approval-rate + decision-speed data from 144,135 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 Tree Works / TPO Discharge Conditions Amendment / NMA

📊 Broxbourne

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.

⚖️ What this council's headline is made of. 31.6% of its typed decisions are tree consents, condition discharges and amendments — consent administration that approves at 94.2%. On actual development decisions the approval rate is 67.7% (186 decisions), 26.5 points lower than the mixed figure.
Use the type chips above to filter to the application type you are actually making — and treat cross-council comparisons of the mixed number with care, since the mix depends on which source fed each council.
🎯 Inverse view — "I want a decision in [month], when do I submit?"

Based on this LPA's typical decision-lag of 56 days (~2 months), the table below shows when to submit if you want your decision to land in a specific month.

If you want a decision in...Submit by (approx.)That submit month's approval rate
Jan Submit by end of Nov 100%
Feb Submit by end of Dec —
Mar Submit by end of Jan 100%
Apr Submit by end of Feb —
May Submit by end of Mar 50%
Jun Submit by end of Apr 100%
Jul Submit by end of May —
Aug Submit by end of Jun 100%
Sep Submit by end of Jul 50%
Oct Submit by end of Aug —
Nov Submit by end of Sep —
Dec Submit by end of Oct —

Inverse calculation is approximate — actual decision time varies (range typically ±30 days). Use the Decision Time Predictor for tighter forecasts.

⏱ Decision speed by application type

How long different application types actually take at Broxbourne. 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: Tree Works / TPO (23 days). Slowest: Amendment / NMA (96 days).

Application type Decisions Approval rate Avg days Range
Tree Works / TPO 74 95.9% 23 d (3 wk) 1–112 d Filter ▸
Full / Major 47 4.3% 94 d (13 wk) 48–274 d Filter ▸
Amendment / NMA 11 81.8% 96 d (14 wk) 26–287 d ✕ clear
Heritage / LB (low sample) 5 0% 91 d (13 wk) 56–171 d Filter ▸
Discharge Conditions (low sample) 1 100% 53 d (8 wk) 53–53 d Filter ▸

ⓘ Month-by-month stats above are filtered to Amendment / NMA 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
Monday 6 100% 159
⚖️ 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)
    144,135 dated decisions where a submission date and a decision are both known. The submission date is received_date, falling back to validated_date — many council portals publish only the validated date, and the statutory clock runs from it. 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