Plan timetable

There is a problem

27 ‘plan’ fields do not match the ‘reference’ field in the plan dataset

entity: 5110096

reference: wbc-local-plan-proposed-plan-consultation-start
plan: undefined
waverley-borough-council-local-plan-2026
plan-event: proposed-plan-consultation-start
event-date: 2028-03-06
actual-date
entry-date: 2026-06-11
notes: We will seek feedback from stakeholders on the proposed local plan for an 8-week period. This is the version of the final Local Plan that we intend to submit to the Secretary of State for examination

How to fix this issue

Your data is missing a plan.

The plan timetable guidance explains how to fix the issue:

plan

This is the unique reference for your overall plan. For example:

LP-BRX-2024
barnet-local-plan-2021-2036
hertfordshire-minerals-and-waste-plan
essex-minerals-plan
essex-waste-plan
county-durham-supplementary-plan

The ‘plan’ field in your plan timetable dataset must match the ‘reference’ field from your plan dataset.

This diagram shows the relationship between the plan dataset and the plan timetable dataset. The reference value from your plan dataset needs to match the plan value in your plan timetable dataset. This is so that we can match your timetable to the right plan.

How to improve Waverley Borough Council’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