Engineer QA App
A phone-friendly web app that walks you through commissioning and acceptance work step by step: HIUs, CIUs, MVHR, plot checks, network equipment. You answer the questions on site; the paperwork writes itself.
What you need. Any modern phone, tablet or laptop browser. Sign-in is through your Microsoft account, so there are no new passwords and no software to install.
Your jobs, in one list. Open the app and see exactly what's assigned to you, where it is, and how far you've got. No chasing spreadsheets or waiting for the office to email a job sheet.
Forms that think. Questions appear only when they apply. Answer that a plot has underfloor heating and the appropriate commissioning process drops in as a new section, pulling with it any relevant design data or drawings. Units, dropdown options and lookup tables are built in, so you're never guessing what format the office wants.
Instant pass/fail. Readings are checked against the commissioning criteria as you type. A failing ΔT or setpoint goes red in the app while you're stood next to the unit and can fix it, not three weeks later when the report bounces and you are on another job.
Fails explained on the spot. A failed or N/A step asks you for a short comment right there. That comment follows the reading into the report, so nobody rings you a month later asking what happened at plot 114.
Photos where they belong. Snap evidence against any step from your phone camera. Mandatory photo steps are flagged, so you know before you leave site that you've captured everything.
Less typing. Site-wide values such as setpoints, design temperatures and device models are set up once as defaults and pre-filled on every plot. You confirm or override; the app records which is which.
Developer QA App
On a heat-network development the commissioning evidence usually lives in a mix of hand-written forms, spreadsheets and long-lost emails. You find out a subcontractor is behind, or that a plot failed, at handover, when it's expensive and delays final acceptance. The Developer QA App makes the works visible while they happen and makes the sign-off chain explicit.
Progress tracker. A traffic-light grid per plot and per section of the works: green complete, yellow in progress, red failed checks, grey untouched. You can see at a glance which blocks are moving and which are stalled, without ringing anyone.
A job lifecycle you can hold people to. Every device on every plot is a job with a state. Who it's assigned to, when they started, and what's outstanding are facts in the system, not claims in a meeting.
Issues surfaced early. Failed checks and N/A answers require an explanatory comment from the engineer at the moment they happen, and a missing explanation is itself flagged as a failure.
Named evidence. Every reading logs who entered it and when, and whether it was typed by the engineer, pre-filled from a site default, or imported. Overriding a default is recorded as a deliberate act.
A real sign-off chain. Engineers submit; contract managers review and reject substandard work back with notes; certificates are generated and signed by the manager, with the name and date stamped into the document; the developer then accepts or rejects the certificate set per plot, with rejection reasons returned to the manager. Three independent stages, all logged.
Audit trail. Assignments, submissions, approvals, rejections, certificate generation and acceptance are written to an immutable audit log.
Certificates without the chase. A certificate tracker shows the full document set for the whole site: which certificates are required for each plot, which exist, which are awaiting your acceptance, which were rejected. Templates can be your own forms imported from any PDF and filled directly from the captured data, so documents look the way your process expects. Existing templates include HIU manufacturer commissioning sheets, unvented cylinder benchmark certificates, MVHR commissioning certificates, TMV certificates and water quality test certificates.
Standards-aligned data, not just documents
Everything is captured against a structured naming standard aligned with HNTAS element types and heat-network protocol addressing. That means the data outlives the PDF: it can feed O&M handover, performance monitoring, KPIs and network operator reporting without re-keying.
HNES studies and monitoring on the same platform
Network operators improving an existing scheme run their Heat Network Efficiency Scheme study on the platform: surveys, HNTAS M4 assessments, the KPI baseline, a modelled works programme with costs and savings, and the signed reports and workbook the scheme asks for, with the capital grant application drafted from the same record. HNTAS monitoring, live site data, KPI calculation and the monthly submission run in the same place.
Your data stays yours
Hosted on Microsoft Azure in the UK, one organisation per tenant, Microsoft sign-in, exported to Excel whenever you want it. Sign-in uses Microsoft Entra with the basic sign-in permissions only (name and email).
Getting access. The platform is invitation-only. Your organisation's admin invites you, or Heatweb sets your organisation up and invites the first admin. You then sign in with your normal Microsoft work account at app.heatweb.cloud.