As an applicant / developer, I need to see the reasons behind each planning condition so that I can understand why it was imposed and how it relates to policy or the proposal.
- Priority
- high
- Status
- proposed
- Themes
- conditions, transparency
- Actors
- applicant, developer
- Source
- interview, other
Justification
Justification just-0019
Keeping `reason` separate from the condition `description` makes both the requirement and its justification explicit. This helps applicants and developers understand why the condition was imposed and how it relates to policy or the proposal, without having to interpret 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:
See complete justification record: just-0019