The History of SAP and RdSAP — From 1993 to the Home Energy Model

The Standard Assessment Procedure (SAP) has been the UK's official method for assessing the energy performance of homes since 1993. Over three decades it was updated seven times, but its core architecture — monthly averaging of energy demand across a simple two-zone model — was never rebuilt. Each version patched new requirements onto a foundation designed for pen-and-paper calculation in a world of gas boilers and basic insulation. RdSAP (Reduced Data SAP), introduced in 2005, extended SAP's reach to existing homes but inherited every limitation. The Home Energy Model (HEM) is not the next patch — it is the fundamental rebuild that three decades of incremental updating deferred.

The Origins — SAP 1993

SAP was first published in 1993 by the Building Research Establishment (BRE) on behalf of the UK Department of the Environment. It was based on BRE's own Domestic Energy Model (BREDEM), a simplified calculation methodology for estimating residential energy consumption.

The original SAP produced a single number: an energy cost rating on a scale of 1 to 100, where 100 represented the lowest running costs. The calculation used standardised occupancy assumptions so the rating reflected the dwelling itself, not the behaviour of its occupants. This was the key design principle — SAP rated buildings, not people.

In 1994, SAP was first cited in the Building Regulations for England and Wales, becoming the approved method for demonstrating compliance with Part L (Conservation of Fuel and Power). From that point, every new home had to be assessed using SAP.

The methodology was straightforward because the buildings were. In 1993, UK homes were heated almost exclusively by gas boilers, construction methods were conventional, and on-site electricity generation was exotic. A monthly calculation — averaging heating demand, solar gains, and weather across each calendar month — was a reasonable simplification. More importantly, it was a practical one: these calculations could be performed by hand or on a basic spreadsheet.

That practical constraint became an architectural constraint. Monthly averaging was not a considered physics decision — it was what the tools of 1993 could manage.

The Early Updates — SAP 1998 and SAP 2001

SAP's first revision came in 1998 as a consolidation of the original methodology. It updated fuel price data and refined minor calculation details, but the architecture was unchanged. The buildings SAP assessed were still predominantly gas-heated, conventionally constructed homes.

SAP 2001 made a more notable change: the rating scale was extended from 100 to 120, because increasingly efficient new homes were clustering at the top of the original scale and the methodology could no longer differentiate between them. The upper extension was a patch — rather than redesigning the scale, the ceiling was simply raised.

These early updates established a pattern that would persist for the next two decades: each revision refined the inputs and assumptions, but the underlying monthly calculation method remained untouched.

The Big Overhaul — SAP 2005 and the EPC Era

SAP 2005 was the most significant overhaul since the original. It was driven by two converging forces: tightening domestic climate policy and the EU Energy Performance of Buildings Directive (EPBD), adopted in 2002, which required all member states to introduce Energy Performance Certificates for buildings.

The key changes in SAP 2005:

• Environmental Impact Rating introduced — for the first time, SAP calculated CO₂ emissions alongside energy costs, producing a separate 1–100 rating. The EPC's twin A–G scales (energy efficiency and environmental impact) both came from SAP 2005.
• Lighting energy demand was added to the calculation for the first time.
• Linear thermal bridging heat losses were incorporated.
• An overheating risk assessment was added.
• Part L 2006 introduced whole-building carbon compliance via Target Emission Rate (TER) and Dwelling Emission Rate (DER) — a shift from elemental fabric checks to whole-building performance. SAP became the engine that calculated whether a dwelling met its carbon target.

EPCs became mandatory for home sales in England and Wales from August 2007, initially for four-bedroom properties, extending to all homes by December 2007. Lettings followed from October 2008. SAP — and its reduced-data sibling RdSAP — became the most widely used energy assessment methodology in the UK overnight.

RdSAP — A Practical Necessity

Full SAP requires detailed construction data: exact U-values, boiler efficiency from manufacturer specifications, precise insulation thicknesses, and specific ventilation data. This information is readily available for new-build dwellings from design drawings and product data sheets.

For existing homes — where original drawings may be lost, cavity widths hidden behind plaster, and boiler models long discontinued — a full SAP assessment would require invasive inspection. Opening up walls and floors to measure insulation is neither practical nor affordable at the scale the EPBD demanded.

RdSAP (Reduced Data SAP) was the solution. First published as version 9.80 in 2005 and deployed from August 2007 alongside EPCs, RdSAP uses a reduced set of inputs based on what an energy assessor can observe during a non-invasive site survey. Where data is unavailable, RdSAP applies default assumptions based on the dwelling's age, type, and construction.

RdSAP has tracked SAP through its versions: RdSAP 9.80 was based on SAP 2005, RdSAP 9.90 on SAP 2009, RdSAP 9.92 on SAP 2012, and RdSAP 10 (published June 2025) on SAP 10.2. Each version expanded the data an assessor could record, but the fundamental trade-off remained: the defaults that made nationwide EPC assessment practical also made individual assessments less accurate.

For more on where RdSAP goes from here, see our RdSAP to HEM transition guide.

Steady Tightening — SAP 2009 and SAP 2012

