💡 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

📊 Chorley

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.

Best month to submit: March — apps submitted then end up with 100.0% approval (sample: 36 decisions). Avoid submitting in April (81.5% approval).
⚖️ What this council's headline is made of. 19.9% of its typed decisions are tree consents, condition discharges and amendments — consent administration that approves at 92.4%. On actual development decisions the approval rate is 88.1% (581 decisions), 4.3 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.
🏆 Best SUBMIT Month
March
Apps submitted then → 100.0% approval (36 decisions)
⚠️ Avoid SUBMITTING In
April
Apps submitted then → 81.5% approval (54 decisions)
⚡ Submit For Fastest Decision
September
Apps submitted then → avg 61 days to decision
🎯 Inverse view — "I want a decision in [month], when do I submit?"

Based on this LPA's typical decision-lag of 95 days (~3 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 Oct 87.3%
Feb Submit by end of Nov 89.6%
Mar Submit by end of Dec 90.9%
Apr Submit by end of Jan 95.7%
May Submit by end of Feb 83.1%
Jun Submit by end of Mar 100%
Jul Submit by end of Apr 81.5%
Aug Submit by end of May 84.4%
Sep Submit by end of Jun 87.4%
Oct Submit by end of Jul 89.6%
Nov Submit by end of Aug 92%
Dec Submit by end of Sep 96.7%

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 Chorley. 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: Amendment / NMA (51 days). Slowest: Heritage / LB (141 days).

Application type Decisions Approval rate Avg days Range
Full / Major 364 90.7% 100 d (14 wk) 30–349 d Filter ▸
Tree Works / TPO 96 95.8% 63 d (9 wk) 14–201 d Filter ▸
Amendment / NMA 44 93.2% 51 d (7 wk) 13–189 d Filter ▸
Advertisement 16 100% 74 d (11 wk) 51–205 d Filter ▸
Heritage / LB 12 91.7% 141 d (20 wk) 55–293 d Filter ▸
Lawful Development (low sample) 6 33.3% 48 d (7 wk) 33–56 d Filter ▸
Discharge Conditions (low sample) 4 0% 162 d (23 wk) 143–185 d Filter ▸
Householder (low sample) 3 66.7% 90 d (13 wk) 55–159 d Filter ▸
Prior Approval (low sample) 2 50% 28 d (4 wk) 1–55 d Filter ▸
Listed Building (low sample) 1 0% 56 d (8 wk) 56–56 d Filter ▸
🤔
Submit-now-or-wait recommendation
BORDERLINE
Current month (November): 89.6% approval. Best (March): 100%. Wait if scheme is borderline; submit now if confident.
Current month's decision speed: ~99 days avg.

📅 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
January 23
95.7%
94d (~13wk) → April 25–252d
February 65
83.1%
95d (~14wk) → May 35–222d
March 36
100%
85d (~12wk) → June 18–251d
April 54
81.5%
98d (~14wk) → July 15–300d
May 77
84.4%
90d (~13wk) → August 10–349d
June 95
87.4%
69d (~10wk) → August 12–208d
July 106
89.6%
71d (~10wk) → September 14–344d
August 75
92%
67d (~10wk) → October 14–336d
September 60
96.7%
61d (~9wk) → November 1–287d
October 55
87.3%
94d (~13wk) → January 10–339d
November 48
89.6%
99d (~14wk) → February 21–280d
December 44
90.9%
102d (~15wk) → March 48–293d

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
Sunday 17 88.2% 125
Monday 136 89.7% 94
Tuesday 118 84.7% 97
Wednesday 137 91.2% 94
Thursday 142 90.1% 96
Friday 176 88.1% 88
Saturday 31 90.3% 80
⚖️ 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