Water Use Transparency: A Critical Shift in Development

Mandatory public reporting of water use isn't just a regulatory checkbox — it's a fundamental reordering of who holds power in infrastructure development decisions.

Governor Spencer Cox's statement was blunt: all water use must be reported publicly, and developers cannot reduce water flowing to the Great Salt Lake. No wiggle room. No phased compliance timeline. No carve-outs for projects already in the pipeline. For developers who've grown accustomed to treating water as a quiet line item in project budgets, that kind of language signals something bigger than a policy update.

It signals that the era of opaque water management in infrastructure development is closing.

Understanding Water Use Reporting Regulations

Water has always been regulated. What's changing is the *visibility* requirement — and that distinction matters enormously.

Traditional water permitting frameworks focused on whether a developer could access water, not on whether the public could see how much was being consumed, when, and for what purpose. Public reporting flips that dynamic. It transforms water from a private operational input into a shared public resource with a transparent ledger.

The requirement that water use be reported publicly — not just filed with regulators — creates accountability that internal compliance programs simply cannot replicate.

The Great Salt Lake context makes this particularly pointed. The lake has lost roughly half its surface area over the past few decades, driven substantially by upstream water diversion for agriculture, municipalities, and development. It now sits at historically low levels, with consequences that extend well beyond aesthetics: dust storms carrying toxic sediment, collapsing brine shrimp ecosystems that support millions of migratory birds, and a regional economy exposed to long-term environmental degradation.

When Cox draws a hard line against development reducing the lake's water supply, he's not being dramatic. The science backs the urgency. The public reporting requirement is the enforcement mechanism — because what gets measured publicly gets managed differently.

Impacts on Infrastructure Development

Here's the non-obvious angle most coverage misses: mandatory water use reporting doesn't just add a compliance burden. It fundamentally changes project economics at the planning stage.

When water consumption becomes a public number, it becomes a negotiating variable — with communities, with regulators, and with investors increasingly focused on ESG metrics. Developers can no longer quietly absorb water costs or exceed estimates without scrutiny. Every gallon becomes a data point in a public record that environmental groups, journalists, and competing stakeholders can analyze.

For large-scale infrastructure projects — data centers, battery storage facilities, solar installations with cleaning and cooling requirements — water exposure is rapidly becoming a material risk disclosure issue, not just an operational one.

Consider data centers specifically. A hyperscale facility can consume millions of gallons of water per day for cooling. That number, reported publicly on a quarterly basis, invites scrutiny that private permitting never did. Developers building in water-stressed regions like the Great Basin will need to model not just whether they *can* secure water rights, but whether their consumption profile will survive public and regulatory pressure over a 20- or 30-year project lifespan.

The shift in long-term development strategy is real. Projects that once seemed viable based on water availability alone now need to account for water optics. That's not irrational — it's the market catching up to ecological reality.

Compliance Strategies for Developers

Getting ahead of mandatory reporting requirements isn't just about avoiding penalties. Done well, it's a competitive advantage.

Developers who build robust water metering and reporting infrastructure early will move faster through future permitting processes, attract capital from ESG-conscious investors, and build credibility with the communities they're trying to develop in. Those who scramble to retrofit compliance frameworks after regulations tighten will spend more and move slower.

A few concrete approaches worth considering:

Real-time metering and digital reporting systems are no longer optional infrastructure for serious developers. Systems that can track consumption at the sub-project level and export data in formats regulators and the public can readily access will become table stakes. Several utilities and third-party water management platforms already offer this capability — the barrier is organizational will, not technology availability.

Water budgeting as a design constraint — not an afterthought — should be embedded into project planning from the earliest feasibility stages. Just as projects model grid interconnection timelines or zoning risk, water consumption limits should be a hard ceiling that shapes engineering decisions, not a variable adjusted after design is complete.

Third-party auditing of water reporting builds credibility that self-reported data cannot. For projects near sensitive ecosystems like the Great Salt Lake, independent verification may become a de facto expectation from regulators and community stakeholders, even if it isn't formally required.

Case Studies: Successful Water Management in Practice

The most instructive examples come from sectors that faced public water scrutiny before infrastructure development did.

Semiconductor manufacturers — Intel, TSMC, Samsung — have operated under intense water reporting expectations for years, driven by both regulatory pressure in water-stressed geographies and investor scrutiny. TSMC's Arizona facilities, for instance, have been subjects of detailed public water consumption commitments, including specific recycling rate targets, before a single tool was installed. The lesson for infrastructure developers: proactive disclosure with specific, verifiable commitments outperforms reactive compliance every time.

Agricultural water users in the Great Salt Lake watershed offer a different kind of case study — a cautionary one. Decades of water diversion without public accountability contributed directly to the lake's decline. The regulatory response now affecting developers is, in large part, a correction to that history. Infrastructure developers who treat the current transparency requirements as burdensome are misreading the room; they're actually benefiting from a regulatory framework that, had it existed earlier, might have preserved more water availability for everyone.

The developers who come out ahead in water-constrained markets will be the ones who treat transparent water management not as a cost center, but as a trust-building asset with regulators, communities, and capital markets.

The Future of Water Use in Development

The trajectory here isn't ambiguous. Reporting requirements will tighten. Geographic scope will expand. What Utah is implementing around the Great Salt Lake today will likely be a model referenced in Nevada, California, Arizona, and other water-stressed states within the next several years.

Several trends are worth tracking closely.

Water markets are maturing. As water rights become more explicitly tradeable in western states, public consumption data will feed directly into pricing mechanisms. Developers who understand their water footprint precisely will be better positioned to navigate those markets — either acquiring rights competitively or demonstrating efficiency that justifies their allocations.

Technology is shifting the baseline of what's achievable. Dry cooling systems, closed-loop water recycling, and AI-driven consumption optimization are moving from experimental to deployable at commercial scale. Developers who invest in these technologies now will have a defensible story when regulators ask hard questions in five years.

Regulatory stacking is coming. Water reporting requirements will increasingly intersect with climate disclosure frameworks, environmental impact assessments, and community benefit agreements. Developers who treat these as separate compliance silos will find themselves managing redundant, conflicting reporting obligations. Those who build integrated environmental management systems early will handle the complexity more efficiently.

The bottom line is straightforward: water is no longer a background assumption in infrastructure development. It's a front-page variable — literally, given the public reporting requirement — that shapes site selection, project design, financing, and long-term operational risk. Developers who internalize that shift now, before it's forced on them, are the ones who will still be building projects in the Great Salt Lake watershed a decade from now.

Explore more about water use transparency and its implications for development.

INTERNAL LINK SUGGESTIONS:

• [INTERNAL LINK: water management strategies]
• [INTERNAL LINK: infrastructure development trends]
• [INTERNAL LINK: ESG metrics in development]