Latest generated outputs 2025-08-29

Author: actions-user

generated/info_model/application/advertising.md

@@ -22,14 +22,21 @@ An application to have conditions approved which have been applied at the time o
 * [Site details](#site-details)
 * [Site Visit Details](#site-visit-details)
 
+### Codelists
+
+* [Contact priority](#contact-priority)
+* [User role type](#user-role-type)
+
 # Application fields
 
 Core planning application structure containing reference information,
 application types, submission details, modules, documents, and fees
 
 
-| reference | name | description | only for application | requirement | notes |
-| --- | --- | --- | --- | --- | --- |
+**Application fields module**
+
+| reference | name | description | requirement | notes |
+| --- | --- | --- | --- | --- |
 | reference | Reference | A unique reference for the data item | MUST |  |
 | application-types | Application types[] | A list of planning application types that define the nature of the planning application | MUST | Select from the **application-type** enum |
 | application-sub-type | Application sub type | Further classification of the application type for specific variations within the main application type | MAY | Select from the **application-sub-type** enum |
@@ -40,7 +47,7 @@ application types, submission details, modules, documents, and fees
 | fee | Fee{} | The fee payable for the application including amounts and transaction details | MAY |  |
 
 
-**Document model**
+**Document component**
 
 field | name | description | required | notes
 -- | -- | -- | -- | --
@@ -51,7 +58,7 @@ document-types | Document types[] | List of codelist references that the documen
 file | File{} | The digital file or a reference to where the file is stored | MUST | 
 
 
-**Fee model**
+**Fee component**
 
 field | name | description | required | notes
 -- | -- | -- | -- | --
@@ -60,7 +67,7 @@ amount-paid | Amount paid | The amount paid towards the application fee | MUST |
 transactions | Transactions[] | References to payments or financial transactions related to this application | MAY | 
 
 
-**File model**
+**File component**
 
 field | name | description | required | notes
 -- | -- | -- | -- | --
@@ -87,21 +94,23 @@ file-size | File size | Size of the file in bytes that can be used to enforce li
 Contact details of the agent acting on behalf of the applicant
 
 
-| reference | name | description | only for application | requirement | notes |
-| --- | --- | --- | --- | --- | --- |
+**Agent contact details module**
+
+| reference | name | description | requirement | notes |
+| --- | --- | --- | --- | --- |
 | agent-reference | Agent reference | A reference to an agent object | MUST |  |
 | contact-details | Contact details{} | A structured object containing contact information for an individual. This component is required for planning in principle (PiP) applications and optional for other application types. Contains email and phone contact information. | MUST |  |
 
 
-**Contact details model**
+**Contact details component**
 
 field | name | description | required | notes
 -- | -- | -- | -- | --
 email | Email | The email address that can be used for electronic correspondence with the individual | MUST | 
 phone-numbers | Phone number(s)[]{} | One or more telephone numbers to contact individual | MUST | 
 
 
-**Phone number model**
+**Phone number component**
 
 field | name | description | required | notes
 -- | -- | -- | -- | --
@@ -115,12 +124,14 @@ contact-priority | Contact priority | The priority of a number | MAY | Select fr
 Details of the agent acting on behalf of the applicant
 
 
-| reference | name | description | only for application | requirement | notes |
-| --- | --- | --- | --- | --- | --- |
+**Agent details module**
+
+| reference | name | description | requirement | notes |
+| --- | --- | --- | --- | --- |
 | agent | agent{} | Details of the agent | MAY |  |
 
 
-**Agent obj model**
+**Agent obj component**
 
 field | name | description | required | notes
 -- | -- | -- | -- | --
@@ -130,7 +141,7 @@ company | Company | The name of a company (that the agent works for) | MAY |
 user-role | User role | The role of the named individual. Agent or proxy | MAY | Select from the **user-role-type** enum
 
 
-**Person obj model**
+**Person obj component**
 
 field | name | description | required | notes
 -- | -- | -- | -- | --
@@ -147,21 +158,23 @@ postcode | Postcode | The postal code | MAY |
 Contact details for the applicant or applicants, including email and phone numbers
 
 
-| reference | name | description | only for application | requirement | notes |
-| --- | --- | --- | --- | --- | --- |
+**Applicant contact details module**
+
+| reference | name | description | requirement | notes |
+| --- | --- | --- | --- | --- |
 | applicant-reference | Applicant reference | Reference to match contact details to a named individual from the applicant details component | MUST |  |
 | contact-details | Contact details{} | A structured object containing contact information for an individual. This component is required for planning in principle (PiP) applications and optional for other application types. Contains email and phone contact information. | MUST |  |
 
 
-**Contact details model**
+**Contact details component**
 
 field | name | description | required | notes
 -- | -- | -- | -- | --
 email | Email | The email address that can be used for electronic correspondence with the individual | MUST | 
 phone-numbers | Phone number(s)[]{} | One or more telephone numbers to contact individual | MUST | 
 
 
-**Phone number model**
+**Phone number component**
 
 field | name | description | required | notes
 -- | -- | -- | -- | --
@@ -179,20 +192,22 @@ Details about the applicants for the planning application,
 including their personal information and contact details
 
 
-| reference | name | description | only for application | requirement | notes |
-| --- | --- | --- | --- | --- | --- |
+**Applicant details module**
+
+| reference | name | description | requirement | notes |
+| --- | --- | --- | --- | --- |
 | applicants | Applicants[]{} |  | MUST |  |
 
 
-**Applicant model**
+**Applicant component**
 
 field | name | description | required | notes
 -- | -- | -- | -- | --
 reference | Reference | A unique reference for the data item | MUST | 
 person | Person{} | Detail to help identify a person | MUST | 
 
 
-**Person obj model**
+**Person obj component**
 
 field | name | description | required | notes
 -- | -- | -- | -- | --
@@ -212,8 +227,10 @@ postcode | Postcode | The postal code | MAY |
 Identifies the national requirement types that apply to this application type
 
 
-| reference | name | description | only for application | requirement | notes |
-| --- | --- | --- | --- | --- | --- |
+**Checklist module**
+
+| reference | name | description | requirement | notes |
+| --- | --- | --- | --- | --- |
 | national-req-types | National requirement types[] | List of the document types required for the given application type | MUST |  |
 
 **Validation rules**
@@ -227,8 +244,10 @@ Information about any conflicts of interest between the applicant/agent and the
 including relationships with staff or elected members
 
 
-| reference | name | description | only for application | requirement | notes |
-| --- | --- | --- | --- | --- | --- |
+**Conflict of interest module**
+
+| reference | name | description | requirement | notes |
+| --- | --- | --- | --- | --- |
 
 **Validation rules**
 
@@ -239,8 +258,10 @@ including relationships with staff or elected members
 Declaration by the applicant or agent confirming the accuracy of the information provided
 
 
-| reference | name | description | only for application | requirement | notes |
-| --- | --- | --- | --- | --- | --- |
+**Declaration module**
+
+| reference | name | description | requirement | notes |
+| --- | --- | --- | --- | --- |
 | name | Name | A name of a person | MUST |  |
 | declaration-confirmed | Declaration confirmed | Confirms the applicant or agent has reviewed and validated the information provided in the application | MUST |  |
 | declaration-date | Declaration date | The date the declaration was made | MUST |  |
@@ -257,8 +278,10 @@ Details about your proposal including related planning permissions,
 development status, and condition information
 
 
-| reference | name | description | only for application | requirement | notes |
-| --- | --- | --- | --- | --- | --- |
+**Description of your proposal module**
+
+| reference | name | description | requirement | notes |
+| --- | --- | --- | --- | --- |
 | related-application | Related application{} | Details of the related planning permission | MUST |  |
 | condition-numbers | Condition numbers[] | List of condition numbers related to this application | MAY |  |
 | has-development-started | Has development started | Whether the development has already started | MUST |  |
@@ -267,7 +290,7 @@ development status, and condition information
 | development-completed-date | Development completed date | Date when development was completed | MAY | Rule: is a MUST if `has-development-completed` is `True` |
 
 
-**Related application details model**
+**Related application details component**
 
 field | name | description | required | notes
 -- | -- | -- | -- | --
@@ -290,8 +313,10 @@ Module for capturing information about materials and details being submitted
 for approval as part of discharging planning conditions
 
 
-| reference | name | description | only for application | requirement | notes |
-| --- | --- | --- | --- | --- | --- |
+**Discharge condition module**
+
+| reference | name | description | requirement | notes |
+| --- | --- | --- | --- | --- |
 | description-list | Description list | Description or list of materials/details that are being submitted for approval | MUST |  |
 
 **Validation rules**
@@ -305,8 +330,10 @@ Information about whether the applicant is trying to discharge part of a conditi
 and details about which part of the condition is being addressed
 
 
-| reference | name | description | only for application | requirement | notes |
-| --- | --- | --- | --- | --- | --- |
+**Part discharge module**
+
+| reference | name | description | requirement | notes |
+| --- | --- | --- | --- | --- |
 | is-discharging-part | Is discharging part | Is applicant trying to discharge part of condition? | MUST |  |
 | discharging-part-details | Discharging part details | Indicate which part of the condition the application relates to | MAY | Rule: is a MUST if `discharging-part` is `True` |
 
@@ -320,8 +347,10 @@ and details about which part of the condition is being addressed
 Information about any pre-application advice sought from the planning authority
 
 
-| reference | name | description | only for application | requirement | notes |
-| --- | --- | --- | --- | --- | --- |
+**Pre-application advice module**
+
+| reference | name | description | requirement | notes |
+| --- | --- | --- | --- | --- |
 | advice-sought | Pre-application advice sought | Whether pre-application advice has been sought from the planning authority | MUST |  |
 | officer-name | Officer name | Name of the planning officer who provided the pre-application advice | MAY | Rule: is a MUST if `advice-sought` is `True` |
 | reference | Reference | A unique reference for the data item | MAY | Rule: is a MUST if `advice-sought` is `True` |
@@ -336,12 +365,14 @@ Information about the location and extent of the site where development
 or works are proposed
 
 
-| reference | name | description | only for application | requirement | notes |
-| --- | --- | --- | --- | --- | --- |
+**Site details module**
+
+| reference | name | description | requirement | notes |
+| --- | --- | --- | --- | --- |
 | site-locations | Site locations[]{} | Details of the sites where development or works are proposed | MUST |  |
 
 
-**Site location model**
+**Site location component**
 
 field | name | description | required | notes
 -- | -- | -- | -- | --
@@ -357,8 +388,8 @@ uprns | UPRNs[] | Unique Property Reference Numbers (UPRNs) for properties withi
 
 **Validation rules**
 
-- At least one site-location must be provided for tree works applications
-- Exactly one site-location for all other applications types
+- {'description': 'At least one site-location must be provided for tree works applications', 'type': 'count-constraint', 'field': 'site-locations', 'when': {'application-type': {'in': ['tree-works']}}, 'require': {'min': 1}}
+- {'description': 'Exactly one site-location for all other applications types', 'type': 'count-constraint', 'field': 'site-locations', 'when': {'application-type': {'not': ['tree-works']}}, 'require': {'exact': 1}}
 - If easting is provided, northing must also be provided and vice versa
 - If latitude is provided, longitude must also be provided and vice versa
 - Site boundary must be valid GeoJSON
@@ -370,15 +401,17 @@ uprns | UPRNs[] | Unique Property Reference Numbers (UPRNs) for properties withi
 Details needed to support a site visit by the planning authority
 
 
-| reference | name | description | only for application | requirement | notes |
-| --- | --- | --- | --- | --- | --- |
+**Site Visit Details module**
+
+| reference | name | description | requirement | notes |
+| --- | --- | --- | --- | --- |
 | can-be-seen-from | Site seen from public area | Can site be seen from a public road, public footpath, bridleway or other public land | MUST |  |
 | contact-type | Site visit contact type | Indicates who the authority should contact to arrange a site visit | MUST | Select from the **site-visit-contact-type** enum |
 | contact-reference | Contact reference | The reference of the applicant or agent who should be contacted for site visits | MAY |  |
 | other-contact | Other site visit contact{} | Details of specifically named contact for site visits | MAY | Rule: is a MUST if `contact-type` is `other` |
 
 
-**Other contact model**
+**Other contact component**
 
 field | name | description | required | notes
 -- | -- | -- | -- | --