Your data has issues
There is a problem
- 12 entries with plan field must match the reference field in the relevant plan
| Reference | Plan | Plan event | Event date | Actual date | Entry date | Notes |
|---|---|---|---|---|---|---|
| LP1-Notice-of-intention-to-commence |
LP-HILLINGDON-2026 Missing associated entity |
publish-notice-intention-commence | 2026-05-12 | 2026-05-28 | ||
| LP2-Scoping-consultation-start |
LP-HILLINGDON-2026 Missing associated entity |
scoping-consultation-start | 2026-07-09 | 2026-05-28 | ||
| LP3-Scoping-consultation-end |
LP-HILLINGDON-2026 Missing associated entity |
scoping-consultation-end | 2026-08-21 | 2026-05-28 | ||
| LP4-Gateway-1 |
LP-HILLINGDON-2026 Missing associated entity |
gateway-1-self-assessment | 2026-09-17 | 2026-05-28 | ||
| LP5-Consultation-LP-Content-evidence-start |
LP-HILLINGDON-2026 Missing associated entity |
plan-content-evidence-consultation-start | 2026-11-05 | 2026-05-28 | ||
| LP6-Consultation-LP-Content-evidence-end |
LP-HILLINGDON-2026 Missing associated entity |
plan-content-evidence-consultation-end | 2027-01-14 | 2026-05-28 | ||
| LP7-Gateway-2 |
LP-HILLINGDON-2026 Missing associated entity |
gateway-2-advice-sought | 2027-03-01 | 2026-05-28 | ||
| LP8-Consultation-proposed-LP-start |
LP-HILLINGDON-2026 Missing associated entity |
proposed-plan-consultation-start | 2027-06-15 | 2026-05-28 | ||
| LP9-Consultation-proposed-LP-end |
LP-HILLINGDON-2026 Missing associated entity |
proposed-plan-consultation-end | 2027-08-27 | 2026-05-28 | ||
| LP10-Gateway-3 |
LP-HILLINGDON-2026 Missing associated entity |
gateway-3-advice-sought | 2027-10-01 | 2026-05-28 | ||
| LP11-Submission-of-LP |
LP-HILLINGDON-2026 Missing associated entity |
examination-submitted | 2027-11-01 | 2026-05-28 | ||
| LP12-Adoption-of-LP |
LP-HILLINGDON-2026 Missing associated entity |
adopted | 2028-05-01 | 2026-05-28 |
How to fix this issue
Your data is missing a plan.
The plan timetable guidance explains how to fix the issue:
plan
How to improve London Borough of Hillingdon’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL