🗓 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.
📊 Dundee
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 58 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 | 91.3% |
| Mar | Submit by end of Jan | 96.7% |
| Apr | Submit by end of Feb | 100% |
| May | Submit by end of Mar | 97.6% |
| Jun | Submit by end of Apr | 100% |
| Jul | Submit by end of May | 100% |
| Aug | Submit by end of Jun | 96.2% |
| Sep | Submit by end of Jul | 94.7% |
| Oct | Submit by end of Aug | 100% |
| Nov | Submit by end of Sep | 97.5% |
| Dec | Submit by end of Oct | 96.4% |
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 Dundee. 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: Discharge Conditions (51 days). Slowest: Full / Major (85 days).
| Application type | Decisions | Approval rate | Avg days | Range | |
|---|---|---|---|---|---|
| Tree Works / TPO | 390 | 97.7% | 54 d (8 wk) | 1–272 d | ✕ clear |
| Full / Major | 45 | 53.3% | 85 d (12 wk) | 0–315 d | Filter ▸ |
| Advertisement | 32 | 96.9% | 62 d (9 wk) | 0–136 d | Filter ▸ |
| Heritage / LB | 26 | 84.6% | 84 d (12 wk) | 3–315 d | Filter ▸ |
| Discharge Conditions | 21 | 95.2% | 51 d (7 wk) | 0–262 d | Filter ▸ |
| Prior Approval (low sample) | 4 | 75% | 28 d (4 wk) | 14–35 d | Filter ▸ |
| Amendment / NMA (low sample) | 3 | 0% | 127 d (18 wk) | 57–196 d | Filter ▸ |
| Listed Building (low sample) | 2 | 100% | 56 d (8 wk) | 41–71 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 | 30 |
96.7%
|
48d (~7wk) | → March | 7–99d |
| February | 37 |
100%
|
64d (~9wk) | → April | 18–221d |
| March | 42 |
97.6%
|
56d (~8wk) | → May | 1–206d |
| April | 29 |
100%
|
54d (~8wk) | → June | 7–162d |
| May | 24 |
100%
|
62d (~9wk) | → July | 10–158d |
| June | 26 |
96.2%
|
56d (~8wk) | → August | 6–272d |
| July | 38 |
94.7%
|
39d (~6wk) | → August | 3–150d |
| August | 38 |
100%
|
52d (~7wk) | → October | 2–224d |
| September | 40 |
97.5%
|
48d (~7wk) | → November | 6–178d |
| October | 28 |
96.4%
|
57d (~8wk) | → December | 4–207d |
| November | 35 |
100%
|
59d (~8wk) | → January | 1–185d |
| December | 23 |
91.3%
|
61d (~9wk) | → February | 16–160d |
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 | 104 | 98.1% | 48 |
| Tuesday | 75 | 98.7% | 57 |
| Wednesday | 60 | 96.7% | 75 |
| Thursday | 76 | 94.7% | 69 |
| Friday | 73 | 100% | 49 |
📊 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.