Dataset

planning permission timeline

Records key events in the processing of a planning application.

Fields

Reference

The reference for the timeline entry

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

No needs satisfied by this field.

Planning application

The reference for the related planning application

Reference: planning-application
Cardinality: 1
Datatype: string
Related dataset: Planning application 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 permission-process-event and field event-date satisfy need dd-need-071.
This field and field permission-process-event and field event-date satisfy need dd-need-096.
This field and field permission-process-event and field event-date satisfy need dd-need-065.
This field and field application-types (dataset planning-application), field development-scale (dataset planning-application), field permission-process-event, field event-date, field planning-application (dataset decision-notice) and field decision-date (dataset decision-notice) satisfy need need-ps-025.
This field and field application-types (dataset planning-application), field development-scale (dataset planning-application), field permission-process-event, field event-date, field planning-application (dataset decision-notice) and field decision-date (dataset decision-notice) satisfy need need-ps-026.
This field and field planning-performance-agreement (dataset planning-application), field permission-process-event and field event-date satisfy need need-ps-027.
This field and field permission-process-event, field event-date and field received-date (dataset planning-application) satisfy need dd-need-066.
This field and field permission-process-event and field event-date satisfy need dd-need-063.
This field and field permission-process-event and field event-date satisfy need dd-need-099.
This field and field permission-process-event and field event-date satisfy need dd-need-101.
This field and field permission-process-event and field event-date satisfy need dd-need-110.
This field and field permission-process-event and field event-date satisfy need dd-need-070.
This field and field permission-process-event and field event-date satisfy need dd-need-072.
This field and field permission-process-event and field event-date satisfy need dd-need-102.
This field and field permission-process-event and field event-date satisfy need dd-need-111.
This field and field permission-process-event and field event-date satisfy need dd-need-076.
This field and field permission-process-event and field event-date satisfy need dd-need-068.
This field and field permission-process-event and field event-date satisfy need dd-need-074.
This field and field permission-process-event and field event-date satisfy need dd-need-107.
This field and field permission-process-event and field event-date satisfy need dd-need-069.
This field and field permission-process-event and field event-date satisfy need dd-need-067.

Permission process event

The type of event in the permission process

Reference: permission-process-event
Cardinality: 1
Datatype: enum
Allowed values: Permission process event codelist
Requirement level: MUST

Guidance

How to use it

Use this field only for the defined planning process milestones in the permission-process-event codelist.

It is not intended to contain every action, contact or audit entry held in a case-management system.

For example, record the start of a consultation period:

json { "planning-application": "23/01234/FUL", "permission-process-event": "consultation-start", "event-date": "2026-08-12" }

Record the end of that consultation period as a separate event:

json { "planning-application": "23/01234/FUL", "permission-process-event": "consultation-end", "event-date": "2026-09-09" }

You do not need to, and are not expected to, create events for individual emails, telephone calls, case notes or site visits unless the activity is represented by a defined codelist value.

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 planning-application and field event-date satisfy need dd-need-071.
This field and field planning-application and field event-date satisfy need dd-need-096.
This field and field planning-application and field event-date satisfy need dd-need-065.
This field and field application-types (dataset planning-application), field development-scale (dataset planning-application), field planning-application, field event-date, field planning-application (dataset decision-notice) and field decision-date (dataset decision-notice) satisfy need need-ps-025.
This field and field application-types (dataset planning-application), field development-scale (dataset planning-application), field planning-application, field event-date, field planning-application (dataset decision-notice) and field decision-date (dataset decision-notice) satisfy need need-ps-026.
This field and field planning-performance-agreement (dataset planning-application), field planning-application and field event-date satisfy need need-ps-027.
This field and field planning-application, field event-date and field received-date (dataset planning-application) satisfy need dd-need-066.
This field and field planning-application and field event-date satisfy need dd-need-063.
This field and field planning-application and field event-date satisfy need dd-need-099.
This field and field planning-application and field event-date satisfy need dd-need-101.
This field and field planning-application and field event-date satisfy need dd-need-110.
This field and field planning-application and field event-date satisfy need dd-need-070.
This field and field planning-application and field event-date satisfy need dd-need-072.
This field and field event-date and field notes satisfy need dd-need-079.
This field and field planning-application and field event-date satisfy need dd-need-102.
This field and field planning-application and field event-date satisfy need dd-need-111.
This field and field planning-application and field event-date satisfy need dd-need-076.
This field and field planning-application and field event-date satisfy need dd-need-068.
This field and field planning-application (dataset planning-application-data) and field validated-data-uri (dataset planning-application-data) satisfy need dd-need-098.
This field and field planning-application and field event-date satisfy need dd-need-074.
This field and field planning-application and field event-date satisfy need dd-need-107.
This field and field event-date satisfy need dd-need-062.
This field and field planning-application and field event-date satisfy need dd-need-069.
This field and field planning-application and field event-date satisfy need dd-need-067.

