Specification

Planning application decision

Working draft

Version: 2.0.0 - published 2025-02-13

See versions - See changelog

Abstract

This specification defines the format for how Planning application decisions must be provided as data.

This technical specification is accompanied by guidance, examples and other tools providing feedback to data providers.

What are technical specifications?

Status of this specification

This is a draft specification, following the standards for planning data process [process]. The contents of this specification are currently under development, and liable to change based on feedback.

This specification is intended to be published as one of a number of official data standards for the provision of planning data under the proposed Levelling-up and Regeneration Act 2023 [LURA].

Warning It is inappropriate to cite this document as other than a work in progress.

Comments and feedback on this specification may be provided on the GitHub discussion or sent to digitalland@communities.gov.uk.

Conformance

As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

The key words MAY, MUST, NOT, and SHOULD in this document are to be interpreted as described in [RFC2119] when, and only when, they appear in all capitals [RFC8174] as shown here.

Documentation page

The documentation page is a web page on your website that MUST be accessible as HTML from a public URL.

The documentation page MUST be owned and operated by the data provider. Where the data provider is a local authority or other public body, the web page MUST be on your .gov.uk domain.

A data provider MUST provide a link to the data for all of the Planning application decisions within its jurisdiction on a documentation page.

The documentation page MUST include:

Data

Planning application

The Planning application data MUST be published in an open data format.

The data MUST contain at least one record for each Planning application.

Each record MUST contain the following fields:

  • reference — The planning application reference (for example, "27/AP/9032")
  • name — Name of the planning application (for example, "Residential alteration to Downton House")
  • description — Brief description of the application (for example, "Alterations to two windows on the southern elevation of the 3rd floor flat")
  • address-text — The address of the site as a single line of text (for example, "11 High Street, Ambridge, BO22 3LL")
  • uprn — The UPRN for the primary address of the site
  • geometry — the boundary of the site as a POLYGON or MULTIPOLYGON, with points in the EPSG 4326 coordinate reference system, and WGS85 datum, encoded in Well-Known Text (WKT) representation of geometry
  • point
  • documentation-url — The URL of this planning application in the planning register.
  • planning-application-type — The reference code for the type of planning application (for example "full-planning-permission") (See list of allowable values)
  • planning-decision — The reference code for the planning decision made (for example "pending" or "permission-in-principle") (See list of allowable values)
  • planning-decision-type — The reference code for the way the decision was made (for example "committee") (See list of allowable values)
  • notes — Optional notes text
  • organisation — The reference code for the organisation responsible for processing the planning application
  • entry-date — The date this data was created or last updated
  • start-date — The date the planning application was submitted
  • decision-date — The date the planning application was decided upon
  • end-date — The date the planning application was withdrawn or removed from the register

Planning application log

The planning application log data MUST be published in an open data format.

The data MUST contain at least one record for each planning application log.

Each record MUST contain the following fields:

  • reference — The reference for the planning application status (for example, "27/AP/9032/FULL")
  • planning-application — The planning application reference (for example, "27/AP/9032")
  • planning-application-status — The reference code for the change of planning application status (for example "validated", "decided" or "under-appeal") (See list of allowable values)
  • documentation-url — The URL for a web page where a user can see the change in the planning application status
  • document-url — The URL for a document which evidences the change in the planning application status
  • notes — Optional notes text
  • organisation — The code for the organisation responsible for processing the application
  • event-date — The date this event happened or the change in status applies from
  • entry-date — The date this data was created or last updated
  • start-date — The date this fact was true from
  • end-date — The date this change of event no longer applies. This is the same as the start-date in case of an error

Planning application document

The planning application document data MUST be published in an open data format.

The data MUST contain at least one record for each planning application document.

Each record MUST contain the following fields:

  • reference — An unique identifier for the document (for example, "27/AP/9032/DOC/3")
  • name — The name of this document
  • description — Brief description of this document
  • planning-application — The planning application reference (for example, "27/AP/9032")
  • document-type — The code for this document type (for example "proposed-plan")
  • documentation-url — The webpage where you can find this document
  • document-url — The URL of the actual document
  • notes — Optional notes
  • organisation — The code for the responsible organisation (for example, local-authority-eng:BST)
  • entry-date — The date this data was created or last updated
  • start-date — The date the document was published

Datatypes

Date

Dates MUST conform to [ISO8601] following the Open Standards for government guidance on formatting dates and times in data [formatting-dates-and-times-in-data].

A date value SHOULD be blank if it is unknown. The date may just contain the year 'YYYY' if only the year is known, or 'YYYY-MM' if only the year and month is known.

Geometry

The boundary for the area as a single POLYGON or MULTIPOLYGON value.

In all cases all points MUST be either in the [WGS84] (EPSG::4326) or [ETRS89] (EPSG::4258) coordinate reference system following the Open Standards for government guidance on the exchange of location points [exchange-of-location-point].

Positions calculated by the WGS84 and ETRS89 systems currently deviate by less than half a metre for points within England. Boundaries provided by this dataset are intended to be used as an index. Survey data SHOULD be used where more precision is needed.

Reference

The reference identifies the entity within a data provider.

A URI for the entity may be constructed by a combination of the reference with a IRI prefix value, or be provided in an optional URI field.

A reference value MUST be suitable as the reference part of a [CURIE] identifier.

A reference MUST be unique within the dataset; it MUST NOT have been used by the data provider to identify a different entity.

A reference SHOULD be persistent. A reference SHOULD be used by the data provider to identify the same entity in the future.

The reference MAY be used in other contexts to refer to the entity. For example, the reference may be used to construct a URL to a web page with more information about the Planning application decision.

A reference SHOULD be short and meaningful to a user. For example, the reference may be used to refer to a Planning application decision when completing a form, or contacting a call centre.

