--- title: "Data Center Site Red Flags: 10 Reasons to Drop a Site Before LOI | Insights | Build" description: "Drop a data center site before LOI when power has no written path to your megawatts and date, the zoning path depends on a discretionary vote you cannot win, the usable acreage is smaller than the plan needs, or title, water, or fiber issues cannot be fixed inside your schedule. Kill early, document why, and replace the site from the same search." url: https://build.inc/insights/data-center-site-red-flags-before-loi --- [Workflows](https://build.inc/insights?category=workflows) # Data Center Site Red Flags: 10 Reasons to Drop a Site Before LOI Drop a data center site before LOI when power has no written path to your megawatts and date, the zoning path depends on a discretionary vote you cannot win, the usable acreage is smaller than the plan needs, or title, water, or fiber issues cannot be fixed inside your schedule. Kill early, document why, and replace the site from the same search. by Build Team • November 4, 2026 • 6 min read Drop a data center site before LOI when any of these is true: the utility cannot show a written path to your megawatts by your date, the zoning path depends on a discretionary approval the community is likely to oppose, the usable acreage is too small once setbacks and wetlands come out, or a title, water, or fiber problem cannot be fixed inside your schedule. Killing a weak site early is cheaper than carrying it through diligence, and the best replacement usually comes from the same search. ## What a red flag is A red flag is a site condition that either cannot be fixed or cannot be fixed within the time and budget the project allows. It is different from a diligence item, which is a question you still need to answer. A good pre-LOI screen separates the two so the team spends money only on sites that can still close. ## The 10 red flags # Red flag Why it kills the site What would change the answer 1 No written utility response, only verbal comfort Unwritten power cannot be underwritten A written service response with megawatts and dates 2 First energization lands after the tenant's window Power arrives too late to support the lease A ramp schedule with an earlier first tranche 3 Required upgrades have no owner or cost estimate Delay and cost risk are open-ended Utility study naming upgrades, timing, and cost responsibility 4 Zoning requires a discretionary approval with visible local opposition Approval risk is high and timing is unknown A by-right path or a clear record of similar approvals nearby 5 Usable acreage falls short after setbacks, easements, wetlands, and floodplain The building and substation do not fit A revised site plan or an adjacent parcel under control 6 Title shows unresolved easements or reservations across the buildable area Can block construction or financing A title cure plan the seller will fund before closing 7 No realistic fiber path within budget Tenants will not sign without diverse connectivity Carrier quotes or a lateral plan with cost and timing 8 Water supply or discharge is unavailable for the cooling design Forces a redesign or kills the permit A cooling approach that fits local water, confirmed with the provider 9 A local moratorium or pending ordinance covers the parcel Rules can change before you file Confirmed grandfathering or a parcel outside the affected area 10 Seller will not grant enough time for power and zoning diligence You would commit capital before key answers exist An option or extended diligence period tied to milestones ## Decision rules 1. **Power first.** If red flags 1 to 3 are present and cannot be cleared quickly, stop. No other strength makes up for power that will not arrive. 2. **Separate fixable from fatal.** A fixable issue needs an owner, a cost, and a date. If you cannot name all three, treat it as fatal for this deal. 3. **Count combined delay, not single items.** Two moderate delays on the critical path can be worse than one large one. 4. **Kill in writing.** Record why each site was dropped so the team does not revisit it and the next search avoids the same pattern. 5. **Replace from the same search.** A dropped site is a signal to promote the next ranked site, not to restart sourcing. ## Pre-LOI screen checklist - Utility contact identified and written response requested - Megawatts by date compared against the tenant or end user requirement - Zoning district, permitted uses, and approval type confirmed - Wetlands, floodplain, and easement overlay on the parcel boundary - Preliminary title review for the buildable area - Fiber routes and nearest carrier facilities mapped - Water and wastewater provider capacity confirmed for the cooling plan - Local moratoriums and pending ordinances checked - Seller's view on diligence time and option structure ## How Build helps Build sources data center sites and validates them against these red flags before your team spends on legal and engineering. The client gets a shortlist of validated powered sites, a written record of why others were dropped, and bundled services to move the chosen site from shortlist to usable land. When a deal stalls on a red flag, Build brings the next site. ## Key takeaways - A red flag is a problem you cannot fix within the project's time or budget, not an open question. - Power, zoning approval type, and usable acreage decide most pre-LOI kills. - Drop weak sites early, document why, and promote the next site from the same search. ## Frequently Asked Questions: What is a red flag in data center site selection? A condition that cannot be fixed, or cannot be fixed within the project's schedule and budget, such as no written path to power by the required date or a zoning approval that is unlikely to pass. What is the most common reason to drop a data center site before LOI? Power. If the utility cannot provide a written response showing enough megawatts by the tenant's date, the site cannot be underwritten no matter how good the land is. How is a red flag different from a diligence item? A diligence item is an open question you still need to answer. A red flag is an answer you already have that makes the site unworkable for this deal. Should a moratorium automatically kill a site? Not always. Check whether the parcel is covered, whether projects already in process are grandfathered, and when the moratorium ends. If none of those help your timeline, drop the site. What should happen after a site is dropped? Record the reason in writing and promote the next ranked site from the same search instead of restarting sourcing. [Workflows ### How to Write a Data Center Site Requirements Brief November 4, 2026](https://build.inc/insights/data-center-site-requirements-brief)[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)