Planner checklist

Data Center Site Selection Checklist for Planners in 2026

By AI Data Center Impact

A useful data center site selection checklist connects each requirement to evidence, an owner and a decision date. Start with load and schedule, test power and the local approval path early, then assess buildable land, fiber, water, hazards and site control. Run inexpensive checks in parallel so an obvious constraint does not wait behind a lengthy study.

Use Clear, Verify and Stop as internal workflow states—not certifications. Clear means the evidence meets your documented requirement at this stage. Verify means a material question is open. Stop means a confirmed constraint conflicts with the requirement and no acceptable remedy is identified. Sources reviewed November 9, 2026.

1. Fix the project requirements

  • Initial and ultimate campus MW, distinguishing IT load from total facility demand.
  • Phase dates, reliability requirements, cooling assumptions and workload needs.
  • Contiguous buildable area for buildings, equipment, circulation and expansion.
  • Latency destinations, carrier requirements and physical-route diversity.
  • Water, wastewater, fuel and emergency-access requirements.
  • Budget, acquisition structure and conditions that would end the review.

Do not change the requirement to make a preferred site appear stronger. If the project changes, version the assumptions and recheck every candidate. For the broader workflow, read the data center site selection guide.

2. Establish a power-service path

Identify the serving utility and request a response to the actual load ramp. Record required studies, service conditions, network upgrades, customer contributions and the assumptions behind each proposed date. A statement about regional growth or a nearby substation does not confirm spare capacity.

Generation interconnection queues and data center load-service processes are different. Ask which process applies and whether any indication is binding. A completed study may still leave agreements, capacity reservations, procurement and construction unresolved.

Clear: adequate evidence for the current decision stage and no schedule-conflicting unresolved condition. Verify: service, cost, upgrades or timing remain conditional. Stop: a confirmed service constraint conflicts with the required ramp and no acceptable alternative is established.

Use the power-first land diligence guide to document evidence strength and site-control dependencies.

3. Measure a usable layout, not just gross acreage

Start with a survey and constraints map. Evaluate setbacks, easements, drainage, flood exposure, wetlands, slope, access, fire lanes and construction staging. Reserve equipment yards and expansion space. The result must support a practical contiguous layout, not a sum of disconnected usable fragments.

Do not automatically subtract every mapped floodplain or wetland as legally unbuildable, or count it as freely usable. Determine jurisdiction, applicable rules, delineation needs and mitigation feasibility with qualified advisers. Public maps are screening inputs, not a substitute for a survey or civil design.

4. Verify fiber routes and delivery

Ask carriers for service availability, route evidence, construction requirements, permits, easements, delivery dates and pricing. Two carrier names do not prove two independent physical paths. Check shared conduits, bridges, rail crossings, exchanges and building entry points.

Evaluate latency on an actual or technically specified network path to the required destination. You cannot measure real network latency from an undeveloped coordinate alone. Keep proposed routes separate from contracted or operating routes.

5. Review zoning and affected neighbors

Confirm whether the proposed use is permitted, conditional or prohibited, and check accessory generation, fuel storage, substations, building dimensions and noise rules. Identify the approving authority and distinguish an application, staff recommendation, hearing vote and final order.

Review active moratoria, meeting records, public comments and project-specific concerns. Map nearby homes, schools, healthcare facilities and other sensitive uses to identify questions for specialist review. A receptor nearby is not proof of a violation; the absence of an organized campaign is not proof of public support.

Community objections are not an automatic Stop. Record the substantive issue, project response and outstanding decision. See the noise complaints guide for an evidence-based account of one common concern.

6. Test water, hazards and emergency access

Separate basin stress from supply authority and utility delivery. Document cooling assumptions, peak-day demand, drought restrictions, sewer capacity and treatment requirements. An advertised water line does not confirm industrial service.

Review flood, drainage, heat, severe weather, wildfire and seismic exposure as relevant to the location. Record the source, date, scenario and need for engineering review. Measure proximity to emergency facilities as context; straight-line distance does not establish response time, staffing, readiness or apparatus capability.

For construction stormwater, EPA describes regulated discharges from sites disturbing one acre or more, including qualifying smaller sites within a common development plan. Confirm jurisdiction and permit requirements with the responsible authority.

7. Connect title and site control to the diligence schedule

Review ownership, access, easements, exceptions, encumbrances and study rights. Have counsel align option or purchase terms with the utility and entitlement dependencies. Record who can waive a condition and what evidence is required before a deposit becomes non-refundable.

An inexpensive site can still be unsuitable. An attractive composite score cannot override a binding access, service or permitting constraint.

Use one comparison register

Apply the same requirements to every candidate
WorkstreamEvidence neededTypical Verify item
PowerUtility response, studies, conditions and phased scheduleUpgrade funding or service milestone unresolved
LandSurvey, title and preliminary usable layoutEasement or drainage issue needs review
FiberPhysical-route and delivery evidenceSecond route is proposed, not committed
Approval and communityCurrent rules, project records and affected-use reviewHearing conditions or mitigation unresolved
Water and hazardsSupply evidence and appropriate specialist assessmentsPeak demand or mitigation scope unconfirmed
Site controlReviewed terms, rights and milestonesControl period ends before a critical study

For every Verify item, name an owner, the missing evidence, a due date and the decision it blocks. Do not rank sites solely by the number of open questions: one unresolved utility condition may matter more than several minor documentation tasks.

Where a Site Viability Scorecard fits

AI Data Center Impact organizes sourced site-screening evidence. The overall Site Viability Score is higher-is-better; individual exposure measures may use a different direction. Supplemental Emergency Response, Labor and sensitive-receptor context must not be presented as additional independently weighted composite dimensions or as proof of readiness.

Receptor screening is a trigger for diligence, not acoustic modeling or permit compliance. Grid proximity is not a queue position or capacity commitment. A separate Community Engagement Playbook supports engagement planning; a score does not establish consent. Confirm current scope and pricing before purchase.

Frequently asked questions

How do AI workloads change the checklist?

They can change load density, cooling, reliability and network requirements. Use the actual design assumptions rather than a generic AI-versus-enterprise multiplier.

How long does interconnection take?

There is no universal duration. Obtain a project-specific service process and conditional schedule from the utility; generic equipment averages do not establish your delivery date.

Does a good score clear a site?

No. A screen organizes questions. The decision still depends on project-specific utility, legal, environmental and engineering evidence.

Continue with the infrastructure risk assessment workflow to assign ownership and track unresolved dependencies.