BlogSite-owner offtake

AI Data Center Site Selection: Land and Grid Access Guide

A practical playbook for owners of land or facilities with unused grid capacity. Learn the criteria AI and GPU data center developers use to screen sites, how to self-score your own property, and what evidence to prepare before you reach out.

Picture a hypothetical owner of a former manufacturing plant. The production lines shut down years ago, but the substation on the property still has capacity the utility has kept in place. She hears that AI developers are hunting for powered sites, so she sends a short email to a dozen of them: “Large industrial site, lots of power, available now.” A few reply with questions she cannot answer. How much capacity is firm? Who owns the substation? Is the parcel zoned for this use? Where is the nearest fiber? The conversations stall.

Her site may be excellent. The problem is that developers screen hundreds of properties, and they move fastest on the ones that arrive with evidence. This guide walks through the criteria AI data center developers and tenants use in site selection, shows how to score your own property honestly, and lists the documents worth assembling before your first call.

1. Start with power you can prove

Power is the first filter in almost every AI data center site selection process. GPU systems draw heavy, steady loads, and developers care about two things: how much capacity exists on paper, and how much can actually be delivered to their equipment on a known schedule. Our primer on AI data center power requirements for site owners explains how these loads differ from typical commercial use. Gather answers to these questions:

  • What capacity is contracted or reserved with the utility today, and is it documented in writing?
  • Is that capacity firm, or can the utility interrupt or curtail it under certain conditions?
  • Who owns the substation, transformers, and switchgear on site, and what condition are they in?
  • What is the historical reliability of the feeding circuit, and is there any record of outages or congestion?
  • Is backup power, such as generators or batteries, already installed or permitted?

If you are unsure who controls the electrical assets, our guide on disclosing substation ownership and control shows how to document it clearly.

2. Document interconnection status and timeline to energization

Developers price time as heavily as capacity. A site that can energize soon is often worth more to them than a larger site that waits years for upgrades. Be precise about where you stand with the utility:

  • Is the site already interconnected at the needed capacity, or is an application pending in a queue?
  • Which studies have been completed, such as system impact or protection studies, and which remain?
  • What network upgrades has the utility identified, and who is expected to pay for them?
  • Are long-lead items like transformers already on site, on order, or still unspecified?
  • What is the realistic critical path from signed deal to energized load?

Our notes on disclosing interconnection queue status and transformer lead time give templates for presenting this information. To see how buyers weigh it, read how GPU offtake buyers screen unused interconnect sites.

3. Secure land control, zoning, and permitting

A developer needs confidence that the land is available, the use is allowed, and the permits are achievable. Gaps here can sink a deal late, after both sides have spent real effort. Confirm:

  • Do you own the parcel outright, or hold a lease or option? Are there liens, easements, or rights-of-way that limit use?
  • Is the parcel zoned for data center, industrial, or utility use, or would it need a rezoning or variance?
  • Which local, state, and environmental permits apply, including air permits for backup generators?
  • Are there wetlands, floodplain designations, or stormwater constraints on the buildable area?
  • Has the local planning office signaled any position on data center projects?

Our guides on land control and lease disclosure and permitting and zoning disclosure cover the documents developers usually request.

4. Map fiber, latency, water, and cooling

Once power and land pass, developers look at connectivity and cooling. Training clusters can tolerate more remote locations, while inference workloads serving users may need lower latency to population centers. Cooling approach shapes water needs and site layout. Prepare:

  • A map of nearby fiber routes, carriers, and any dark fiber, with approximate distance to the property line.
  • Whether diverse fiber paths can reach the site, so a single cut does not isolate it.
  • Available water sources, supply agreements, and any limits on withdrawal or discharge.
  • Whether existing buildings or pads can support liquid-cooled equipment, dry coolers, or other heat rejection.
  • Local noise limits that could affect cooling equipment placement.

Cooling designs vary by vendor and hardware generation, so treat specific requirements as something to confirm against the vendor’s published specifications. Factory-produced micro data centers, like the ones Pacific deploys, can reduce the need for heavy on-site construction. Reviewing Pacific’s GPU compute catalog shows the GPU systems tenants ask about. For details, see our notes on fiber and dark fiber and water makeup.

5. Assess climate, natural hazards, and community

Developers and their insurers want to know what could damage or delay the site, and how neighbors are likely to respond. Being upfront about known risks builds trust faster than hoping no one asks. Work through:

  • Flood, wildfire, seismic, hurricane, and severe storm exposure, with any official maps or elevation certificates.
  • Local climate conditions that affect cooling efficiency, such as sustained high heat or humidity.
  • Geotechnical conditions and groundwater, especially if new foundations are needed.
  • Who the key local stakeholders are: elected officials, economic development staff, neighbors, and community groups.
  • Any past or current opposition to industrial projects in the area, and what concerns were raised.

Our guides on flood and fire risk disclosure and community stakeholder status show how to summarize these factors honestly.

6. Understand your deal structure options

Owners often assume the only path is selling the land. In practice there are several structures, each with different risk, involvement, and upside. At a qualitative level, the common options include:

  • Outright sale of the land and electrical rights to a developer.
  • A ground lease, where you keep ownership and the developer builds and operates.
  • A powered land arrangement, where you supply the site and energy and a partner deploys equipment.
  • A joint venture or revenue share tied to the compute capacity deployed on the site.
  • Offtake-style agreements where a buyer commits to use capacity built on your property.

Have your attorney and financial advisor review any structure before you commit. Our overview of powered land for data centers compares these paths in more depth, and the GPU offtake brief for site owners explains how offtake buyers think about commitments.

7. Score your site and build the evidence pack

Before outreach, score each criterion as strong, workable, or a gap, and attach the document that supports your rating. Where you have a gap, write down what it would take to close it. Use this self-assessment checklist:

  • Power: capacity documented in writing, firmness confirmed, electrical asset ownership clear.
  • Interconnection: queue position or existing service documented, studies listed, upgrades identified.
  • Timeline: a realistic path to energization with long-lead items named.
  • Land control: deed, lease, or option on file, with easements and encumbrances listed.
  • Zoning and permits: current zoning confirmed, required permits identified, local contacts known.
  • Fiber: routes and carriers mapped, path diversity assessed.
  • Water and cooling: sources documented, constraints noted, noise limits checked.
  • Hazards: flood, fire, seismic, and storm exposure mapped, geotechnical data gathered.
  • Community: stakeholders identified, history of local sentiment summarized.
  • Deal structure: preferred options ranked, advisors engaged.

Package the results as a short site summary with an appendix of supporting documents. A site with honest gaps and a clear plan reads far better than one that overstates readiness. When you are ready to go further, our pillar on turning a powered site into an AI factory site covers what happens after a developer says yes.

To review your site’s score and evidence pack with Pacific Intelligent Technologies, Inc., book a site evaluation call. Bring your utility documents, a parcel map, and any studies or permits you already hold.

FAQ

What matters most in AI data center site selection?

Deliverable power on a known timeline usually comes first. Land control, permitting, and fiber follow closely. A site that documents all four clearly will get faster, more serious responses.

Do I need every study and permit before contacting developers?

No. Developers expect some open items. What helps is knowing which items are done, which are pending, and which have not started, with documents attached for anything complete.

Can a smaller site with unused power still attract interest?

Yes. Factory-produced micro data centers are designed for sites that cannot host a large campus. If your power is documented and the land is controlled, a modular deployment may be a good fit.

Continue on the mothership

This satellite stops at the playbook. Transactions, specs, and comparisons live on pacificmachines.com. If the next step is a human, book 30 minutes with Harper.

Book 30 min