Overview The PostSubmissionApplication schema extends the core application data model to track the full lifecycle of a planning application after it enters a back office planning system. This schema captures the submission, validation, consultation, assessment, and appeal stages, along with comments from the public and specialist consultees.
Schema Structure PostSubmissionApplication is a discriminated union type that varies based on the applicationType. The generic structure includes:
The specific type of application (e.g., “pp.full.householder”, “ldc.proposed”, “pa.part1.classA”)
Extended application data tracking the application through the planning process Core application information including reference number, current stage, and status The local planning authority’s reference number for this application
Current stage in the planning process (submission, validation, consultation, assessment, appeal)
status
ApplicationStatus
required
Current status (undetermined, granted, refused, withdrawn, etc.)
localPlanningAuthority
LocalPlanningAuthority
required
Information about the local planning authority processing the application Name of the local planning authority
Official code for the authority
Whether public comments are accepted throughout the process
Details about when and how the application was submitted ISO 8601 datetime of submission
Channel used for submission (e.g., “PlanX”, “Planning Portal”)
Validation stage information (if the application has reached this stage) ISO 8601 datetime when application was validated
Whether the application was deemed valid
Explanation if application was invalid
Consultation period details (if applicable for this application type) ISO 8601 datetime when consultation period began
ISO 8601 datetime when consultation period ends
When the public notice was published
Assessment and decision information ISO 8601 datetime of the decision
decision
AssessmentDecision
required
The decision made (granted, refused, withdrawn, etc.)
Details of the formal decision notice
Planning conditions attached to a granted permission
Appeal information if the decision was appealed ISO 8601 datetime when appeal was lodged
The Planning Inspectorate’s decision (allowed, dismissed, split)
ISO 8601 datetime of appeal decision
The planning officer handling the application Comments received during the application process Array of comments from members of the public Unique identifier for the comment
When the comment was submitted
Whether the comment supports or objects to the application
Brief summary of the comment
Array of comments from specialist consultees (e.g., highways, conservation officer) Name of the consultee organization or department
The consultee’s recommendation
Detailed comments from the consultee
Files associated with the application, including those uploaded during submission and added later What stage or aspect the file relates to (submission, validation, consultation, assessment, appeal)
When the file was uploaded
submission
PrototypeApplication
required
The original application data as submitted through the digital planning service
metadata
PostSubmissionMetadata
required
Extended metadata tracking the application through the system Local planning authority code
Unique identifier for this application
Original submission datetime
When this payload was generated
Application Lifecycle Stages The PostSubmissionApplication tracks applications through these stages:
1. Submission
Application received by the local planning authority
Initial triage and allocation to case officer
2. Validation
Case officer checks application is valid and complete
May request additional information
Application is validated or invalidated
3. Consultation
Public consultation period (typically 21 days)
Specialist consultees are consulted
Comments and representations received
4. Assessment
Case officer assesses application against planning policies
Recommendation made
Decision issued (granted, refused, or withdrawn)
5. Appeal (if applicable)
Appellant lodges appeal with Planning Inspectorate
Appeal process conducted
Inspector’s decision issued
Example Payload Here’s an example of a Lawful Development Certificate application in the submission stage:
{ "applicationType" : "ldc.proposed" , "data" : { "application" : { "reference" : "ABC-123-XYZ" , "stage" : "submission" , "status" : "undetermined" }, "localPlanningAuthority" : { "name" : "London Borough of Hackney" , "code" : "LBH" , "publicCommentsAcceptedUntilDecision" : true }, "submission" : { "submittedAt" : "2024-03-01T09:00:00.000Z" , "submittedVia" : "PlanX" }, "caseOfficer" : { "name" : "Casey Officer" , "email" : "[email protected] " } }, "files" : [ { "association" : "submission" , "uploadedAt" : "2024-03-01T09:00:00.000Z" , "name" : "proposed-plans.pdf" , "type" : [ "sitePlan.proposed" ] } ], "submission" : { "applicationType" : "ldc.proposed" , "data" : { /* Original PrototypeApplication data */ } }, "metadata" : { "organisation" : "LBH" , "id" : "faae04cd-0ec2-479e-b7fb-14b3e7acae35" , "submittedAt" : "2024-03-01T09:00:00.000Z" , "generatedAt" : "2024-03-01T09:01:00.000Z" , "schema" : "https://theopensystemslab.github.io/digital-planning-data-schemas/@next/schemas/postSubmissionApplication.json" } }
Supported Application Types PostSubmissionApplication supports all application types defined in the ApplicationType enum, including:
All Planning Permission types (pp.*)
All Prior Approval types (pa.*)
All Lawful Development Certificate types (ldc.*)
Listed Building Consent
Advertisement Consent
Works to Trees
And many more
Each type uses the same base structure with type-specific variations in the data fields.
JSON Schema The complete JSON Schema definition is available at:
https://theopensystemslab.github.io/digital-planning-data-schemas/@next/schemas/postSubmissionApplication.json
This schema contains sensitive information including personal data. Ensure appropriate data protection measures are in place when storing or transmitting PostSubmissionApplication data.
PrototypeApplication The original application schema
PostSubmissionPublishedApplication Redacted version for public access
Application Base application schema