SANS 10400-XA explained: what property developers actually need to know

SANS 10400-XA is one of those compliance requirements that most property developers know they need to meet but few understand in any detail. It arrives as a line item in a specification, gets handed to an engineer, and is generally considered dealt with once the relevant boxes are ticked at design stage.

That approach works, until it doesn't.

The developers who understand SANS 10400-XA properly, not just as a compliance hurdle but as a framework that shapes how energy systems need to be designed, managed, and reported on, are the ones who avoid the expensive conversations that happen six months after handover.

What the regulation actually requires

SANS 10400-XA is the South African National Standard that governs energy usage in buildings. It sets minimum requirements for the energy efficiency of new buildings and major renovations, covering everything from insulation and glazing to hot water systems and lighting.

For property developers, the most operationally significant requirement is around hot water systems. The standard requires that a minimum percentage of hot water heating energy comes from renewable sources, typically solar, depending on the building type and location. This is where geyser management becomes a compliance question, not just an efficiency one.

The compliance gap that nobody talks about

Here's where most developments run into trouble. Meeting SANS 10400-XA at design stage is relatively straightforward. You specify the right number of solar geysers, you get the right certification, and the building passes inspection.

What the standard doesn't guarantee is that the system continues to perform as designed after handover. A solar geyser installation that's correctly sized and installed can still underperform significantly if the load isn't being managed intelligently. If geysers are heating from the grid during peak hours because nobody has set the right parameters, if solar capacity is being wasted because timing isn't optimised, the compliance intent of the installation is being undermined in practice.

This is the gap that creates problems for body corporates and facilities managers who inherit developments post-handover. The paperwork says compliant. The bills say otherwise.

What intelligent management adds

The difference between a SANS 10400-XA compliant installation and one that actually delivers on its compliance intent is active management.

This means monitoring actual solar utilisation in real time, not just at installation. It means setting and enforcing parameters that prioritise solar heating during periods of generation. It means being able to demonstrate, with data, that the system is performing as designed, which is increasingly what trustees, body corporates, and building occupants want to see.

One of our clients achieved 89% solar utilisation across a geyser fleet in a single month. That number doesn't happen by accident. It happens because the system is actively managed, the load is being switched intelligently between solar and grid, and the performance is being tracked continuously.

What developers should be specifying

The practical implication for developers is that SANS 10400-XA compliance shouldn't end at installation. The systems you specify should include a management layer that continues to optimise performance and generate the reporting that proves it.

Specifying a connected infrastructure management platform alongside your geyser installation means the development you hand over is one that body corporates can actually manage. It also means the compliance credentials of the development remain defensible long after handover, which matters increasingly as energy accountability becomes a standard expectation of buyers and residents.

If you're currently specifying new developments and want to understand how to meet SANS 10400-XA in a way that holds up operationally, not just on paper, we're happy to walk through what that looks like in practice.