The Climate Change Act 2008 set a legally binding target to reduce UK greenhouse gas emissions by 80% by 2050 (later strengthened to net zero in 2019). Buildings account for roughly 30% of UK emissions, so each successive Part L update — and the SAP version underpinning it — was a step on the pathway to meeting those targets.

SAP 2009 introduced party wall heat loss (previously ignored), incorporated thermal mass into heating and cooling demand calculations, and added space cooling modelling. It underpinned Part L 2010, which required a 25% reduction in CO₂ emissions compared to Part L 2006.

SAP 2012 introduced the Fabric Energy Efficiency Standard (FEES) — measuring the thermal performance of the building fabric itself, independent of the heating system. This was a significant conceptual step: for the first time, SAP assessed how well a building was built, not just how efficiently it was heated. SAP 2012 underpinned Part L 2013, which delivered a modest 6% improvement over Part L 2010.

Through these updates, the pattern continued: each version asked more of SAP, but the monthly calculation engine stayed the same. The building stock was changing faster than the tool assessing it. Heat pumps were gaining market share, solar PV installations were rising, and the electricity grid was decarbonising rapidly — but SAP's monthly time resolution could not model any of these dynamics.

The Numbering Change — SAP 10.x

The jump from SAP 2012 to SAP 10.0 was more than a naming convention change — it reflected a long and troubled development process. The version originally designated “SAP 2016” entered consultation in late 2016 but was not published until July 2018, by which point calling it “SAP 2016” would have been misleading. The shift to version numbering (10.0, 10.1, 10.2) was a pragmatic acknowledgement that SAP updates no longer matched tidy calendar-year cycles.

SAP 10.1, published in late 2019, contained arguably the most consequential single change in SAP's history: the grid electricity CO₂ emission factor was updated from 0.519 kgCO₂/kWh (the SAP 2012 figure, based on the 2012 grid mix) to 0.136 kgCO₂/kWh. Overnight, electricity became less carbon-intensive than mains gas (~0.21 kgCO₂/kWh) in SAP's calculations. This single number shifted the economic and environmental case decisively toward heat pumps — a technology the monthly methodology still could not properly model.

SAP 10.2 followed in 2021 and became the regulatory standard from June 2022, underpinning Part L 2021 — the “interim uplift” requiring a 31% reduction in carbon emissions for new homes. SAP 10.2 added PV battery storage and diverters to the methodology, revised domestic hot water calculations, and required the Thermal Mass Parameter to be calculated from actual construction elements rather than rough defaults. But the fundamental architecture — monthly time resolution, two-zone model, simplified heat balance — remained unchanged.

SAP 10.3 — The Final Patch

SAP 10.3, announced in May 2025, is the final version of SAP. It was created because the Home Energy Model — the government's intended long-term replacement — was not yet ready for regulatory use when the Future Homes Standard needed to launch.

SAP 10.3 is a modified version of SAP 10.2 that uses the FHS notional dwelling specification and revised primary energy and carbon factors. It provides a familiar, tested methodology as a bridge to HEM, allowing the industry to achieve FHS compliance using tools and workflows they already understand.

The government confirmed a dual methodology approach: both SAP 10.3 and HEM can be used to demonstrate compliance with the Future Homes Standard during the transition period. But the implicit message of SAP 10.3's existence is clear — even the government acknowledges that SAP, after three decades, cannot carry the Future Homes Standard alone. HEM will follow SAP 10.3 into regulatory use, and SAP 10.3 will eventually be phased out.

For a detailed comparison of the two compliance routes, see our SAP 10.3 vs HEM guide.

The Lesson — Why Patching Was Not Enough

Looking back across SAP's 30-year history, a clear pattern emerges. Each version added new requirements to a methodology that was never designed to support them:

• SAP 2005 bolted carbon emissions onto an energy cost calculator
• SAP 2009 added thermal mass modelling to a monthly time resolution that could not use it properly
• SAP 10.1 updated carbon factors to reflect a decarbonised grid, but the monthly engine still could not model the dynamic technologies that decarbonisation depends on
• SAP 10.2 added battery storage modelling to a framework with no concept of when during the day electricity is generated or consumed

The technologies that define modern low-carbon homes — heat pumps with variable COP, solar PV with self-consumption, MVHR, battery storage, smart controls — are all fundamentally dynamic. Their performance depends on what is happening hour by hour, or even minute by minute. A monthly calculation cannot capture this, no matter how many parameters are added.

The Climate Change Committee recognised this in its 2019 report UK Housing: Fit for the Future? and again in its 2022 progress report to Parliament, recommending a next-generation assessment methodology. The government responded by commissioning HEM in 2021 — not another SAP update, but a complete rebuild based on international standard BS EN ISO 52016-1:2017, running at half-hourly time resolution with a dynamic physics simulation engine.

SAP served its purpose for 30 years. But the world it was designed for — gas boilers, basic insulation, no on-site generation — no longer exists. HEM is the methodology the UK needs for the homes it is now building. For a full comparison of the two methodologies, see SAP vs HEM.

Frequently Asked Questions

Related Pages