Overview
The Enforcement schema defines the data structure for planning enforcement reports submitted through digital planning services in England. These reports allow members of the public to notify local planning authorities about suspected breaches of planning control, such as unauthorized development or breaches of planning conditions.
What is Planning Enforcement?
Planning enforcement involves investigating and taking action against breaches of planning control, including:
Development carried out without planning permission
Failure to comply with planning conditions
Unauthorized changes of use
Works to listed buildings without consent
Unauthorized advertisements
Non-compliance with stop notices or enforcement notices
Schema Structure
Core enforcement report data Report type information Always “breach” for enforcement reports
Always “Report a planning breach”
Information about the person reporting the breach Title (Mr, Mrs, Ms, etc.)
Contact address of the complainant Organization details if reporting on behalf of an organization
property
Site & PropertyType
required
Details of the site where the breach is occurring Site address information Source of address data (e.g., “Ordnance Survey”)
Unique Property Reference Number
Unique Street Reference Number
Local authority district(s) the site falls within
Type of property (e.g., “residential.dwelling.house”, “commercial.office”)
Digital boundary of the breach site GeoJSON Feature representing the site boundary
Details of the enforcement report Digital boundary of the specific breach area if different from the site boundary
Timing of the breach ISO 8601 date when the breach started or was first noticed
ISO 8601 date when the breach ended (if applicable). Ongoing breaches will not have an end date.
Detailed description of the planning breach
Categorical types of enforcement breach
alter - Alteration
boundary - New or modified boundary fence or wall
change.use - Change of use
demolish - Demolition
equipment - Equipment or machinery
extend - Extension
harm.heritage - Harm to heritage asset
harm.trees - Harm to trees
lighting - Lighting
new.building - New building
signage - Signage or advertising
works.listed - Unauthorized works to listed building
works.trees - Unauthorized works to protected trees
The ordered list of questions and answers from the report submission journey
Optional supporting files such as photographs or documents evidencing the breach Classified file types (e.g., “photographs.existing”)
Description of what the file shows
Metadata about the digital service and submission Local planning authority code (max 4 characters)
Unique identifier (UUID) for this enforcement report
ISO 8601 datetime when the report was submitted
URL reference to the JSON schema version
Digital planning service provider
Breach Types
The schema supports the following breach type categories:
Physical Development Breaches
Alteration - Unauthorized alterations to existing buildings
Extension - Unauthorized extensions
New Building - Unauthorized new buildings or structures
Demolition - Unauthorized demolition
Boundary - Unauthorized fences, walls, or gates
Change of Use - Unauthorized changes to how land or buildings are used
Heritage and Conservation
Harm to Heritage Asset - Actions affecting listed buildings or conservation areas
Works to Listed Building - Unauthorized works to listed buildings
Harm to Trees - Damage to protected trees
Works to Trees - Unauthorized works to trees with TPOs
Signage - Unauthorized signs or advertisements
Lighting - Unauthorized lighting installations
Equipment - Unauthorized equipment or machinery
Example Payload
Here’s an example of an enforcement report for unauthorized works:
{
"data" : {
"application" : {
"type" : {
"value" : "breach" ,
"description" : "Report a planning breach"
}
},
"complainant" : {
"name" : {
"first" : "Ebenezer" ,
"last" : "Scrooge"
},
"phone" : {
"primary" : "0123456789"
},
"email" : "[email protected] " ,
"address" : {
"line1" : "16 Bayham Street" ,
"town" : "Camden Town" ,
"postcode" : "NW1 0JU" ,
"country" : "UK"
}
},
"property" : {
"address" : {
"latitude" : 51.3873264 ,
"longitude" : 0.506217 ,
"title" : "EASTGATE HOUSE, HIGH STREET, ROCHESTER" ,
"source" : "Ordnance Survey" ,
"uprn" : "000044009430" ,
"postcode" : "ME1 1EW"
},
"localAuthorityDistrict" : [ "Medway" ],
"region" : "South East" ,
"ward" : "Rochester West & Borstal" ,
"type" : {
"value" : "commercial.leisure.museum" ,
"description" : "Museum / Gallery"
},
"boundary" : {
"site" : {
"type" : "Feature" ,
"geometry" : {
"type" : "MultiPolygon" ,
"coordinates" : [[[ ... ]]]
}
},
"area" : {
"hectares" : 0.295809 ,
"squareMetres" : 2958.09
}
}
},
"report" : {
"date" : {
"start" : "2024-01-15"
},
"description" : "Unauthorized extension has been built at the rear of the property without planning permission" ,
"projectType" : [
{
"value" : "extend" ,
"description" : "Extension"
}
]
}
},
"responses" : [
{
"question" : "What type of breach are you reporting?" ,
"responses" : [
{
"value" : "Extension"
}
],
"metadata" : {
"sectionName" : "About the breach"
}
}
],
"files" : [
{
"name" : "photo-of-extension.jpg" ,
"type" : [ "photographs.existing" ],
"description" : "Photograph showing the unauthorized extension from the rear garden"
}
],
"metadata" : {
"organisation" : "MEDW" ,
"id" : "xyz-789-abc" ,
"submittedAt" : "2024-02-01T15:45:00.000Z" ,
"schema" : "https://theopensystemslab.github.io/digital-planning-data-schemas/@next/schemas/enforcement.json" ,
"source" : "PlanX"
}
}
Data Protection Considerations
Enforcement reports contain sensitive information:
Complainant Confidentiality
Many enforcement reports are submitted anonymously or with confidentiality requests
Local planning authorities must protect complainant identities where requested
Consider redacting complainant details before sharing data
Subject Rights
Property owners have rights under data protection legislation
Balance transparency with privacy protection
Be cautious when publishing enforcement data
Investigation Sensitivity
Active enforcement cases may be sensitive
Consider carefully what information is made public and when
Enforcement Process
After receiving an enforcement report, local planning authorities typically:
Initial Assessment - Determine if there appears to be a breach
Site Visit - Visit the site to gather evidence
Investigation - Investigate the breach and consider planning history
Decision - Decide whether enforcement action is expedient
Action - May issue enforcement notice, breach of condition notice, or other action
Resolution - Monitor compliance or pursue further action
Not all breaches warrant enforcement action. Local planning authorities use discretion based on the harm caused and public interest.
JSON Schema
The complete JSON Schema definition is available at:
https://theopensystemslab.github.io/digital-planning-data-schemas/@next/schemas/enforcement.json
Application Planning application schema
PreApplication Pre-application advice schema