The 75-day bargain: what the NSW data centre framework trades and what it leaves open

New South Wales has put numbers around data centre efficiency and attached something valuable to meeting them: speed. The result is Australia’s most substantial state-level data centre framework yet. The bargain raises a second question: once a project earns its faster assessment on design performance, who verifies what the facility actually delivers? This analysis walks through what the framework does, the trade at its centre and the accountability loop still to be closed.

What the framework actually is

The framework has three working parts. The first is a set of guidelines built on six principles: world-class environmental and efficiency standards, no net cost to consumers and communities, funding for additional water and energy supply, enhanced local community infrastructure, investment in future industries across the supply chain and a demonstrated commitment to training and skills. The second is a planning bargain: qualifying projects are offered a streamlined pathway that includes Secretary’s Environmental Assessment Requirements within two months and a development application assessment taking no longer than 75 days in state government hands, supported by a dedicated concierge function inside the planning department. The third is cost allocation reform: regulatory changes intended to ensure data centres pay for the electricity network upgrades they require rather than shifting those costs to households, with the Independent Pricing and Regulatory Tribunal reviewing whether water pricing reflects the full cost of servicing these facilities.

Around the edges sit the machinery pieces: an Industry Advisory Forum, annual review of the guidelines and a new Office of AI within the Cabinet Office. Nineteen projects valued at $50.3 billion are currently in the State Significant Development pipeline, which is the scale this framework will immediately govern.

The numbers are real numbers

The most significant feature of the guidelines is easy to miss: they contain actual figures. Projects can qualify through one of two efficiency pathways. The first requires a design PUE of 1.25 or lower together with a design WUE of 1.0 or lower for potable water (1.6 for non-potable). The second allows a design PUE of 1.3 where design WUE is held to 0.44 or lower, recognising that power and water efficiency pull against each other in cooling design: the trade we walked through in our water analysis, where zero-water designs buy their savings with electricity. Both pathways are defined at mature utilisation, assuming 100 per cent IT load under average annualised climate conditions, with PUE and WUE measured under the ISO/IEC 30134 series. Water-intensive cooling must use recycled water for cooling operations or have a clear agreement with the relevant utility to transition to rainfall-independent supply and the Guidelines recognise that potable water may be used during that transition.

This matters because Australian assessment practice has mostly run on adjectives: world-class, best-practice, industry-leading. A numeric threshold can be checked. A claim of 1.25 either holds or it does not. For the first time in Australia, a government has written efficiency numbers into an approval gate and that alone moves the public conversation from assertion toward evidence. The Guidelines are candid about the starting point: existing planning requirements specify no water efficiency measure at all and the government’s own analysis found nine of twelve proposed projects reporting an average WUE of 1.0.

The trade at the centre

The bargain is speed for standards. For operators, assessment time is money at a scale most public debate underestimates: a committed hyperscale tenant, financed land and a connection agreement can make a year of planning delay worth more than any single compliance cost in the guidelines. A 75-day pathway is therefore a powerful incentive and attaching it to measurable commitments rather than to lobbying is good design. The cost allocation reforms complete the trade: the network upgrades a facility requires are to be paid for by the party creating the need, which addresses the most common and most legitimate community objection to data centre growth, that everyone else’s bill quietly carries it.

Taken together, the six principles read remarkably like the questions communities, councils and this Institute have been asking all year. Efficiency standards, full-cost water, network costs carried by the operator, local benefit, skills. The framework is in large part a governmental restatement of the assessment table.

What the published materials leave open

The thresholds in the guidelines are design values: design PUE, design WUE. A design value is a promise about how a facility will perform, made at approval time, before the facility exists. Operating performance is a different number and every practitioner knows the two diverge: real facilities run partial loads, hot summers, commissioning years and equipment ageing that no design calculation fully anticipates.

There is a further complication in the methodology itself. The design metrics assume mature utilisation at 100 per cent IT load. Real facilities may take years to approach that level and some never reach it. At lower utilisation the supporting infrastructure does not scale down in proportion to the IT load: UPS systems, transformers, pumps, fans and cooling plant carry fixed and part-load losses, while redundancy architecture keeps multiple systems running below their most efficient point. A facility designed for a PUE of 1.25 at full load may legitimately operate at a materially higher figure at partial load. Verification is therefore more than asking whether 1.25 became 1.25: it means understanding performance across the load profile the facility actually carries.

The published materials are detailed about how promises will be assessed and much quieter about how performance will be verified. Three questions follow directly. Who measures the operating PUE and WUE of an approved facility and how often? To whom are the results reported and are they public? What happens when a facility that qualified for the 75-day pathway at 1.25 runs at 1.4?

This is not a hypothetical concern. The government’s own demand analysis estimates that six of every seven megawatts of connection requests may represent phantom demand. That is a different issue from environmental performance, but it carries the lesson that matters for a fast-expanding market: commitments made before construction are not the same thing as outcomes delivered afterwards. A framework that rewards strong commitments with speed needs a mechanism that measures delivery with the same care.

The honest reading is that some of this machinery exists in outline. The Guidelines say applicants will need to demonstrate compliance, commitments made in an environmental impact statement can become conditions of consent and compliance is monitored through existing processes, including annual reviews and independent audits. That is more than nothing and less than a complete answer. Existing compliance processes can enforce conditions of consent, including commitments carried through from an environmental impact statement. What the Guidelines do not clearly establish is whether the design PUE and WUE values that qualify a project for streamlined assessment will translate into ongoing operational measurement, comparison and public reporting. Our noise and water analyses reached the same structural finding at facility scale and the NSW framework now poses it at market scale: the verification gap is the distance between what is promised at approval and what is measured in operation.

The distinction matters because verification cannot be reduced to checking a single number. A facility approved at 1.25 at full IT load should not be expected to report 1.25 at half that load; what should be tested is whether actual performance is consistent with the approved design at the utilisation and conditions actually experienced. That requires operating data, context and a repeatable method for comparing design intent with delivered performance. It is why the Institute’s assessment work treats verification as a distinct stage of the infrastructure lifecycle rather than an extension of development approval and why we have built tools to help communities, councils and decision-makers test whether commitments made at assessment can later be measured against operating outcomes. The NSW framework makes that capability more relevant, not less: measurable approval thresholds create the basis for measurable accountability.

What it means beyond New South Wales

Every other Australian jurisdiction now has a reference point. Councils assessing proposals outside NSW can reasonably ask why a project that would need to commit to 1.25 in Sydney should be assessed against adjectives elsewhere. States drafting their own approaches will be compared with this one. The federal Senate inquiry into the data centre build-out, due to report in November, now has a live state example of what codified standards look like. Tasmania, where major data centre proposals are currently being assessed without an equivalent state framework, illustrates the contrast particularly clearly. That is an observation about frameworks, not about any project.

The bottom line

The NSW framework is the most substantial piece of data centre policy any Australian state government has produced: real numbers, a real incentive and cost allocation that answers the fairest community objection. What its published materials leave open is the operating half of the bargain. NSW has written the performance promise and attached real value to making it. The next step is closing the accountability loop: measure what gets built, understand how it performs at the load it actually carries and verify that the operating outcome matches the approved design intent. The numbers now exist. The question is who verifies them.

A topical commentary from the Digital Infrastructure Institute. For assessment practice across all jurisdictions, see our State & Territory Frameworks.

Sources

• NSW Government, Nation leading framework to harness NSW data centre investment, ministerial release, August 2026
• Infrastructure NSW, Data Centres and the NSW Data Centre Guidelines, August 2026
• w.media, NSW puts data centres on fast track, but developers face higher costs, August 2026