What to look for in heat pump design software
What this post covers: This guide covers how heat pump design software works, why accurate inputs matter more than calculation speed, what to look for in a tool that genuinely reduces design risk rather than just automating the workflow, and how Spruce approaches the specific failure modes that cause heat pump installations to underperform.
The short answer: Heat pump design software automates fabric and ventilation heat loss calculations, sizes emitters and pipework, and generates MCS-compliant documentation. The hard part is getting the inputs right: room dimensions, construction materials, and air change rates. Software that catches input errors before they reach the calculation reduces real design risk. Software that just runs the numbers faster moves the risk upstream without removing it.
There is a version of "heat pump software" marketing that focuses entirely on speed: go from survey to system design in less time, with fewer clicks, and a professional-looking report at the end. In part, that framing is true, speed is a genuine benefit. But it misses what actually causes heat pump installations to underperform.
Most heat pump system failures do not trace back to arithmetic. The calculation, once you have the right inputs, is time consuming but relatively straightforward. The failures trace back to input errors: a wall material misidentified, an air change rate underestimated for a draughty Victorian terrace, a floor type assumed rather than confirmed. Software produces a precise-looking output from those inputs regardless of whether they are correct. A professional report does not mean a correct one.
The best heat pump design tools are built around this reality. The question to ask of any software is not "how fast does it calculate?" but "what does it do to catch input errors before they become wrong answers?"
How does heat pump design software work?
Heat pump design software takes property-specific inputs and runs fabric and ventilation heat loss calculations for every room in the building. The results are used to size the heat pump, emitters, and pipework for the design flow temperature.
The two core calculations are:
Fabric heat loss: how heat conducts through walls, windows, floors, and roof:
Qfabric = U × A × ΔT
Where U is the U-value of the material (W/m²K), A is the surface area (m²), and ΔT is the temperature difference between inside and outside on the design day.
Ventilation heat loss: how warm air escapes and is replaced by cold outside air:
Qventilation = V × ACH × 0.33 × ΔT
Where V is the room volume (m³), ACH is the air change rate per hour, and 0.33 is the specific heat capacity of air.
Software handles both calculations simultaneously across every room and aggregates the results into a total building heat loss figure. From there, it applies the design flow temperature to calculate the required emitter output in each room, checks that against available emitter specifications, and produces a compliant system design.
The calculation itself takes seconds once the inputs are entered. The inputs are what take time and what carry risk.
What separates tools: Some software pre-loads U-values from an existing EPC, which reduces manual input time for properties with a current certificate. Others require manual input for every element. For properties without an EPC, or where EPC data is based on assumptions rather than direct assessment, manual input is always required — and the engineer's material judgment is the key variable.
Citation capsule: Heat pump design software calculates fabric heat loss (Qfabric = U × A × ΔT) and ventilation heat loss (Qventilation = V × ACH × 0.33 × ΔT) for every room, then uses these results to size the heat pump, emitters, and pipework at the design flow temperature. The accuracy of the output is determined by the accuracy of the U-value, area, and ACH inputs.
Why do accurate inputs matter as much as fast calculations?
An engineer who has been doing manual heat loss calculations for years can run the conduction and ventilation formulas in a spreadsheet. It takes longer than software, but the arithmetic is the same.
Consider the two most common input errors:
Material misidentification: Mistaking a solid brick wall (U-value ~2.1 W/m²K) for a cavity wall (~0.5 W/m²K) changes the fabric heat loss for that element by a factor of four. In a property with substantial solid wall area, this error alone can shift the total heat loss by 2–4 kW. Potentially the difference between a 9 kW and 12 kW heat pump, or between adequate and undersized radiators throughout.
ACH underestimation: Getting the air change rate wrong for a draughty period property, assuming 0.5 ACH when the actual rate is closer to 1.5, can double the ventilation heat loss contribution. In a large Victorian terrace, that can add 3–5 kW to the total.
Both errors produce a report that looks correct. The software runs the formula accurately on the wrong inputs and generates a professional output that gives the engineer, and the customer, false confidence in the result.
This is the real risk that heat pump design software either addresses or ignores. Fast calculation with weak input validation is speed without safety. The tools that reduce real design risk are the ones built around catching these errors before they reach the output.
What should good heat pump design software catch before it runs the calculation
Not all software approaches input validation the same way. Here is what to look for:
Feature | What it does | Why it matters |
Validated U-value libraries by construction type and build period | Assigns validated thermal values based on material and age rather than accepting any engineer input | Reduces material misidentification, the most common fabric heat loss error |
EPC import with override capability | Pre-loads EPC U-values as a starting point, but allows the engineer to override where on-site assessment differs | Saves time without sacrificing accuracy; EPC values are assumptions, not measurements |
ACH reference ranges by property type | Surfaces appropriate ACH ranges for the building type being surveyed | Reduces ACH underestimation (most common in period properties with draughts and open chimneys) |
LiDAR room measurement | Measures room dimensions in seconds, calculates volume automatically | Eliminates manual dimension input errors; volume feeds directly into the ventilation formula |
Plan tracing for new builds | Allows survey from PDF architectural drawings | Enables accurate pre-construction heat loss without physical measurement |
ΔT50 conversion for emitter sizing | Automatically adjusts published radiator output to the system's actual design flow temperature | Eliminates a common sizing error where engineers spec radiators at published output rather than design-condition output |
Offline capability | Allows survey input without a mobile signal, syncing when connectivity is restored | Removes the need for handwritten notes that get transcribed later (a source of transcription errors) |
The last point matters more than it might seem. One of the quieter sources of input error in heat loss surveys is the gap between on-site observation and data entry. An engineer who writes dimensions in a notebook and transcribes them later introduces a transcription error risk that does not exist when input happens on site. Offline-capable software closes that gap.
What does oversizing actually cost a homeowner — and why does it matter for your business?
The case for accurate heat pump sizing is usually made in terms of efficiency. An oversized heat pump cycles more frequently, which reduces its SCOP and increases running costs. But the business case for the installer is worth being explicit about.
An oversized heat pump that cycles excessively will produce customer complaints. The homeowner notices temperature instability. They see electricity bills higher than the installer promised. They may attribute this to a poor installation rather than a sizing error. That complaint becomes a review. That review costs future work.
The numbers are significant. A heat pump running at SCOP 2.0 due to oversizing and cycling costs roughly 50% more to run than the same heat pump operating correctly at SCOP 3.0 (Carbon Trust, Heat Pump Efficiency Review, 2023). On a typical UK home using 12,000 kWh of heat per year, that is a running cost difference of approximately £500–£800 per year at current electricity prices. That's a difference the homeowner will notice and attribute to the installation.
Correct sizing, by contrast, produces a system that runs as designed, meets the efficiency estimates in the quote, and generates the kind of customer satisfaction that produces referrals. The commercial case for accurate heat loss calculation is not just compliance. It is the difference between a customer who recommends you and one who doesn't.
How does heat pump software handle MCS compliance documentation?
For MCS-certified installers, the design documentation is not optional. MCS:2025 requires that every heat pump installation is accompanied by a heat loss calculation, an emitter sizing schedule, and a system specification that are all internally consistent and traceable.
Producing these documents manually from spreadsheet outputs is time-consuming and prone to inconsistency between documents. If the heat loss calculation changes at any point during the design process, every downstream document needs to be updated manually and the audit risk is that they are not.
Software that generates MCS-compliant documentation automatically from the same calculation that drives the system design eliminates this inconsistency risk. The heat loss figure in the design is the same figure in the compliance document, because they come from the same source.
For BUS grant applications, this consistency is particularly important. The MCS certificate, the heat loss calculation, and the system specification must all align. Discrepancies between them can delay or prevent grant payment.
MCS:2025 requires heat pump installations to be accompanied by a heat loss calculation, emitter sizing schedule, and system specification that are internally consistent and traceable. Software that generates MCS-compliant documentation from the same calculation used for system design eliminates the inconsistency risk that arises when documents are produced separately. All documentation must be ready within 30 calendar days of commissioning under the new certificate window (MCS Scheme Documents, 2025).
How Spruce handles heat loss surveys and system design
Spruce is built around the reality that input accuracy is the primary risk in heat pump system design.
The platform includes multiple survey methods (LiDAR scanning on mobile devices, plan tracing for new builds, and manual room measurement). All of which feed directly into the calculation engine without a transcription step. Offline capability means survey data is entered on site, not written down and typed up later. U-values are drawn from validated libraries by construction type, with EPC import available where applicable. ACH reference ranges are surfaced by building type to reduce the most common ventilation input error.
From the survey inputs, Spruce runs the fabric and ventilation calculations, converts emitter output to ΔT50 at the design flow temperature, sizes the system, and generates MCS-compliant documentation. All from the same data, with no manual document production step.
The result is a system design you can defend: consistent documentation, traceable methodology, and a heat loss figure that reflects what is actually in the building.
Book a demo to see the full workflow, or speak to our team to discuss your current survey and design process.
Frequently asked questions about heat pump design software
What is the difference between heat pump design software and a heat loss calculator? A heat loss calculator runs the fabric and ventilation formulas for a single room or whole building and produces a heat loss figure in kilowatts. Heat pump design software does the same calculation but then uses the results to drive a full system design: heat pump selection, emitter sizing at the design flow temperature, pipework sizing, hot water cylinder specification, and MCS-compliant documentation. A standalone heat loss calculator is a calculation tool. Heat pump design software is a workflow tool that takes you from survey inputs to a complete, compliant system design in one process.
Can heat pump software work from architectural plans for new builds? Yes. For new builds or major renovations where the property does not yet exist or is not accessible for measurement, good heat pump design software allows you to trace PDF floor plans and assign construction materials from the specification. The heat loss calculation methodology is identical. The inputs come from the plan rather than physical measurement. This is particularly useful for volume house-builders and developers who need to design heating systems before construction begins.
Does heat pump software replace the need for an on-site survey? No. Software processes the data you give it. It does not assess the property for you. The on-site survey is where you identify construction materials, assess ventilation characteristics, measure or confirm room dimensions, and observe factors that are not visible in drawings or EPC data (open chimneys, suspended floors, unusual thermal bridges). Software can speed up data entry on site and reduce transcription errors, but the engineering judgment that informs the inputs remains the engineer's responsibility.
What happens if I input wrong data into heat pump design software? The software will produce a precisely wrong answer. Calculation software is only as accurate as its inputs. If a wall material is misidentified, an ACH rate is underestimated, or a room dimension is wrong, the heat loss figure will be wrong in proportion to the error. Good software includes validation features (validated U-value libraries, ACH reference ranges, and dimension sanity checks) that reduce the likelihood of these errors. But no software can compensate for an incomplete or inaccurate on-site survey.
Is MCS-compliant documentation automatically generated? In good heat pump design software, yes. The heat loss calculation, emitter sizing schedule, and system specification are generated from the same underlying data, ensuring internal consistency. This matters for MCS audits, where discrepancies between design documents are a common compliance failure. It also saves significant time per job. Manual production of MCS-compliant documents from spreadsheet outputs typically takes one to two hours; software generation takes minutes.
What should I look for when evaluating heat pump design software? The most important question is not "how fast is it?" but "what does it do to catch input errors?" Look for: validated U-value libraries by construction type and build period; ACH reference ranges by property type; LiDAR measurement capability; offline data entry so inputs happen on site rather than being transcribed; automatic ΔT50 conversion for emitter sizing; and integrated MCS-compliant documentation. A tool that runs fast calculations from bad inputs is more dangerous, because the professional output suppresses the engineer's instinct to sanity-check.