Skip to main content
Planning application data standard

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

Dataset

section 106 agreement

Records of section 106 agreements linked to developments

Fields

Reference

The reference for the section 106 agreement

Reference
reference
Cardinality
1
Datatype
string
Requirement level
MUST

No needs satisfied by this field.

Name

Title or plain-language label for the section 106 agreement so it can be identified

Reference
name
Cardinality
1
Datatype
string
Requirement level
SHOULD

No needs satisfied by this field.

Decision notice

The reference for the decision notice tied to the section 106 agreement

Reference
decision-notice
Cardinality
1
Datatype
string
Related dataset
Decision notice dataset
Requirement level
MUST
Needs this field satisfies

Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field document-url and field documentation-url satisfy need dd-need-016.
  • This field and field document-url and field documentation-url satisfy need dd-need-122.
Document URL

The URL to the published section 106 agreement document

Reference
document-url
Cardinality
1
Datatype
url
Requirement level
SHOULD
Needs this field satisfies

Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field documentation-url satisfy need dd-need-061.
  • This field and field decision-notice satisfy need dd-need-016.
  • One of these fields or field documentation-url satisfy need dd-need-016.
  • This field and field decision-notice satisfy need dd-need-122.
  • One of these fields or field documentation-url satisfy need dd-need-122.
Documentation URL

The URL of the page where the section 106 agreement can be found

Reference
documentation-url
Cardinality
1
Datatype
url
Requirement level
MUST
Needs this field satisfies

Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field document-url satisfy need dd-need-061.
  • This field and field decision-notice satisfy need dd-need-016.
  • One of these fields or field document-url satisfy need dd-need-016.
  • This field and field decision-notice satisfy need dd-need-122.
  • One of these fields or field document-url satisfy need dd-need-122.

Examples

Agreement linked to a decision notice

The agreement has one stable reference for the published record even if source systems also hold legal, finance or supplier identifiers. It links to the decision notice rather than using the planning application reference as its own identity.

Example formats

Table

Field Value
reference section-106-2026-0123
name Section 106 agreement for Former Crown Works
decision-notice decision-2026-0123
document-url https://example.org/planning-applications/2026-0123-ful/section-106-agreement.pdf
documentation-url https://example.org/planning-applications/2026-0123-ful

JSON

{
  "reference": "section-106-2026-0123",
  "name": "Section 106 agreement for Former Crown Works",
  "decision-notice": "decision-2026-0123",
  "document-url": "https://example.org/planning-applications/2026-0123-ful/section-106-agreement.pdf",
  "documentation-url": "https://example.org/planning-applications/2026-0123-ful"
}

Needs satisfied by this dataset

Datasets should only be included in the specification if they satisfy user needs.

dd-need-061 partial satisfied, confidence high

Linked need: dd-need-061

Justification record: just-0029

This dataset is required to satisfy this need.

Recording section 106 agreements as a dataset provides a consistent record of their use. The document-url or fallback documentation-url provides access to the legal documents for further analysis.

This only partially satisfies the need because obligation types, amounts, beneficiaries, mitigation and community benefits are not recorded in structured form for comparison across developments.