🗓 Submission Timing Intelligence
When is the best month — and weekday — to submit your planning application? Real approval-rate + decision-speed data from 144,167 dated decisions across UK LPAs.
📊 Blaby
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.
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 43 days (~1 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 Dec | 100% |
| Feb | Submit by end of Jan | 100% |
| Mar | Submit by end of Feb | 100% |
| Apr | Submit by end of Mar | 100% |
| May | Submit by end of Apr | — |
| Jun | Submit by end of May | 100% |
| Jul | Submit by end of Jun | 100% |
| Aug | Submit by end of Jul | 92.3% |
| Sep | Submit by end of Aug | 100% |
| Oct | Submit by end of Sep | 100% |
| Nov | Submit by end of Oct | 100% |
| Dec | Submit by end of Nov | 100% |
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 Blaby. 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 (44 days). Slowest: Full / Major (101 days).
| Application type | Decisions | Approval rate | Avg days | Range | |
|---|---|---|---|---|---|
| Full / Major | 397 | 92.2% | 101 d (14 wk) | 28–362 d | Filter ▸ |
| Discharge Conditions | 126 | 99.2% | 85 d (12 wk) | 8–298 d | Filter ▸ |
| Tree Works / TPO | 107 | 99.1% | 44 d (6 wk) | 7–174 d | ✕ clear |
| Amendment / NMA | 30 | 96.7% | 53 d (8 wk) | 2–283 d | Filter ▸ |
| Advertisement | 18 | 100% | 66 d (9 wk) | 36–163 d | Filter ▸ |
| Householder | 16 | 100% | 66 d (9 wk) | 35–125 d | Filter ▸ |
| Conservation Area (low sample) | 7 | 100% | 37 d (5 wk) | 30–45 d | Filter ▸ |
| Heritage / LB (low sample) | 7 | 100% | 154 d (22 wk) | 54–292 d | Filter ▸ |
| Lawful Development (low sample) | 4 | 75% | 59 d (8 wk) | 42–74 d | Filter ▸ |
| Prior Approval (low sample) | 3 | 100% | 37 d (5 wk) | 35–41 d | Filter ▸ |
| Outline (low sample) | 1 | 0% | 113 d (16 wk) | 113–113 d | Filter ▸ |
ⓘ Month-by-month stats above are filtered to Tree Works / TPO 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 |
|---|---|---|---|---|---|
| January | 16 |
100%
|
42d (~6wk) | → February | 12–174d |
| February | 3 |
100%
|
35d (~5wk) | → March | 23–49d |
| March | 5 |
100%
|
29d (~4wk) | → April | 14–42d |
| May | 4 |
100%
|
67d (~10wk) | → July | 42–98d |
| June | 10 |
100%
|
42d (~6wk) | → July | 26–60d |
| July | 13 |
92.3%
|
61d (~9wk) | → September | 11–120d |
| August | 20 |
100%
|
44d (~6wk) | → September | 29–63d |
| September | 9 |
100%
|
34d (~5wk) | → October | 7–56d |
| October | 16 |
100%
|
41d (~6wk) | → November | 30–56d |
| November | 4 |
100%
|
52d (~7wk) | → January | 25–64d |
| December | 7 |
100%
|
40d (~6wk) | → January | 30–51d |
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 received | Decisions | Approval rate | Avg days |
|---|---|---|---|
| Monday | 30 | 100% | 45 |
| Tuesday | 21 | 100% | 38 |
| Wednesday | 31 | 100% | 49 |
| Thursday | 9 | 100% | 46 |
| Friday | 15 | 93.3% | 43 |
📊 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,167 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.