PropertyMetrics does not maintain a private database of sale prices or planning decisions. A search requests data from the named public services and records the retrieval time. If a source fails, the workspace reports the failure rather than replacing it with sample data.
HM Land Registry Price Paid Data
The workspace uses the HM Land Registry linked-data transaction endpoint to retrieve up to 100 residential transactions matching an exact postcode, ordered by completion date. Displayed fields may include the address, recorded price, completion date, property type, tenure, new-build indicator and transaction category.
Price Paid Data is published under the Open Government Licence v3.0 with additional conditions applying to address data. PropertyMetrics preserves a link to the source record for each displayed transaction.
- Attribution: Contains HM Land Registry data © Crown copyright and database right 2021.
- Price Paid Data documentation and downloads
- Open Government Licence v3.0
Postcodes.io and the ONS Postcode Directory
Postcodes.io resolves the entered postcode to coordinates and administrative geography. The returned point is used as a postcode centroid. The service draws on the Office for National Statistics Postcode Directory and related open geographic data.
The full workspace also uses the nearest-postcode endpoint to select up to eight postcode centroids within 750 metres, including the subject postcode. A separate HM Land Registry query is made for each selected postcode. Returned distance is measured between postcode centroids and is retained only as a discovery label; it is not a claim of physical or market similarity.
- Attribution: Contains Ordnance Survey, Royal Mail and National Statistics data.
- Postcodes.io service documentation
Planning Data platform
For postcodes resolved to England, the first release checks a selected group of Planning Data datasets at the returned centroid: Article 4 direction areas, conservation areas, flood-risk zones, green belt, listed buildings and tree-preservation zones.
Planning Data is licensed under the Open Government Licence v3.0. Dataset availability, geometry and completeness vary by local authority. Results do not replace local searches, title review or professional planning advice.
- Attribution: Contains planning data licensed under the OGL v3.0.
- Planning Data platform
Energy Performance of Buildings Data
EPC data is deliberately marked as not connected. The government service requires a separate account and API access, and its records have specific licence and data-protection conditions. PropertyMetrics does not infer an EPC rating, floor area or recommended works when that source is absent.
Energy Performance of Buildings Data service
Fields not supplied by the connected sources
No connected source establishes present condition, bedrooms, internal floor area, lease length, service charge, ground rent, survey defects, asking price, achieved rent or suitability of finance. These remain user evidence or professional-review items.
Derived summaries created by PropertyMetrics
Counts, medians, quartiles, observed ranges, yearly groups, property-type groups and repeat-address matches are calculated from the transactions returned during a request. They are not fields supplied by HM Land Registry and are not official market statistics.
- A yearly median is not mix-adjusted and can move when the types of properties sold change.
- A repeat-address match uses normalised address text and can miss renamed, renumbered or corrected records.
- A nominal difference between repeat sales does not adjust for inflation, works, transaction costs or tenure changes.
Availability and caching
Source responses may be unavailable, revised or delayed. The PropertyMetrics service may cache a successful response briefly to reduce load on public infrastructure, but saved cases do not freeze or republish the underlying datasets. Users should revisit the source when a fact is decision-critical.
Comparison and watchlist storage
The area-comparison board makes the same source request for each postcode; it does not use a separate proprietary market dataset. Watchlist baselines store returned transaction identifiers and summary fields in browser local storage. A watchlist refresh can therefore detect a changed response but cannot explain whether the change came from a new registration, source correction or altered upstream coverage.