Text

All text fields MUST be encoded in UTF-8 [RFC3629] following the Open Standards for government guidance on encoding characters [encoding-characters].

Historical data

Entries SHOULD be ordered by the entry-date, with older entries appearing before later entries.

The end-date field should be used to indicate when an entity is no longer applicable. Entries SHOULD NOT be removed from the data except to correct a mistake, or for the purposes of redacting personal or sensitive information.

Open data formats

Data which does not contain geospatial information (a point or geometry field) MUST be provided as (CSV).

Geospatial data MUST be provided in at least one of the following open data formats:

The preferred format for representing geospatial data is Comma Separated Value (CSV) with the geometry and point fields containing Well Known Text [WKT].

The data MAY also be provided in other data formats such as a [ZIP] archive containing a collection of ESRI shapefiles [Shapefile], a Mapinfo TAB [TAB] file.

Security and privacy considerations

The data MUST NOT contain any personal or sensitive information, unless explicitly required by this specification, or legislation.

There is a risk of people's names or other personally identifiable information appearing in the data, in particular notes, description and other text fields. It is the responsibility of the data provider to review and redact such information before publication. For example, the [OGL3] licence does not cover personal data in the Information.

Colophon

This document is © Crown Copyright and available under the Open Government Licence version 3 licence.

Acknowledgements

The specification builds upon work from the local digital pathfinding local planning authorities, the Reducing Invalid Planning Applications (RIPA) and Back Office Planning System (BOPS) projects.

References

Normative references

[RFC2119]
Key words for use in RFCs to Indicate Requirement Levels. IETF Best Current Practice. https://tools.ietf.org/html/rfc2119
[RFC8174]
Ambiguity of Uppercase vs Lowercase in [RFC2119] Key Words. IETF Best Current Practice. https://datatracker.ietf.org/doc/html/rfc8174
[RFC3629]
UTF-8, a transformation format of ISO 10646. IETF Internet Standard. https://datatracker.ietf.org/doc/html/rfc3629
[RFC4180]
Common Format and MIME Type for Comma-Separated Values (CSV) Files. IETF Informational. https://datatracker.ietf.org/doc/html/rfc4180
[RFC7946]
The GeoJSON Format. Proposed Standard. https://datatracker.ietf.org/doc/html/rfc7946
[RFC3339]
Date and Time on the Internet: Timestamps. IETF Proposed Standard. https://datatracker.ietf.org/doc/html/rfc3339
[tabular-metadata]
Metadata Vocabulary for Tabular Data. W3C Recommendation. https://www.w3.org/TR/2015/REC-tabular-metadata-20151217/
[tabular-data-model]
Model for Tabular Data and Metadata on the Web. W3C Recommendation. https://www.w3.org/TR/2015/REC-tabular-data-model-20151217
[GML]
Geography Markup Language (GML). Open Geospatial Consortium standard (ISO 19136-1:2020). https://www.ogc.org/standards/gml
[OGL3]
Open Government Licence for public sector information. Version 3. https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/
[crown-copyright]
Crown copyright. Section 163 of the Copyright, Designs and Patents Act 1988 as works made by officers or servants of the Crown in the course of their duties. https://www.nationalarchives.gov.uk/information-management/re-using-public-sector-information/uk-government-licensing-framework/crown-copyright/

Informative references

[LURA]
Levelling-up and Regeneration Act. Originated in the House of Commons, Session 2022-23. https://www.legislation.gov.uk/ukpga/2023/55/enacted
[process]
Department for Levelling Up, Housing and Communities planning data standards design process (under development)
[CURIE]
CURIE Syntax 1.0 A syntax for expressing Compact URIs. W3C Working Group Note. https://www.w3.org/TR/2010/NOTE-curie-20101216/
[encoding-characters]
Encoding characters Open Standards for Government. https://www.gov.uk/government/publications/open-standards-for-government/cross-platform-character-encoding-profile
[persistent-resolvable-identifiers]
Persistent resolvable identifiers. Open Standards for Government. https://www.gov.uk/government/publications/open-standards-for-government/persistent-resolvable-identifiers
[formatting-dates-and-times-in-data]
Formatting dates and times in data. Open Standards for Government. https://www.gov.uk/government/publications/open-standards-for-government/date-times-and-time-stamps-standard
[publishing-government-documents]
Publishing government documents. Open Standards for Government. https://www.gov.uk/government/publications/open-standards-for-government/viewing-government-documents
[exchange-of-location-point]
Exchange of location point. Open Standards for Government. https://www.gov.uk/government/publications/open-standards-for-government/exchange-of-location-point
[tabular-data-standard]
Tabular data standard. Open Standards for Government. https://www.gov.uk/government/publications/recommended-open-standards-for-government/tabular-data-standard
[using-csv]
Using CSV file format. Central Digital and Data Office guidance. https://www.gov.uk/guidance/using-csv-file-format
[csv-on-the-web]
CSV on the Web: A Primer. W3C Working Group Note. https://www.w3.org/TR/tabular-data-primer/
[EPSG-4326]
WGS84 - World Geodetic System 1984, used in GPS. EPSG Geodetic Parameter Dataset. https://epsg.io/4326
[GDAL]
GDAL. Open Source Geospatial Foundation. https://gdal.org/
[URI-Fragment]
https://en.wikipedia.org/wiki/URI_fragment
[TAB]
MapInfo TAB format. https://en.wikipedia.org/wiki/MapInfo_TAB_format
[Shapefile]
ESRI Shapefile format. https://en.wikipedia.org/wiki/Shapefile
[ZIP]
ZIP format. https://en.wikipedia.org/wiki/ZIP_(file_format)

Previous versions

These specifications are living documents. When we make material changes to the data structure we update the version number.

Previous versions of the planning-application-decision specification are: