MEP and electrical design liability on data centers
On most buildings, a power or cooling problem is an inconvenience. On a data center it is the loss the whole building exists to prevent, and the people who lose money are the owner and every tenant inside. Here is where the exposure sits for mechanical and electrical engineers, and what to put in writing before you start.
More heat per rack, and water at the rack
Rack densities are rising. Uptime Institute’s 2025 survey put the average rack at about 7.6 kW, up from 6.8 kW the year before, with more than 80% of operators saying their densest rack was still under 30 kW.[4][5] The averages hide the new AI halls, which is why ASHRAE’s data center committee, TC 9.9, has published liquid cooling guidance: rack heat loads keep climbing, and moving that heat with air alone takes more airflow than a room can deliver.[7]
ASHRAE’s guidance recommends a coolant distribution unit to separate the facility water system from the technology cooling loop that reaches the servers, monitoring of coolant quality and filtration, and a plan to migrate load if cooling fails.[6][7] Each of those is a design decision with your name on it. So is the demarcation line itself: who designs the loop inside the rack, who designs the plant, and who is responsible for the connection between them. Our practical view: if the drawings do not show that line, a claim will draw it for you.
N+1, 2N and what a Tier rating does and does not promise
In the shorthand engineers use, N is the capacity the load needs, N+1 adds one spare component, and 2N duplicates the whole system on separate paths. Owners often state a target in Uptime Institute’s Tier terms instead. Uptime describes Tier III as concurrently maintainable, meaning equipment can be maintained or replaced without shutting the site down, and Tier IV as building on Tier III by adding fault tolerance.[8]
The liability point is simple. A Tier target, an N+1 requirement or a 2N one line diagram describes a topology. It does not describe performance under every failure. Outages usually come from the places redundancy does not reach: a shared controls network, a common bus, a single pipe header, a transfer scheme that has never been tested under load. When your contract says “Tier III” or “fully redundant” without saying what that means on this project, an owner can later argue you promised an outcome, not a level of care.
Selective coordination and arc flash
The National Electrical Code (NFPA 70) requires overcurrent devices on emergency systems to be selectively coordinated with the devices upstream and downstream, with parallel rules for legally required standby systems and critical operations power systems in sections 701.32 and 708.54.[9] The rule for emergency systems says the coordination is to be selected by a licensed professional engineer or another qualified person.[10] A 2023 amendment added that when those devices are replaced, or the system is modified, coordination has to be re-evaluated.[9] Section numbers have moved between editions, so check the edition your jurisdiction adopted.[10]
NFPA 70E, the workplace electrical safety standard, requires the arc flash risk assessment to be reviewed at intervals of no more than five years and updated when the system has a major modification.[11] Data centers change constantly. Every added hall, substituted breaker or new tenant feed is a modification. If your scope includes these studies, write down what data they rely on and that they are only valid for the system as studied.
Why one outage becomes a large claim
Uptime Institute reports that outages have become less frequent for four years in a row, but they remain expensive: 54% of operators in its survey said their most recent significant outage cost more than $100,000, and about one in five said it cost more than $1 million.[1][2] Power is the most common cause of serious outages, with UPS problems the most frequent source.[3] Uptime also found that 80% of operators believe better management and processes would have prevented their most recent incident.[2]
For a designer, the damages that matter are not the cost of fixing a breaker. They are lost revenue, service credits paid to tenants, and lost data. Those are consequential damages.
How contracts treat downtime
Colocation agreements often exclude consequential, incidental and lost profit damages, and may cap direct damages at a multiple of the fees paid.[13] The operator has limited its own exposure to tenants. The question for you is whether your contract with that operator does the same.
Lawyers writing on these waivers advise naming the losses rather than relying on the word “consequential.” A Jones Walker article recommends that a waiver expressly cover loss, corruption or unavailability of data and downtime or service interruption damages, and notes that lost profits and revenue should be named directly because a broad reference may not be enough.[12] Courts read these words differently by state, so have counsel review the clause for the governing law.[12]
- Ask for a mutual waiver of consequential damages that names downtime, lost revenue, service credits and data loss.
- Ask for a cap on your total liability tied to your fee or your insurance limit.
- Strike any promise of uptime, availability or Tier certification as an outcome. Design to a target with professional care.
- Watch for indemnities that make you responsible for tenant claims. Liability you take on by contract may not be insured.
Six steps before you issue drawings
Write a basis of design
Name the IT load per rack and per hall, the cooling method, the redundancy target and whether a Tier certification is sought. Get the owner to sign it. When the load changes, it is the document that shows what you were asked to design.
List your assumptions
Utility capacity, fault current from the utility, equipment the owner selected, tenant fit out you do not control. Assumptions that are written down become scope limits. Assumptions that are not become arguments.
Name the studies and who owns them
Short circuit, coordination and arc flash studies are often split between the engineer of record, the switchgear vendor and the electrical contractor. Say in the contract which you perform and on what data.
Hunt single points of failure
Walk every path from the utility to the rack and from the chiller or CDU to the chip. Controls, a shared bus, a common pipe header and one transfer scheme are where redundancy quietly ends.
Get an independent peer review
On a large hall, a second set of eyes on the one line diagram and the cooling topology costs little against one outage. Keep the comments and your responses.
Revisit after every change
A new tenant, a denser rack or a substituted UPS can undo coordination and arc flash results. Treat each one as a design change with a fee and a revised study.
Taking on your first data hall?
Send us the contract and your current policy. We will tell you where the downtime exposure sits and what your coverage says about it.
MEP liability on data centers, in plain words
Will my professional liability policy pay for a client’s downtime losses?
It depends on the policy wording, the contract and the facts. A professional liability policy responds to claims arising from negligence in your professional services, and many exclude liability you assume by contract beyond what the law would impose. A consequential damages waiver in the contract is usually the first line of protection, not the policy.
Is designing to Uptime Tier III a guarantee of uptime?
No. Uptime describes Tier III as concurrently maintainable and Tier IV as fault tolerant. Those describe the topology of the infrastructure. Your contract should say you design to a stated target using reasonable professional care, not that the site will never go down.
Why does selective coordination come up on data centers?
The National Electrical Code requires it for emergency, legally required standby and critical operations power systems, and the 2023 amendment requires it to be re-evaluated when protective devices are replaced or the system is modified. On a data center that changes often, that is an ongoing obligation, not a one time study.
What should I ask my broker before taking on a hyperscale hall?
Whether your limit is shared across all your projects, whether a project specific policy is available, how the policy treats liability assumed by contract, and whether your application describes data center and redundancy design accurately.
Related
- Data centers: the project page
- Commissioning and integrated systems testing: the liability
- Power, generation, batteries and water: the new exposures
- The clauses in hyperscaler and colocation contracts
- Practice policies, project policies and limits on large projects
- Insurance for electrical engineers
- Insurance for mechanical and HVAC engineers
- Insurance for MEP engineers
Sources
- Uptime Institute, Annual Outage Analysis 2025 (keynote report)
- Uptime Institute, “Uptime Announces Annual Outage Analysis Report 2025” (press release, Business Wire)
- Computer Weekly, “Datacentre outages decreasing in frequency, Uptime Institute Intelligence data shows”
- Uptime Institute, Global Data Center Survey 2025 (keynote report)
- Upsite Technologies, “Rack Density Rises While PUE and Outage Frequency Remain Flat” (a cooling vendor’s summary of the Uptime survey)
- Building Design + Construction, “ASHRAE releases best practice guide for liquid cooling systems in data centers”
- DatacenterDynamics, “ASHRAE publishes liquid cooling guidelines as chip power moves into uncharted territory”
- Uptime Institute Journal, “Explaining the Uptime Institute’s Tier Classification System”
- NFPA, Tentative Interim Amendment 23-11 to NFPA 70 (2023 NEC), selective coordination
- IAEI Magazine, “Selective Coordination: What the Inspector Needs to Know”
- CBS Field Services, “Avoid myths and misconceptions about arc flash study guidelines” (an electrical testing firm)
- Jones Walker (a law firm), “Before consequential becomes catastrophic,” published by ConsensusDocs
- Pillsbury (a law firm), “Legal provisions to negotiate in a colocation agreement”
General information only, not legal advice, current as of November 2026. Code sections and editions vary by jurisdiction. Whether a claim is covered depends on the policy wording and the facts. Have counsel review your contract.
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.