Data Center Water Permits: There Is No Federal Permit — and That's Exactly Why Siting Teams Get Blindsided
← Back to Blog Environmental

Data Center Water Permits: There Is No Federal Permit — and That's Exactly Why Siting Teams Get Blindsided

No single federal permit governs data center water use. State laws, groundwater districts, and cooling design now decide whether your site gets water.

by iSi Environmental

If you are siting a data center and your permitting checklist has a line that says “federal water permit,” delete it. No such permit exists. Water supply for a data center is governed by state water law — prior-appropriation rights and groundwater district permits across the plains and the West, riparian and registration regimes further east — plus the local utility’s willingness to sign a will-serve letter. That is precisely why siting teams get blindsided: there is no single agency, no single application, and no single answer that covers your second site the way it covered your first. And during the 2026 legislative sessions, the state layer moved fast — at least 30 bills in 16 states targeted data center water use, and four states enacted laws (MultiState legislative tracker).

Here is the actual permit map, what changed in 2026, and how to screen a site before you option the land.

Is There a Federal Permit for Data Center Water Use?

No. Water quantity is state jurisdiction. The federal hooks are real but indirect: an NPDES permit (or the state-equivalent program) under the Clean Water Act for cooling-tower blowdown discharge, and construction stormwater permitting during the build. Neither one controls how much water you can withdraw or buy — that question belongs to the state engineer, the groundwater district, or the utility, depending on where you are standing.

This structure has a practical consequence. A developer who cleared water supply in one state has learned almost nothing transferable about the next state. In prior-appropriation states — Kansas, Colorado, Idaho, Utah, and Texas groundwater districts — a new high-volume consumptive use generally requires a new appropriation or permit from a system that is often fully or over-appropriated. In those basins, water availability, not regulation, is the first gate. The permit can be denied not because your project is disfavored but because the water is already spoken for.

Which States Enacted Data Center Water Laws in 2026?

Four states enacted laws this session, and they do not point in the same direction:

  • Idaho H 895 — new data centers must use non-consumptive cooling designs or take municipal/district-supplied water. The law applies to data centers built on or after July 1, 2026 (Idaho Capital Sun coverage; primary text at the Idaho Legislature, H 895).
  • Utah HB 76 (Data Center Water Transparency Amendments) — large data centers must disclose projected and actual water use, notify local water providers, and file pre-construction and annual operational reports (Utah Legislature, HB 76).
  • South Dakota SB 135 — utility-cost and shortage protections for residents, and clarified regulatory authority over data centers (South Dakota Legislature, SB 135).
  • West Virginia HB 4983 — a recruitment bill, not a restriction: a “High Impact Data Center” program with project confidentiality, which passed the Senate 28–6 on March 11, 2026 (West Virginia Legislature, HB 4983).

Read those four together and the pattern is not “states are cracking down.” The policy direction is bifurcating: some states are building transparency and design mandates, others are building confidentiality shields to win the projects. Roughly 25 more bills remain pending across the country (MultiState tracker). For a siting team, that means the incentive package and the water restriction can come out of the same statehouse — sometimes in the same session.

What Is Kansas Doing About Data Center Water — Recruiting or Restricting?

Both, simultaneously, and that split-screen is the clearest version of the national pattern.

Kansas enacted SB 98, a 20-year sales-tax exemption for data centers that carries water-restriction conditions (Kansas Dept. of Commerce fact sheet). The same legislature is now considering SB 400, which would require closed-loop cooling systems for data centers and authorize municipalities, district attorneys, and the state attorney general to seek injunctions against violators (Kansas Legislature, SB 400). SB 400 is pending — not enacted as of this writing — but a developer committing to evaporative cooling in Kansas right now is betting against a live bill with an injunction remedy attached. For an operating data center, an injunction against your cooling system is not a fine you absorb. It is a shutdown order.

The statute is only half the Kansas picture. The other half is older and harder: appropriation availability. Kansas groundwater runs through five Groundwater Management Districts (GMDs), and the Ogallala-area districts are heavily appropriated. A site inside one of those districts needs a water-availability answer from the Division of Water Resources before the incentive math means anything. The 20-year tax exemption is worth nothing on a quarter-section with no appropriable water.

Can a Texas Groundwater District Deny a Data Center Water Permit?

Yes — and districts have. Texas has no statewide data center water statute yet. The permitting reality is the groundwater conservation district (GCD) layer: the district where your well sits writes the rules, and districts have denied permits and explored moratoriums on high-volume users. On April 16, 2026, the Blanco-Pedernales GCD passed a resolution calling on the legislature for clarity on industrial water rights as data center growth approaches (The Texan). That is a regulatory body asking for backup before the wave hits — a signal worth taking at face value.

The screening move is straightforward: identify the GCD before you option land (boundaries and contacts at the Texas Water Development Board), pull its management plan and high-volume permitting rules, and budget for contested-case timelines. A contested-case fight over a high-volume permit costs months of schedule and real legal spend; screening districts costs an afternoon. District denials are no longer theoretical, so the order of operations matters: GCD first, land second.

Will Closed-Loop Cooling Make the Water Permit Problem Go Away?

Possibly faster than legislation will. Two of the largest data center builders announced closed-loop designs — one with zero-water-evaporation cooling for upcoming facilities (Data Center Dynamics), and Oracle announced closed-loop cooling for its AI data centers in February 2026 (Oracle announcement). If the hyperscale design standard goes closed-loop, consumptive water use becomes a transitional problem for new builds — the industry engineering around the issue before most statehouses finish legislating it.

