How to screen data center candidate sites for water stress, grid capacity and local regulatory exposure quickly

1. Start with consistent site and project inputs

Create one candidate record per site with a stable identifier, a validated location, jurisdiction, development stage and source for the location. Separate a parcel coordinate from an approximate town, address or campus point. An early map search can identify an area of interest; it does not establish title, parcel boundaries or the availability of land.

Keep the assumed project consistent across the comparison: intended electrical load, initial and ultimate demand, ramp schedule, cooling concept, expected water use, backup-generation concept and target dates. Label these as planning assumptions until confirmed. Two sites screened against different loads or cooling assumptions are not an equivalent comparison.

State the decision being made and the review date. A shortlist for further study needs a different evidence depth from a later land or development commitment. Give each open question an owner, so a fast screen creates an actionable work list rather than a collection of disconnected maps.

2. Read water stress as context, not a supply commitment

Start with the location and geographic scale of the water evidence. WRI describes baseline water stress as water use relative to naturally available water, which helps identify competition for the resource. Its indicator guidance also calls this a big-picture view: local conditions can vary, and the baseline indicator does not account for water quality or environmental needs.

Keep baseline stress, drought, groundwater conditions and project demand as different questions. A historical or modeled regional indicator is not a live measurement at the parcel, an industrial water right, a permitted withdrawal or a guarantee of reliable service. Record the source vintage and whether the evidence describes a watershed, aquifer, county or a specific service arrangement.

Ask the water provider and qualified reviewers about the proposed cooling design, demand assumptions, potable or reclaimed supply options, seasonal restrictions, treatment, discharge and any applicable rights or allocations. Preserve written project-specific responses with their dates and conditions. Do not assume that low regional stress means the requested service is available, or that a cooling label alone establishes actual demand.

Use the first screen to identify which questions need deeper water diligence. Missing evidence on supply, rights or service remains unknown. It should not become a favorable entry in the candidate table simply because the map is quiet or a regional indicator looks better than another location.

Source: WRI: Aqueduct Water Risk Indicators

3. Separate nearby grid assets from deliverable capacity

Nearby substations, transmission lines and power plants can help frame an initial utility conversation. They do not establish the serving utility, available or deliverable capacity, an accepted load-service request, a queue position, required upgrades or time to power. A plant’s generating capacity is not spare electrical capacity allocated to your proposed site.

Confirm the relevant service provider and the process for the requested load. Supply the proposed location, demand, ramp schedule and timing rather than asking only whether a substation is nearby. Dominion Energy’s published data center load letter, for example, requests electrical-load details and a load ramp-up schedule. It illustrates project-specific inputs, not a nationwide service rule or an offer of capacity.

Keep a generator interconnection queue, transmission-service request and large-load service request separate. A position in one process does not demonstrate a position in another. Record the actual request type, utility or operator, project reference, date and current status where verified; otherwise leave those fields unknown.

Collect the applicable written utility assessment, study results, upgrade assumptions, dependencies, costs and service terms through the proper process. A preliminary discussion and a binding service arrangement are different evidence. A proximity-based grid screen must remain labeled as screening until the relevant project-specific facts are confirmed.

Source: Dominion Energy: Data Center Load Letter

4. Check local regulatory exposure against the actual proposal

Identify the jurisdiction and current land-use classification, then review the adopted zoning text, map, comprehensive plan and application requirements with local staff and counsel. Confirm how the proposed use and project design would be reviewed. An administrative approval path, special or conditional use, rezoning and another discretionary process are not interchangeable.

Distinguish an adopted ordinance, a proposed amendment, a bill, a staff recommendation and an approval condition. Record effective dates and the application or parcel to which the evidence relates. A state-level legislative signal or county summary can prompt review, but it does not by itself establish the legal requirements for this project.

Ask qualified reviewers to identify applicable water, wastewater, stormwater, air, backup-generation, building and other requirements. Applicability depends on the activity, design, discharge and responsible authority. EPA’s NPDES basics explains that the destination and character of a discharge matter and directs users to the permitting authority. Do not treat that general guidance as a conclusion that every candidate needs the same permit.

Keep disclosure frameworks separate from development permissions. A reference to IFRS S2, ESRS E3, SB 253 or SB 261 provides context; it does not establish that a particular entity is in scope or that a parcel is permitted. Record the questions counsel must resolve rather than presenting a general framework as a site approval.

Source: EPA: NPDES Permit Basics

5. Compare the evidence before comparing the candidates

Use a compact comparison record with a row for each site and separate entries for water, grid and local rules. For each entry, preserve the finding, source, date, geographic scale, coverage limit, confidence or verification status, open question and responsible reviewer. This is a recommended review format, not a claim that the product automatically fills every field.

Compare findings only when the project assumptions and source definitions are compatible. A current project-specific letter should not be treated as equivalent to an old regional map. A county indicator displayed at a site coordinate remains county evidence. Mark differences in coverage and vintage so apparent precision does not conceal an unequal comparison.

