Your AI Strategy Has an Unpriced Climate Liability
Every board that has approved an AI strategy in the last eighteen months has also approved an environmental liability it hasn’t measured, disclosed, or put on the risk register. Most boards don’t know this yet. They will.
The Guardian’s recent reporting on Australia’s datacentre boom describes a proposed hyperscale facility on Mamre Road in Sydney’s outer west — 52 hectares, six four-storey buildings, 936 cooling units, and 852 diesel backup generators. That last number is worth sitting with. Eight hundred and fifty-two diesel generators, on a single site, as backup infrastructure for the kind of compute that runs the AI tools your organisation has been enthusiastically rolling out. This is what your AI strategy looks like at the infrastructure layer. The question for board directors — particularly those with ESG or audit committee responsibility — is whether that picture is anywhere in your disclosures.
It isn’t. And that’s a governance problem, not an environmental one.
The Vendor Abstraction Problem
Those of us who sat at board tables during the cloud migration of the 2010s watched the same pattern play out. Organisations moved workloads to hyperscale cloud providers and, in doing so, effectively laundered the infrastructure risk through a vendor relationship. The physical reality — the servers, the power draw, the cooling, the geographic concentration of data — became invisible because it sat inside someone else’s contract. Boards approved the business case. The infrastructure complexity disappeared into a service agreement.
AI adoption is doing this again, at greater scale and with greater environmental consequence.
When your organisation licenses a large language model, subscribes to a copilot tool, or builds internal capability on top of a foundation model API, you are consuming compute that lives in a physical facility, draws significant power, consumes significant water, and generates significant emissions. The vendor manages the facility. Your procurement team manages the contract. Nobody is managing the environmental exposure as a first-order business risk — because the abstraction makes it easy not to.
The fact that you don’t own the datacentre does not mean you don’t own the liability. Your investors, regulators, and customers will not accept that distinction indefinitely.
Why This Is a Disclosure Problem Now
Australia’s climate disclosure landscape is shifting in ways that make this a near-term governance issue, not a theoretical future one. The Treasury Laws Amendment (Financial Market Infrastructure and Other Measures) Act introduces mandatory climate-related financial disclosures for large entities, aligned with ISSB standards, with a phased start from the 2025–26 financial year. Under IFRS S2, organisations are required to disclose material climate-related risks and opportunities — including Scope 3 emissions, which is where cloud and AI infrastructure consumption sits for most enterprises.
Scope 3 is precisely where AI compute lives. It is emissions that occur in your value chain but outside your direct operations. The ISSB framework does not care that the emissions are generated by a vendor. It requires disclosure of material Scope 3 categories. For organisations with meaningful AI workloads, compute-related emissions are becoming material. The accounting methodology is still maturing, but the disclosure obligation is not waiting for the methodology to catch up.
ASIC has already signalled that greenwashing enforcement extends to omission, not just misstatement. Approving an AI strategy that promises efficiency and innovation, without disclosing the environmental cost of the infrastructure that strategy depends on, is exactly the kind of selective disclosure that regulators have been flagging.
The Risk Register Gap
The practical problem is that most organisations are not connecting their AI strategy to the environmental balance sheet. The AI programme sits with the Chief Digital Officer or the CTO. The ESG programme sits with the sustainability team or the CFO. The disclosure obligation sits with the legal and company secretarial function. None of these groups are talking to each other about this specific issue.
The result is a risk that is visible from the outside — to regulators, to activist investors, to journalists — but invisible on the inside, where it would need to be managed.
This is a structural governance failure, not an oversight. The incentive for the team driving AI adoption is to show progress. The incentive for the sustainability team is to show improvement. Nobody’s incentive is to calculate how many diesel generators are running in Western Sydney to support the productivity tools approved last quarter.
Board directors with audit committee or ESG committee responsibility need to close this gap by asking a direct question: what is the estimated carbon and water footprint of our AI workload consumption, and where does that exposure sit in our disclosures? If the answer is “we don’t know” or “that’s a vendor question,” you have found the gap.
What Boards Should Actually Do
This does not require a sustainability audit before you can use AI. It requires honest accounting.
First, treat AI infrastructure consumption as a procurement risk category, not just an IT decision. Every material AI vendor contract should include a data request for emissions intensity, water usage effectiveness, and the energy mix of the relevant datacentre regions. Vendors with genuine sustainability commitments will have this. Vendors who can’t answer it are telling you something.
Second, your next ESG disclosure cycle should include an explicit assessment of whether AI compute consumption is a material Scope 3 category. If your organisation has approved significant AI investment, the answer is probably yes. If you haven’t done that assessment, the disclosure is incomplete by definition.
Third, stop treating “the vendor handles infrastructure” as a risk transfer. It is a risk delegation. Delegation does not remove the obligation. If the infrastructure is exposed — to regulatory change, to carbon pricing, to water scarcity constraints, to community opposition at the planning stage — your business model is exposed, because your AI capability depends on that infrastructure existing and remaining accessible.
The Board’s Real Question
The question for boards is not whether to adopt AI. That decision is largely made. The question is whether the governance surrounding AI adoption is proportionate to its actual risk profile — financial, operational, and environmental.
At the moment, for most organisations, it isn’t. The AI strategy was approved with a business case. The environmental liability was not part of that business case. The disclosure framework is now catching up to require it.
The boards that get ahead of this will make a deliberate choice to connect AI strategy to ESG disclosure before the regulator makes that connection for them. The boards that don’t will find themselves explaining, in hindsight, why 852 diesel generators didn’t appear anywhere in their climate risk disclosures.
That is not a technical question. It is a governance one. It belongs at your table.