PlanningTrack API · Free beta

Coverage and missing data

Collected evidence is useful only when its limits remain visible.

Directory, summaries, and details

An authority directory entry does not establish a working feed. Summary counts reflect inventory discovered from source lists; detailed counts reflect completed record collection. Historical completeness remains unverified. An operational daily feed requires seven successful cycles and a recent successful read.

Missing values

Summary dates and coordinates are null when missing. Optional detail fields are omitted. An empty document or condition array is not proof that the council publishes none; inspect its availability field.

• complete: the section was collected completely.
• partial: some section evidence is missing.
• unavailable: the section could not be read.
• not_published: the source explicitly publishes none.

Addresses and maps

Address and postcode searches match published text. They do not establish verified property or UPRN relationships. Map queries only match records with collected coordinates. Records without coordinates are excluded, so a map is not a complete planning history.

Dates and documents

Published application dates differ from the time we first observed or last checked a record. Preserve date precision. Document endpoints return metadata and council links; PDFs are not hosted, extracted, or interpreted. A link may need the council’s current browser session.

Display source context

Show council links, last-checked time, and completeness alongside application data. Source records may have newer changes. Supplementary provider observations remain separate and do not establish fresh council evidence.