The Home Energy Model is set to underpin compliance for new homes under the Future Homes Standard, and the software choices being made on live UK housing projects need to anticipate that shift. Many teams still rely on SAP-based tools to get through planning, specification and Part L submissions, but the gap between design intent and as-built evidence is closing fast. The winners will be platforms that can work today, interoperate with BIM and product data, and carry forward cleanly into HEM workflows without forcing a complete reset mid-programme.
TL;DR
/>
– Prioritise tools with a published HEM roadmap, open data export and robust audit trails from design to as‑built.
– Demand native handling of ventilation, airtightness, thermal bridging and overheating in one workflow, not bolt‑ons.
– Specify API/IFC links so house types, product specs and plot changes flow between models and site packages.
– Contract for competence: assessor accreditation, change control, and training for design managers and M&E leads.
– Pilot on a small plot run to prove evidence packs, clash points and programme impacts before committing site‑wide.
How to specify HEM-ready energy modelling software in the UK
/> Start with capability across the entire domestic pathway: early-stage massing and house‑type templates, detailed fabric and services inputs, Part L compliance checks, overheating assessment, and an as‑built evidence pack. HEM-ready doesn’t just mean a future module; it means a data model that can transparently show assumptions and sources, maintain versioning, and output machine‑readable files for verification when new test suites and accreditation arrive. If the platform can’t expose the basis of U‑values, psi‑values, system efficiencies and control logic, it will become a liability when auditors probe the chain of decisions.
Insist on interoperability. IFC or Revit plug‑ins should let you map walls, roofs, windows and thermal junctions without re‑typing. Product data sheets for heat pumps, emitters and MVHR need structured properties (not PDFs) so performance curves and commissioning limits translate into the model. Look for two‑way links to document control: when a door spec changes or a junction detail is updated, the model flags compliance consequences and prompts a sign‑off, notifies the design manager, and logs the delta for the as‑built pack.
Commercially, get clarity on licensing, concurrency and cloud storage. Programmes shift, phases overlap, and you’ll need multiple users across design, energy assessment and M&E to touch the same job without corrupting it. Confirm the vendor’s UK helpdesk hours, update policy during planning conditions crunch, and how legacy SAP models will be migrated to HEM calculations when the switch occurs. Finally, overheating workflows should reflect UK practice for dwellings, with weather files, glazing shading inputs and window‑opening assumptions you can defend at technical review.
# Procurement checklist
/>
– Ask for a written HEM transition plan, including how existing SAP models and libraries will be upgraded without data loss.
– Require evidence pack outputs: thermal bridging schedules, photographic evidence placeholders, test certificates and change logs in a single export.
– Specify BIM/data integration: IFC import, parameter mapping for constructions, doors/windows, and an API for house‑type libraries.
– Mandate role‑based access, version control and a full audit trail tied to RIBA stages and site milestones.
– Confirm native overheating assessment and ventilation/airtightness pathways are included, not third‑party plugins only.
– Set minimum competence: named accredited assessors, training for design managers/M&E leads, and response times for model updates during design freeze.
– Agree on data ownership and retention so the developer can reuse models across plots and phases without fresh licences.
# Common mistakes
/>
– Treating HEM as a bolt‑on to legacy SAP workflows; the data structure and audit trail expectations are different.
– Ignoring thermal bridging libraries and psi‑values until late stage, then discovering detail changes tip compliance offside.
– Relying on PDFs and emails for product performance, which prevents reliable model updates and causes re‑keying errors.
– Buying on licence price alone without testing evidence pack exports or change control in a live plot scenario.
Managing interfaces and risk across design, site and compliance
/> Picture a 90‑unit suburban scheme with mixed house types on a tight programme. The developer’s design manager is pushing for a design freeze next month so plots can break ground before winter. The energy assessor is still iterating heat pump emitter sizing while the timber frame subcontractor requests confirmation of insulation thickness to firm up factory slots. A late change to patio door spec arrives from procurement, nudging U‑values. The M&E subcontractor wants clarity on MVHR spacings that clash with joist layouts. Building control is asking how as‑built evidence will track against each plot, not just the prototype.
In that kind of pressure, the software has to be the shared reference point. House‑type templates should lock agreed fabric and service options, with parameterised alternatives the commercial team can switch between with known compliance impacts and cost. Thermal junction details and psi‑values must sit in a controlled library tied to drawings, so if a junction detail is substituted, the model flags the compliance delta for every affected plot. Change control should start in the model: a door spec swap updates thermal performance, pushes a notification to the energy assessor and M&E lead, and requires a sign‑off before releasing updated drawings to site.
Risk lives in the handoff. Ensure commissioning data flows back: air‑tightness tests, ventilation flow rates and heat pump commissioning sheets should slot into the evidence pack per plot. If the platform supports on‑site apps for tagged photos at critical junctions, you’ll close the loop between detail intent and what went into the wall. Agree who owns the golden thread: often the developer holds the master model, while the energy consultant manages compliance states and the principal contractor populates as‑built evidence during construction.
Measuring value: what good looks like in practice
/> Value here is not another dashboard. It’s fewer late-stage surprises, faster decisions when the spec shifts, and a cleaner compliance sign‑off. On a pilot plot run, measure the turnaround time from a spec change (say, window g‑value or emitter type) to a new compliance result with updated drawings. Track how many manual re‑entries are needed to push changes from BIM to energy model; zero re‑keying should be the goal. Assess the completeness of the evidence pack before pre‑plaster: are photo slots, thermal junction references and test placeholders aligned to the actual build sequence?
There’s also programme value. When overheating is assessed early with realistic shading and ventilation assumptions, clashes with facade design and occupant comfort can be resolved before planning conditions bite. A robust audit trail reduces the back‑and‑forth with building control at completion. If you’re using MMC, confirm the platform handles factory tolerances and substituted materials without rebuilding the model. For vendor selection, run a bake‑off using one house type, two product swaps and one junction change; score not just compliance outputs, but how clearly the software explains “what changed, where, and why it still passes”.
Three questions for the next project meeting: Which decisions are currently stuck in email that the model should own? Where would a product swap today most likely derail compliance? Who signs off each plot’s evidence pack and when in the programme?
FAQ
/>
Do we need to replace our current SAP tool immediately?
Not necessarily. Many teams will continue using SAP-based tools while preparing for HEM. The key is selecting a platform with a clear migration path so today’s models, libraries and evidence can move forward without rework. Ask vendors to demonstrate how an existing project will transition when HEM accreditation lands.
# Who should own the HEM model and its data?
/> On most housing schemes the developer benefits from owning the master model so it can be reused across phases and plots. The energy assessor typically manages compliance states, while the principal contractor contributes as‑built evidence. Make data ownership explicit in contracts, including retention, access for building control, and reuse rights for future developments.
# How does HEM-ready software link with BIM and product information?
/> Look for IFC/Revit connections that map constructions, openings and thermal junctions directly into the energy model. Product data for heat pumps, MVHR and windows should come in as structured attributes rather than PDFs, so performance curves and control options flow through. Test the round‑trip: change a component in BIM, reconcile in the model, and push an updated schedule back to drawing packages.
# What competence and training should be written into appointments?
/> Specify accredited assessors for domestic energy modelling and require named individuals, not just a company badge. Include training for design managers, M&E leads and site engineers on the change control and evidence capture process inside the software. Add response times for model updates during design freeze and at pre‑plaster, when decisions are most time‑critical.
# How do we handle mid‑programme design changes without derailing compliance?
/> Treat the model as the single source of truth for change control. When a spec shifts, trigger a model update, rerun compliance/overheating, and issue a controlled change note tied to affected plots and drawings. Agree a small governance group (design manager, energy assessor, M&E lead) that can approve swaps quickly with documented impacts on performance, cost and programme.
