Dataset

planning condition

Records of individual planning conditions

Fields

Reference

The reference for the planning condition

Reference: reference
Cardinality: 1
Datatype: string
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 satisfies need dd-need-052.

Name

A plain-language label for the condition

Reference: name
Cardinality: 1
Datatype: string
Requirement level: SHOULD

Guidance

How to use it

Use a short, plain-language label that helps people recognise the condition without reading its full text.

Use a name that describes the subject of the condition. Do not use a condition number, reference or the full condition text as the name.

Examples

Good

Approved Plans
Construction hours
External materials
Contaminated Land

Avoid

Condition 1
Reason
a blank name
the full condition text

No needs satisfied by this field.

Description

The text of the condition that must be met

Reference: description
Cardinality: 1
Datatype: string
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 satisfies need dd-need-042.
This field satisfies need dd-need-104.
This field satisfies need dd-need-105.

Reason

An explanation of why the condition was imposed

Reference: reason
Cardinality: 1
Datatype: string
Requirement level: MUST

Guidance

How to use it

Record the authority's published reason for imposing the condition. Keep this separate from the text of the condition itself.

Use the reason given in the decision notice. Do not create, summarise or infer a reason when one has not been published.

Examples from the sample planning-condition data include:

For the avoidance of doubt and in the interests of proper planning.
To ensure that satisfactory refuse and recycling facilities for construction, excavation and demolition are provided for each phase of the development. (Policies 5.17 of the London Plan and EN7 of the Lambeth Local Plan 2015)
To safeguard future users or occupiers of this site and the wider environment from irreversible risks associated with the contaminants which are present.

The complete published reason may include references to relevant legislation or development plan policies. Retain these as part of the reason.

Needs this field satisfies

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

This field satisfies need dd-need-036.

Organisation

The organisation that maintains the condition clause

Reference: organisation
Cardinality: 1
Datatype: enum
Allowed values: Organisations codelist
Requirement level: MUST

Guidance

How to use it

Record the organisation that maintains the condition clause. For an authority's standard or locally authored condition, use that planning authority's organisation identifier.

This is not necessarily the organisation that requested the condition in a particular case. Record that organisation as requested-by on the related decision-condition record.

No needs satisfied by this field.

Examples

Three-year commencement condition

This example uses a short name to identify the condition and records the condition text separately from the authority's reason for imposing it.

Table

Field	Value
`reference`	COM03
`name`	Commencement - 3 Years
`description`	The development to which this permission relates must be begun not later than the expiration of three years beginning with the date of this permission.
`reason`	This condition is required to be imposed by Section 91 of the Town and Country Planning Act 1990 (as amended).
`organisation`	local-authority:CMD

JSON

{
  "reference": "COM03",
  "name": "Commencement - 3 Years",
  "description": "The development to which this permission relates must be begun not later than the expiration of three years beginning with the date of this permission.",
  "reason": "This condition is required to be imposed by Section 91 of the Town and Country Planning Act 1990 (as amended).",
  "organisation": "local-authority:CMD"
}

Condition requested by another organisation

This condition clause is maintained by the planning authority. Its use on a particular decision can separately record the organisation that requested it.

Example formats

Table
JSON

Table

Field	Value
`reference`	ENV01
`name`	Contaminated land
`description`	No development shall commence until a scheme to assess and remediate land contamination has been submitted to and approved in writing by the planning authority.
`reason`	To ensure that contamination risks to people and controlled waters are identified and addressed.
`organisation`	local-authority:CMD

JSON

{
  "reference": "ENV01",
  "name": "Contaminated land",
  "description": "No development shall commence until a scheme to assess and remediate land contamination has been submitted to and approved in writing by the planning authority.",
  "reason": "To ensure that contamination risks to people and controlled waters are identified and addressed.",
  "organisation": "local-authority:CMD"
}

Needs satisfied by this dataset

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

dd-need-002 fully satisfied, confidence medium

Linked need: dd-need-002

Justification record: just-0015

This dataset is required to satisfy this need.

Creating a dedicated planning condition dataset enables conditions to be recorded in a structured, manageable way so they can be tracked and discharged consistently.