In short
A contractor building an AI data center who runs into bad soil, hidden utilities, or other physical surprises that the contract did not disclose can often get more time and money, provided the contract has a differing site conditions clause and the contractor gives prompt written notice. Most standard construction contracts include such a clause. The federal clause, FAR 52.236-2, and the private clause, AIA A201-2017 section 3.7.4, both place that risk on the owner for two kinds of surprises, including conditions that do not match the contract documents, and conditions that are simply not normal for that kind of work. 48 C.F.R. § 52.236-2, AIA I’ll walk through what counts as a differing site condition, how the major contract forms handle it, what the century-old Spearin doctrine adds, and why the compressed timelines and performance pressure of AI data centers make these disputes especially expensive.
What is a differing site condition?
A differing site condition is a physical condition at the job site that is not what the contract documents led the contractor to expect. It could be bad soil, hidden rock, buried debris, or anything underground or concealed that makes the work harder or more expensive than the contractor priced. When the contract has a clause that addresses these surprises, the contractor can ask for an equitable adjustment. That is a change to the contract price or the schedule, or both, to account for the extra cost and delay.
The idea is not new. The federal government adopted its first differing site conditions clause in 1927. Before that, contractors had to guess at what was under the ground and inflate their bids to cover the risk. By agreeing to absorb some of that risk itself, the government got lower bids overall. ABA Construction Lawyer
If a contract has no DSC clause, the opposite rule applies. Under the common law doctrine of sanctity of contract, the contractor bears the risk of unknown physical conditions. The Supreme Court stated this in Dermott v. Jones, 69 U.S. 1 (1864). The only exceptions are if the owner lied about the site or broke an implied warranty. So on any private project, the first question is whether the contract includes a DSC clause at all, and whether it has been struck out. If the parties delete the clause, courts have held that the risk stays on the contractor.
Where do the standard contract clauses come from?
The federal government’s clause is now called FAR 52.236-2. It has been mandatory since 1984 for any fixed-price construction contract above the simplified acquisition threshold, currently $250,000. The regulation itself requires it. FAR 36.502, 48 C.F.R. § 52.236-2
In the private sector, a widely used differing site conditions clause is found in AIA Document A201-2017, Section 3.7.4. The AIA publishes the family of form contracts that architects and owners commonly use. AIA
Other industry groups have their own versions. ConsensusDocs 200 uses Section 3.16.2. ConsensusDocs Guidebook The Engineers Joint Contract Documents Committee, or EJCDC, uses C-700 Section 5.04. Law Explorer And the Design-Build Institute of America, DBIA, uses Document No. 535, Section 4.2.2. Law Explorer All of these clauses are structured similarly. They define two main categories of surprise conditions, known as Type I and Type II, and they require the contractor to give prompt notice.
What are the three types of differing site conditions?
Construction lawyers and claims consultants group these surprises into three types. Understanding the type tells the contractor what it must prove.
| Type | Description | Example | What the contractor must show |
|---|---|---|---|
| Type I | The actual physical condition is materially different from what the contract documents indicated. | The owner’s soils report said the ground was dense sand, but the contractor hit a layer of soft clay that cannot support the foundation. | The contractor must prove it reasonably interpreted the contract documents as making a representation about the site, the actual conditions were not reasonably foreseeable from outside information, the contractor relied on the representation, and the difference caused extra cost or time. |
| Type II | The condition is physically unusual and not something a reasonable contractor would expect in that location and type of work. The owner made no particular representation. | A buried river channel in an area where no such channels have been recorded. | The contractor must prove the condition was unknown and unusual, and that it differed materially from what is ordinarily encountered. This is harder than Type I. |
| Type III | Hazardous materials or contamination that was not disclosed in the contract. | Buried drums of industrial solvent, asbestos, or contaminated soil. | Not all standard forms mention Type III, but many public agency contracts do. The risk is usually assigned to the owner regardless. |
Type I in more detail
Type I is the stronger claim because the owner made an affirmative statement about the ground. Under federal law, the contractor must meet four elements, namely (1) a reasonable contractor reading the whole contract would think the documents made a promise about the site. (2) The actual site conditions were not reasonably foreseeable to the contractor based on information available outside the contract documents. (3) The contractor actually relied on that contract representation when bidding. And (4) the condition differed materially and that difference caused the extra cost and delay. Law firm analysis
Type II in more detail
Type II covers the genuinely freakish find. Because the owner never said anything, the contractor has to show the condition was not only unexpected but also unusually different from what contractors normally deal with in that kind of work and in that region. This is harder to prove, and contract language about site investigation duties (like FAR 52.236-3 or equivalent) can make it more difficult. 48 C.F.R. § 52.236-3, Government contracts analysis
What does the Spearin doctrine add?
The Spearin doctrine is a separate rule from a 1918 Supreme Court case, United States v. Spearin, 248 U.S. 132. It says that when an owner gives a contractor detailed plans and specifications, the owner impliedly warrants that they are accurate and that the contractor can build from them. If the plans are wrong, the owner pays for the consequences. This applies to both public and private projects, including design build and construction manager at risk jobs.
The Spearin doctrine can help a contractor even when the DSC clause might not. For example, if the owner’s soils report in the contract documents misstated the bearing capacity, the contractor may have both a Type I DSC claim and a Spearin claim. The key is that the contractor must show it reasonably relied on the inaccurate information and that the error made the work more expensive or longer. And a general clause requiring the contractor to visit the site does not cancel Spearin. The contractor’s duty to inspect does not require it to uncover hidden design flaws.
How do the notice rules work?
Every standard DSC clause requires the contractor to notify the owner, and often the architect or engineer, immediately after discovering a condition. The purpose is to give the owner a chance to investigate before the condition is covered up. If the contractor fails to give notice on time, it may lose its right to an adjustment.
The following table shows the key notice deadlines across the major form contracts.
| Contract form | Notice deadline |
|---|---|
| FAR 52.236-2 | Promptly, and before disturbing the conditions. The Contracting Officer can extend the deadline. 48 C.F.R. § 52.236-2 |
| AIA A201-2017 § 3.7.4 | No later than 14 days after first observing the condition. AIA A201-2017 § 3.7.4, City of New Braunfels sample |
| ConsensusDocs 200 § 3.16.2 | Prompt written notice. No fixed number of days. Law Explorer |
| EJCDC C-700 § 5.04 | Promptly, before further disturbing the condition. Law Explorer |
| DBIA 535 § 4.2.2 | Promptly, and no later than 14 days after the condition was encountered. Law Explorer |
The FAR clause is strict. It says no equitable adjustment is allowed without the required notice, though the Contracting Officer has discretion to extend the deadline. And once final payment is made, no request for an equitable adjustment for differing site conditions shall be allowed if made. 48 C.F.R. § 52.236-2(d)
On an AI data center project, the safest rule is to give notice the same day the condition is spotted and in strict compliance with the contract’s specific deadline.
Can an owner shift the risk back to the contractor?
Owners often try to avoid DSC claims by adding disclaimers to the information they provide. A soil report might be labeled for preliminary information only or not guaranteed. But courts have consistently ruled that a one-sided disclaimer cannot override a DSC clause. The leading case is Metcalf Construction Co. v. United States, 742 F.3d 984 (Fed. Cir. 2014).
In Metcalf, the Navy gave the design builder a soils report stating the soils were not expansive. They were. The contractor sought $27 million in extra costs on a $49 million contract. The Federal Circuit held that the DSC clause preserved the contractor’s right to rely on the government’s data, and the government’s for preliminary information only label did not change that. The court also said that a post-award site inspection requirement did not negate the DSC clause. The government’s duty of good faith and fair dealing requires it to stand behind the information it chooses to give.
Earlier cases reached the same conclusion. In Foster Construction C.A. v. United States, 435 F.2d 873 (Ct. Cl. 1970), the court held that even unmistakable contract language disclaiming drill-hole data did not wipe out the right to rely when a DSC clause was present. And when a contract contains both a DSC clause and a conflicting disclaimer, an order-of-precedence clause will usually give the DSC clause the upper hand. Roy Strom Excavating v. Miller-Davis Co., 501 N.E.2d 717 (Ill. App. 1986). Pressbooks
The only sure way for an owner to push subsurface risk onto the contractor is to delete the DSC clause entirely, but even then, if the owner provided defective plans, the Spearin implied warranty may still apply.
What site conditions are common in AI data center builds?
AI data center construction faces the same subsurface hazards as any large project. Unsuitable soils, unexpected groundwater, undocumented underground utilities, buried debris, rock formations, contaminated soil, drainage issues, and concealed old structures all appear regularly. But the following conditions are especially painful in the fast moving AI data center context.
- Undocumented underground utilities. AI data centers need enormous power and connectivity. When a contractor hits an unmarked line, the project can stop cold.
- Soils that cannot bear the weight. A typical server hall is extremely heavy, with a density far beyond a standard commercial building. A geotechnical study done for a speculative office park may not be enough.
- Groundwater surprises. A water table higher than expected can flood excavations, trigger dewatering requirements, and delay foundation work.
- Contaminated materials. As developers hunt for cheap power in rural areas, they sometimes build on old industrial sites where buried waste appears unexpectedly.
- Infrastructure constraints that feel like site conditions. A contractor may discover after breaking ground that the local utility cannot deliver the promised power, or the municipal water pressure cannot support cooling. These are not physical subsurface conditions in the traditional sense. Whether a court or arbitrator would treat a utility shortfall as a DSC, force majeure, or owner caused delay depends heavily on the specific contract language. At least one reported decision has squarely addressed it, holding that lack of electrical power is not a physical condition within the differing site conditions clause. Continuing education resource, Industry research report
How do compressed timelines and delivery models amplify the risk?
AI data center projects are measured in months, not years. A 12 to 18 month schedule is common because cloud providers have committed to tenants under strict service-level agreements. That speed creates pressure that can turn an ordinary DSC into a crisis.
First, geotechnical work gets rushed. Soil borings may be too few or too shallow. Foundation designs get locked in before the full subsurface picture is clear. When a differing condition surfaces, the contractor is already on a tight path, and every day of delay costs money.
Second, the powered shell delivery model adds complexity. In a powered shell, the owner or tenant occupies one part of the building while construction continues in the next. If a DSC is found in an active zone, the vibration, dust, or temperature change from the remediation work can damage operating servers. The phased build out, in which tenants may be operating servers in one area while construction continues in another, increases the likelihood of performance issues, equipment contamination, and potential liability for the general contractor. AGC, AGC
Third, liquidated damages in AI data center contracts are often steeper than in ordinary construction. Because the owner faces heavy penalties under its own leases, it passes that risk down to the contractor. A two month delay caused by a DSC can trigger enormous financial consequences unless the contractor can prove entitlement to an extension of time.
Finally, insurance can fall short. A builder’s risk policy typically excludes defective workmanship. Much of an AI data center’s value is in the technical installations, cooling systems, UPS units, generators, lithium-ion batteries, switchgear, and structured cabling. If a DSC forces a hurried fix that later fails, the policy may not cover the defective work itself. Most policies do include an ensuing loss clause that covers resulting damage, but the line between the two is often litigated. AGC
What does a real AI data center DSC dispute look like?
The most direct example is Rogers-O’Brien Construction v. Microsoft. In May 2020, the Dallas-based contractor sued Microsoft in federal court in San Antonio over a roughly $1 billion AI data center project. The two buildings, totaling nearly 400,000 square feet, were in the Texas Research Park. Rogers-O’Brien claimed it was owed $34.2 million, including $13.6 million in retainage, for unpaid work, extended overhead, and delay damages. CourtListener
The contractor alleged that Microsoft failed to supply critical equipment, coordinate vendors, and integrate software, leading to cascading problems. Faulty components, water intrusion that required replacing server buses, and the loss of key personnel all contributed to the delay. Rogers-O’Brien also pointed to design errors and said Microsoft did not respond to its requests for intervention. ENR, Amended Complaint
The case did not reach a trial. It was administratively closed in August 2020 pending arbitration, and then dismissed with prejudice in April 2023, signaling a confidential settlement. The terms remain sealed. But the dispute shows how the speed, scale, and interdependency of an AI data center build can turn a large project into a costly fight over who bears the risk of what went wrong.
Not every site related surprise is a subsurface condition. In 2024, a Chilean environmental court partially reversed Google’s permit for an AI data center in Cerrillos over aquifer impact concerns during a drought. Google halted the plan and committed to an air based cooling redesign. While that was a permitting and environmental fight rather than a DSC claim, it illustrates how a site condition, water availability, can derail an AI data center project and force a redesign. Global Arbitration Review
How are these disputes resolved?
AI data center construction disputes are increasingly resolved through arbitration rather than courtroom litigation. The reasons are practical. Arbitration is confidential, which helps protect the owner’s proprietary technology and the hyperscaler’s trade secrets. The parties can choose an arbitrator with deep expertise in power systems, cooling engineering, and data infrastructure, rather than leaving those questions to a generalist judge or jury. And arbitration can handle cross-border issues more smoothly when the project involves international partners or supply chains.
Most contracts set up a tiered process. The parties might first require negotiation between project-level representatives. If that fails, the dispute escalates to senior management. Next comes mediation, and finally binding arbitration. This structure offers multiple chances to settle before a formal proceeding begins.
Dispute values are climbing. The Arcadis 2024 Construction Disputes Report found the average value of North American construction disputes jumped 43% since 2021, and nearly 30% of projects reported supply chain disruptions in 2023. For data centers, where a single US project can cost $7 million to $12 million per megawatt and 3.9 gigawatts of capacity was under construction in North America in 2024 (up 69% from the year before), the total exposure is enormous. Global Arbitration Review
Key takeaways
- Before breaking ground, confirm the contract includes a differing site conditions clause. If it is missing or struck, the contractor bears the subsurface risk, and the bid should reflect that.
- Type I claims are the strongest. Put the owner’s geotechnical data into the contract documents. A mere report labeled for reference only is weaker, but as Metcalf shows, it does not always defeat a DSC claim.
- Notice is everything. Train site supervisors to spot a condition, stop work, and send a written notice the same day within the contract’s deadline. For AIA A201 § 3.7.4 jobs, that is 14 days. For DBIA, 14 days. For FAR, promptly before disturbing the condition.
- AI data centers compress the timeline. When a DSC appears, document immediately the chain of causation linking the condition to each day of delay and each dollar of extra cost.
- Infrastructure failures, such as utility capacity shortfalls and grid delays, are a gray area. They may not fit the traditional DSC definition. Address them expressly in the contract as a separate risk allocation, rather than counting on a DSC clause to cover them.
- Owners who want to push subsurface risk to the contractor should delete the DSC clause and require the contractor to acknowledge a thorough pre-bid investigation. But even that will not always defeat a Spearin claim if the owner furnished defective plans.
- Choose your dispute forum in the contract. Arbitration keeps proprietary technology secret and lets you select a neutral with relevant technical expertise.
Frequently asked questions
Q:What is a differing site condition?
A:A differing site condition is a physical condition at a construction site that is materially different from what the contract documents showed, or that is unusually different from what a reasonable contractor would expect. If a contract contains a DSC clause, the contractor can ask for an equitable adjustment in price or time.
Q:Does every construction contract have a differing site conditions clause?
A:No. Federal contracts over $250,000 must have one. Most private form contracts, such as the AIA A201, include one. But parties are free to delete it. Without it, the risk of unknown physical conditions falls on the contractor under the common law rule.
Q:What is the difference between a Type I and a Type II DSC?
A:A Type I condition is one that differs materially from what the contract documents indicated. A Type II condition is physically unusual and not something a contractor would normally expect, but the owner made no specific representation about it. Type I is easier to prove because the owner said something that turned out to be wrong.
Q:What is the Spearin doctrine?
A:The Spearin doctrine comes from a 1918 Supreme Court case. It says that when an owner furnishes plans and specifications, it impliedly warrants they are accurate and can be built. If they are not, the owner is responsible for the resulting cost and delay.
Q:How quickly must a contractor notify the owner of a differing site condition?
A:It depends on the contract. The AIA A201 § 3.7.4 gives 14 days. The DBIA 535 gives 14 days. The federal FAR clause requires notice promptly and before the condition is disturbed. The best practice is to give written notice the same day the condition is found.
Q:What should a contractor do when it finds an unexpected condition?
A:Stop the affected work. Photograph and document the condition. Send a written notice to the owner and the architect or engineer within the contract deadline. Do not disturb the condition unless there is an immediate safety threat. Then track all cost and schedule impacts.
Q:Can an owner avoid a DSC claim by disclaiming the accuracy of its soil report?
A:Usually not. Courts have repeatedly held that broad disclaimers do not override a DSC clause. The Metcalf decision is the leading example. An owner who wants to shift subsurface risk needs to take stronger steps.
Q:Are utility capacity shortages considered differing site conditions?
A:This is unsettled. A utility’s failure to provide enough power is not a physical subsurface condition. Most contracts would treat it as an owner-caused delay or force majeure, not a DSC. The parties should address power availability expressly in the contract.
Q:Why is arbitration common in AI data center construction disputes?
A:Arbitration keeps the design details and proprietary technology confidential. It also lets the parties select an arbitrator with expertise in power, cooling, and data infrastructure, and it handles international issues efficiently.
Q:Does builder’s risk insurance cover the cost of fixing a differing site condition?
A:Generally not. Builder’s risk covers physical damage, not the cost of changing the design or work method to address an unexpected condition. If the DSC causes physical damage, the resulting loss might be covered under an ensuing-loss provision, but the direct cost of dealing with the condition is not.
Subscribe to The Compute Law Brief
The Compute Law Brief is a free weekday newsletter on the law of AI infrastructure across tax, real estate, construction, power, and deals. The big US build markets and federal law. Three minutes a morning. No paywall, and no email gate to read the blog. Subscribe if you want it in your inbox.
Junde Liu, JD, LL.M. (Taxation) candidate at UF Law. Originally published on Compute Law Blog. This article is general information and does not constitute legal advice. Reading it does not create an attorney client relationship. The reader should not act on the basis of any content here without first consulting a licensed attorney in the relevant state. Last reviewed for accuracy May 23, 2026.