Skip to main content

This is a proof of concept viewer for the planning permission specifications - your feedback will help us to improve it.

Back dd-need-036

See reasons for each condition

Satisfied

As an applicant, I need to know why each planning condition was imposed and how it relates to policy or the proposal so that I can understand, comply with or challenge the requirements attached to the permission.

Priority
high
Status
proposed
Themes
conditions, transparency
Actors
applicant
Source
interview, other
Variations
dd-need-118

Justification

Justification just-0019

Keeping `reason` separate from the condition `description` makes both the requirement and its justification explicit. This helps applicants understand why the condition was imposed and lets planning authorities maintain a transparent and auditable record without relying on a combined block of text. For now, the need is satisfied by `planning-condition.reason`, keeping `decision-condition` as the dataset that joins a condition to a particular decision. This placement is provisional while the distinction between reusable condition clauses and conditions as imposed is investigated. If the model changes, this justification must be reviewed, but the need for the reason remains.

Satisfaction: full; Confidence: high

Satisfied by:

Field
reason
in

See complete justification record: just-0019