Event date

The date the event occurred

Reference: event-date
Cardinality: 1
Datatype: datetime
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 planning-application and field permission-process-event satisfy need dd-need-071.
This field and field planning-application and field permission-process-event satisfy need dd-need-096.
This field and field planning-application and field permission-process-event satisfy need dd-need-065.
This field and field application-types (dataset planning-application), field development-scale (dataset planning-application), field planning-application, field permission-process-event, field planning-application (dataset decision-notice) and field decision-date (dataset decision-notice) satisfy need need-ps-025.
This field and field application-types (dataset planning-application), field development-scale (dataset planning-application), field planning-application, field permission-process-event, field planning-application (dataset decision-notice) and field decision-date (dataset decision-notice) satisfy need need-ps-026.
This field and field planning-performance-agreement (dataset planning-application), field planning-application and field permission-process-event satisfy need need-ps-027.
This field and field planning-application, field permission-process-event and field received-date (dataset planning-application) satisfy need dd-need-066.
This field and field planning-application and field permission-process-event satisfy need dd-need-063.
This field and field planning-application and field permission-process-event satisfy need dd-need-099.
This field and field planning-application and field permission-process-event satisfy need dd-need-101.
This field and field planning-application and field permission-process-event satisfy need dd-need-110.
This field and field planning-application and field permission-process-event satisfy need dd-need-070.
This field and field planning-application and field permission-process-event satisfy need dd-need-072.
This field and field permission-process-event and field notes satisfy need dd-need-079.
This field and field planning-application and field permission-process-event satisfy need dd-need-102.
This field and field planning-application and field permission-process-event satisfy need dd-need-111.
This field and field planning-application and field permission-process-event satisfy need dd-need-076.
This field and field planning-application and field permission-process-event satisfy need dd-need-068.
This field and field planning-application and field permission-process-event satisfy need dd-need-074.
This field and field planning-application and field permission-process-event satisfy need dd-need-107.
This field and field permission-process-event satisfy need dd-need-062.
This field and field planning-application and field permission-process-event satisfy need dd-need-069.
This field and field planning-application and field permission-process-event satisfy need dd-need-067.

Notes

Optional notes that provide additional context about the timeline event

Reference: notes
Cardinality: 1
Datatype: string
Requirement level: Not specified

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 permission-process-event and field event-date satisfy need dd-need-079.

Examples

Application process events

Create a separate timeline record for each event and select its type from the permission-process-event codelist. This example distinguishes submission, completion of the validation check, the date from which the authority treated the application as valid and the consultation period.

Table

`reference`	`planning-application`	`permission-process-event`	`event-date`
EVT01	2026/0123/FUL	application-submitted	2026-02-14
EVT02	2026/0123/FUL	validation-completed	2026-02-20
EVT03	2026/0123/FUL	valid-from	2026-02-16
EVT04	2026/0123/FUL	consultation-start	2026-02-23
EVT05	2026/0123/FUL	consultation-end	2026-03-16

JSON

[
  {
    "reference": "EVT01",
    "planning-application": "2026/0123/FUL",
    "permission-process-event": "application-submitted",
    "event-date": "2026-02-14"
  },
  {
    "reference": "EVT02",
    "planning-application": "2026/0123/FUL",
    "permission-process-event": "validation-completed",
    "event-date": "2026-02-20"
  },
  {
    "reference": "EVT03",
    "planning-application": "2026/0123/FUL",
    "permission-process-event": "valid-from",
    "event-date": "2026-02-16"
  },
  {
    "reference": "EVT04",
    "planning-application": "2026/0123/FUL",
    "permission-process-event": "consultation-start",
    "event-date": "2026-02-23"
  },
  {
    "reference": "EVT05",
    "planning-application": "2026/0123/FUL",
    "permission-process-event": "consultation-end",
    "event-date": "2026-03-16"
  }
]

Needs satisfied by this dataset

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

No recorded links yet.