The planning data service and how current its datasets are

The national planning data service at planning.data.gov.uk is the closest thing England has to a single map of planning constraints, and its datasets are only as current as the bodies that publish them. Every entity on the platform carries a publishing organisation and a collection date, which means you can tell how old a conservation area boundary or an Article 4 direction is before you rely on it. Treat the platform as the fastest first pass on a site and the authority's own map as the position of record.

For a planning consultant assembling a constraints appraisal, that distinction is the whole discipline. A designation missing from the platform has not necessarily been revoked. It may simply never have been published in a machine-readable form.

What the service publishes, and what it leaves out

The platform gathers datasets from two quite different sources. National bodies supply the layers they maintain anyway, so listed buildings, scheduled monuments, registered parks and gardens, sites of special scientific interest, National Parks, National Landscapes and Green Belt extents are generally present and reasonably current.

Local planning authorities supply the rest, and this is where coverage is patchy. Conservation area boundaries, Article 4 direction areas, tree preservation orders and brownfield land registers all depend on an authority publishing data to the required specification. Many have. Some have not, and some have published part of what they hold.

What the service does not do is interpret. It will tell you that a polygon exists and who published it. It will not tell you which policy applies, whether the boundary was amended last month, or whether the version on the authority's website differs.

Finding the publisher behind a dataset

Every dataset page names the organisation responsible, and every individual entity page carries the source and the date it was collected. Use both.

The practical routine is short:

1. Open the dataset page and read the specification, so you know what the fields mean.
2. Check which organisations have supplied data for that dataset, because absence of an authority tells you as much as the presence of a boundary.
3. Open the individual entity and note its entry date and start date, which are different things.
4. Follow the source link back to the publisher's own endpoint.
5. Record the collection date in your appraisal, not just the finding.

That last step matters when a report is read a year later. A constraints schedule that says the site is outside any conservation area, without saying when the data was collected, invites the question you cannot then answer.

Why the data lags adoption

A council adopts an Article 4 direction at committee, publishes a notice, and the direction takes effect on a stated date. Publishing a machine-readable dataset and having it collected by the national platform is a separate administrative act, and the gap between the two can be substantial.

The same is true in the other direction. A conservation area appraisal that adjusts a boundary produces a new polygon only once the authority republishes. Designations that predate digital record keeping are sometimes captured from scanned maps, with the imprecision that implies at the edges.

None of this makes the platform unreliable. It makes it a source with a known lag, which is a different problem and a manageable one. Where the finding is decisive for your advice, go behind it.

Cross-checking against the authority's own map

For any constraint that changes your recommendation, check three places rather than one.

The authority's own interactive map or constraints search comes first, because that is what the case officer will consult. The statutory register and recent committee reports come next, since a designation made in the last few months may appear there before it appears anywhere else. For heritage assets, the National Heritage List for England is definitive on listing and grade, and a listed building's official entry will tell you more about what is protected than a polygon ever will.

Flood zones deserve their own mention. The Flood Map for Planning is the authority for Flood Zones 2 and 3, and a Flood Risk Assessment has to be based on it rather than on a generalised national layer. The same logic applies to protected sites, where the Defra mapping service carries the detail. If you are reading habitat inventory data for an ecology scoping exercise, the national planning platform is the wrong tool entirely.

Taking an extract you can put in a report

Downloads are available as CSV and as GeoJSON, and there is a query interface for anyone who wants to build a repeatable check rather than clicking through. For a one-off site appraisal the download is usually enough.

Two habits make extracts defensible. Save the raw download alongside your appraisal rather than only the map you produced from it, and record the date you took it. Where a client challenges a constraint six months later, producing the file you actually used ends the conversation quickly.

Do not crop the extract to your red line before saving it. Designations close to but outside a site frequently matter, and a listed building 40 metres away can shape a scheme as much as one on it. That proximity is exactly what a Heritage Statement has to address.

Telling the publisher something is wrong

The platform does not own the data, so corrections go to the publishing organisation. For a local dataset that means the council. For a national layer it means the body that maintains it.

Report it properly and in writing. Give the entity reference, the dataset, the nature of the error and the evidence, and copy the case officer if the error affects a live application. Errors do get fixed. But not on your programme, so do not plan around a correction arriving. State the discrepancy in your submission instead, set out which version you have relied on and why, and let the officer resolve it on the file.

Using it for a constraints appraisal

The sensible place for the platform is early. Run it at the point you are deciding whether a site is worth pursuing, before anyone is paid to draw anything.

A workable sequence is a national platform sweep for designations, then the authority's map for local designations and policy allocations, then the flood and protected site services, then a check on whether the strategic road network is engaged if access is onto or near a trunk road, then the register for planning history. Each step either closes a question or generates a survey requirement. By the end you know which technical reports the site is going to need and roughly what the evidence base will cost.

Where public rights of way could cross the site, the platform will not help you, since the definitive map is held by the county or unitary authority. Checking the definitive map is a separate exercise and one that catches out more schemes than it should.

PlanScope checks a site against Environment Agency flood data, Historic England listed buildings and conservation areas, and Natural England protected site layers, then flags which reports the constraints point towards. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.