The Home Energy Model is edging into UK workflows as the industry shifts toward the Future Homes agenda, and with it comes a more granular, data-hungry way to prove compliance for new dwellings. Whether you sit in design management, site delivery or energy assessment, the winning move is to get your software stack sorted early and your data pathways nailed down before groundworks start.
TL;DR
/>
– Expect accredited front-end software that plugs into the Home Energy Model engine; insist on clear version control and exportable audit trails.
– Gather plot-by-plot evidence: fabric specs, psi-values, airtightness tests, ventilation and heat pump commissioning sheets, and photo records of critical details.
– Lock a geometry workflow from BIM to the HEM tool, or agree a 2D method and stick to it; inconsistency kills programme.
– Treat product swaps as design changes that must be re-modelled; keep a live register of model-impacting items.
– Build control will look for a coherent as-designed and as-built story; set up your CDE to make that story easy to prove.
Plain-English concepts for the Home Energy Model
/> – What it is: The Home Energy Model (HEM) is the new calculation framework being introduced in the UK to assess new homes’ energy performance. It aims to simulate dwelling performance with more time-aware inputs and a clearer data structure than legacy approaches.
– How compliance will look: As with previous Part L workflows, expect accredited software to provide the interface, with the HEM engine under the bonnet. The model will be run at design stage for specification sign-off and again as-built to reflect what actually got installed and commissioned.
– Data depth goes up: The model demands robust geometry, accurate fabric performance, thermal bridging inputs, airtightness targets and tests, plus detailed services data: heat source performance, ventilation system specifics, hot water storage losses, controls logic, and low/zero carbon tech like PV.
– Evidence matters: Building control and assessors will rely on stated values backed by evidence. That means product data sheets, calculation certificates, photos of junctions before they’re covered up, and commissioning outputs tied to the specific plot.
– Interface and traceability: The conversation shifts from “what U-values did you assume?” to “which product, which junction value, which test certificate, and where’s the file?”. Versioning and traceability will be core to compliance.
On real sites: workflow and roles
/> Picture a timber-frame housing site in the North West, 62 plots across four house types. The design manager is trying to freeze the psi-value library while procurement negotiates a late switch in cavity closers. The site manager is pushing to board out roofs before a wet week, but the energy assessor wants photos of eaves insulation installed to pattern. The M&E coordinator is juggling slots for airtightness testing and MVHR commissioning while the painter wants plots closed up. The heat pump deliveries are staggered, and an alternative cylinder is proposed because the preferred unit is on a twelve-week lead. Building control has pencilled in a pre-handover inspection next fortnight. Everyone’s looking at the programme, but the HEM model needs consistent inputs and evidence, or the as-built sign-off slips.
Here’s how a realistic flow lands:
– Design stage: Agree the HEM tool, data dictionary and geometry method. Lock a schedule of model-impacting items (fabric, junctions, ventilation, heat source, PV, controls). Freeze psi-values and U-value calculations for each house type with tolerances understood by site.
– Pre-start: Build a plot-by-plot evidence plan—photo points for insulation and airtightness layers, upload tags in the CDE, and named roles for capturing data. M&E design must provide declared heat source performance and ventilation data in a structured template.
– During build: Keep geometry consistent—any dimensional changes or window swaps flagged to the assessor. Track substitutions through a change register that triggers remodelling if performance is affected.
– Commissioning: Sequence airtightness testing before MVHR balancing where needed; collect electrical load and setpoint details for heat pumps; capture cylinder model numbers and losses; and secure PV handover sheets if applicable.
– As-built: Run the HEM model with real test values, installed products and final services configurations. Package evidence for building control with clear references back to model inputs.
Pitfalls and fixes
/> – Geometry drift across plots: Relying on sketches or variable rough openings leads to misaligned areas and window ratios in the model. Fix by exporting geometry from your BIM or implementing a robust 2D schedule that the assessor recognises, then hold it via revision control.
– Thermal bridging ambiguity: “Typical” junction values without a calculation basis are a risk. Either adopt an approved junction library with installation requirements or procure 2D/3D calculations to BR497 principles; train site teams on what “good install” looks like.
– Services uncertainty: Heat pump performance, MVHR SFP and specific fan power, hot water cylinder losses and control strategies are often fuzzy until late. Mandate product data templates at procurement, with fields that map to the HEM tool, and block swaps without reassessment.
– Evidence scattered across emails: Photos and certificates vanish into inboxes. Use the project CDE with plot-level folders and mandatory file naming so the assessor can rebuild the evidence chain without delay.
# Common mistakes
/>
– Treating product swaps as “like for like.” Small differences in cylinders, fans or closers can move the model. Run a quick impact check before approving changes.
– Leaving psi-values to the assessor at the end. If junctions aren’t fixed early, detailers and installers won’t align to the assumed value.
– Booking airtightness too late. With finishes in, finding and fixing leaks is slower and costs more time.
– Assuming the software auto-fixes bad inputs. The tool is only as good as the data. Garbage in still yields headaches with building control.
The data and software stack you actually need
/> – The HEM front-end: Select accredited compliance software that uses the published HEM engine. Demand clarity on engine version, audit exports, and a way to lock design-stage versus as-built runs for each plot.
– Geometry workflow: Decide early whether you’ll drive inputs from BIM (IFC or a simple area schedule) or a disciplined 2D take-off. Whatever you pick, write down the method and stick to it; mixed methods breed errors.
– Fabric performance: Collate U-value calculations for external walls, roofs, floors, doors and glazing systems, with declared product conductivities and tolerances. Reference thermal mass where the method requests it.
– Thermal bridging: Either adopt a standardised junction set with installation requirements, or commission junction-specific psi-values. Store drawings, calculations and installation photos in a way the assessor can link to each house type or plot.
– Airtightness: Set target permeability at design; capture test certificates plot-by-plot; log where remedial works altered the tested value. Ensure installers know the air barrier line and photo-capture before cover-up.
– Services data: For ventilation, record system type, manufacturer data for efficiency and specific fan power, duct layout notes and commissioning balances. For heating and hot water, capture heat source model and performance data under relevant test conditions, emitter types, flow temps, storage volumes and standing losses, and control arrangements. For PV, record kWp, inverter model and array orientation/tilt.
– Evidence handling: Use a CDE with mandatory fields that correspond to HEM inputs. Every time a model-impacting item changes, it should generate a notification to the energy assessor along with the supporting data.
Procurement-facing checklist for HEM compliance
/>
– Confirm your HEM software accreditation, engine version and exportable audit trail before RIBA Stage 3.
– Issue product data templates for insulation, windows, cylinders, ventilation units, heat pumps and controls that map to HEM input fields.
– Agree a psi-value strategy (standard library or project-specific calculations) and lock details into subcontract scopes.
– Set up a plot evidence matrix: photos at insulation layers, junctions, service penetrations, and plant labels, with upload deadlines.
– Build a change-control trigger list so substitutions affecting thermal or services performance cannot proceed without re-modelling.
– Programme airtightness tests and ventilation/heat pump commissioning dates to land in time for as-built modelling and building control review.
The UK market will stress-test HEM as vendors release tool updates and building control teams align their expectations. Keep an eye on transitional arrangements, training offers for assessors and site teams, and how early adopters are handling junction evidence and services data granularity.
FAQ
# Which software will be accepted for HEM compliance?
/> Look for tools that clearly state they are aligned with the Home Energy Model engine and are recognised for Part L workflows. Vendors will provide release notes showing the engine version and any guidance notes; ask for an audit export to satisfy building control queries. Where in doubt, confirm with your energy assessor and building control before design freeze.
# What data must be captured during construction to support the as-built model?
/> Gather airtightness test certificates, ventilation and heat pump commissioning sheets, and photos of key junctions and insulation layers before they’re concealed. Record installed product model numbers for services and store relevant data sheets. Keep any thermal bridge evidence and U-value calculations that match the final construction as installed.
# How do product substitutions affect the Home Energy Model?
/> Even small changes—like a different cavity closer, cylinder or MVHR unit—can alter key inputs. Treat these as controlled changes: notify the energy assessor, re-run the model if performance might shift, and update evidence files. This protects handover dates and avoids surprises during building control checks.
# Who should own and manage the HEM model on a housing project?
/> Typically the energy assessor maintains the model, but the main contractor or developer must supply verified inputs and evidence. Clarify responsibilities at appointment, including turnaround times for design changes and where the master dataset lives. A clear RACI avoids disputes when programme pressure is high.
# Can BIM data be used directly for HEM inputs?
/> Yes, but only if the export is structured to match what the HEM tool needs. Many teams find a hybrid approach works best: BIM for areas and orientations, with a controlled schedule for openings and constructions. Always run a test export early and agree how updates will be handled to prevent geometry drift.
