Skip to main content

Overview

The Application schema represents the core data structure for planning applications in England that are generated by digital planning services. This schema captures all the information needed from the initial application submission, including applicant details, property information, proposal details, supporting files, and user responses throughout the application journey.

Schema Structure

The Application schema is composed of five main sections:
data
object
required
Core application data organized into logical sections
preAssessment
PreAssessment[]
The result of the application based on information provided by the user, prior to assessment by a planning officer. Available for certain application types like Prior Approval and Lawful Development Certificates.
responses
Responses
required
The ordered list of questions, answers, and their metadata captured throughout the application journey. Each response includes the question text, user’s answer(s), and optional metadata like policy references and section names.
files
File[]
required
List of files uploaded and attached to the application
metadata
Metadata
required
Metadata about the digital planning service and submission

Application Types

The Application schema supports numerous application types, including:

Planning Permission

  • Full householder applications
  • Minor applications
  • Major applications
  • Outline applications
  • Retrospective applications
  • Listed building applications

Prior Approval

  • Part 1 Class A (larger home extensions)
  • Part 1 Class AA (additional storeys)
  • Part 3 (changes of use)
  • Part 4, 6, 7, 11, 14, 16, 17, 18, 19, 20 (various permitted development rights)

Lawful Development Certificates

  • Existing use or development (LDC Existing)
  • Proposed use or development (LDC Proposed)

Other Application Types

  • Listed Building Consent
  • Advertisement Consent
  • Works to Trees (notices and consents)
  • Hedgerow Removal Notice
  • Land Drainage Consent

Example Payload

Here’s an example of a Planning Permission Full Householder application:
{
  "data": {
    "application": {
      "type": {
        "value": "pp.full.householder",
        "description": "Planning Permission - Full householder"
      },
      "fee": {
        "calculated": 258,
        "payable": 258,
        "category": {
          "sixAndSeven": 258
        },
        "exemption": {
          "disability": false,
          "resubmission": false
        },
        "reduction": {
          "sports": false,
          "parishCouncil": false,
          "alternative": false
        }
      },
      "declaration": {
        "accurate": true,
        "connection": {
          "value": "none"
        }
      }
    },
    "user": {
      "role": "proxy"
    },
    "applicant": {
      "type": "individual",
      "name": {
        "first": "David",
        "last": "Bowie"
      },
      "email": "[email protected]",
      "phone": {
        "primary": "Not provided by agent"
      },
      "address": {
        "sameAsSiteAddress": true
      },
      "ownership": {
        "interest": "owner.sole",
        "certificate": "a"
      }
    },
    "property": {
      "address": {
        "latitude": 51.4656522,
        "longitude": -0.1185926,
        "title": "40, STANSFIELD ROAD, LONDON",
        "source": "Ordnance Survey",
        "uprn": "100021892955",
        "postcode": "SW9 9RZ"
      },
      "boundary": {
        "site": {
          "type": "Feature",
          "geometry": {
            "type": "Polygon",
            "coordinates": [[[...]]]
          }
        },
        "area": {
          "hectares": 0.012592,
          "squareMetres": 125.92
        }
      }
    },
    "proposal": {
      "projectType": [
        {
          "value": "extend.rear",
          "description": "Rear extension"
        }
      ],
      "description": "Construction of a single-storey rear extension"
    }
  },
  "responses": [...],
  "files": [...],
  "metadata": {
    "organisation": "LBH",
    "id": "abc-123-xyz",
    "submittedAt": "2024-01-15T12:00:00.000Z",
    "schema": "https://theopensystemslab.github.io/digital-planning-data-schemas/@next/schemas/application.json"
  }
}

JSON Schema

The complete JSON Schema definition is available at:
https://theopensystemslab.github.io/digital-planning-data-schemas/@next/schemas/application.json
The @next version reflects the latest development version. For production use, reference a specific released version number.

PreApplication

Schema for pre-application advice requests

PrototypeApplication

Prototype schema with additional metadata

PostSubmissionApplication

Extended schema for applications in back office systems

Build docs developers (and LLMs) love