Australia's 2.16-gigawatt AI lease starts with a disclosure gap

01

WHAT ACTUALLY CHANGED

Reuters reported on September 16 that Anthropic signed a lease at Singapore-based developer Zerra DC's proposed Western Downs Digital Park near Dalby, about 250 kilometres west of Brisbane. Two people familiar with the plans supplied the core deal details, according to Reuters, and Anthropic and Zerra declined comment. Reuters also said the intended workload is inference, the daily work of running trained models, rather than training them. That reporting supports a proposed tenant agreement. It does not supply a signed lease, tenant capacity, term, price, commencement condition, or direct company confirmation.

Queensland Premier David Crisafulli separately told parliament that Anthropic would buy into the first stage of the project. The Guardian reported that statement and described the wider proposal as a four-stage development valued at A$31.9 billion in planning material. The project value is not the value of Anthropic's lease, verified construction spending, or money already committed. The Premier's announcement is public political confirmation of intended participation, but the commercial documents and complete conditions remain unavailable.

The proposed campus has a total peak capacity of 2.16 gigawatts. ABC reported on September 14 that the four-stage project could use about 47 gigawatt-hours per day at full build-out, compared with Queensland's average daily consumption of 170 gigawatt-hours. Those comparisons show the proposal's scale. They do not establish day-one demand, the first stage's load, average utilization, one tenant's share, a construction schedule, or whether every phase will reach operation.

The land-use decision is unfinished. ABC reported that Zerra lodged a development application with Western Downs Regional Council and that the project could take four to six years to build. The Guardian said the local application remains pending and covers land of about 725.5 hectares, part of it used as a feedlot. Queensland's planning department says local governments usually assess and decide development applications, publish reasons, consider submissions when notification applies, and may impose conditions or refuse an application. A proposal, lease, and political announcement do not replace that process.

The energy and cooling story is still mostly a set of promises. Reuters said sources described renewable power-purchase agreements, direct connection to the grid, developer-funded connection costs, and closed-loop air cooling intended to reduce clean-water use. ABC reported that the site is near solar, wind, a major substation, and three gas-fired power stations, while Queensland leaders have argued for an energy-agnostic approach that could include coal and gas. No public contract, connection study, hourly load profile, generation schedule, water balance, emissions estimate, or independent engineering review resolves those competing descriptions.

02

WHY THIS MATTERS

A gigawatt is a rate, not a construction schedule. Putting 2.16 gigawatts in a headline can make one enormous load sound as if it switches on at once. The useful document would split the campus into stages, list the maximum and expected load for each, name every tenant share that can be disclosed, show the earliest energization date, and state the conditions that must be met before the next stage begins. Without that table, a maximum campus plan gets mistaken for a current fact.

New generation does not automatically mean lower bills or a stable grid. The outcome depends on what is built, when it connects, whether it operates when the data center needs power, which network upgrades become necessary, who guarantees the cost, and what happens if the tenant leaves. A credible proposal should publish the connection pathway, modelling assumptions, upgrade account, security deposit, curtailment rules, cancellation liability, and reconciliation method. Otherwise, existing customers are being asked to trust a sentence where an invoice belongs.

A closed loop is not a complete water answer. Air-cooled or recirculating systems may reduce routine consumption compared with evaporative cooling, but a project can still use water during construction, equipment cleaning, fire protection, offices, landscaping, humid conditions, emergency operations, or onsite generation. The developer should publish source, withdrawal, consumption, discharge, temperature, drought, and contingency figures for each stage. Reduced is useful. Measured is better.

The development sits in a working rural landscape shaped by agriculture, gas, electricity infrastructure, and earlier resource disputes. Local residents will experience roads, construction traffic, housing pressure, emergency-service demand, land conversion, noise, taxes, jobs, and any groundwater or transmission effects before distant AI users do. A community-benefit agreement can help only if its money, milestones, governance, audit rights, remedies, and duration are public and enforceable.

Inference campuses make the cloud physically local. A chatbot answer may feel weightless, but it is produced by servers connected to land, transmission, generation, cooling, labor, and public institutions. That makes this proposal a useful test for the next wave of AI infrastructure: can governments preserve commercial confidentiality while still giving communities enough evidence to judge cumulative load, public cost, environmental limits, and the conditions under which a project must slow, pay, repair, or stop?

03

WHERE IT COULD HELP

• Require one public stage table showing land disturbed, buildings, tenant capacity, maximum load, expected average load, energization date, generation source, network works, water use, jobs, taxes, and approval status before construction or expansion
• Create a grid-cost ledger that names each substation, transmission line, storage asset, generator, study, security payment, upgrade payer, cancellation risk, curtailment rule, and final cost reconciliation without exposing genuine security-sensitive details
• Publish an independently reviewed water balance for ordinary days, peak heat, drought, maintenance, construction, fire protection, onsite generation, and emergency operation, with monitoring points and enforceable withdrawal and discharge limits
• Give residents one plain-language portal for the complete application, referral requests, revised studies, submissions, hearing dates, decision reasons, conditions, monitoring data, complaints, enforcement actions, community-benefit payments, and appeal routes
• Make later stages conditional on measured performance from earlier ones, including power demand, reliability, emissions, water, traffic, noise, local procurement, workforce claims, incidents, complaints, and correction of any missed limit