Joint listed building data specification
Updated 2 March 2026
Applies to England and Wales
© Crown copyright 2026
This publication is licensed under the terms of the Open Government Licence v3.0 except where otherwise stated. To view this licence, visit nationalarchives.gov.uk/doc/open-government-licence/version/3 or write to the Information Policy Team, The National Archives, Kew, London TW9 4DU, or email: psi@nationalarchives.gov.uk.
Where we have identified any third party copyright information you will need to obtain permission from the copyright holders concerned.
This publication is available at https://www.gov.uk/government/publications/hm-land-registry-local-land-charges-programme/joint-listed-building-data-specification--3
Listed building data requirements
This specification aligns the listed building data requirements of Local Land Charges Programme and the Ministry of Housing, Communities & Local Government’s Digital Planning Programme, enabling local authorities to use a single dataset that serves both programmes and reduces administrative burden.
| Name | Attribute/Value Type/Multiplicity | Comment |
|---|---|---|
| Registration date | registration-date: Date 1 | |
| Originating Authority | originating-authority: String 1 | |
| Point for further information | further-information-location: String 1..3 | |
| Geometry Identifier | ID: Identifier 1 | |
| Land Interest Geometry | land-interest-geometry: GeoJSON feature collection 1 | |
| Land Description | land-description: Feature 1 | All charges must have a Land Description, which can be either Charge Address or Charge Geographic Description |
| Charge Address | land-description: charge-address: Feature attribute 0..1 | |
| Secondary Address Information | land-description: charge-address Line 1: String 1 | Where Charge Address is used this attribute must be entered |
| Primary Address Information | land-description: charge-address Line 2: String 0..1 | |
| Supplementary Address Information | land-description: charge-address Line 3: String 0..1 | |
| Supplementary Address Information | land-description: charge-address Line 4: String 0..1 | |
| Supplementary Address Information | land-description: charge-address Line 5: String 0..1 | |
| Supplementary Address Information | land-description: charge-address Line 6: String 0..1 | |
| Postcode | land-description:postcode: String [1 | Where Charge Address is used this attribute must be entered |
| Unique Property Reference Number | uprn: Integer 1 | Where Charge Address is used this attribute must be entered |
| Charge Geographic Description | land-description: charge-geographic-description: String 0..1 | |
| Local Land Charge Register Part | old-register-part: Integer 0..1 | |
| Originating authority charge identifier | originating-authority-charge-identifier: String 0..1 | |
| Statutory Provision | statutory-provision: String 0..1 | |
| LA File Reference | further-information-reference: String 0..1 | |
| Date charge created | charge-creation-date: Date 0..1 | |
| Supplementary Charge Information | supplementary-information: String 0..1 |
Suggested mapping
This specification aligns the listed building data requirements of Local Land Charges Programme and the Ministry of Housing, Communities & Local Government’s Digital Planning Programme, enabling local authorities to use a single dataset that serves both programmes and reduces administrative burden.
| MHCLG Requirements | Name | Attribute/Value Type/Multiplicity | Comment |
|---|---|---|---|
| Listed-building | Originating authority charge identifier | originating-authority-charge-identifier: String 0..1 | This field should be populated by the HE reference (where available) |
| name | Land Description | land-description: Feature 1 | Name of the property or land |
| entry-date | Registration date | registration-date: Date 1 | Registration date is Date of entry on the Local Land Charges Register, for existing charges it is the date entered on the current register. |
| start-date | Date charge created. | charge-creation-date: Date 0..1 | Date charge created is Date on which the registered charge first came into existence. |
| end-date | Expiry Date | expiry-date: Date 0..1 | Only used ‘where the charge is enforceable for a fixed term’ so would be reasonably certain this is not applicable to LB |