Compliance & assurance · AVM
Coverage & Limitations
Assess coverage for the property, date and workflow you intend to support. Geographic coverage does not guarantee that every submitted property will receive an automated valuation.
Current Scope
Automated valuations currently cover residential property in England and Wales: detached, semi-detached and terraced houses and bungalows, plus flats and maisonettes. Freehold and leasehold requests use the applicable fields in the Request Schema.
Read GET /v3/releases/current for the active release, supported countries and property types, valuation-date window and available capabilities. These are release-specific; do not infer Scotland or Northern Ireland support from the product's UK positioning.
Coverage Is Not Acceptance
The /v3/coverage endpoint checks postcode and optional UPRN presence separately, without producing a valuation. It does not verify that they belong together. A positive coverage check does not guarantee a valued response: the actual request must still satisfy input, identity, evidence and supported-market requirements.
Keep three measures separate: coverage of your target population, the proportion receiving usable automated results, and the accuracy of those results against suitable outcomes.
Data and Property Limitations
Recorded transactions and property attributes can contain omissions, reporting delays or measurement differences. The request may not fully represent interior condition, defects, title restrictions, service charges or unusual legal arrangements. Recent works and changes in the local market may not yet be reflected in available records.
Check identifiers, floor area, property type, tenure and valuation date before relying on a result. Review input_resolution to see which stored values were applied and which inputs were derived or ignored. See Identity and Stored Data.
Referrals and Missing Results
A supported location can still contain an unsuitable automated case. Unusually large land holdings, unusual characteristics, low liquidity and insufficient evidence may require manual valuation. Unsupported geography is rejected rather than referred.
Farms, materially mixed-use assets and other non-residential uses are outside the intended scope. Do not describe them as ordinary residential stock to fit the schema. Input checks cannot identify every unreported use, restriction or defect.
status=referred is an expected outcome without a point estimate. Provide a manual-review path; do not silently replace a referral with a previous value, a zero or a guessed estimate. Rejected inputs and execution failures are different outcomes, documented in Errors and Retries.
Proposed Properties
The development endpoints estimate proposed or unregistered homes on an as-complete new-build basis. They do not inherit stored subject-property attributes. They are not a development appraisal, construction-cost assessment or residual land valuation.
Assess specification, completion timing, incentives, service charges, legal terms and sales risk separately. Use an existing-property endpoint for a registered home, including one that has been refurbished or extended. See Development Valuations.
Appropriate Reliance
An AVM does not replace a physical inspection, professional valuation, legal due diligence or credit policy where required. Set acceptance rules appropriate to the use case and refer uncertain or unusual cases to a qualified professional.