Almost every council search request needs a property boundary plan attached. It's one of those steps that looks like nothing on paper and quietly eats time in practice.
The plan usually comes from the same place: HM Land Registry's INSPIRE Index Polygons. They're free, they're national, and they're indicative — which is exactly the word that matters here. Get that word wrong and you risk treating a rough extent as a legal boundary.
Here's what INSPIRE polygons actually are, how search firms use them to attach a plan to a council request, and why the boring download-convert-attach routine costs more than you'd think.
What are INSPIRE Index Polygons?
INSPIRE Index Polygons are HM Land Registry's open dataset showing the indicative extent of registered freehold titles in England and Wales. Each polygon has a Land Registry INSPIRE ID, the data is updated monthly, and it's released under the Open Government Licence — so any firm can use it freely.
The dataset exists because of the EU INSPIRE Directive, which required public bodies to publish certain spatial data in a common form. HM Land Registry's contribution was the freehold extents. You can read the official guidance on HM Land Registry INSPIRE Index Polygons and download the INSPIRE dataset directly.
What it gives you is a mapping layer: draw a property, get the polygon that broadly covers it. What it does not give you is an address database, charge information, or anything resembling a search result. It's geometry, nothing more.
Are INSPIRE polygons the legal boundary of a property?
No — and this is the caveat to get right. INSPIRE Index Polygons are indicative boundaries for registered freehold land. They show roughly where a title sits, not the precise legal line. They aren't definitive, they aren't the title plan, and they aren't a full address or search dataset.
This trips people up because the polygons look authoritative. They're crisp, they snap to features, they came from Land Registry. But "indicative" is doing real work in that sentence. The general boundaries rule means even the official title plan rarely fixes an exact line, and the INSPIRE layer is a step further removed again.
So what are they good for? Telling a council, unambiguously, which parcel of land your search covers. That's the job. Locating the property, not adjudicating where the fence should be. If a client wants the exact legal boundary, that's a title plan and possibly a surveyor — not an INSPIRE polygon.
Why does a council search request need a boundary plan?
A council needs to know exactly which parcel of land a search covers before it can return the right local land charges and CON29 answers. A boundary plan removes the ambiguity that a postal address can't always resolve — and most councils expect one attached in their own preferred format.
The ambiguity is real. Flats inside a converted house, plots split off a larger title, new-builds that don't have a settled address yet, garden land sold separately. In each case the address line is either missing or shared, and the plan is what pins the request to the right piece of ground.
The plan isn't only for the council's benefit. A clear, consistent boundary plan on every request is also your own audit trail. If a search ever comes back queried, the plan you attached shows precisely what you asked about. Firms that scribble or skip it lose that protection without realising.
How do search firms attach an INSPIRE plan today?
Most firms do it by hand, and the routine is the same everywhere: find the property, grab the INSPIRE polygon, export it, convert it to whatever the council or portal accepts, then attach it to the request. Each order is only a few minutes. Across a week of orders, it's hours.
I've watched processors do this hundreds of times. Open the mapping tool. Search the address. Zoom in. Confirm the right polygon. Screenshot or export. Drop it into the right format. Rename it sensibly. Attach. None of it is hard. All of it is friction, and friction at volume is cost.
The format problem is the sneaky part. One council wants a PDF. A provider portal wants an image of a particular size. Another expects the plan embedded in the request itself. So the same polygon gets reworked two or three ways depending on where it's going, and your team carries that knowledge in their heads.
Where the minutes hide
The download is quick. The conversion is quick. The attaching is quick. That's exactly why nobody flags it — no single step is slow enough to complain about. Add them up across every order, every day, and it's one of the bigger invisible drains in the back office.
| Step | Manual approach | Generated from live data |
|---|---|---|
| Find the property | Search the mapping tool, confirm the polygon | Resolved from the matched UPRN |
| Get the plan | Export or screenshot the INSPIRE polygon | Drawn from live data automatically |
| Format it | Convert per council/portal requirement | Produced in the required format |
| Attach it | Rename, drop into the request | Attached to the request in one step |
| Time per order | A few minutes | Seconds |
How does generating the plan in one click change the workflow?
When the boundary plan is generated from live data at the point you raise the request, the whole download-convert-attach routine disappears. The property is already matched to a UPRN, the polygon is already known, and the plan comes out in the format that specific council or provider needs. One click, not a sequence.
That's the difference between a step a person performs and a step the system handles. The processor isn't choosing the right polygon, isn't remembering which council wants which format, isn't renaming files. They raise the request and the plan is on it, correct, every time.
In our experience across firms processing fifty to several hundred searches a week, the boundary-plan step is one of the most consistently underestimated. Operators rarely list it when you ask what slows them down — yet remove it and you give a busy processor back real minutes on every order, which is exactly where back-office margin lives.
This connects to the broader council knowledge problem: the format a plan needs is itself a per-council quirk, the same kind of detail that usually lives in one person's memory. Bake it into the system and it stops being something anyone has to know.
"The boundary plan is the perfect example of a job that's too small to fix and too frequent to ignore. Nobody ever said 'we're drowning in INSPIRE downloads.' But when I added up the seconds across a week's orders, it was always more than anyone guessed. The plans you don't have to make are the cheapest plans you'll ever attach."
— Valerie Bennett, Personal Search Veteran · June 2026
What INSPIRE polygons are and aren't — the short version
To keep it straight: INSPIRE Index Polygons are HM Land Registry's free, monthly-updated dataset of indicative freehold extents in England and Wales, each with an INSPIRE ID. They're excellent for showing a council which property you mean. They are not legal boundaries, not title plans, and not a search dataset.
Use them for what they're built for. Attach a clear plan to every request so the council searches the right ground. Don't oversell what the plan represents to a client, and don't let your team burn minutes producing it by hand when it can come from live data.
That's the whole story: the right plan, in the right format, on the right council request — without anyone having to download a thing.
This is one piece of running a personal search business well. See how council data in Valio handles the per-council formats, or explore the features that build the plan into every order.
See how it works → · How the council knowledge base is built → · Try Valio →