Skip to main content

This is a new service – your feedback will help us to improve it.

Your data has issues

There is a problem

  • 12 issue of type invalid category value
Reference Plan Plan event Event date Actual date Entry date Notes
LP2045-notice Wokingham Local Plan 2045

Publish notice of intention to commence local plan preparation

Invalid category value

2026-06-30 2026-06-30 2026-06-30
LP2045-cfs-start Wokingham Local Plan 2045

Call for Sites starts

Invalid category value

2026-07-06 2026-07-04
LP2045-cfs-end Wokingham Local Plan 2045

Call for Sites Ends

Invalid category value

2026-09-01 2026-07-04
LP2045-scope-start Wokingham Local Plan 2045

Scoping consultation starts

Invalid category value

2026-10-05 2026-07-04
LP2045-scope-end Wokingham Local Plan 2045

Scoping consultation ends

Invalid category value

2026-11-16 2026-07-04
LP2045-gate-1 Wokingham Local Plan 2045

Publication of Gateway 1 self-assessment

Invalid category value

2027-02-26 2026-07-04
LP2045-content-evidence-start Wokingham Local Plan 2045

Consultation on local plan content and evidence starts

Invalid category value

2027-11-08 2026-07-04
LP2045-content-evidence-end Wokingham Local Plan 2045

Consultation on local plan content and evidence ends

Invalid category value

2027-12-20 2026-07-04
LP2045-proposed-start Wokingham Local Plan 2045

Consultation on proposed Local Plan starts

Invalid category value

2028-08-14 2026-07-04
LP2045-proposed-end Wokingham Local Plan 2045

Consultation on proposed Local Plan ends

Invalid category value

2028-10-09 2026-07-04
LP2045-submit Wokingham Local Plan 2045

Submit for examination

Invalid category value

2029-03-05 2026-07-04
LP2045-adopt Wokingham Local Plan 2045

Adoption

Invalid category value

2029-07-31 2026-07-04

How to fix this issue

Your data is missing a plan-event.

The plan timetable guidance explains how to fix the issue:

plan-event

How to improve Wokingham Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL