The Definitive Guide toAI Data Centers
Ask the GuideAboutAccount

Chapter 2.6

In this chapter · 7 sections
Term help

Insurance & Risk Transfer

In 2026 the risk-transfer market grades your design like a second lender: capacity is rationed, delay-in-startup capacity can cap the insured construction program, and an uninsurable cooling or battery choice can strand financing. Recovery depends on the covered event, the insured interest and payment timing.

POWER-BOUNDGOODPUT

What you'll decide here

  1. Whether you can place the delay-in-startup (DSU) layer your lenders require: DSU can cap a placement even when physical-damage capacity is available.
  2. Whether your cooling, battery and fire design clear the insurer's bar (FM Global, IRI or carrier-specific) before a gap gets you repriced, sub-limited or declined.
  3. How much value sits behind one A-rated carrier versus a layered tower: $10–20B campuses outgrew single-carrier appetite, so layering and retentions are financing inputs.
  4. What financing documents require for valuation, limits, deductibles, exclusions, lender status and any GPU collateral warranty: a conditional warranty is not an unconditional collateral floor.
  5. Which tail risks you transfer by indemnity or parametric cover (weather, seismic, grid-down BI, coolant and PFAS liability, cyber) and which a captive retains.

By this chapter you have a workload (Chapter 1.1), a financing structure (Chapter 2.5) and a contract stack (Chapter 2.4). Insurance sits underneath all three, and it is routinely treated as the boring last form to sign. In 2026 that instinct is expensive. The risk-transfer market is now a second underwriting desk, running in parallel with your lenders, that grades the same design on a different axis. Lenders ask 'will this earn its cost of capital'. Underwriters ask 'how badly does this lose money when it fails, and how correlated is that loss with every other policy on our book.' When the underwriter says no, or yes-but-sub-limited, or yes-but-only-if-you-change-the-cooling, the consequence lands on the financing schedule and the engineering basis, not on a renewal spreadsheet.

The policies track the lifecycle, and so does the chapter: builder's risk / construction-all-risk (CAR) and delay-in-startup (DSU) during the build; property and business-interruption (BI) in operation; the liquid-cooling and lithium/BESS insurability problem that has repriced the pool; how insurability now drives design through FM-class loss-prevention approvals; the GPU-collateral protection terms some financings require; and the tail covers (parametric, environmental and cyber) that sit outside the property tower. What changed is the pool itself. An AI campus concentrates more replaceable value, more novel failure modes and more catastrophe-correlated accumulation into a single footprint than almost any asset class the property market underwrites, and the market has noticed. For each scenario, calculate the insured interest, apply the trigger, retention and limit, then name the committed cash that funds the uncovered loss and the collection delay. Engineering approval and a large headline limit do not establish recovery.

Builder's risk, CAR and the DSU overlay

During construction the asset is covered by builder's risk (US) or construction-all-risk (CAR) (international). Either one covers insured physical damage to the works and declared materials. Include transit and off-site storage explicitly for long-lead equipment, with the covered journeys, locations and limits matched to the shipment and storage values. For an AI build this is non-trivial, because the most valuable, most fragile, longest-lead items (the GPUs, the liquid-cooled NVL-class racks, the 50–100 MVA transformers, the switchgear) are in motion or in storage for months before they are energized. A transit or warehouse loss on a sold-out component (CoWoS-constrained accelerators, >12-month-lead HV transformers) does not merely cost the replacement value. It costs the schedule. → long-lead exposure in Chapter 2.3.

That schedule exposure is what the delay-in-startup (DSU) overlay, sometimes called ALOP (advance loss of profits), is built to address. DSU is time-element cover that triggers when an insured physical-damage event during construction pushes back the date the facility can begin earning. DSU does not pay for the damaged transformer (builder's risk does that). It pays the insured financial loss from the delayed start-up that damage caused, on the basis the policy states. For an AI campus whose revenue is a signed hyperscaler take-or-pay or a credit-tenant lease, the DSU exposure can dwarf the physical-damage exposure. A practitioner-cited illustration: a 50 MW facility leased at ~$150/kW-month puts roughly $45M of gross revenue at risk over a six-month delay (Commercial Risk, 2025), and a gigawatt campus scales that by 20x. That figure is the exposure, not the indemnity. Bridge it to the insured sum before you set the limit: DSU commonly insures gross profit or specified standing charges and debt service (a loss-of-rent formulation differs), net of saved expenses and subject to the time excess, indemnity period and sub-limits.

Check the defects exclusion and testing cover before counting recovery. LEG 1/96 excludes loss or damage caused by defects. LEG 2/96 can cover resulting damage but excludes the rectification costs that would have been incurred immediately before that damage. Under LEG 3/06, once damage occurs, the excluded replacement or rectification cost is the cost of improving the original material, workmanship, design, plan or specification. A defect's existence alone does not establish covered damage. DSU depends on delay from covered damage and its own exclusions, so separate excluded defect repairs from covered resulting damage. Price broader defects cover against its retention, and match both physical-damage and DSU testing-and-commissioning terms to hot testing and the IST schedule in Chapter 2.1.

DSU can cap a construction placement even when physical-damage capacity is available. Aon's May 2026 construction conference identified damage-driven start-up exposure as a constraint for some insurers. Some underwriters treat the DSU sum insured as a PML-like (probable-maximum-loss) exposure, curb their line sizes against it and regard it as disproportionate to premium (Aon; Commercial Risk, 2025). Test the available DSU limit against the insured financial loss and lender covenant alongside the works limit. The recurrent drafting fight is a power-supply delay: DSU responds only when insured physical damage causes the delay, so an off-site utility or third-party generation loss needs explicit coverage, and a schedule miss without covered damage does not trigger DSU. → the interconnection-and-energization risk this insures against in Chapter 3.4.

10 MW; $100/kW-month rent; 20% saved expense; 30-day policy month; damage completion day 90; no-damage start day 30; 15-day excess; 6-month maximum; $1.0m limit.modeled
Landlord transformer-fire and DSU wording assumptions
Scope & caveats

For a landlord, decide how much of a construction delay its DSU layer could recover. Assume 10 MW of leased capacity at $100/kW-month, a 30-day policy month, full rent at the agreed accepted-service date and saved variable expense of 20% of that rent. Assume a covered on-site transformer fire during the insured works, repair/restoration ending 90 days after the planned start, and an independent permit delay that would have prevented all rent for the first 30 of those days even without the fire. Adopt a hypothetical gross-profit DSU wording that adjusts the no-damage start for that permit delay, deducts a 15-day time excess from the resulting incremental delay, has a six-month maximum indemnity period and a $1.0 million limit. Assume no partial rent, extra expense, salvage, other recovery, underinsurance penalty or other deductible; fixed standing charges are already inside insured gross profit. The timing isolates the covered-loss and concurrent-delay mechanisms in this chapter. No policy, adjuster agreement or insured event is represented as real. Capacity and rent are exact normalization constants whose product makes the monthly rent easy to audit, not a landlord quote. The saved-expense fraction is chosen inside [0,1]. Calendar month length is an explicit policy convention. Damage/no-damage dates, excess, maximum period and limit are selected hypothetical wording inputs: the delay stays inside the period while the monetary limit binds. No-covered-damage and higher-limit variants test distinct coverage boundaries. Zero partial rent, extra expense, salvage, other recoveries, underinsurance penalty and extra deductibles isolate the Chapter 2.6 gross-profit/delay mechanism. No policy or adjuster finding is implied.

Calculate the landlord’s lost interest, then the policy response. Rent per policy month = leased MW × kW per MW × rent per kW-month. Insured gross profit = rent × (one − saved-expense share). Total loss = full delay / policy-month length × insured gross profit. Incremental damage delay = damaged start − no-damage start; payable days = max(zero, incremental delay − time excess). Recovery is the lesser of payable gross-profit loss and the policy limit, inside the maximum period. Retained loss reconciles to independent delay, time excess and loss above the monetary limit.

$1.0m recovery; $2.4m net loss; $1.4m retainedderived
Landlord covered-delay recovery and retained loss
Scope & caveats

Under the assumed wording: rent=10 MW×1,000 kW/MW×$100/kW-month=$1.0m/month. Saved expense=.20×rent=$0.20m/month, so gross profit=$0.80m/month. Total delay loss=90/30×.80=$2.4m. No-damage start day 30 versus damaged start day 90 gives 60 incremental days. Payable delay=max(0,60−15)=45 days, below the six-month maximum; 45/30×.80=$1.2m before the $1.0m cap. Retained $1.4m=.80 independent permit delay+.40 time excess+.20 limit shortfall. With no covered damage, recovery is zero and retained loss is $2.4m. Raising only the limit to $1.2m removes the $0.20m limit shortfall. Monetary outputs use two significant figures; policy day counts are exact conventions.

Fund both retained loss and the interval before payment. The no-covered-damage flip leaves the whole net delay loss with the landlord, and raising only the monetary limit removes only the limit shortfall. Repair cost belongs to works cover, and debt service is not added again to gross profit. Munich Re’s DSU training supplies the damage, gross-profit and time-deductible method. 2.1 supplies both schedules, 2.4 supplies custody and recoveries, and 2.5 funds the gap.

The AI-campus risk-transfer stack — fork by fork
LayerWhat it coversTriggerBinding constraint in 2026Consequence if it falls short
Builder's risk / CARPhysical damage to works and materials; transit and off-site storage where included in the policyInsured physical damage during constructionTransit/storage limits on sold-out, high-value componentsA transit loss on a CoWoS-constrained part re-dates energization, not just replacement
Delay-in-startup (DSU/ALOP)Insured financial loss from delayed first earning, on the policy's gross-profit, standing-charge or loss-of-rent basisCovered physical damage during construction that delays scheduled business commencementDSU sum insured treated as PML; capacity rationed; power-delay coverage contestedUnplaceable DSU layer re-dates financial close; lender covenant unmet
Property (operational)Physical loss/damage to the operating facility & equipmentInsured peril (fire, water, mechanical)Single-carrier appetite below $10–20B campus values; nat-cat accumulationLayered tower required; per-occurrence sub-limits on water/liquid losses
Business interruption (BI)Lost net income plus continuing normal operating expenses, with extra expense where insuredCovered property loss impairing operationsBI tied to compute capacity & interconnected-campus dependencyContingent-BI and grid-down exclusions leave the real outage cause uncovered
GPU collateral / residual valueProperty cover plus any deal-specific collateral warranty or residual protectionCovered property loss, or a qualifying liquidation shortfall under the warranty termsThin secondary market; reinsurance appetite for the residual floorLender advances less, prices wider, or the financing does not clear
Tail (parametric / environmental / cyber)Weather/seismic, coolant & PFAS liability, cyber-driven outageIndex threshold (parametric) or named peril (indemnity)Basis risk (parametric); PFAS exclusions; cyber accumulationSelf-insured retention or a captive absorbs the tail the market won't price
Each layer is a distinct policy with its own market, trigger, and binding constraint. 'Binding constraint' is the variable that actually rations capacity or terms in 2026, not the headline limit. Practitioner ranges; see keynumbers for sourced figures.

Property and business interruption for a GPU-dense, liquid-cooled facility

Once the campus is live, cover shifts to property + business interruption, and the AI build breaks two assumptions the property market spent decades calibrating. The first is value concentration. SemiAnalysis's August 2025 hyperscaler model puts a GB200 NVL72 rack-scale server at $3.1M, before networking, storage and other deployment costs. Value the hardware generation you are buying, and its cooling fault domain, in the property-loss scenario. A gigawatt campus stacks tens of billions of replaceable silicon into one geofence. Swiss Re flags individual campuses reaching ~$20B of construction value before equipment is even installed, and projects global data-center-linked premium rising to ~$24.2B by 2030 from ~$10.6B (Swiss Re Institute, March 2026, citing Aon). S&P projects construction-related coverage alone could reach ~$10B of premium in 2026, roughly twice the global aviation market.

The second broken assumption is BI structure. Business-income cover commonly measures lost net income plus continuing normal operating expenses during the policy's period of restoration; extra-expense cover addresses insured additional costs of maintaining or restoring operations. An AI campus's income, though, is tied to computing capacity and to interconnected-campus dependencies. A substation or CDU loss can strand goodput across racks that suffered no physical damage, and revenue is governed by SLAs and goodput contracts, not floor area. Power is also the largest single cause category: in Uptime Institute's survey, power accounts for ~45% of respondents' most recent impactful outage, most often on-site UPS failures rather than the utility. Both halves land awkwardly. On-site electrical failure belongs to equipment breakdown and machinery BI, while a utility interruption or dependent-property loss is exactly where standard property BI carries exclusions. The result is a coverage gap over the most likely loss, which is why operators increasingly add contingent-BI, service-interruption and parametric grid-down covers, and why the goodput-vs-availability framing of Chapter 12.2 is also an insurance argument.

Then there is the loss-history shock that has actually moved premiums: fire and water. FM's 15-year study finds fire drives ~42% of loss costs from only ~11% of events, so fire is rare but catastrophic. Water is the other: liquid- and water-related damage accounts for ~24% of data-center loss costs across that same multi-year review (Swiss Re). The category predates direct-to-chip cooling, since it counts sprinkler leakage and facility-water events, and DLC now adds a new mechanism. A leak in a direct-to-chip loop is not a mopping job; it is a high-value, energized-electronics water event. That loss history, plus the new exposure a pressurized loop puts inside the rack, is why liquid-cooled halls now see per-occurrence water sub-limits and higher retentions, and why the cooling decision in Chapter 5.4 is also a premium decision.

The liquid-cooling and lithium/BESS insurability problem

Two engineering choices that define the 2026 AI campus, pervasive direct-to-chip liquid cooling and rack-integrated or facility-scale lithium-ion energy storage (BBUs and BESS), give underwriters distinct leak, fire and accumulation scenarios to price. Get the carrier's terms before either configuration is released.

Liquid cooling put water (and, in dielectric designs, specialty fluids) next to the most valuable energized electronics ever installed at density. Water was already ~24% of data-center loss costs on the sprinkler and facility-water history above (Swiss Re), and DLC adds a pressurized loop at the rack. Underwriters respond with per-occurrence water sub-limits, leak-detection and CDU-redundancy requirements, and credit for designs that physically separate the technology-cooling and facility-water loops. The leak-detection and concurrent-maintainability engineering of Chapter 5.4 therefore belongs in the underwriting submission. A premium credit, surcharge or decline belongs to the carrier's actual offer.

Lithium-ion is the sharper problem because its failure mode is thermal runaway, a self-sustaining, propagating, hard-to-suppress fire that, when sited rack-level inside the data hall, sits next to the silicon it is meant to protect. Distinguish that rack-integrated configuration from a separated stationary BESS: location and propagation boundaries change the loss. FM's loss-prevention guidance treats it as a first-class hazard through two data sheets. FM DS 5-33's April 2025 revision added approved off-gas detection and clarified outdoor-container BESS protection; its current edition is April 2026. Its two-hour cutoff-room construction applies to indoor facility ESS. DS 5-32's July 2026 edition separately covers data-hall BBUs and room compartmentation, and it directs that rooms with distributed Li-ion BBUs be protected with automatic quick-response sprinklers or an FM Approved HC-2 water-mist system, not clean-agent or hybrid water/inert-gas systems as the BBU fire strategy (FM DS 5-32, 2026). Apply the installation-specific controls in Chapter 6.5, including that BBU sprinkler or HC-2 water-mist protection.

The two-phase-immersion episode shows how fast a fluid choice can become an environmental-liability and supply-continuity problem. 3M's exit from PFAS manufacturing, including its Novec fluids, was completed at the end of 2025 (ServeTheHome; C&EN), and it disrupted a cooling supply chain. Its separate $10.5–12.5B US public-water-supplier settlement is not a two-phase-immersion loss estimate (3M 2025 Form 10-K). Coverage follows the pollution policy's wording.

Record whether each engineering recommendation is a condition to bind, a condition after binding or advisory, and obtain the written consequence of leaving it open. Product approval does not accept the installed project.

How insurability drives design

In 2026, insurability runs upstream of design, not downstream of it. The mechanism is the loss-prevention approval. Carriers in the FM-style 'highly protected risk' tradition (FM, plus IRI/GXS-lineage and carrier-specific equivalents) do not merely price a finished design. They publish data sheets that specify what they will insure, conduct plan review before construction, and tie favorable terms to FM-Approved components and configurations. Data-sheet conformance supports underwriting but does not establish the offered terms. Obtain the carrier's written acceptance, limits, retentions and conditions for the installed design, and record the actual consequence of each open recommendation.

The insurer's data sheet becomes a de facto design code beside NFPA, ASHRAE and the local AHJ, and on the novel hazards (Li-ion placement, DLC leak control, off-gas detection) it is often stricter and more current than the building code, because the carrier carries the loss. The forks this creates are concrete: choose a battery chemistry and placement that clears DS 5-33, or accept a fire sub-limit and a higher retention; follow the installation-specific separation and detection controls in Chapter 6.5, or accept the consequence the carrier writes into its offer; separate the cooling loops and instrument them for leak detection, or eat a water sub-limit. None of these is a post-design negotiation. Each is a design input that, if discovered late, forces a re-engineering or a worse policy. It is the same one-way-door dynamic the cooling cliff creates in Chapter 5.1, except the gate here is an underwriter's signature.

Deep dive: why the FM-Approved gate is cheaper to clear at design than to negotiate at bind

The temptation is to treat the loss-prevention bar as a negotiation: build what you want, then argue for terms. The economics run the other way, for the same reason the cooling cliff does, because the gate is a discontinuity, not a slope. A design that conforms to the carrier's data sheets enters underwriting as a candidate for highly protected risk (HPR) treatment. A design that departs on a novel hazard, such as rack-level Li-ion outside the carrier's data-sheet protection or a single-loop DLC design without leak isolation, is not priced 'a little worse'; it can be modeled by the carrier with fat tails. Departures can change placement, limits or retentions; the written offer determines the consequence. A sub-limit is a hard cap on what the carrier will pay for that peril, and a higher retention means you self-insure the first tranche.

Late discovery is costly because by financial close the design is frozen, the long-lead gear is ordered, and the only levers left are accept the worse terms or re-engineer and slip the schedule. Both are expensive, and the slip can be worse than the premium because it cascades into the DSU exposure and the energization date the whole capital stack is built around. So put the carrier's loss-prevention engineer in the design reviews from the basis-of-design stage, where you put the AHJ and the lender's independent engineer, and design in data-sheet conformance rather than litigating it at bind. → the basis-of-design discipline in Chapter 1.1; fire-design specifics in Chapter 6.5.

~$10Bforecast
data-center construction-related coverage premium projected for 2026 — ~2x the global aviation market
~24%
share of data-center loss costs that are liquid- or water-related over a multi-year review; DLC adds a new mechanism
Scope & caveats

About 24% of loss costs in the cited historical review; includes sprinkler and other water mechanisms. Not a DLC-only incidence rate, current-project probability or explanation of a quoted sublimit.

42% / 11%
fire's share of loss cost vs share of loss events — rare but catastrophic (15-yr study)
~25% / ~40%modeled
Swiss Re modeled share of operating, in-construction and planned US data-center capacity in 3+ large-hail-day / significant tornado zones
Scope & caveats

Swiss Re CatNet hazard screening assigns county-level GW totals to county centroids rather than individual site coordinates. The tornado category is 3+ days per year with (E)F1 or stronger tornadoes within a 25 km x 25 km grid cell.

~150 bps/yr
USD.AI-disclosed Barkr collateral-warranty cost; conditional shortfall coverage capped at 80% of warrantied amount
Scope & caveats

One named USD.AI/Barkr collateral-warranty program; not a market-wide RVI price or coverage standard.

Recovery is conditional on a qualifying liquidation shortfall and subject to the warrantied schedule, stated cap and program/policy terms; it is not an unconditional collateral floor.

GPU-collateral lender insurance and total-loss treatment

When silicon secures a loan, the lender's insurance requirements become financing covenants, not an operational nicety. CoreWeave's March 31, 2026 disclosure identifies an $8.5B delayed-draw facility secured by HPC infrastructure and a customer contract. Facility capacity is distinct from debt drawn. The structure mirrors decades-old aircraft and equipment finance: the financing documents specify required property coverage, the valuation and settlement basis, insured parties, loss-payee status, limits, deductibles and exclusions. A covered physical-damage or theft recovery can still differ from replacement cost or the loan balance, and naming a lender does not create an unconditional make-whole result. → the financing structures this protects, including that facility, in Chapter 2.5.

The harder problem is not the fire that destroys a rack. It is the slow-motion total loss the property policy does not cover: economic obsolescence. A GPU that still works perfectly can be worth a fraction of its book value because a successor part displaced it, and that residual collapse is the central credit risk of GPU-backed debt (see the depreciation debate in Chapter 1.8). One disclosed structure is USD.AI's Barkr-backed collateral warranty. At origination, valuers set a warrantied value schedule for the collateral across the loan life, and if a liquidation event realizes value below the schedule, institutional reinsurance covers the shortfall up to ~80% of the warrantied amount. USD.AI disclosed an approximately 150 bps/yr cost, netted from interest yield, for that program (USD.AI, May 2026); it is not a market-wide price. The conditional warranty schedule can inform collateral valuation, which lets a lender advance more against the asset and price tighter than against an unhedged, thin secondary market. But recovery depends on a qualifying liquidation, realized value, the warranty's cap and all policy and program terms; it is not an unconditional insured minimum. Test the exact conditions before treating a warranty as recoverable cash.

The fork, then, is whether your financing can actually source the residual-value insurance (RVI) floor it assumes. Availability and pricing outside the disclosed program are not established by that source. If a deal cannot place the residual protection its credit model assumes, the lender must haircut recovery, reduce the advance, reprice or reject the structure under its own documented terms. Here, insurability and financing are the same decision.

Parametric, environmental and cyber: the tail the property tower won't price

Three exposures sit awkwardly inside a standard property/BI tower, and the AI campus pushes each hard enough that operators increasingly transfer them separately.

  • Parametric weather / seismic / grid-down. Where indemnity BI is slow, contested and exclusion-riddled (especially for grid-down and contingent losses), parametric cover pays on an objective index trigger (a measured wind speed, ground acceleration or grid-frequency/outage event at the site), with faster settlement using independent trigger data and the policy's payment conditions. The price is basis risk: the indexed payout and your economic loss can diverge, including a real loss that never trips the trigger. Parametric fits the utility-interruption slice of the power tail, an off-site event an index can measure, while on-site electrical failure belongs to equipment-breakdown and machinery BI and a dependent-property loss to contingent BI. Match the cover to the cause; the outage statistic cannot select the policy. It pairs naturally with the BYOP/island-mode resilience of Chapter 3.4.
  • Environmental liability. Coolants, dielectric fluids, refrigerants, diesel and battery electrolytes create spill, cleanup and liability exposures. Identify each substance's legal classification and the policy's pollution and PFAS wording. 3M completed its PFAS-manufacturing exit at the end of 2025; its 2025 Form 10-K reports $10.5–12.5B payable during 2024–2036 for the US public-water-supplier settlement. Those payments are not a two-phase-immersion loss estimate, but they show how a fluid choice can become a long-tail liability. Obtain the dedicated environmental-impairment / pollution-legal-liability policy's express treatment of the chosen fluid before counting liability recovery.
  • Cyber. An AI campus is a high-value cyber target whose compromise can cause physical and business-interruption loss, not just data loss. Marsh's Q2 2026 index reports global cyber renewal rates down 4%, the twelfth consecutive quarterly decline, with stable capacity and continued insurer competition. Systemic control-plane and OT accumulation still requires underwriting of the covered events, exclusions and limits. This global series does not establish a data-center-specific premium trend. The underwriter's fear is accumulation: a single exploited control-plane or OT vulnerability replicated across a fleet is a correlated, systemic loss.

The common thread: each of these is a tail the property tower either excludes or prices separately, which is why large operators stand up a captive insurer, a wholly owned vehicle that formally retains the layers the market won't price efficiently and turns an unpriced gap into a funded, balance-sheet-managed retention. The captive is not a way to avoid insurance; it is the structure that makes self-insuring the tail explicit, capitalized and auditable. Fund the uncovered event and the delay before payment, including any captive retention.

Deep dive: basis risk, and why a parametric policy is a bet on your own correlation

Parametric insurance uses an agreed index and payout schedule to reduce detailed loss adjustment, so it settles faster and removes much of the indemnity-claims fight. It replaces one risk with another. An indemnity policy pays your actual loss, after the adjuster agrees. A parametric policy pays according to the contract's trigger, loss-declaration and payment conditions: Swiss Re STORM, for example, requires confirmed economic loss. Basis risk is the mismatch between indexed payout and economic loss, including loss without a trigger. The worst case is the loss the index misses: the storm passed just outside the measurement footprint, or the grid frequency dipped just short of the trigger, and a paid premium becomes no recovery exactly when you needed it.

The engineering response is to design the trigger as carefully as you design the cooling loop. Select independent measured or modeled data that tracks the site's exposure, not a regional average that washes out your local event, and calibrate the trigger and payout schedule to your loss curve. For an AI campus the threshold is often a grid-outage duration or a frequency excursion, not just a weather metric. Parametric is most defensible exactly where indemnity is weakest: fast-onset, objectively measurable, exclusion-prone perils such as grid-down, named windstorm and seismic. It is least defensible for slow, diffuse, hard-to-index losses. The decision is therefore not 'parametric or indemnity' but 'which tail is well enough indexed that parametric beats a contested indemnity claim.' → the grid-down resilience that drives the demand for this in Chapter 3.4 and Chapter 12.2.

What a defensible risk-transfer position produces

A risk-transfer position that survives lender diligence and board scrutiny is a set of decisions, made at the basis-of-design stage and carried through close, that the rest of the project inherits:

  • An insurability-gated design basis. The cooling, battery and fire-design choices are validated against the carrier's loss-prevention data sheets before the basis-of-design freezes. The loss-prevention engineer reviews alongside the AHJ and the lender's independent engineer, so FM-class conformance is designed in, not litigated at bind.
  • A placed, layered program matched to the financing schedule. CAR sized to insured works values and DSU sized to the insured delayed-start financial loss after saved expenses, plus an operational PD/BI tower syndicated across enough A-rated capacity to cover the campus value, with the retentions and per-occurrence sub-limits (water/liquid, fire, cyber, nat-cat) understood and accepted as financing inputs.
  • A collateral-protection package the lender's covenant actually requires. The property valuation basis, limits, deductibles, exclusions and lender status the financing documents require, plus any deal-specific collateral warranty, with its trigger, cap and recovery schedule stress-tested independently.
  • An explicit tail strategy. A named decision on which tails (grid-down, environmental/PFAS, cyber) are transferred parametrically or through dedicated liability cover, and which are retained in a capitalized captive, so the gap is funded, not discovered.

The recurring anti-pattern is treating insurance as procurement instead of design: choosing the cooling, the battery placement and the fire suppression on engineering grounds alone, then discovering at bind that the configuration is sub-limited or declined. At that point the only levers are a worse policy or a re-engineering that slips the energization date the entire capital stack depends on. Insurability is a design input. The cheapest place to clear the underwriter's bar is the design review; the most expensive is financial close.

This chapter sits between the money and the metal. The financing structures whose covenants demand this cover (DDTLs, GPU-backed ABS, the maturity mismatch) are in Chapter 2.5. The contract stack that allocates risk before it is insured is in Chapter 2.4, and the long-lead procurement exposure the builder's-risk transit cover protects is in Chapter 2.3. On the engineering side, the fire design that gates Li-ion insurability is in Chapter 6.5. The DLC leak control and loop separation that earns or loses a water sub-limit is in Chapter 5.4, with the density wall that forced liquid in Chapter 5.1. The energy-supply and grid-down resilience that drives DSU and parametric demand is in Chapter 3.4. The goodput-vs-availability reframing that recasts BI as a compute-capacity (not floor-area) loss is in Chapter 12.2, and the depreciation and residual-value debate that the GPU-collateral and RVI covers rest on is in Chapter 1.8.
Cite this chapter
Fehn, J. (2026). Insurance & Risk Transfer (Chapter 2.6). The Definitive Guide to AI Data Centers. https://aidatacenterguide.com/part-2-project-delivery-schedule-procurement-contracts-and-risk/2-6-insurance-and-risk-transfer (accessed 2026-10-05).
@misc{aidc-2-6,
  author       = {Fehn, Jacob},
  title        = {Insurance & Risk Transfer (Chapter 2.6)},
  howpublished = {The Definitive Guide to AI Data Centers},
  year         = {2026},
  url          = {https://aidatacenterguide.com/part-2-project-delivery-schedule-procurement-contracts-and-risk/2-6-insurance-and-risk-transfer},
  note         = {Accessed 2026-10-05}
}
Spotted an error? Suggest an edit