The Future Homes Standard will ultimately offer two compliance routes: the Home Energy Model (HEM) via the ECaaS platform, and SAP 10.3 as an interim alternative. Both routes use the same notional building approach — comparing the proposed dwelling against a reference building with standardised specifications — but they differ significantly in how they perform the underlying calculations.
The Notional Building Approach
FHS compliance is based on comparing the proposed dwelling (the actual home being designed) against a notional building (a reference dwelling). This approach has been used in Part L for years, but the FHS notional building specification is significantly more demanding.
How It Works
- The notional building is automatically generated — same size, shape, and orientation as the proposed home, but with standardised specifications for fabric, heating, ventilation, and renewable energy
- Both the proposed dwelling and the notional building are assessed using the same calculation methodology (HEM or SAP 10.3)
- The calculation produces target rates from the notional building (TER, TPER, TFEE) and dwelling rates from the proposed home (DER, DPER, DFEE)
- The proposed dwelling passes if its dwelling rates are equal to or better than (i.e. lower than or equal to) all the target rates
FHS Notional Building Specification
The FHS notional building is specified with:
| Element | Notional Building Specification |
|---|---|
| External walls | 0.18 W/m²K |
| Ground floor | 0.13 W/m²K |
| Roof | 0.11 W/m²K |
| Windows | 1.2 W/m²K |
| Doors | 1.0 W/m²K |
| Airtightness | 3 m³/(h·m²) @ 50 Pa |
| Heating | Air source heat pump |
| Hot water | Heat pump with cylinder |
| Ventilation | MVHR (90% heat recovery) |
| Solar PV | 40% of floor area coverage |
| Wastewater heat recovery | Included |
For detailed discussion of each fabric element, see our Part L Changes page.
Compliance Metrics
The FHS uses three primary compliance metrics. The proposed dwelling must meet or beat all three targets simultaneously:
Target Emission Rate (TER) and Dwelling Emission Rate (DER)
These measure carbon dioxide emissions in kg CO₂/m²/year. The DER must be ≤ the TER. This is the headline metric that drives the 75–80% carbon reduction.
HEM uses forward-looking carbon emission factors (averaging expected grid carbon intensity from 2025 to 2029) rather than the historical factors used in previous versions of SAP. This properly credits the trajectory of grid decarbonisation and gives electric heating systems (heat pumps) a more favourable carbon factor than under older SAP versions.
Target Primary Energy Rate (TPER) and Dwelling Primary Energy Rate (DPER)
These measure primary energy consumption in kWh/m²/year. Primary energy accounts for the full energy chain, including extraction, generation, and distribution losses. The DPER must be ≤ the TPER.
The primary energy metric prevents excessive reliance on any single energy source and ensures overall energy efficiency, not just low carbon.
Target Fabric Energy Efficiency (TFEE) and Dwelling Fabric Energy Efficiency (DFEE)
The TFEE/DFEE acts as a backstop for fabric performance, measured in kWh/m²/year. It ensures that compliance is not achieved solely through services (a large heat pump and extensive PV) while neglecting the building envelope. The DFEE must be ≤ the TFEE.
Backstop (Limiting) Values
In addition to the three performance metrics, individual fabric elements have backstop U-values that cannot be exceeded regardless of trade-offs elsewhere:
| Element | Backstop U-value |
|---|---|
| External walls | 0.26 W/m²K |
| Ground floor | 0.18 W/m²K |
| Roof | 0.16 W/m²K |
| Windows | 1.6 W/m²K |
| Doors | 2.0 W/m²K |
These backstops match the current Part L 2021 notional values, ensuring no FHS home can have worse fabric than a home built to the 2021 interim standard.
The Two Compliance Routes
Route 1: HEM via ECaaS
The HEM route is the government's preferred long-term compliance methodology. Assessments are performed through the ECaaS (Energy Calculation as a Service) platform — a centralised cloud API run by MHCLG.
How it works:
- The assessor enters dwelling data into a software interface built by an approved software provider
- The software submits the data to the ECaaS API, which runs the HEM calculation using the Rust implementation of HEM
- ECaaS returns the results — dwelling rates (DER, DPER, DFEE), comparison against the notional building, and a pass/fail determination
- The software displays the results and generates the compliance documentation
Advantages of the HEM route:
- More accurate modelling — half-hourly timesteps capture real-world performance of heat pumps, PV, and batteries
- Consistent results — every assessment uses the identical calculation engine, eliminating inter-software discrepancies
- Better credit for good design — orientation, thermal mass, solar self-consumption, and smart controls are properly rewarded
- Future-proof — HEM will be the sole compliance methodology once the dual period ends
Considerations:
- Data requirements are higher — significantly more detailed input data than SAP, including specific product make/model data
- Calculation time is longer — approximately 5–10 minutes per run, compared to near-instantaneous SAP results
- Internet connection required — the calculation is performed server-side via the API
- New workflow — assessors need to learn the new data requirements and interface
Route 2: SAP 10.3
SAP 10.3 is an updated version of the Standard Assessment Procedure that has been retained as an interim compliance route during the transition to HEM.
Advantages of the SAP 10.3 route:
- Familiar workflow — assessors who know SAP can use familiar tools and processes
- Faster turnaround — SAP calculations are near-instantaneous
- Lower data requirements — fewer input fields than HEM
- Existing software — SAP software providers can update existing tools to SAP 10.3
Limitations:
- Less accurate modelling — monthly timesteps cannot capture the real-world performance of heat pumps, PV self-consumption, or battery storage as precisely
- May be less generous — for well-designed homes with good orientation, battery storage, and smart controls, HEM may give more favourable results
- Temporary — the SAP route will eventually be withdrawn; the industry must transition to HEM
- Software inconsistencies — the multiple third-party SAP engine model continues, with its historical inter-software variability
HEM vs SAP 10.3 — Side-by-Side
| Factor | HEM (via ECaaS) | SAP 10.3 |
|---|---|---|
| Time resolution | Half-hourly (17,520 steps) | Monthly (12 steps) |
| Calculation engine | Centralised ECaaS API | Multiple third-party providers |
| Calculation time | 5–10 minutes | Near-instantaneous |
| Data requirements | Significantly more detailed | Familiar SAP inputs |
| Heat pump modelling | Variable COP by timestep | Simplified seasonal COP |
| PV modelling | Half-hourly generation + self-consumption | Monthly generation estimate |
| Battery storage | Charge/discharge modelled | Limited modelling |
| Ventilation model | Pressure-driven (EN 16798-7) | Simplified shelter factors |
| Results consistency | Identical engine, identical results | Varies between software providers |
| Long-term viability | Permanent — the future methodology | Temporary — will be withdrawn |
Choosing Your Compliance Route
The choice between HEM and SAP 10.3 depends on the project, the assessor's experience, and the building design:
Consider the HEM Route When:
- The design features heat pumps, solar PV, and/or battery storage — HEM models these more accurately and may give more favourable results
- The building has good orientation and glazing strategy — HEM's half-hourly solar modelling rewards good passive design
- You want consistent, auditable results — ECaaS guarantees identical calculations regardless of software provider
- You are building at scale and want to invest in learning the HEM workflow for long-term benefit
- The design includes innovative technologies that benefit from half-hourly modelling (smart controls, demand-side response)
Consider the SAP 10.3 Route When:
- The assessor is experienced with SAP and the project timeline is tight
- The design is straightforward — standard house type with heat pump and basic PV, where the more detailed HEM modelling may not provide significant advantage
- Specific product data for all heating and ventilation equipment is not yet available in the PCDB for HEM
- The project is early in the transition and the team is still building HEM expertise
HEM Data Requirements
One of the most significant practical differences is the volume and specificity of data that HEM requires. Testing during the HEM pilot showed that a standard house type takes approximately 1 hour 40 minutes to input in HEM versus around 20 minutes in SAP (excluding geometry and U-value calculations).
New data points required by HEM include:
- Site altitude and noise nuisance potential
- Detailed geometry — more precise than SAP requires
- Individual hot water outlet specifications — tap flow rates, shower types (mixer, electric, thermostatic)
- Detailed pipework — lengths and insulation for all hot water distribution
- Specific product data — make and model for all heating and ventilation equipment, referenced against the PCDB
- PV inverter specifications — including efficiency curves
- Thermal bridge details — psi-values for each junction, or accredited construction detail references
Frequently Asked Questions
Can I still use SAP to demonstrate FHS compliance?
Yes — SAP 10.3 is the only route at FHS launch. HEM follows at least 3 months later. Once both are available, they run in parallel for a minimum of 24 months. Both routes must demonstrate the same performance against the FHS notional building.
What is the notional building approach?
The notional building is a reference dwelling of the same size and shape as the proposed home, with standardised specifications. The proposed dwelling must perform at least as well as the notional building across all compliance metrics (TER, TPER, TFEE). This “whole-building performance” approach allows flexibility in how individual elements are specified.
What is ECaaS and why is it required for the HEM route?
ECaaS (Energy Calculation as a Service) is the centralised cloud API run by MHCLG that performs all HEM calculations. It ensures every assessment uses the identical, up-to-date engine, eliminating the inter-software discrepancies that affected SAP. Software providers build user interfaces on top of the API.
What compliance metrics does the FHS use?
Three metrics: the Target Emission Rate (TER) for carbon, the Target Primary Energy Rate (TPER) for primary energy, and the Target Fabric Energy Efficiency (TFEE) as a fabric backstop. The proposed dwelling's rates must equal or beat all three targets simultaneously.
Should I choose the HEM route or the SAP 10.3 route?
It depends on your project. HEM provides more accurate modelling — particularly beneficial for homes with heat pumps, PV, and batteries — and may give more favourable results for well-designed homes. SAP 10.3 uses familiar tools and may be preferable during the early transition. Many teams may benefit from running both in parallel on a pilot house type.
Related Pages
Part L Changes
The fabric and energy specifications that define the FHS notional building.
Transitional Arrangements
Deadlines, plot registration, and strategies for the transition period.
SAP vs HEM
Detailed technical comparison of the two calculation methodologies.
SAP 10.3 vs HEM
Detailed comparison of the two FHS compliance routes with practical guidance.