What Makes Land Ready for a Data Center?
A useful site description explains what has been established, what remains conditional, and when the next decision is expected.
A large tract and a nearby power line can start a conversation. They do not finish the evaluation.
For anyone reading a data center site announcement, “ready” deserves a follow-up question: ready for what? A property ready for an initial review is different from a site ready to support a particular building, electrical load, and construction schedule.
A practical way to evaluate readiness is to separate the evidence into four questions: Can the intended use proceed? What can be built? How will it be served? What must happen next?
1. Establish the approval pathway
Start with the jurisdiction’s current rules and the property’s actual approval record. A broad description such as “industrial land” is not a substitute for identifying the applicable use and any conditions attached to it.
Loudoun County offers an instructive example of why timing matters. Its data center standards page describes changes approved in March 2025 and a grandfathering framework for certain earlier applications. The county cautions that outcomes depend on individual circumstances and that the controlling ordinance and resolution take precedence over its illustrative guide. [1]
The lesson extends beyond that county: state the specific approval, its date, its scope, and the work still required. Do not let “approved” stand alone.
2. Separate the parcel from the development plan
Ask for a clear accounting of the property. Which boundary does the acreage describe? Which area is proposed for buildings and equipment? Where are access, drainage, utility corridors, and buffers shown?
These are review questions, not a universal formula for developable acreage. The useful deliverable is a site-specific plan with its assumptions visible. A headline acreage number should not be asked to answer questions the underlying plan has not resolved.
3. Define the power and cooling requirements
Electrical readiness should describe a load and a schedule. Dominion Energy’s public guidance describes site-specific power planning and staged service as facilities increase their loads. It also identifies customer information such as a site plan, load letter, and load ramp schedule as part of the process. Those are utility-specific procedures, not a national service guarantee. [2]
Ask what the stated megawatts represent, which phase they serve, what infrastructure is contemplated, and what evidence supports the expected delivery date.
Cooling deserves the same precision. DOE’s federal data center guidance describes an evaporative cooling configuration and links its water requirements to heat loads and system efficiency. That example should not be treated as a water-demand assumption for every facility. [3] Identify the proposed design before discussing its water needs.
4. Put the dependencies on one timeline
For review purposes, organize each open item around a decision, an owner, and supporting evidence. An expected completion date is more useful when the reader can see what must happen before it.
A simple readiness statement might read: “The proposed use has received the specified local approval. The site layout remains under review. Initial electrical service is being evaluated for a defined phase. The full-build schedule remains conditional.” This is an illustrative reporting format, not a description of an NGLC property.
Precision makes the conversation more productive. It gives a developer something to evaluate, a community something to understand, and a reader a way to distinguish a promising location from a documented development opportunity.
Sources
[1] Loudoun County — Data Center Standards & Locations
Reviewed October 27, 2026. Primary source; follow the link to review the original.
[2] Dominion Energy — Data Center Requests
Reviewed October 27, 2026. Primary source; follow the link to review the original.
[3] U.S. DOE — Cooling Water Efficiency Opportunities for Federal Data Centers
Reviewed October 27, 2026. Primary source; follow the link to review the original.
Updates & corrections
No corrections recorded.
Related reading
Ready to Move?
We respond within one business day to developers, landowners, and community leaders.