--- title: "How to Write a Data Center Site Requirements Brief | Insights | Build" description: "A data center site requirements brief states the megawatts you need and when, the minimum acreage, target markets, latency and fiber needs, cooling and water approach, zoning tolerance, deal structure, and budget for land. Writing it first turns a vague search into a ranked shortlist of sites that fit, and it gives every broker, utility, and consultant the same target." url: https://build.inc/insights/data-center-site-requirements-brief --- [Workflows](https://build.inc/insights?category=workflows) # How to Write a Data Center Site Requirements Brief A data center site requirements brief states the megawatts you need and when, the minimum acreage, target markets, latency and fiber needs, cooling and water approach, zoning tolerance, deal structure, and budget for land. Writing it first turns a vague search into a ranked shortlist of sites that fit, and it gives every broker, utility, and consultant the same target. by Build Team • November 4, 2026 • 5 min read A data center site requirements brief is a one-page document that tells everyone working on your search exactly what a site must have: how many megawatts by what date, how much usable land, which markets, what fiber and latency you need, how you will cool, what approvals you can tolerate, and how you want to hold the land. Write it before the search starts. Without it, teams collect sites that look good on a map and fail on power or timing. ## Who needs a requirements brief - **Neoclouds** that need GPU capacity live in a specific quarter and cannot wait on a long utility ramp - **Developer sites teams** sourcing land for powered shells, campuses, or build-to-suit deals - **Enterprise and AI tenants** comparing build, lease, or partner options - **Capital partners** that want a clear test for which sites are worth funding diligence on ## What goes in the brief Section What to state Example of a clear entry Power Megawatts needed at first energization and at full build, with dates First phase by a named quarter, full load by a later year Timing tolerance The latest acceptable date for first power Anything later than the target quarter is out Land Minimum usable acres after setbacks, wetlands, and easements Usable acres, not gross acres Markets Target states, utilities, or regions, plus any to avoid A short list of utilities, not just states Fiber and latency Carrier diversity, distance to key network hubs, latency limits Two diverse routes required Cooling and water Air, liquid, or hybrid design, and water use expectations Closed-loop design, low water use Approvals Whether you accept rezoning or special use permits By-right preferred, discretionary approval only with precedent Deal structure Purchase, option, ground lease, or joint venture Option with diligence milestones Budget Land budget range and who funds diligence and upgrades Who pays for utility studies and deposits Kill criteria Conditions that remove a site immediately No written utility response, active moratorium ## Decision rules for a good brief 1. **Lead with megawatts and dates.** Power timing filters out more sites than any other line in the brief. 2. **Use usable acres.** Gross acreage hides setbacks, wetlands, and easements that shrink the buildable area. 3. **Name utilities, not just states.** Power availability varies widely between utilities in the same state. 4. **State your approval tolerance.** A team that cannot wait on a discretionary vote should say so up front. 5. **Write the kill criteria down.** Agreed kill criteria stop debates about weak sites later. 6. **Keep it to one page.** If the brief is too long, the people sourcing for you will not use it. ## Common mistakes - Asking for "power" without megawatts and a date - Listing ideal conditions instead of minimums, which eliminates workable sites - Leaving out who pays for utility studies, deposits, and upgrades - Changing the brief mid-search without telling brokers and consultants - Treating latency and fiber as nice to have when tenants require them ## Requirements brief checklist - Megawatts at first energization and full build, with dates - Latest acceptable first power date - Minimum usable acreage - Target utilities and markets, plus exclusions - Fiber diversity and latency requirements - Cooling design and water expectations - Approval types you will accept - Preferred land structure and diligence period - Land budget and who funds studies and upgrades - Written kill criteria ## How Build helps Build turns a requirements brief into a sourced and validated shortlist. The client gets sites that meet the brief on deliverable power, land, fiber, water, and entitlements, ranked on what lands inside their window, with bundled services to take the chosen site from shortlist to usable land. If the first site stalls, Build sources the next one against the same brief. ## Key takeaways - A requirements brief gives every party in a site search the same target. - Megawatts by date, usable acres, and approval tolerance do most of the filtering. - Written kill criteria save weeks of debate over sites that will not close. ## Frequently Asked Questions: What is a data center site requirements brief? A short document that defines what a site must have before a search starts, including megawatts and dates, usable acreage, target markets, fiber and latency needs, cooling and water approach, approval tolerance, deal structure, and kill criteria. Why do neoclouds need a requirements brief? Neoclouds usually need capacity live by a specific date. A brief that leads with megawatts and a latest acceptable power date removes sites that cannot deliver in time before anyone spends on diligence. Should the brief use gross or usable acres? Usable acres. Setbacks, wetlands, floodplain, and easements can remove a large share of a parcel, so gross acreage overstates what can be built. How long should a requirements brief be? About one page. It should state minimums and kill criteria clearly enough that brokers, utilities, and consultants can apply it without a meeting. When should the brief be updated? When the tenant requirement, timing, or budget changes. Share each update with everyone sourcing sites so the search stays consistent. [Workflows ### Data Center Site Red Flags: 10 Reasons to Drop a Site Before LOI November 4, 2026](https://build.inc/insights/data-center-site-red-flags-before-loi)[Workflows ### Data Center Land Option Agreements: How to Hold a Site While Power Is Validated November 3, 2026](https://build.inc/insights/data-center-land-option-agreement-power-validation)[Workflows ### Floodplain and Wetlands Screening for Data Center Sites November 2, 2026](https://build.inc/insights/data-center-floodplain-wetlands-screening)