Your data has issues

There is a problem

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

Reference	Plan	Plan event	Event date	Entry date
wafsp-publish-notice-intention-commence	westmorland-and-furness-council-supplementary-plan Missing associated entity	publish-notice-intention-commence	2026-06-30	2026-06-30
wafsp-scoping-consultation-start	westmorland-and-furness-council-supplementary-plan Missing associated entity	proposed-plan-consultation-start	2028-06-12	2026-06-30
wafsp-scoping-consultation-end	westmorland-and-furness-council-supplementary-plan Missing associated entity	proposed-plan-consultation-end	2028-08-07	2026-06-30
wafsp-examination-submitted	westmorland-and-furness-council-supplementary-plan Missing associated entity	examination-submitted	2028-10-09	2026-06-30
wafsp-adopted	westmorland-and-furness-council-supplementary-plan Missing associated entity	adopted	2028-04-30	2026-06-30

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 Westmorland and Furness 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