Short answer: A data center site selection RFP should ask providers how they prove power, not only how they find land. The questions that separate strong providers are about evidence: what sources they read, how they score deliverable capacity, how often they refresh findings, who verifies the output, and what you receive at the end. Ask for a sample site file with sources. This guide lists the questions to put in an RFP for AI site selection or site selection services, grouped by topic. It follows the Build order for data center site selection: sites, then validation, then bundled services.
What should the RFP include before the questions?
Your requirements. Providers can only answer well if you state target megawatts, energization date, markets, density, cooling preference, water limits and exclusions. Our guide to writing a site requirements brief covers the format.
Which questions should you ask?
Power
How do you separate available capacity from deliverable capacity, and what evidence level do you require before calling a site viable? See available vs deliverable capacity.
Which utility and grid operator documents do you read, and can you cite them per site?
How do you treat queue position? The IEA notes queues contain duplicative or speculative projects (IEA).
How do you track new large load rules? In PJM, for example, loads of 50 MW or more at one site are now defined as Large Loads (PJM filing).
Will you contact the utility, and at what stage?
Zoning and permitting
How do you confirm whether the use is by-right or needs a special use permit? See by-right zoning vs special use permits.
How do you monitor moratoriums and pending ordinance changes?
Do you screen wetlands, floodplain and airspace before shortlisting?
Water, fiber and land
How do you assess water availability for the cooling method we plan?
How do you confirm diverse fiber routes and lateral cost?
How do you check title, easements and mineral rights at the shortlist stage?
Method and verification
Which steps are automated and which are reviewed by a named expert?
How often do you refresh findings, and how do you flag what changed?
What is your error-handling process when a source conflicts with another?
Can we see a sample site file with every claim sourced?
Deliverables and handoff
What exactly do we receive: ranked list, site files, test fits, a decision memo?
Can you carry a passing site into design, permitting and preconstruction, or does work restart with a new team?
What happens if a shortlisted site fails validation?
How should you score the answers?
| Criterion | Strong answer | Weak answer |
|---|---|---|
| Power evidence | Evidence levels with sources per site | Distance to substation only |
| Verification | Named expert review of deciding facts | Model output without review |
| Freshness | Scheduled re-checks with change flags | One-time report |
| Permitting | Zoning path and moratorium watch per site | Zoning district label only |
| Handoff | One record carried into bundled services | Report ends at shortlist |
This rubric is Build's framing. For a fuller tool rubric, see our AI site selection tools scorecard, and for vendor categories see data center site selection software and AI data center site selection companies compared.
Which red flags should end the conversation?
No sources behind power claims.
Capacity quoted without a date.
No answer on how often findings are refreshed.
No expert named for verification.
A deliverable that stops at a map.
What does Build do?
Build is the development execution engine for infrastructure and data centers, built for quality and speed. We answer these questions with a sourced site file: sites first, then validation of power, zoning, water and fiber, then bundled services that carry a passing site into design and permitting. That is AI native development. See Build's site selection services.
Key takeaways
Put your requirements in the RFP so providers can answer against them.
Ask how providers prove deliverable power, verify output and refresh findings.
Request a sample site file with sources, and score answers on evidence, not volume.