As a planning officer or member of the public, I need to know which version of each submitted document is current and which versions have been superseded, so that I can rely on the right evidence and understand what changed.
- Priority
- high
- Status
- proposed
- Themes
- transparency, traceability
- Actors
- planning-officer, member of public
- Source
- community-session
Justification
Justification just-0033
The need to distinguish current and superseded documents is partly met when a planning-application-document record can point to the earlier document record it replaces. This makes document succession explicit within a planning application and helps users trace which later document displaced which earlier one. This is only a partial satisfaction because `replaces` alone does not fully identify the current document in every chain, explain what changed between versions, or cover more complex versioning cases such as one document being replaced by several later documents.
Satisfaction: partial; Confidence: medium
Satisfied by:
All of:
See complete justification record: just-0033
Justification just-0034
Adding a readable `name` to each planning-application-document record partly supports access to documents by making document lists understandable without opening each file or inferring a title from the URL. It also partly supports distinction between current and superseded documents because users can compare document titles alongside references when reading a replacement chain. This is only a partial satisfaction because `name` does not itself provide document access, identify the current version, or explain what changed between document versions.
Satisfaction: partial; Confidence: medium
Satisfied by:
All of:
See complete justification record: just-0034