🗓 Submission Timing Intelligence
When is the best month — and weekday — to submit your planning application? Real approval-rate + decision-speed data from 144,156 dated decisions across UK LPAs.
📊 Brecon Beacons
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 23 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 | 33.3% |
| Jul | Submit by end of Jun | 100% |
| Aug | Submit by end of Jul | 100% |
| Sep | Submit by end of Aug | 100% |
| Oct | Submit by end of Sep | 100% |
| Nov | Submit by end of Oct | 66.7% |
| 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 Brecon Beacons. 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 (37 days). Slowest: Heritage / LB (134 days).
| Application type | Decisions | Approval rate | Avg days | Range | |
|---|---|---|---|---|---|
| Full / Major | 188 | 90.4% | 113 d (16 wk) | 27–365 d | Filter ▸ |
| Discharge Conditions | 88 | 100% | 65 d (9 wk) | 1–351 d | Filter ▸ |
| Heritage / LB | 28 | 100% | 134 d (19 wk) | 29–364 d | Filter ▸ |
| Amendment / NMA | 27 | 88.9% | 37 d (5 wk) | 8–177 d | ✕ clear |
| Tree Works / TPO | 10 | 100% | 43 d (6 wk) | 34–61 d | Filter ▸ |
| Advertisement (low sample) | 6 | 66.7% | 94 d (13 wk) | 56–113 d | Filter ▸ |
| Listed Building (low sample) | 2 | 100% | 172 d (25 wk) | 56–287 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 |
|---|---|---|---|---|---|
| January | 5 |
100%
|
32d (~5wk) | → February | 21–61d |
| May | 3 |
33.3%
|
22d (~3wk) | → June | 8–37d |
| June | 3 |
100%
|
32d (~5wk) | → July | 15–55d |
| October | 3 |
66.7%
|
30d (~4wk) | → November | 26–37d |
| December | 3 |
100%
|
27d (~4wk) | → January | 23–33d |
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 | 5 | 100% | 30 |
| Tuesday | 6 | 83.3% | 62 |
| Wednesday | 9 | 77.8% | 30 |
📊 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,156 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.