
Turn every UK planning application, document and policy into a single, queryable dataset so your team can ship powerful planning tools fast.
Every local planning authority in England in one normalised, continuously updated API.
Every application and document runs through our pipeline so documents, people, classifications, statuses and conditions are all linked and ready to query.

Understand every document
Planning reports and notices become structured fields with conditions, policies and recommendations ready to query.
Richer summaries
Jump straight to the key points in long officer reports with generated summaries that surface recommendations, objections and risks.
Field‑ready outputs
Consume conditions, policy references and recommendations as clean fields in your own schema instead of scraping PDFs.
Richer summaries
Jump straight to the key points in long officer reports with generated summaries that surface recommendations, objections and risks.
Field‑ready outputs
Consume conditions, policy references and recommendations as clean fields in your own schema instead of scraping PDFs.
Officer report
12 pages
Decision notice
3 pages
Design statement
18 pages
LLM pipeline
Recommendations
>
Officer recommendation
>
Suggested changes
>
Recommendation
Conditions
>
Pre‑commencement
>
Design / materials
>
Amenity / privacy
>
Construction management
Policy references
>
Local plan policies
>
NPPF paragraphs
See every person
View every application linked to an architect or agent and see their full portfolio across councils.
Cross‑council portfolios
View every application linked to an architect, agent or applicant across all covered authorities in one place.
Network context
Spot frequent collaborators and repeat objectors by seeing who appears together on applications and decisions.
Cross‑council portfolios
View every application linked to an architect, agent or applicant across all covered authorities in one place.
Network context
Spot frequent collaborators and repeat objectors by seeing who appears together on applications and decisions.
Planning application
Approved
23/04567/FUL
Oxford City Council
Identity resolution
Jane Roberts
Applicant
3 applications
2 councils
Heritage Planning Ltd
Agent
27 applications
9 councils
Smith + Carter Architects
Architects
14 applications
5 councils
Standardise every type
Apply one planning taxonomy so local labels roll up into consistent categories.
One taxonomy, many councils
Translate local labels into a shared hierarchy so "householder" and "minor residential" are treated as the same category.
Filter by intent, not by wording
All minor residential extensions nationally with one parameter. No lookup tables in your code.
One taxonomy, many councils
Translate local labels into a shared hierarchy so "householder" and "minor residential" are treated as the same category.
Filter by intent, not by wording
All minor residential extensions nationally with one parameter. No lookup tables in your code.

Householder extension
22/09876/REM
Camden City Council
Minor residential development
23/01452/FUL
Leeds City Council
Domestic rear extension
24/00631/HSE
Oxford City Council
Householder
Minor residential
Domestic extension
Classification engine
Unified classification
>
Development type
Residential
>
Sub-type
Minor-Extensions
>
Use class
C3
Track every status
Apply one planning taxonomy so local labels roll up into consistent categories.
Normalised lifecycle
Map dozens of raw portal statuses into a single, consistent set of stages from received to decided.
Duration tracking
Measure how long applications sit at each stage. See where cases stall. Compare processing times across councils or application types, without writing your own status mapping.
Normalised lifecycle
Map dozens of raw portal statuses into a single, consistent set of stages from received to decided.
Duration tracking
Measure how long applications sit at each stage. See where cases stall. Compare processing times across councils or application types, without writing your own status mapping.
Planning application
24/01892/FUL
Camden City Council
Idox
Awaiting decision
Agile
Pending consideration
NEC
Under review
Status decoder
Normalised status
>
Current status
In assessment
>
Previous
Validated
>
Next
Decided
Surface every condition
Apply one planning taxonomy so local labels roll up into consistent categories.
Categorised obligations
Group conditions into pre‑commencement, design, amenity and more so you can analyse patterns at scale.
Source-linked
Every extracted condition links back to the exact clause in the decision notice so your users can check the source.
Categorised obligations
Group conditions into pre‑commencement, design, amenity and more so you can analyse patterns at scale.
Source-linked
Every extracted condition links back to the exact clause in the decision notice so your users can check the source.
Decision notice
Document
"…No development shall commence until a detailed materials schedule has been..
"…The first-floor side window shall be obscure glazed and non-opening below 1.7m to protect neighbour amenity."
"…The first-floor side window shall be obscure glazed and non-opening below 1.7m to protect neighbour amenity."
Condition extractor
Structured conditions
Summary
>
Pre‑commencement
Submission of detailed materials schedule for walls, roof, and windows.
>
Design / materials
>
Amenity / privacy
>
Construction management
Trace the line from national policy to local practice at scale. Useful for policy teams, appeal preparation and planning risk assessment.

We embed every chunk of every document so you can ask questions that keyword search would miss entirely.
>
"Applications near listed buildings where heritage impact was contested"
>
"Drainage conditions imposed after Environment Agency objection"
>
"Proposals citing paragraph 11 refused on character grounds"
>
"Officer reports mentioning overlooking in conservation areas"
>
Applications near listed buildings where heritage impact was contested
27 applications
All councils
2018-2026
Rear extension adjacent to Grade II listed building
Oxford City Council
|
22/09876/FUL
Semantic Match
0.92
Approved
"…heritage impact was contested by the Conservation Officer due to harm to the listed building."
Roof terrace within conservation area near Grade II listed building
Camden
|
23/04789/FUL
Semantic Match
0.89
Refused
""Members considered that the proposal would cause unacceptable heritage impact to the adjacent listed building and refused permission."
Two-storey side extension beside Grade II listed building
Leeds City Council
|
22/03147/HSE
Semantic Match
0.87
Approved
""The Conservation Officer initially contested the heritage impact, but revisions reduced harm to an acceptable level."
Change of use of former stable block near Grade II listed building
Manchester City Council
|
24/00563/FUL
Semantic Match
0.85
Pending
""Concerns were raised that the heritage impact on the nearby listed building remained contested at committee."
A clean REST API with consistent schemas, real time webhooks, bulk exports and a search endpoint you can expose directly to your own users.

12 High Street, Oxford
We maintain the scrapers, run the extraction pipeline, normalise the data and host the infrastructure. You ship the features your customers are asking for.

Webhooks
Subscribe to status changes, new documents and new conditions so your product reacts to planning events as they happen.
Bulk and sync
Pull full dataset exports for initial loads, then keep everything current with lightweight incremental updates.
Search endpoint
Expose the same semantic search to your users with natural language queries, relevance scores and clear source references.
Use the same API key to turn on additional datasets whenever you need them, from risk and environment to geography and market context.

>
What planning authorities are covered?
All 340+ local planning authorities in England are included, with select coverage in Wales and Scotland.
How fresh is the data?
What happens when a council portal changes or goes down?
What kinds of documents do you process?
How is this different from other planning data providers?
How does semantic search work?
What's the API like to work with?
Can I see the data before I integrate?