Two cautions before you bank on that:

  1. The trade-off is electricity. Closed-loop and mechanical chilling shift the load from the water meter to the power interconnection — the water-energy nexus does not disappear, it moves. In markets where the interconnection queue is already the binding constraint, “we solved water” can mean “we made power harder.”
  2. The design class is becoming the regulatory trigger. Idaho H 895 regulates by cooling design — non-consumptive or municipal supply (Idaho Capital Sun). Kansas SB 400 would do the same if enacted (Kansas Legislature). Your cooling design decision is no longer just an engineering and OPEX call — it determines which statutes apply to you and which permits you need. Make it first, on purpose, with the permit map in front of you.

How Reliable Is the Data Behind the Data Center Water Story?

Less reliable than the headlines suggest — and that cuts both ways in a siting decision.

The most-cited statistic in circulation is that roughly two-thirds of 809 planned U.S. AI data center projects sit in areas with existing water shortages. That figure is industry-press analysis, not government data (Tom’s Hardware) — useful as a directional signal, not as a basis for a board memo. Meanwhile, California — the state with arguably the strongest interest in the question — cannot currently quantify statewide data center water use (CalMatters, May 2026). California has proposed, but not enacted, legislation that would bar local approval of new or expanded data centers without water-use disclosure and prohibit development in overdrafted San Joaquin Valley groundwater basins absent state water-manager approval.

Even the new transparency laws will not fix the public data gap. Utah HB 76 collects detailed water-use filings and then treats them as protected records — only aggregated, anonymized information reaches the public (Utah Public Radio; HB 76 text). That is transparency to regulators, not to communities. For a developer, the operational read is this: regulators will increasingly know your numbers, the public will increasingly demand them, and the aggregate datasets everyone argues from will stay thin. Your site-specific water analysis has to stand on its own, because the public record will not carry it.

What Permits and Approvals Does a Data Center Water Supply Actually Require?

The real checklist, in the order the approvals bind you:

  1. Water supply authorization — a new appropriation or water right from the state, a groundwater district or GMD permit, or a municipal will-serve commitment. This is the long-lead, deniable item.
  2. The will-serve letter, if you take municipal supply. Municipal supply routes around most of the new state restrictions — Idaho H 895 expressly allows it — which makes utility negotiation the cheapest compliance strategy wherever capacity exists. Document the commitment; do not rely on a conversation.
  3. NPDES (or state-equivalent) discharge permit for cooling-tower blowdown. The discharge chemistry — TDS, biocides, anti-scalants — determines whether you pretreat to a POTW or permit a direct discharge. Start this early; the answer can change your site civil design.
  4. Construction stormwater permitting during the build.
  5. State-specific reporting obligations — in Utah, HB 76 pre-construction water-use reports and provider notification belong in the development schedule, not bolted on afterward (HB 76).

Enforcement under the 2026 statutes is too new to have a track record — no state enforcement action has surfaced yet under the four enacted laws. But the mechanisms are visible: Kansas SB 400’s remedy would be injunctive, Texas districts enforce through denial, curtailment, and civil penalties under district rules, and water-quality citizen litigation has already reached the sector — a $20.5 million nitrate settlement involving a major data center operator’s discharge has been reported in secondary press. The exposure is not a fixed penalty schedule. It is your operating permission.

How Should a Siting Team Screen a Site for Water Risk?

Six steps, in order:

  1. Classify your cooling design’s water profile first — consumptive evaporative, closed-loop, or air-cooled. Idaho H 895 and Kansas SB 400 both regulate by design class, and this single choice drives every downstream permit.
  2. In Kansas: screen the parcel against the five GMDs and confirm appropriation availability with DWR before optioning land. Track SB 400’s status before committing capital to evaporative cooling.
  3. In Texas: identify the GCD, pull its management plan and high-volume rules, and price the contested-case scenario into the schedule.
  4. In Utah: build HB 76 reporting and provider notification into the development timeline.
  5. Secure the blowdown discharge path early — POTW pretreatment versus direct NPDES discharge is a design-stage decision, not a commissioning-stage one.
  6. Paper the will-serve. Where municipal capacity exists, it is the cleanest route through the new state laws. Get the commitment in writing with volumes and term.

One deadline is already on the calendar: Idaho H 895 applies to data centers built on or after July 1, 2026 (Idaho Capital Sun). Everything else is moving — roughly 25 bills still pending in 2026 sessions — which means the screening you ran last quarter may not describe the state you are permitting in next quarter.

Where Does Environmental Due Diligence Fit in Data Center Siting?

Water is one gate in a siting decision that also turns on what is already in the ground. The same land-option timeline that should include a GCD or GMD screen should include a Phase I Environmental Site Assessment — because discovering a recognized environmental condition after you have committed to a site costs far more than finding it before. A permit hold or a late-discovered site condition can stall a build measured in months; at data center construction carrying costs, that delay dwarfs the cost of doing the diligence in the right order.

iSi Environmental is based in Wichita with a national footprint across 40 states — which puts us in the middle of the plains-state corridors where this build-out and these water fights are converging. We handle environmental permitting, water and NPDES discharge permitting support, and site due diligence including Phase I ESAs for industrial and large-footprint projects. If you are screening sites in Kansas, Texas, or anywhere the water question is now a siting gate, talk to us before you option the land.

Sources

Tags: