Why is cooling water suddenly a liability?
Cooling water used to be invisible on the balance sheet of risk. That is changing fast. Government is building the evidence base for mandatory, location-based water reporting, and new mandates would restrict evaporative cooling in water-stressed areas, where water use effectiveness is coming under direct scrutiny.
Much of the proposed new capacity is planned for catchments that are already stressed. So local water availability is becoming a condition of getting built and staying online, not a background detail. Once a site's water draw is a published, accountable figure, it is a liability you manage rather than an assumption you make.
What changes when you design water out?
Designing water out means rejecting the same heat with far less fresh water, and reusing what you do use rather than evaporating it away. Closed-loop and non-evaporative approaches cut the water a site draws and turn its consumption into a controlled, reportable number.
It also removes a supply risk. A site that depends less on a stressed local network is less exposed when that network is under restriction, so resilience and efficiency come together in the same design.
Why act before the rules are mandatory?
Because the direction of travel is set, and retrofits are always harder than designs. Building water efficiency in now protects planning consent, avoids stranded capacity in water-stressed regions, and turns a looming reporting obligation into a position you can already evidence.
The alternative is discovering, once reporting bites, that your water number is the one holding back your next site.




















