Guidance

Provide your development plan data

Working Draft

23 January 2026

This guidance is under development. Help us improve it and give your feedback by email.

Follow this guidance when providing your development plan data.

Local planning authorities (LPAs) must create, publish and keep a timetable up to date for a local plan, minerals plan, waste plan, or supplementary plan created or updated using the new local plan system.

Providing planning data means making it available publicly to a standard so that services such as planning.data.gov.uk can find it, understand its quality, and trust it will be sustained. Help design this and other data standards to ensure they your needs.

Providing your development plan data

Take the following steps to provide your development plan data:

  1. Prepare your data
  2. Check your data
  3. Publish your data
  4. Tell us about your data
  5. Keep your data up-to-date

Prepare your data

Start by reviewing any data we may already have about your organisation on planning.data.gov.uk using the check and provide service. This might include:

  • any data you have provided in the past
  • information found on your website
  • open data from other public sources

We treat the data you provide as being more authoritative than data we have collected from you previously, or found elsewhere.

You can download tabular data we have for your organisation as a CSV file from the check and provide service and edit it using a spreadsheet or other CSV editors.

Similarly, you can download geospatial data we have for your organisation as CSV or GeoJSON from planning.data.gov.uk and modify it using QGIS or other GIS tools.

You must provide data containing the mandatory fields identified here where required by law. Otherwise your data does not need to be complete or perfect to start with. For many purposes having some data is better than no data, so start by providing the best development plans information you have, and continue to iterate and improve it over time.

Files

For development plans you need to provide 2 datasets:

You may also provide the following dataset:

Each dataset needs to be provided in a separate CSV file following the government tabular data standard.

The fields and format of the data you need to prepare are documented below, and formally defined in the technical specifications attached to this page.

Field names

You can use uppercase or lowercase names for your fields, and any punctuation characters are ignored, meaning the following examples are all valid ways of naming the start-date field in your data:

  • StartDate
  • Start Date
  • START_DATE
  • start.date

Reference values

Each dataset has a reference field. Reference values are important to help people find and link to the data. Where you don’t have a reference for an item, you will need to create one that is:

  • unique within your data
  • persistent — it doesn’t change when the data is updated

A good reference is something you already use. Where these aren't unique, you make them unique by appending the year, or even the full date. Great references are short, easy to read, to pronounce and remember.

Date values

All dates must be in the format YYYY-MM-DD, following the guidance for formatting dates and times in data.

Where you don't know the precise date you can enter just the month YYYY-MM or even just the year YYYY. The platform will default a start-date to the first of the month, or the first of January, and an end-date to the last day of the month, or the last day of December. For example:

  • 2025-04-19
  • 2025-04
  • 2025

Development plan dataset

Mandatory fields

Your development plan data must contain the following fields:

  • reference
  • name
  • dataset
  • period-start-date
  • period-end-date
  • documentation-url
  • document-url
  • required-housing

reference

Give each local plan a unique reference. For example:

  • LP-BRX-2024
  • 34069/County-Durham-Plan
  • central-lincolnshire
  • barnet-local-plan-2021-2036

name

Use the title of the adopted local plan document. For example:

  • County Durham Plan
  • South Oxfordshire Joint Local Plan

dataset

Enter one of the following values to indicate the type of development plan:

  • local-plan
  • supplementary-plan
  • minerals-plan
  • waste-plan

period-start-date

Enter the start of the plan period. This is usually just a year in YYYY format. For example:

  • 2026

period-end-date

Enter the end of the plan period. This is usually just a year in YYYY format. For example:

  • 2038

documentation-url

The URL of the webpage on your website for the local plan

Each entry in the local plan dataset should link to a documentation webpage that includes the information in the entry as well as links to where this data may be downloaded, and any other supporting documents. Where there are several local plans listed on a single webpage, you can use an anchor link (fragment identifier) to make the URL for each plan unique. For example:

  • https://eastcambs.gov.uk/planning-and-building-control/planning-policy-and-guidance/adopted-local-plan/local-plan
  • https://example.com/local-plans/#example-local-plan-2011
  • https://example.com/local-plans/#example-local-plan-2024

