Skip to content

Schemas

Jessica McInchak edited this page Sep 19, 2024 · 3 revisions

Schemas

Multiple data schemas related to the life cycle of a planning application are defined within this repository.

Here's an overview of them.

Pre-application

Coming soon

Application

An application describes a planning application at the point of submission from an applicant to a Local Authority.

Its high-level shape is:

  • applicationType- One of these statutory application types (#TODO link list)
  • data - Structured information parsed from the responses
    • application - Applicable fees, declarations, associated pre-applications or applications
    • user - Role of the user applying for themself or on behalf of someone else
    • applicant - Contact details for the applicant, their agent if applicable, owners, site contacts, and more
    • property - Details about the property as it exists now, the site address, applicable designations and constraints
    • proposal - Details about the works being proposed and changes to the property
  • responses - All questions and answers applicable to this users journey, including policy references and service metadata
  • preAssessment - An assessment of this application, determined by flags picked up by answers. Pre-assessment is based on the users responses only, and is pending validation by a planning officer who will issue a formal decision
  • files - Labelled list of files uploaded by the user to support this application
  • metadata - Technical information about this payload like its unique session identifier, service URL, and which version of the schema it was validated against

Decision

TBD

Assessment

TBD

Appeals

TBD

<< More contributions here! >>

TBD

Clone this wiki locally