Digital Local Plans: The Data Trail Land Teams Should Start Using Now

The new local-plan system makes parts of the plan process easier to track as data rather than prose. That is useful, but it is easy to overstate what has changed.

As at 2 August 2026, the approved standard covers plan data, timetable data and the local-plan housing requirement. It does not yet turn every site assessment, constraint or allocation into one complete national dataset.

The opportunity is therefore practical: use the structured data that exists, preserve its provenance and connect it to the site evidence you already hold.

What the approved standard covers

The statutory guidance published on 13 May 2026 relates to the Planning Data (England) Regulations 2026.

For plans in the new system, authorities must publish two datasets:

• a plan dataset; and

• a plan-timetable dataset.

The plan dataset carries information such as the plan reference, name, type, description, period, document links and entry date. Where applicable, it also includes the authority and required-housing fields.

The timetable dataset records events against the plan, including an event date and, later, the actual date.

Why references matter more than filenames

The standard requires a unique reference for each plan and each timetable event. A good reference should remain stable when the data is updated.

That is a small but important design principle for a land team. Do not use the downloaded filename as the identity of a plan or milestone. Filenames change. Stable references let you compare versions and link multiple sites to the same authority event.

The same principle should apply to promoted sites: one stable site identity, with changing evidence attached to it.

The minimum ingestion record

When you use an authority dataset, preserve:

• authority name and code where provided;

• plan reference and name;

• dataset type;

• source webpage URL;

• endpoint or document URL;

• entry date;

• date your team retrieved it; and

• a copy or hash of the version used for the decision.

Do not detach a number from its source. “Housing requirement: 10,852” is not a reliable record without the plan, date and status that give the number meaning.

Dates should drive exceptions

The standard uses YYYY-MM-DD for full dates and sets out required milestone values for timetable events. That consistency makes simple change detection possible.

A weekly comparison should flag only:

• a new plan or timetable entry;

• a changed event date;

• an actual date added;

• a changed housing requirement;

• a new document URL; or

• a missing item that existed in the prior version.

The team can then decide whether the change affects any promoted site. The data should reduce noise, not generate a new inbox of undigested alerts.

Keep structured data and documents together

The guidance on public availability asks authorities to publish certain documents in machine-readable and searchable formats as well as meeting applicable data standards.

For a land team, the useful pattern is:

structured event → source document → affected site → decision

For example, a timetable dataset may show that the content-and-evidence consultation date moved. The source page should lead to the published consultation material. The site record should then identify whether the revised date changes an evidence deadline or representation strategy.

What not to automate blindly

Structured data does not remove planning judgement.

Do not automatically infer that:

• a site is allocated because it appears in a map;

• a changed timetable improves the site’s prospects;

• a housing requirement is adopted policy merely because it is published; or

• an authority’s assessment is correct because it is machine-readable.

Status, source and date still matter. So does the distinction between adopted policy, draft guidance, consultation evidence and an authority’s working assessment.

A five-part data checklist

Before relying on a local-plan data point, confirm:

1. Identity — Which plan, authority and site does it belong to?

2. Status — Is it adopted, proposed, guidance, evidence or consultation material?

3. Date — When was it entered, published and checked?

4. Source — Can another team member reach the authoritative document?

5. Decision — What, if anything, changes for the promoted site?

Digital plan data is valuable because it can expose change quickly. Its value is lost if the team strips away the context needed to act on it.

For a working monitoring structure, see The Planning Watchlist Every Land Team Should Maintain. For turning timetable data into action, read Build a Promotion Calendar From the Local-Plan Timetable.