🗓 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.
📊 Doncaster
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 68 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 | 98.2% |
| Feb | Submit by end of Dec | 90.9% |
| Mar | Submit by end of Jan | 93.8% |
| Apr | Submit by end of Feb | 92.4% |
| May | Submit by end of Mar | 93.1% |
| Jun | Submit by end of Apr | 89.6% |
| Jul | Submit by end of May | 87% |
| Aug | Submit by end of Jun | 93.4% |
| Sep | Submit by end of Jul | 92.9% |
| Oct | Submit by end of Aug | 98.4% |
| Nov | Submit by end of Sep | 91.5% |
| Dec | Submit by end of Oct | 95.3% |
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 Doncaster. 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 (24 days). Slowest: Discharge Conditions (79 days).
| Application type | Decisions | Approval rate | Avg days | Range | |
|---|---|---|---|---|---|
| Full / Major | 658 | 92.4% | 66 d (9 wk) | 20–343 d | Filter ▸ |
| Discharge Conditions | 143 | 93% | 79 d (11 wk) | 2–301 d | Filter ▸ |
| Tree Works / TPO | 81 | 100% | 24 d (3 wk) | 0–126 d | Filter ▸ |
| Amendment / NMA | 58 | 93.1% | 60 d (9 wk) | 5–246 d | Filter ▸ |
| Advertisement | 27 | 96.3% | 58 d (8 wk) | 23–175 d | Filter ▸ |
| Heritage / LB (low sample) | 5 | 100% | 74 d (11 wk) | 34–125 d | Filter ▸ |
📅 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 | 64 |
93.8%
|
66d (~9wk) | → March | 3–205d |
| February | 79 |
92.4%
|
57d (~8wk) | → April | — |
| March | 87 |
93.1%
|
66d (~9wk) | → May | 1–361d |
| April | 77 |
89.6%
|
73d (~10wk) | → June | — |
| May | 177 |
87%
|
66d (~9wk) | → July | — |
| June | 136 |
93.4%
|
49d (~7wk) | → August | — |
| July | 127 |
92.9%
|
53d (~8wk) | → September | — |
| August | 62 |
98.4%
|
54d (~8wk) | → October | 1–292d |
| September | 71 |
91.5%
|
64d (~9wk) | → November | — |
| October | 86 |
95.3%
|
71d (~10wk) | → December | — |
| November | 57 |
98.2%
|
62d (~9wk) | → January | 1–258d |
| December | 66 |
90.9%
|
74d (~11wk) | → February | 3–246d |
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 | 233 | 91.8% | 85 |
| Tuesday | 233 | 93.6% | 79 |
| Wednesday | 213 | 90.6% | 72 |
| Thursday | 215 | 93% | 68 |
| Friday | 220 | 91.8% | 72 |
📊 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.