Guidance

Publish your local plan data

Working Draft

8 November 2025

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

Follow this guidance when providing your local plan data.

You must follow this approved data standard to meet the requirements of the Town and Country Planning (Local Planning) (England) Regulations 2026 and the Planning Data (England) Regulations 2026.

Local planning authorities (LPAs) must create, publish and keep a plan timetable up to date. This applies to the following plans that you create or update using the new plan-making system:

  • local plans
  • minerals and waste plans
  • supplementary plans 

Providing planning data means making it available publicly to a standard, so that anyone using services such as planning.data.gov.uk can:

  • find it
  • understand its quality, meaning and purpose
  • trust it will be accurate and maintained

Providing your local plan data

Take the following steps to provide your local 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 previously collected or that we find elsewhere.

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

You must provide data for the mandatory fields identified.

Datasets

For local plans you may provide the following dataset:

You need to provide each dataset in a separate CSV file and follow the government tabular data standard.

Field names

You can use a field name with uppercase, lowercase and any punctuation characters. For example, you can use any of the following names for 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 your data. If you do not have a reference value for an item, you will need to create one that:

  • is unique within your data
  • does not change when the data is updated

A good reference is something you already use. If your reference is not unique, you can make them unique by adding the year or full date. Great references are:

  • short
  • easy to read
  • easy to pronounce and remember

Date values

All dates must be in the format YYYY-MM-DD as set out in 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

Local plan dataset

List the local plans you are responsible for with one row for each current, emerging or historical local plan.

Mandatory fields

Your Local plan data must contain the following fields:

  • reference
  • documentation-url
  • document-url

reference

Give each local plan a unique reference.

For example:

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

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

Your Local plan data should also contain the following fields:

  • name
  • dataset
  • period-start-date
  • period-end-date
  • local-planning-authorities
  • mineral-planning-authorities
  • waste-planning-authorities
  • local-plan-process
  • entry-date
  • start-date

name

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

  • County Durham Plan
  • South Oxfordshire Joint Local Plan

dataset

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 may be just the year in YYYY format. For example:

  • 2038

local-planning-authorities

Enter the reference (the GSS code) for the Local Planning Authority area covered by this local 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 GSS code for the  Mineral Planning Authority area that this minerals plan covers. For a joint minerals plan, enter the list of references and separate each of them with a semi-colon.

For example:

  • E47000001
  • E60000331;E60000225

waste-planning-authorities

Enter the GSS code for the  Waste Planning Authority area that this local or supplementary plan covers. For a joint waste plan, enter the list of references and separate each of them with a semi-colon.

For example:

  • E47000001
  • E60000331;E60000225

local-plan-process

Indicate the local plan examination process for the local plan using one of the following values:

  • 2012 for plans prepared under the Town and Country Planning (Local Planning) (England) Regulations 2012, including transitional arrangements
  • 2026 for plans prepared under new Local Planning Regulations (TBD)

entry-date

Enter the date you created or modified the data.

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 Local 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

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

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.

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

  • local-planning-authority
  • required-housing
  • committed-housing
  • allocated-housing
  • broad-locations-housing
  • windfall-housing
  • entry-date
  • start-date

local-planning-authority

This should be the GSS code (statistical geography) for the local-planning-authority area to which the housing numbers apply. See the Local Planning Authority dataset.

For example:

  • E60000001 — The GSS code for the County Durham LPA area

required-housing

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

For example:

  • 24852

committed-housing

Enter the amount of housing already committed for development within this local-planning-authority area.

allocated-housing

Enter the total number of homes planned for through local plan housing site allocations including housing components of mixed-use site allocations within this local-planning-authority area.

For example:

  • 9239

broad-locations-housing

Enter the total number of homes expected towards the end of the local plan period and attributed to ‘broad locations for growth’, as opposed to site allocations within this local-planning-authority area.

For example:

  • 15660

windfall-housing

Enter the total number of homes expected to arise from housing sites not specifically identified in the local plan within this local-planning-authority area.

For example:

  • 160

entry-date

Enter the date you created or modified the data.

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

Local plan document dataset

Provide a list of documents associated with your local plan. Add a separate row with a link to each document on your website.

Mandatory fields

Your Local plan document data must contain the following fields:

  • reference
  • name
  • local-plan
  • document-url

reference

Give each document a unique reference.

name

Enter the title of the document.

local-plan

Enter the reference for the local plan which the document is associated with.

For example:

  • LP-BRX-2024
  • central-lincolnshire

document-url

Enter the URL for the document. This is often a PDF file.

Your Local plan document data should also contain the following fields:

  • document-types
  • documentation-url
  • entry-date
  • start-date

document-types

Enter at least one of the following local-plan-document-type values:

  • adoption-statement
  • area-action-plan
  • core-strategy
  • financial-viability-study
  • inspectors-report
  • local-development-scheme
  • local-plan
  • local-plan-review
  • policies-map
  • strategic-flood-risk-assessment
  • strategic-housing-market-assessment
  • supplementary-planning-document
  • sustainability-apprasial
  • site-allocations
  • viability-assessment
  • sustainability-appraisal

You can list more than one category, separated by a semi-colon ';' character.

For example:

  • local-plan
  • local-plan;core-strategy;site-allocations

documentation-url

Enter the URL of the webpage on your website which documents and links to this document.

For example:

  • https://calderdale.gov.uk/planning-and-building-control/planning-policy/local-plan

entry-date

Enter the date you created or modified the data.

start-date

Enter the date the document was published.

Optional fields

Your Local plan document data may also contain the following fields:

  • description
  • end-date
  • notes

description

end-date

Enter date when the document was archived. Otherwise leave this field blank.

notes

Enter any notes or commentary which helps to understand this data.

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

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, use the check and provide service to tell us where it is. This is so we can index the data and quickly make it available nationally on planning.data.gov.uk.

For each dataset, you will need to provide the:

  • source webpage URL where the information in the data is presented on your website
  • endpoint URL where you can collect the data

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 the service feedback to make sure that your data meets the specification.

We update planning.data.gov.uk with any changes to the data at all the endpoint URLs each day.

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

Email digitalland@communities.gov.uk to get help.

You can help improve the design of this and other planning data at design.planning.data.gov.uk.

Technical specifications

Local plan technical specification (8 November 2025)

HTML