Keep layer-level findings alongside any overall score. A summary can help organize attention, but it cannot replace a missing service fact or a governing requirement. Explain why a candidate needs a follow-up rather than turning every unknown into a single favorable or unfavorable label.

6. Work quickly by separating screening from confirmation

Begin with the same minimum input record for every candidate, then review the available source-backed water, grid and regulatory context. Capture obvious mismatches, coverage gaps and unresolved material questions immediately. This prevents repeated research on a candidate whose basic location or proposed load is still unclear.

Prepare focused questions for specialists instead of requesting an undirected study. A utility inquiry should identify the requested load and ramp. A water inquiry should describe the cooling concept and demand assumptions. A planning inquiry should identify the parcel, intended use and decision path that needs confirmation.

A fast initial screen does not mean instant utility studies, engineering conclusions or permitting answers. Set review depth according to the next decision and the material unknowns. There is no universal screening duration or safe shortcut around the service provider’s, engineer’s or authority’s work.

7. Use the Site Viability Scorecard within its actual scope

AI Data Center Impact’s Site Viability Scorecard screens one U.S. site using available climate and water, nearby grid, Community Fit and permit context, with sources and limitations. It helps organize early questions across these layers. It is not an engineering feasibility study, legal conclusion, water-service commitment or confirmation of electrical capacity.

Emergency-response capacity, sensitive-receptor and noise screening, and construction workforce context are supplemental signals where available. They are not additions to the composite viability score or compliance certificate. A nearby receptor can trigger further diligence; it does not establish modeled noise levels or compliance with a local standard.

A mapped or pre-screened candidate inventory is a starting point for exploration, not an exhaustive catalog of development-ready parcels. Membership does not establish land availability, title, utility service or approval. Apply consistent assumptions and verify the precise location of the actual candidate before relying on a site-specific report.

Choose the agreed scope for the decision. A single-site scorecard, separately scoped Community Engagement Playbook and analyst-assisted diligence engagement have different jobs and deliverables. Check current pricing and evidence coverage before purchase. This guide does not promise automatic collection of every utility letter, application, right, study or record it recommends reviewing.

8. Keep community questions alongside the technical screen

Water use, generation, infrastructure works and land-use changes may also be topics of public discussion. Review dated, project-linked comments and the actual decision process rather than inferring people’s views from a regional score or demographic profile. Community Readiness and Community Fit describe documented context, not community consent.

Separate an observed statement or public event from a broad civic indicator, an organization’s position and an adopted government decision. Neither a large contact list nor an absence of comments establishes trust, influence or support. Missing participation evidence remains a gap to investigate, not a favorable result.

If engagement work is needed, use the separate before-capital Community Fit guide to plan participation, identify the questions that input can affect and preserve differing views. Technical follow-up and direct participation should inform each other, but neither substitutes for the other.

9. Document the next decision and refresh the shortlist

Bring the candidate comparison into a decision record showing the proposal reviewed, source dates, relevant process, material unknowns and next actions. Identify who can resolve each question and what evidence would change the decision. Advancing for further study is not the same as declaring a site ready for construction or capital commitment.

Refresh when the location, applicant, demand, cooling assumptions, schedule, service facts or governing requirements change, and before a later commitment relies on the earlier screen. Preserve the dated record used at each decision so later documents are not mistaken for evidence that was available earlier.

Confirm critical questions with the utility, water provider, engineers, planners and counsel before the commitment that relies on their answers. Keep missing information visible and preserve conditions on written responses. Screening is useful because it directs that work, not because it removes the need for it.

Quick candidate-screening checklist

• Validate the location and jurisdiction; distinguish parcel evidence from approximate points.
• Use consistent load, ramp, cooling, water-demand and timing assumptions.
• Record water-stress context separately from supply, rights and service confirmation.
• Label nearby grid assets as proximity evidence, not available megawatts.
• Verify service provider, request type and utility evidence where available.
• Distinguish adopted local rules, proposed changes and project-specific conditions.
• Keep sources, dates, evidence scale and gaps beside each finding.
• Assign material questions to qualified reviewers before advancing the decision.

Frequently asked questions

Sources and review date

Reviewed 2026-10-08.

• WRI: Aqueduct Water Risk Indicators

  Definitions and limitations of regional indicators; baseline water stress is not a parcel-level service assessment.

• Dominion Energy: Data Center Load Letter

  An example of utility-requested load and ramp inputs, not a nationwide rule, study result or capacity commitment.

• EPA: NPDES Permit Basics

  General discharge-permitting guidance; project applicability must be checked with the responsible authority.

Scope and limits

Written by AI Data Center Impact, the provider of the scorecard discussed here. This educational guide is not independent product validation, legal advice, engineering feasibility, confirmation of water or electrical service, or a permit conclusion. External sources support the specific screening distinctions described, not our product or scoring model. Recommended review steps are not a promise of automatic product collection or a guaranteed turnaround. Sources reviewed October 8, 2026.