Insurance is what stands behind the liability cap.

Section 01

Why insurance backs the liability cap.

A liability cap is a promise to pay. Insurance is what makes the promise collectible. If a serious failure produces a loss within the cap but the seller lacks the coverage or the balance sheet to pay it, the buyer's remedy is a claim against a party that cannot satisfy it. The insurance clause closes that gap by requiring the seller to carry coverage sized to the risks the TSA creates, so the buyer can actually recover when a covered loss occurs.

The risk is sharpest where the seller is a carved-out entity, a smaller provider, or a special purpose vehicle without deep reserves. In a carve-out, the buyer sometimes receives services from an entity whose financial strength it has not fully diligenced. The insurance requirement protects the buyer regardless of the seller's balance sheet, because the claim is paid by the insurer rather than the seller alone. This matters most for the high consequence risks that sit above or near the liability cap.

Insurance also disciplines the seller's behavior. A seller carrying meaningful cyber and professional indemnity coverage has an insurer with an interest in the seller's controls and conduct. The buyer benefits indirectly from that oversight. The insurance clause and the liability cap are two halves of the same protection, and the buyer should negotiate them together. How the cap is sized is covered in TSA liability cap negotiation.

Section 02

The coverages that matter.

The first coverage is cyber and data breach insurance. Where the TSA involves shared systems, data processing, or the seller's access to buyer data, a breach can produce regulatory fines, notification costs, and third party claims that exceed any fee based cap. Cyber coverage is the single most important policy for a TSA that touches data, and the buyer should require limits sized to the realistic cost of a breach, not a token figure.

The second is professional indemnity, sometimes called errors and omissions, which covers loss caused by the seller's negligent performance of the services. The third is general liability, covering bodily injury and property damage where services are delivered on site. The fourth, where relevant, is crime or fidelity coverage protecting against fraud by the seller's personnel, which matters for finance, payroll, and treasury services where the seller handles money.

The buyer should match the required coverages to the services in the catalog. A TSA dominated by IT and data services needs strong cyber and professional indemnity. A TSA covering payroll and treasury needs crime coverage. The buyer should not accept a generic insurance schedule that ignores the actual risk profile of the services. The coverage must map to where the loss could actually arise. How these risks surface in disputes is set out in TSA data protection disputes.

Section 03

Limits, evidence, and the additional insured.

Required limits should be sized against the potential loss, not copied from a template. A cyber limit far below the realistic cost of a breach leaves the buyer exposed exactly where it most needs cover. The buyer should set minimum limits per coverage that reflect the consequence of failure for the specific services, and should require the limits to be maintained for the full term and for a tail period after exit, because claims often surface after the service ends.

Evidence matters as much as the requirement. The buyer should require certificates of insurance at signing and on each renewal, and the right to request the underlying policies where a question arises. A requirement with no evidence mechanism is unenforceable in practice, because the buyer learns the coverage lapsed only when it tries to claim. Certificates on a defined schedule keep the coverage visible throughout the term.

The buyer should consider requiring additional insured status or a waiver of subrogation where appropriate, so the buyer can claim directly under the seller's policy and the insurer cannot pursue the buyer after paying. These mechanics turn the seller's insurance into a protection the buyer can reach rather than a policy the buyer merely hopes exists. They should be confirmed before signing alongside the audit and reporting provisions in TSA audit rights.

Section 04

Where sellers push back.

The first pushback is on limits. The seller argues that the required limits are disproportionate to the fee and that maintaining high cyber limits is expensive. The buyer's counter is that the limit should reflect the loss, not the fee, and that the seller already carries insurance for its own operations. The buyer is asking the seller to confirm and evidence coverage it should hold anyway, sized to the risk the TSA actually creates.

The second pushback is on the tail period. Sellers resist maintaining coverage after the TSA ends. The buyer should hold for a tail, because professional indemnity and cyber claims often surface months after the service stops. Coverage that lapses at the term end leaves the buyer exposed for losses that arose during the TSA but became apparent later. A defined tail closes that window.

The third pushback is on evidence and additional insured status. Sellers prefer to assert coverage rather than evidence it, and resist naming the buyer as additional insured. The buyer should require certificates on a schedule and pursue additional insured status where the risk justifies it. The cost to the seller is low and the protection to the buyer is real. Settling these mechanics before signing avoids discovering a coverage gap during a claim, which is the same logic that makes pre-signing leverage decisive, as explained in TSA pre-signing leverage.

Section 05

Confirming coverage before Day One.

Insurance is a pre-signing clause because the buyer needs the coverage in place before the seller starts delivering services that could cause loss. A buyer that signs without confirming the seller's coverage is exposed from Day One on every service in the catalog. The clause must be settled, and the certificates received, before the TSA goes live.

The practical sequence is to map the coverages to the services, set limits against potential loss rather than against fees, require certificates at signing and renewal, secure a tail period, and pursue additional insured status where the risk justifies it. Align the insurance clause with the liability cap and carve-outs so the coverage actually backs the liabilities the seller has accepted.

The buyer that confirms coverage before Day One turns the liability cap from a promise into a collectible right. The buyer that signs without checking holds a cap backed by a balance sheet it never examined and a policy it never saw. Insurance is the unglamorous clause that decides whether every other remedy in the contract can actually be paid.

FAQ

Insurance questions buyers ask.

What insurance should a TSA require from the seller?

Match the coverage to the services. A data heavy TSA needs cyber and professional indemnity. On site services need general liability. Finance, payroll, and treasury services need crime or fidelity coverage. The buyer should not accept a generic schedule that ignores the actual risk profile of the catalog.

How high should the insurance limits be?

Sized against the potential loss, not the fee. A cyber limit far below the realistic cost of a breach leaves the buyer exposed where it most needs cover. Set minimum limits per coverage that reflect the consequence of failure, and require them to be maintained for the term and a tail period.

Why require a tail period of coverage after exit?

Because professional indemnity and cyber claims often surface months after a service stops. Coverage that lapses at the term end leaves the buyer exposed for losses that arose during the TSA but became apparent later. A defined tail keeps the seller insured for that window.

How does insurance relate to the liability cap?

The cap is the seller's promise to pay; insurance is what makes the promise collectible. A cap is worth little if the seller lacks the coverage or balance sheet to satisfy a claim. The buyer should negotiate the two together so the coverage actually backs the liabilities the seller has accepted.

Related Reading

More on TSA negotiation.