The clauses in hyperscaler and colocation contracts
Data center owners write contracts around one fear: the building going dark. Those terms reach engineers and consultants directly, or through a design-builder’s subcontract. Here are the eight clauses we see most, why each matters, and what to ask for.
Small fee, very large building
A mechanical or electrical design fee on a data hall is a small share of what the owner stands to lose if the hall fails. Reed Smith notes that contractors generally resist full exposure to losses such as loss of use and lost profits, because they may not be able to absorb them.[1] A design firm with a fraction of a contractor’s balance sheet has even less room.
The second difference is the route the contract takes. Many data centers are delivered by design-build, so the engineer signs with the builder, and the builder passes down the owner’s terms.[3] Our practical view: the riskiest clauses often arrive in a paragraph that says the subconsultant is bound to the design-builder as the design-builder is bound to the owner.
What you will see, and what to ask for
Consequential damages: waived, or not
Why it matters. Downtime, lost revenue and tenant credits dwarf a design fee. Wilson Elser notes that damages from a design professional’s error on a data center could easily far exceed the fee.[2] The AIA owner and architect form carries a mutual waiver, and Clark Hill notes a mutual waiver is more likely to be accepted than a one sided one.[4] Owner drafted contracts may delete it.
Ask for. A mutual waiver that names lost profits, loss of use, downtime and tenant credits, and that is not cancelled by a carve-out wide enough to swallow it.
Uncapped indemnity and duty to defend
Why it matters. A promise to defend the owner is a promise to pay its lawyers from the first day of a claim, before anyone finds fault. Zweig Group explains that courts treat a contractual duty to defend as going beyond common law liability, which brings it within the contractual liability exclusion in professional liability policies.[5]
Ask for. Indemnity limited to your negligence and in proportion to it, with no duty to defend, or defense costs reimbursed only after fault is found. Tie it to an overall cap.
Liquidated damages flowed down
Why it matters. Owners and tenants run on committed go-live dates. Reed Smith describes delay remedies as heavily negotiated and mentions sub-caps on delay damages.[1] Gallagher describes a mismatch where a tenant’s service level agreement carries significant liquidated damages while the contractor’s liability is capped.[7] If that exposure is pushed down to a designer by flow-down, it lands on a firm whose policy may not answer it.
Ask for. No liquidated damages on design services. If they stay, a sub-cap, a clear trigger tied to your own late deliverables, and LDs as the sole remedy for that delay.
Fitness for purpose and performance guarantees
Why it matters. King & Spalding notes that owners may want performance liquidated damages, or rejection rights, where missing performance levels such as PUE would hurt the project’s commercial viability.[6] A guarantee is a promise of a result, not of reasonable care. ASCE opposes warranty and guarantee clauses in engineering service contracts,[8] and one underwriting manager states that professional liability policies do not cover breach of express warranty or guarantee claims.[9]
Ask for. Design “in accordance with the professional standard of care” to meet stated design criteria, with PUE and capacity stated as design targets, not guaranteed outcomes.
High limits and additional insured
Why it matters. Owners on large campuses often ask for limits and endorsements a mid-size firm does not carry. Additional insured status is available on general liability, but one underwriting manager explains it does not work on a professional liability policy.[10]
Ask for. Additional insured on GL only, professional liability limits you actually carry or a project policy, and “if commercially available” on any promise to keep coverage after completion.
IP and confidentiality
Why it matters. AIA B101 keeps the architect and its consultants as owners of their instruments of service and gives the owner a license to use them.[11] Our practical view: hyperscaler and developer forms often take ownership outright and reuse the design across many sites, which multiplies the number of buildings a single error can reach.
Ask for. If the owner owns or reuses the design, a release from liability for reuse on other sites without you, and confidentiality terms you can actually operate.
Termination for convenience
Why it matters. Data center programs change fast, and phases get cancelled. B101-2017 includes a fill point for a termination fee the owner pays on a termination for convenience.[11] Our practical view: owner forms often pay only for work performed to date, with nothing for demobilization or subconsultant cancellation costs.
Ask for. Payment for work done, reimbursables, subconsultant termination costs and a stated termination fee, plus release of liability for unfinished documents.
Pass-through clauses from a design-builder
Why it matters. On design-build, the engineer often signs with the builder, not the owner. Gallagher describes design-build and delegated design as a main source of professional exposure on data centers.[3] AIA’s C401 shows the mechanism: it incorporates the prime agreement and flows its provisions down to the consultant.[12] Every clause above can arrive this way, in a document you were never shown.
Ask for. A copy of the prime contract before you sign, a flow-down limited to your scope, and an order of precedence that lets your own subcontract terms win.
Signing a clause is not the same as insuring it
Professional liability is written to answer claims that your services fell below the standard of care. Promises that go further, a duty to defend, a guaranteed PUE, liquidated damages for a tenant’s lost go-live, are where policies most often stop.[5][9] Whether a particular claim is covered depends on the policy wording and the facts.
Our practical view: read the contract and the policy side by side before you sign, and treat any clause your policy will not answer as a cost on your own balance sheet. For limits and project policies, see practice policies, project policies and limits.
Five things to do before you price the job
- Ask for the owner’s form, and the prime contract if you are signing with a design-builder, before you price the job.
- Price the contract terms, not only the hours. A duty to defend or a guarantee is a cost even when it is never used.
- Put a limitation of liability in your proposal so it is on the table from the start.
- State your design criteria in writing: the redundancy level, the load, the PUE assumptions and who supplied them.
- List the insurance you carry today, with limits, so the gap is visible before signing, not after.
Questions to ask your broker: does my policy exclude contractual liability and guarantees, would it answer liquidated damages, and can I meet this owner’s limits without buying limits I do not need?
Got a hyperscaler or design-builder contract?
Send it to us with your current policies. We show you which clauses your insurance would answer and which it would not.
Data center contracts, in plain words
Will a hyperscaler really change its contract for a consultant?
Sometimes, often less than you would like. Our practical view: firms tend to get further on a few clauses that matter most, such as the consequential damages waiver, duty to defend and guarantees, than on a long markup.
Does my professional liability policy cover what I agree to in the contract?
Not automatically. Professional liability policies are generally built around negligence, and many exclude liability you take on only by contract, such as a duty to defend or a guarantee. Whether a claim is covered depends on the policy wording and the facts.
Why does a pass-through clause matter so much?
Because it can bind you to the owner’s terms through the design-builder’s subcontract, including liquidated damages and indemnities, without your name ever appearing in the owner’s contract.
Related
- Insurance for data center projects
- Practice policies, project policies and limits on large projects
- Speed to power: schedule pressure and delay claims
- MEP and electrical design liability on data centers
- NDAs, security requirements and the drawings themselves
- Insurance for electrical engineers
- Insurance for MEP engineers
- Insurance for commissioning agents
Sources
- Reed Smith, “Liability clauses in data center construction contracts” (June 2025, a law firm)
- Wilson Elser, “A New Frontier: Data Center Design and Construction” (a law firm)
- Gallagher, “Professional liability exposures for data center contractors” (a broker)
- Clark Hill, “Critical Risk Mitigation Provisions for Design Contracts, Part 1: Waiver of Consequential Damages” (a law firm)
- Zweig Group, “Take a look” on duty to defend clauses (a management consultancy)
- King & Spalding, “Building Data Centers: Key Considerations” (a law firm)
- Gallagher, “Managing SLA liability in data center projects” (a broker)
- ASCE Policy Statement 388, Warranty and Guarantee Clauses for Professional Engineering Service Contracts
- Victor Insurance Canada, Risk Management Advisory on express warranties and professional services (an underwriting manager)
- Victor Insurance, “Additional insured status” (an underwriting manager)
- AIA Contract Documents, Summary of B101-2017, Owner and Architect agreement
- AIA Contract Documents, Summary of C401-2017, Architect and Consultant agreement
General information only, not legal advice, current as of November 2026. Contract terms and their enforceability vary by state and by form; have an attorney review any contract before you sign. Whether a claim is covered depends on the policy wording and the facts.
Tell Us About Your Firm. We’ll Tell You What We See.
Starting out or renewing, with a policy in hand or not. If something is worth discussing, we’ll call. If not, we’ll say so.