Check planning restrictions for many postcodes at once
Paste up to 100 postcodes, or the first column of a spreadsheet, and get every designation for each one in a single table you can download as CSV. Useful for sourcing sites, surveying a patch or checking a portfolio. Batch checks are part of Groundwork Pro.
- Up to 100 postcodes
- CSV export
- 14 checks per postcode
How it works
Paste a list, get a table
- Paste up to 100 postcodes, one per line or separated by semicolons, or paste a spreadsheet: Groundwork reads the first column and ignores the rest, so a reference column can stay next to it.
- Lines without a digit, such as a header row, are skipped, and repeated postcodes are checked once.
- Each postcode is placed at its centre point from the Office for National Statistics postcode directory, then checked against the same data as a single check, across England, Wales and Scotland. Northern Ireland postcodes are not supported and are marked as such.
- The results appear as a table you can download as CSV. A full list of 100 takes a minute or two, because each postcode is checked against the flood map live.
Example input
postcode,reference SW1A 1AA,Plot 1 CF10 3RB,Plot 2 EH1 2NG,Plot 3
Pasted from a spreadsheet, this checks the three postcodes in the first column; the header and the reference column are ignored.
What each column means
- query (CSV only)
- What you pasted for that line, exactly as you pasted it.
- Postcode
- The postcode as the national directory writes it. In the CSV it is empty when the postcode could not be found; the table shows what you pasted instead.
- Council
- The local planning authority at the postcode’s centre. In the table, a row without one says why: postcode not found, outside the nations Groundwork covers, or a point outside every council boundary.
- outcome (CSV only)
- Postcode found, Postcode not found, Outside the UK nations we cover, or Northern Ireland postcode: not supported, so you can filter the rows that need a second look.
- checked_at_utc (CSV only)
- When the batch ran, in UTC, so a saved file shows how current its results are.
- 14 check columns
- One column per restriction, from tree preservation orders and conservation areas to flood zones and battlefields. Both the table and CSV say None found when the published data has no match; other cells say Applies here, Nearby (within 50 metres of a boundary), No council data (the snapshot Groundwork uses has no data for that check from the council) or Not checked (Groundwork has not integrated that check in the nation, or the source did not answer).
Batch or single check?
A single check lets you drag the pin onto the exact building, shows each designation on a map with its name, date and distance, links to its record where the source has one, and makes a PDF report with Pro.
A batch check answers one question fast for many places: does anything apply around each postcode, and what. It uses the postcode’s centre point, so where a boundary runs through a postcode, open that one in a single check before you rely on it.
Who uses it
- Surveyors and conveyancers screening a list of instructions before they open each file.
- Builders, developers and land agents sourcing sites, who need to drop plots in conservation areas, the green belt or flood zones early.
- HMO landlords and letting agents checking a portfolio for Article 4 directions.
- Housing associations and estate teams surveying the restrictions across their stock.
FAQ