Skip to main content

​
Overview

The PreApplication schema represents requests for pre-application advice submitted through digital planning services in England. Pre-application advice allows potential applicants to discuss their proposals with the local planning authority before submitting a formal planning application, helping to identify potential issues early and improve the quality of subsequent applications.

​
Schema Structure

The PreApplication schema has a similar structure to the Application schema but is tailored for pre-application advice requests:
​
data
object
required
Core pre-application data organized into logical sections
​
responses
Responses
required
The ordered list of questions and answers captured throughout the pre-application journey, including policy references and contextual metadata
​
files
File[]
required
List of supporting documents and drawings uploaded with the pre-application request
​
metadata
PlanXMetadata
required
Metadata about the digital planning service and submission

​
Key Differences from Application Schema

While PreApplication shares structural similarities with the Application schema, there are important differences:

​
Simplified Applicant Information

  • No ownership certificates required
  • No agent details (user makes request directly)
  • Less formal declaration requirements

​
No Fee Calculations

  • Pre-application fees are typically handled separately
  • No Community Infrastructure Levy (CIL) information

​
Exploratory Proposals

  • Proposal details may be less specific
  • Boundary information may be approximate
  • Drawings and plans may be conceptual

​
Example Payload

Here’s an example of a pre-application advice request: 
{
  "data": {
    "application": {
      "type": {
        "value": "preApp",
        "description": "Pre-application advice"
      }
    },
    "user": {
      "role": "applicant"
    },
    "applicant": {
      "type": "individual",
      "name": {
        "first": "Ted",
        "last": "Hughes"
      },
      "email": "[email protected]",
      "phone": {
        "primary": "0123456789"
      },
      "company": {
        "name": "Poet Laureates"
      },
      "address": {
        "sameAsSiteAddress": true
      }
    },
    "property": {
      "address": {
        "latitude": 53.5020957,
        "longitude": -1.0205473,
        "title": "75, MAIN STREET, AUCKLEY",
        "source": "Ordnance Survey",
        "uprn": "100050747612",
        "postcode": "DN9 3HW"
      },
      "ward": "Finningley",
      "localAuthorityDistrict": ["Doncaster"],
      "region": "Yorkshire and The Humber",
      "type": {
        "value": "residential.house.detached",
        "description": "Detached"
      },
      "planning": {
        "designations": [
          {
            "value": "tpo",
            "description": "Tree Preservation Order (TPO) or zone",
            "intersects": false
          },
          {
            "value": "greenBelt",
            "description": "Green belt",
            "intersects": false
          }
        ]
      }
    },
    "proposal": {
      "projectType": [
        {
          "value": "extend.rear",
          "description": "Rear extension"
        }
      ],
      "description": "Considering a two-storey rear extension to provide additional living space",
      "boundary": {
        "site": {
          "type": "Feature",
          "geometry": {
            "type": "Polygon",
            "coordinates": [[[...]]]
          }
        }
      }
    }
  },
  "responses": [
    {
      "question": "What type of property is it?",
      "responses": [
        {
          "value": "House"
        }
      ],
      "metadata": {
        "sectionName": "The property"
      }
    }
  ],
  "files": [
    {
      "name": "concept-sketch.pdf",
      "type": ["proposals.illustration"]
    }
  ],
  "metadata": {
    "organisation": "DONC",
    "id": "def-456-uvw",
    "submittedAt": "2024-02-10T10:30:00.000Z",
    "schema": "https://theopensystemslab.github.io/digital-planning-data-schemas/@next/schemas/preApplication.json",
    "source": "PlanX"
  }
}

​
Use Cases

PreApplication requests are typically used for:
  • Early stage proposals - Discussing initial ideas before investing in detailed plans
  • Complex projects - Getting guidance on applications that may be controversial or technically challenging
  • Policy interpretation - Understanding how planning policies apply to a specific site
  • Design feedback - Obtaining comments on proposed design approach
  • Procedural guidance - Clarifying what information will be needed for a formal application

​
JSON Schema

The complete JSON Schema definition is available at: 
https://theopensystemslab.github.io/digital-planning-data-schemas/@next/schemas/preApplication.json
Pre-application advice is discretionary and fees vary by local planning authority. The schema does not currently include fee information.

Application

Full planning application schema

PrototypeApplication

Prototype schema with extended metadata

Build docs developers (and LLMs) love

Get started for freeTalk to us