top of page
Search

UKGBC is right. Now comes the hard part.

  • Cleo
  • May 11
  • 4 min read

Last month, the UK Green Building Council published two reports calling for urgent action on retrofit and energy optimisation across the UK's commercial building stock. The case they make is clear: with most of today's buildings still in use by 2050, we cannot build our way to net zero. We have to improve what already exists.


At PontePatros, we welcome this call. We also recognise the challenge embedded within it.


Calling for action is necessary. But action without evidence risks repeating one of the built environment's most persistent problems: work gets done, money gets spent, and buildings still don't perform as intended.


The gap between intent and outcome


UKGBC's energy optimisation report identifies data use as a distinct, essential step in the retrofit journey; sitting between aligning incentives and taking action. That framing matters. It acknowledges something the sector has been slow to confront: the performance gap is not just a construction problem. It is a measurement problem.


Buildings are retrofitted to a design standard. Insulation is installed, ventilation systems upgraded, heat pumps commissioned. But without ongoing monitoring, there is often no reliable way to know whether those interventions are working as intended. For the building, or for the people living and working inside it.

Damp persists. Indoor air quality degrades. Energy use doesn't fall in the way modelled. And organisations are left managing complaints rather than preventing the conditions that cause them.


This is not a hypothetical. It is the lived experience of housing associations, local authorities, and landlords managing large portfolios of older stock.


What "use data effectively" actually requires


UKGBC's four-step framework for energy optimisation — engage stakeholders, align incentives, use data effectively, take action — is a sound structure. But step three deserves more unpacking than a single report can offer.

Using data effectively in retrofit and building performance contexts requires:

  • Continuous, real-time monitoring rather than one-off post-completion assessments

  • Sensor infrastructure that works reliably in dense, hard-to-reach environments — social housing blocks, mixed-tenure estates, commercial warehouses

  • Connectivity that doesn't fail when building fabric or geography limits signal

  • Platforms that surface insight, not just readings — so asset managers and building safety teams can act before problems escalate


This is precisely what PontePatros was built to address. Our IAQ sensor platform is connectivity-agnostic — operating across LoRaWAN, 5G, and NB-IoT — specifically because no single network technology works everywhere it needs to. We are currently validating this approach in dense social housing environments through the Digital Catapult's Smart Nano ACTAP programme.


Retrofit assurance as a discipline


UKGBC's reports rightly emphasise tailored, portfolio-wide approaches over one-size-fits-all solutions. We would go further: retrofit without assurance is incomplete.


The organisations that will lead on decarbonisation are not just those that invest in fabric improvements and low-carbon systems. They are the ones that build in the monitoring capacity to prove those improvements are working and to catch performance drift before it becomes a regulatory, reputational, or human problem.


Awaab's Law has changed the legal context for social landlords. The Future Homes Standard will raise the bar for new build. The Decent Homes Standard review is ongoing. Against this backdrop, evidence of building performance is shifting from a nice-to-have to a fundamental requirement.


Data should belong to everyone it affects


UKGBC calls for collaboration across the value chain. We want to be precise about what that means to us, because it shaped every decision we made when building this platform. When we set out to create PontePatros, the founding question was not just what data do asset managers need? It was who is affected by what happens inside these buildings, and what do they need to know?


The answer is not one stakeholder. It is residents who live with damp and poor air quality. It is housing officers responding to complaints. It is asset managers making investment decisions. It is contractors trying to understand whether their work held. It is local authorities meeting their duty of care. It is retrofit programmes needing evidence that interventions have actually performed.

Monitoring data that sits in one organisation's dashboard — visible only to the landlord, invisible to everyone else — does not serve this system. It serves one party in it.


But transparency alone is not the goal. Data is only meaningful when it aids a story. W

hen it helps someone understand something they couldn't before, and do something differently as a result.


For a resident, that might mean understanding why their home feels cold after a retrofit and adjusting how they use their heating. For a contractor, it might mean seeing that a ventilation method underperformed on a previous job and changing their approach on the next. For a housing officer, it might mean spotting a pattern across a block before a single complaint is made. For a retrofit programme manager, it might mean evidence that one intervention outperformed another. Evidence that shapes the next ten decisions.


This is what we mean by shared intelligence. Not a dashboard that everyone can log into, but a platform where every stakeholder has access to the insight that is relevant to them in a form they can act on.


Our goal from the beginning has been to make building performance legible to all the people trying to understand it, improve it, or be protected by it. Not just shared ambition, but shared sight and shared agency.


UKGBC is right that the sector needs to act with urgency. We would add: it also needs to act with openness. Buildings should perform as promised and everyone with a stake in that promise should be able to see whether it is being kept, and know what to do when it isn't.

 
 
 

Comments


bottom of page