Skip to main content

How it works

How to compare an EPC score, step by step

This page walks through using the comparison: what to have ready, what each of the four published views actually covers, and how to read the figures without over-reading them. It also sets out the data notes, privacy position and accessibility approach.

For the step-by-step detail of how the aggregates are built, see the full methodology and the data sources and licensing pages. If you are new to certificates, our annotated sample EPC explains each part of a certificate using a fictional example.

Compare an EPC score

What to have ready

  1. 1The official certificateHave the property's own EPC in front of you, from the official register. Every figure you enter comes from it.
  2. 2The outward postcode district onlyThe first part of the postcode, such as AL1 or M11. Never a full postcode, a street address, a UPRN or a certificate number: none of those are used or needed.
  3. 3The recorded property typeThe property type as recorded on the certificate, for example house or flat.
  4. 4The construction age bandThe construction age band recorded on the certificate, for example 1930–1949.
  5. 5The current score, and potential if you have itThe current energy efficiency score from 1 to 100 is required. The potential score is optional and is also taken from the certificate.

If you do not have the current certificate, first use our guide to finding your official EPC certificate. On the comparison page you enter those details, select Show comparison, and read the four published views that appear. Everything runs in your browser: nothing is submitted or stored. If you are unsure which band a score falls in, the A to G band reference lists every score range.

Worked example with published figures

Fictional input scenario — not a real certificate or property

The inputs below are invented to show how the comparison reads. They describe no real property, certificate, address or household. The aggregate figures they produce are the genuine published figures for those groups.

Postcode district
AL1
Property type
House
Construction age band
1930–1949
Current score entered
60 (band D)
Four separate published views for a score of 60, each with its own scope, published property count, median current score and difference from the entered score.
Published viewProperties publishedMedian current scoreScore 60 compared
All current properties in postcode district AL1Every published current property in the district. Property type and construction age are both mixed.13,072699 points below
House-type current properties within AL1Same property type, this district only. Construction age is mixed.6,691655 points below
All property types built 1930–1949 within AL1Same construction age band, this district only. Property type is mixed, so this is not the count of houses of that age in AL1.1,720633 points below
House, built 1930–1949, across England and WalesSame property type and construction age, all areas. This national view carries no district restriction.1,825,282633 points below

These four counts describe four separate published groups. They overlap, so they must never be added together, and they are not a narrowing hierarchy ending in one matched cohort. No published cell combines district, property type and construction age.

Every figure on this site comes from the published aggregate files in this release: national totals from national.json, district views from the matching postcode-district file, and national type-and-age groups from archetypes.json. Each page draws only on the files relevant to the figures it shows.

Reading the figures without over-reading them

Methodology in brief

A summary of how the published aggregates are produced. The methodology page holds the detail.

  1. 1Start from the official domestic certificate historyThe analysis starts from 27,654,564 domestic certificate-history rows for England and Wales, with a source snapshot ending 31 July 2026.
  2. 2Reduce to one current property per valid UPRNCertificates are grouped by valid UPRN and only the latest certificate for each property is kept, giving 19,324,312 current properties. 485,734 raw rows have an invalid or null UPRN and are excluded.
  3. 3Attach a postcode district and sector19,172,788 current properties join to a postcode district and sector using the ONS UPRN lookup, a join success of 99.21588929013359%.
  4. 4Aggregate into published viewsProperties are aggregated into whole-district, district-by-property-type, district-by-construction-age and national type-and-age views. Only aggregate rows are published: counts, medians, means and band shares.
  5. 5Apply suppressionAny group with fewer than 5 properties is withheld, so no small group can be identified from the published figures.
  6. 6Summarise recorded recommendationsRecommendation rows (102,824,532 domestic rows) are counted by national property type and construction age. Figures describe association with the certificate's total potential gap, never an item-specific uplift.

Data notes

Certificate-history rows
27,654,564
Domestic certificate-history rows for England and Wales, snapshot ending 31 July 2026.
Current properties
19,324,312
“Current” means the latest certificate recorded for each valid UPRN in this analysed release. A property that has been reassessed appears once, using its most recent certificate.
Joined to district and sector
19,172,788
Current properties matched to a postcode district and sector, a join success of 99.21588929013359%.
Domestic recommendation rows
102,824,532
Recorded recommendation rows summarised by national property type and construction age.

485,734 raw domestic certificate rows carry an invalid or null UPRN. Without a valid property identifier they cannot be reduced to one current property, so they do not enter the current-property comparison.

This aggregate release does not combine postcode district, property type and construction age in one published cell. The four views below are shown separately and must not be read as a single jointly matched cohort. The national property type and construction age archetype is the closest combined attribute view; the district views add geographic context.

Recommendation figures are associations with a certificate's total potential SAP gap, not item-specific causal uplifts. The average shown is the average total current-to-potential certificate gap for properties carrying that recommendation. It is not the point uplift of that measure, and it does not show cause and effect. No cost estimates are shown, because this release does not contain validated current costs.

This is not live data and it does not update automatically. The source snapshot ends 31 July 2026 and this release was generated on 23 August 2026.

Underlying data: EPC Register (MHCLG), ONS National Statistics UPRN Lookup. Contains public sector information licensed under the Open Government Licence v3.0.

Limitations

Privacy

The comparison form runs entirely in your browser. There are no accounts, no sign-in, no database, no payment processing, no advertising and no contact form, and the details you type are never sent anywhere for storage. Only a postcode district is asked for, never a full postcode or an address.

No street address, full postcode, UPRN, certificate number, API token or private certificate record is included in this release. The production hosting platform does record aggregate page hits and sets two short-lived cookies for analytics and security.

Full detail is in the privacy notice and the cookies page. See also the terms of use and coverage.

Accessibility

  • Every control is reachable and operable by keyboard, with visible focus outlines.
  • Semantic headings, lists and landmarks, plus a skip link to the main content.
  • Band and status information is always labelled in text, so nothing depends on colour alone.
  • Tables are scrollable by keyboard, and every figure is available as a labelled number.
  • Touch targets are at least 44 pixels, and motion is reduced when the system asks.

Useful next steps

Retrieve the property’s own certificate from the official register, read its recorded elements and ordered recommendations, then use the comparison for aggregate context. This release publishes aggregate views only, because that is what can be shown without exposing an address, a full postcode, a UPRN or a certificate identifier.

Compare an EPC score