Skip to main content

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

data
object
required
Core enforcement report data
responses
Responses
required
The ordered list of questions and answers from the report submission journey
files
File[]
Optional supporting files such as photographs or documents evidencing the breach
metadata
PlanXMetadata
required
Metadata about the digital service and submission

Breach Types

The schema supports the following breach type categories:
  • 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
  • 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:
  1. Initial Assessment - Determine if there appears to be a breach
  2. Site Visit - Visit the site to gather evidence
  3. Investigation - Investigate the breach and consider planning history
  4. Decision - Decide whether enforcement action is expedient
  5. Action - May issue enforcement notice, breach of condition notice, or other action
  6. 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

Build docs developers (and LLMs) love