Water Availability Is Only the First Water Question in Data Center Site Selection

The rapid expansion of hyperscale and AI-driven data centers is evolving how developers evaluate site viability across the United States. Power availability still dominates early conversations, but water is becoming an equally important constraint, especially as data center development expands into smaller, more environmentally sensitive rural watersheds.

For many developers, the first water-related question is straightforward: Is enough water available to support cooling demand and operations?

But that’s only the first question to ask. A site with access to water does not automatically translate into a feasible site for long-term operations.

For decades, many large industrial facilities operated near urban waterways already shaped by heavy industrial use and modified hydrology. Today’s data center projects increasingly target more rural areas where streams, wetlands and aquatic habitats support increased biodiversity, protected species and more stringent water quality standards. That shift changes the permitting landscape significantly.

Developers increasingly need to evaluate water intake, use, discharge, natural resources and community expectations together. The projects that move most efficiently through permitting are often the ones that begin environmental due diligence before site acquisition is finalized, not after engineering assumptions are already in place.

These questions influence far more than utility planning. They shape permitting timelines, cooling system design, operational flexibility and long-term development risk.

Large hyperscale campuses may withdraw millions of gallons of water per day depending on cooling design, climate conditions and future buildout phases. Regulators and communities are evaluating those withdrawals more closely, particularly during drought conditions or in watersheds with limited flow capacity.

Developers that evaluate intake and discharge together early in site selection can identify permitting constraints before major engineering decisions become costly to revise.

Most data centers draw water from the local municipal drinking water utility. Some facilities, however, use water intake structures to withdraw water directly from nearby water bodies, particularly when a campus includes power generation or water and wastewater treatment infrastructure. In these cases, water withdrawal permitting has become increasingly complex because regulators are evaluating not only the volume of water withdrawn, but also the broader effects on watersheds and aquatic ecosystems.

Large intake volumes from freshwater sources can trigger a federal nexus with overlapping federal and state reviews involving water use permitting, wetlands, stream impacts and endangered species consultation. Intake structures themselves may affect fish passage, entrainment of freshwater mussels and other sensitive aquatic species depending on intake location, flow conditions and screen design.

Each additional review requirement can affect permitting timelines, infrastructure costs and overall site viability.

Low-flow conditions also matter. During seasonal drought or reduced stream flow, regulators may evaluate whether withdrawals could affect downstream water users, habitat quality or ambient water temperature.

In some cases, developers may need to consider alternative strategies such as cooling towers, reclaimed water systems or groundwater withdrawals. Those alternatives can reduce permitting pressure in certain watersheds, but they often introduce substantial capital and operational costs that may not have been part of the original data center design.

Cooling-system blowdown water may require permits or treatment before discharge due to the chemical contaminants. Even so, thermal discharge often presents the most technically complex permitting challenge for water-cooled data centers.

Under Section 316(a) of the Clean Water Act, heat is regulated as a pollutant. Developers must demonstrate that thermal discharges will continue to protect balanced native populations of aquatic life within the receiving waterbody.

That process requires far more than a standard discharge application. Thermal studies and hydrodynamic modeling evaluate how discharged water mixes under varying flow conditions and temperatures within the receiving stream. Regulators also require detailed field studies to understand how temperature changes could affect aquatic communities, sensitive species and habitat conditions throughout the year.

The complexity and required time of these studies can surprise project teams that have not previously managed industrial water permitting at this scale.

Field studies may require seasonal biological surveys, baseline water quality characterization and aquatic habitat assessments that cannot be completed on demand. Missing a seasonal survey window can create schedule impacts that extend well beyond a typical construction planning cycle.

Engineering decisions made early in project design can significantly reduce permitting risk later. Cooling system selection, intake location, discharge configuration and diffuser design all influence thermal performance and regulatory review.

Projects that integrate environmental permitting and engineering strategy from the beginning often maintain greater flexibility as site conditions and regulatory expectations evolve.

Freshwater mussels, wetlands, federally listed bats and other protected species can trigger extensive environmental review requirements, including Section 7 consultation with the U.S. Fish and Wildlife Service. In some situations, natural resources permitting and consultation can extend project timelines by up to 24 months.

Representative Important Species (specific organisms selected by regulators to serve as proxies for the health of an ecosystem in a particular area) of fish and benthic macroinvertebrates can trigger yearlong aquatic inventories for comparison to thermal variances for different life stages of aquatic biota. These studies take time to complete, evaluate and report data and ultimately negotiate with regulatory agencies.

Many of these requirements depend on seasonal survey windows.

For example, mussel surveys, bat habitat assessments and wetland delineations often require field work during specific times of year. If a project misses those windows, developers may need to wait months before collecting the data necessary to continue permitting.

That reality creates a significant challenge for projects operating under aggressive development schedules. Environmental due diligence should begin before land acquisition is finalized, particularly for sites near high-quality streams, jurisdictional wetlands or known habitats for threatened and endangered species. Early desktop feasibility studies can help developers identify potential permitting constraints before site control decisions limit alternatives.

One of the most common causes of avoidable delay is treating environmental permitting as a series of isolated workstreams.

In practice, NPDES permitting, water withdrawal approvals, wetlands permitting, endangered species consultation and other federal and state reviews often overlap and trigger a broader federal nexus. Each process can influence the timing and technical requirements of the others.

Sequential permitting strategies rarely align with the speed-to-market expectations associated with modern data center development.

Successful projects coordinate environmental studies, engineering design and permitting strategy in parallel. Early coordination between aquatic ecologists, permitting specialists, engineers and regulatory agencies helps teams identify technical issues sooner and avoid redesigns later in the process.

That coordination becomes especially important for multi-phase developments where future buildout assumptions may influence current permitting decisions.

Public perception is directly influencing how communities respond to data center development. Communities may support the economic benefits associated with digital infrastructure, but many also want clearer answers about long-term water use, aquatic impacts and sustainability commitments.

Questions focus on:

• Impacts to rivers and streams
• Groundwater withdrawals
• Drought resilience
• Effects on aquatic life
• Long-term operational sustainability

Developers that communicate clearly and transparently about water management strategies can build stronger credibility with regulators, local stakeholders and elected officials.

That credibility matters when projects require complex permitting decisions, infrastructure investment or long-term operational commitments within smaller communities.

Before committing to a site, we recommend that developers evaluate several interconnected environmental and permitting considerations:

• Water intake feasibility
• Receiving stream quality and designated use classification
• Threatened and endangered species presence or absence
• Wetlands and jurisdictional waters
• Thermal discharge constraints
• Cooling technology alternatives
• Permit sequencing and schedule risks

Developers that build a water permitting matrix during early site evaluation can compare locations more effectively before major capital commitments occur.

That process helps teams understand not only whether water is available, but whether the site can realistically support long-term operations within the project schedule and regulatory environment.

As data center development accelerates, water strategy is inseparable from site strategy.

The projects that move forward most efficiently increasingly treat water intake, discharge, aquatic ecology and permitting risk as core development considerations from the beginning of the project lifecycle, not as downstream compliance issues to solve later.