document-url

Enter the URL for the main or core plan document. This is usually a PDF file. For example:

  • https://www.walthamforest.gov.uk/sites/default/files/2024-02/LBWF_LocalPlan_LP1_Feb2024_compressed.pdf

required-housing

Enter the minimum number of homes that the plan seeks to provide during the plan period. For example:

  • 24852

This field is mandatory for new local plans. When producing a joint local plan you should also provide an entry for each local-planning-authority area in a separate local-plan-housing dataset.

Your development plan data should also contain the following fields:

  • local-planning-authorities
  • mineral-planning-authorities
  • waste-planning-authorities
  • entry-date
  • start-date

local-planning-authorities

Enter the reference (the GSS code) for the Local Planning Authority area covered by this local or supplementary plan. For a joint local plan, enter the list of Local Planning Authority references, each separated by semi-colon ';' character. For example:

  • E60000001
  • E60000132;E60000133;E60000135;E60000136

mineral-planning-authorities

Enter the reference for the Mineral Planning Authority area covered by this minerals plan. For a joint minerals plan, enter the list of Mineral Planning Authority references, each separated by semi-colon ';' character. For example:

  • GMCA

waste-planning-authorities

Enter the reference for the Waste Planning Authority area covered by this waste plan. For a joint waste plan, enter the list of Waste Planning Authority references, each separated by semi-colon ';' character. For example:

  • NLWA

entry-date

Enter the date this data was created or modified.

start-date

Enter the date when the plan was officially adopted. This value should match the relevant entry for when the plan was recorded as being adopted in the local-plan-timetable. Leave this value blank for plans which are being prepared, or haven't yet been adopted.

Optional fields

Your development plan data may also contain the following fields:

  • end-date
  • notes

end-date

Enter the date the local plan was withdrawn or revoked, otherwise leave this field blank.

notes

You may provide notes on how this data was made, and help users differentiate the plan from others with a similar name. For example:

  • Barnsley's Local Plan as adopted by Full Council on 3 January 2019

Development plan timetable dataset

Record the key events and milestones in the timetable when producing your development plan. For new local plans your timetable must include a precise predicted-date against each entry. Update the entry to include the actual date in the start-date field when the event takes place.

For local plans, minerals plans, and waste plans being produced under the new local plans process, your timetable must include a entry for each of the following events:

  • commenced
  • scoping-consultation-start
  • scoping-consultation-end
  • gateway-1-self-assessment
  • content-consultation-start
  • content-consultation-end
  • gateway-2-advice-sought
  • gateway-2-advice-published
  • proposed-plan-consultation-start
  • proposed-plan-consultation-end
  • gateway-3-advice-sought
  • gateway-3-advice-published
  • gateway-3-further-advice-sought
  • gateway-3-repeat-advice-published
  • examination-submitted
  • examination-recommendations-published
  • adopted

Supplementary plans being produced under the new local plans process must contain a row for each of the following events:

  • commenced
  • proposed-plan-consultation-start
  • proposed-plan-consultation-end
  • examination-submitted
  • adopted

Your development plan timetable may also include rows with dates for each of the following events:

  • main-modification-consultation-start
  • main-modification-consultation-end
  • examination-pause-start
  • examination-pause-end
  • additional-consultation-start
  • additional-consultation-end
  • annual-monitoring-report-published
  • plan-evaluation-report-published
  • withdrawn
  • revoked

Mandatory fields

Your development plan timetable data must contain the following fields:

  • reference
  • development-plan
  • development-plan-event
  • predicted-date

reference

Give each event a reference which is unique for the event within the dataset. Where a timetable has more than one event of the same type, you can add a date to make them unique. For example:

  • LP1-public-consultation
  • LP1-public-consultation-2025

development-plan

Enter the reference of the development plan which this event forms part of its timetable. For example:

  • LP-BRX-2024
  • central-lincolnshire

development-plan-event

Enter a Development Plan Event reference. For example:

  • commenced
  • examination-submitted
  • adopted

predicted-date

Enter the date when this event is expected to happen. For example:

  • 2027-01-01

New local plans require a single, precise date. When recording events for older schemes where the predicted date is a range, you may record an approximate date for the period.

Your development plan timetable data should also contain the following fields:

  • entry-date
  • start-date

entry-date

Enter the date this data was created or modified.

start-date

Enter the date when the timetable event occurred. Leave this field blank when the event is in the future.

Optional fields

Your development plan timetable data may also contain the following fields:

  • notes

notes

Enter any notes or commentary which helps you or others understand how this data was made, or how it may be interpreted.

Local plan housing number dataset

Use this dataset to provide the individual required-housing number for each Local Planning Authority within a joint new local plan. You may also use this dataset to provide additional housing numbers related to a local plan. There is no need to provide this dataset for other kinds of plan.

Mandatory fields

Your local plan housing number data must contain the following fields:

  • reference
  • local-plan
  • required-housing

reference

Give each set of housing numbers a unique reference value. For example:

  • 34069/County-Durham-Plan
  • central-lincolnshire
  • barnet-local-plan-2021-2036

local-plan

Enter the reference for the local plan which these numbers apply.

required-housing

Enter the minimum number of homes that the plan seeks to provide within this local-planning-authority area. For example:

  • 24852

Your local plan housing number data should also contain the following fields:

  • entry-date
  • start-date

entry-date

Enter the date this data was created or modified.

start-date

Enter the date these numbers were finalised.

Optional fields

Your local plan housing number data may also contain the following fields:

  • end-date
  • notes

end-date

Enter the date these numbers were withdrawn, otherwise leave this field blank.

notes

You may provide a short description to help users differentiate the plan from others with a similar name. For example:

  • Barnsley's Local Plan as adopted by Full Council on 3 January 2019

Check your data

Use the check and provide service to review your data before you publish it. The service will show you how the data will appear on planning.data.gov.uk along with feedback on how you might improve your data.

Publish your data

Publishing your data consists of two parts:

  • An endpoint where the data can be downloaded from
  • A source webpage where the information contained in the data is presented on your website

Endpoint

Make your data available at a public endpoint. An endpoint is a URL from which anyone can download the data. This can be either:

  • a single file hosted on your website
  • a file hosted on another public website including GitHub
  • an Open Geospatial Consortium Web Feature Service (OGC WFS)
  • an open application programming interface (API) such as ArcGIS

Ensure your endpoint URL is documented and linked to from a public webpage to help people easily find and download the data.

The documentation webpage for your endpoint should include a clear statement that the data is provided as open data under the Open Government Licence.

Source webpage

The source webpage is where a user can see the same information that is shown in the data. This is usually one of your existing planning policy pages on your official .gov.uk website.

It is important that the source webpage links to the endpoint documentation webpage to help users trust the authenticity of the data.

Tell us about your data

Once you have published the data, tell us about it so we can index and quickly make it available nationally on planning.data.gov.uk.

Use the check and provide service to tell us where it is.

You will need to provide for each dataset:

  • the source webpage URL where the information in the data is presented on your website
  • the endpoint URL from which the data can be collected

The service also asks for your name and email address as a point of contact in case of any issues.

Keep your data up-to-date

Continue to improve your data, and act on the feedback from the service to ensure your data meets the specification.

You also need to update and republish your data whenever there's a change to your development plans information.

We look for changes to the data at all of the endpoint URLs we know about every night, so we can quickly update planning.data.gov.uk.

It is simpler if you publish your changes to the same endpoint URL. If you create a new endpoint you need to tell us about your data again.

Contact us

If you need any help at any stage of the process, let us know by emailing digitalland@communities.gov.uk and a member of our team will be in touch.

You can participate in improving the design of this data, and help ensure planning data meets your needs at design.planning.data.gov.uk.

Technical specifications

Development plan technical specification (23 January 2026)

HTML