Does Your Tech E&O Policy Cover What You Promised in the Contract?
Your tech E&O policy covers your negligence, not every promise in your MSA. Here's what typically pays for indemnities, SLA credits, warranties and liquidated damages, and which fixes close the gaps.
Your contract and your policy don't cover the same ground
Your sales team just signed a customer's paper. It includes an uncapped indemnity for data incidents, 99.9% uptime backed by service credits, a warranty that the platform "will perform in accordance with the documentation," and liquidated damages of 1% of fees per day if go-live slips. Your tech E&O policy has a $5 million limit. Whether $5 million is enough is the second question. The first is whether any of those promises are insured.
Often, several aren't. Nearly every technology errors and omissions or professional indemnity wording has some version of a contractual liability exclusion. In tech E&O, the contractual liability exclusion strips out cover for liability you took on by contract beyond what you'd owe under general law anyway. Treat the policy as a backstop for the whole contract and you'll get caught out. It mainly backstops claims that you did the work badly.
How the exclusion reads, and the carve-back that does the heavy lifting
A typical clause excludes "liability assumed by the insured under any contract or agreement, except to the extent the insured would have been liable in the absence of such contract." That exception is the carve-back, and most coverage outcomes turn on it. The adjuster asks two things: did this obligation come from the contract, and would you have been liable without it?
A coding error that corrupts client data, a misconfigured integration, or bad implementation advice usually passes. A duty of reasonable care exists anyway, either in negligence or as a term the law implies into service contracts. What usually fails is anything bigger than the law would impose: fault-free hold-harmless promises, fixed payment amounts, outcome guarantees and fee refunds.
Two things complicate this. First, many modern tech E&O forms affirmatively insure breach of contract arising from your services, then exclude specific items such as warranties, guarantees, penalties, service credits and fee returns. Read the insuring agreement and the exclusions together. Second, jurisdiction changes the test. In common-law markets such as the UK, Australia, Singapore and India, "liability absent the contract" points to tort and implied terms. In civil-law systems such as Germany, France or the UAE, contract is the main source of liability, so wordings written for those markets often refer to liability exceeding what applicable law would impose. Ask your broker which test your form uses.
What typically pays: indemnities, SLA credits, warranties and liquidated damages
The table shows how mainstream tech E&O wordings usually treat common contract promises. Individual policies vary, and endorsements can change any row.
| Contract promise | Typical treatment | Why |
|---|---|---|
| Indemnity for third-party claims caused by your negligent services | Usually covered | You'd owe this liability without the clause |
| Broad indemnity for "any loss" regardless of fault | Covered only to the extent you were actually at fault | The fault-free portion is purely contractual |
| IP infringement indemnity | Varies; often sublimited, and patents frequently excluded | Insurers price IP risk separately |
| SLA service credits | Usually excluded | Agreed price adjustments, not damages |
| Express warranties or performance guarantees | Excluded beyond negligent breach | Guarantees of results go further than a duty of care |
| Liquidated damages | Excluded, or covered only up to provable actual loss | Fixed sums aren't tied to fault or loss |
| Refund or credit of your own fees | Usually excluded | Return of revenue isn't treated as loss |
The pattern is consistent: indemnity coverage follows fault and loss, not contract wording. SLA credits rarely count as professional liability because they're a price mechanism, not compensation for harm.
Four hypothetical claims and how they usually play out
The payroll miscalculation
Say a 60-person payroll SaaS vendor in Singapore pushes an update that miscalculates employer contributions. A client spends $400,000 on corrections and claims it back. This is classic negligent performance, so it typically pays, subject to the retention and any exclusion for fines the client paid.
The missed uptime quarter
The same vendor misses its 99.9% target in one quarter and owes a 15% service credit worth $36,000. That's excluded, and the vendor carries it. If the outage also caused the client provable losses through negligence, the client's damages claim could still be covered.
The late implementation
A systems integrator in Germany agrees to liquidated damages of $5,000 per day and delivers 40 days late: $200,000. If the integrator's negligence caused the delay, the insurer may pay up to the client's provable loss, which could be well under $200,000. If the delay came from client scope changes, or from understaffing with no actual error, expect little or nothing.
The no-fault security indemnity
A UK managed service provider agreed to indemnify a client for "any losses arising from a security incident." The client's own employee falls for a phishing email. The MSP did nothing wrong, so only the contract triggers the indemnity, and it's excluded. Some wordings fund defense costs until coverage is decided. The indemnity itself stays uninsured, and the MSP's cyber policy probably won't pick it up either.
Why the limitation of liability clause matters more than the policy limit
Your policy can only respond to what your contract exposes you to. A well-drafted limitation of liability clause, for example a cap at 12 months' fees with consequential loss excluded, keeps most claims inside your insured limit. Carve-outs undo that. Uncapped liability for data protection, confidentiality or IP can quickly push exposure past both the cap and the policy.
Local law also limits what a cap can achieve. German standard-terms rules generally don't let you exclude liability for intent or gross negligence. UK unfair contract terms legislation applies a reasonableness test. Indian courts can award reasonable compensation up to a stated sum rather than automatically the full amount. UAE civil law lets courts adjust agreed compensation toward actual loss. A cap that looks solid on paper may not hold. Many buyers now negotiate a separate "super-cap" for data incidents, commonly a multiple of annual fees, and size their E&O and cyber limits to match it.
Policy wording fixes to raise with your broker
- Indemnity carve-back: affirmative cover for indemnities in written client contracts, to the extent the underlying claim arises from your wrongful act.
- Narrower warranty exclusion: limit it to express guarantees of results, cost estimates and delivery dates. A blanket exclusion for "any warranty" is too broad.
- Liquidated damages exclusion amendment: cover up to the amount you'd have owed as ordinary damages. Some carriers will also offer a dedicated sublimit.
- Damages definition: confirm it includes defense costs you've contractually agreed to pay for the client.
- Service credits: rarely insurable. A few markets offer small sublimits, but budget for credits as an operating cost.
For clean risks, some of these endorsements come at little or no extra premium. A meaningful liquidated damages sublimit more often adds a noticeable percentage to premium. Treat any figure as a typical 2026 market range that varies by contract and region, and confirm with your broker. Revenue, the size of your largest contracts, claims history and a disciplined contract review process move the price most. Send your five largest MSAs with the submission, because underwriters price unknown contract terms conservatively.
Contract fixes to raise with your lawyer before the next signature
- Tie every indemnity to fault: "to the extent caused by the supplier's breach or negligence."
- Make service credits the sole and exclusive remedy for availability failures.
- Draft liquidated damages as a genuine pre-estimate of loss, capped, and the exclusive remedy for delay.
- Use "reasonable skill and care" instead of fitness-for-purpose or outcome guarantees.
- Align the liability cap and any super-cap with your E&O and cyber limits, and exclude consequential loss.
- Add an insurance checkpoint to your contract playbook so non-standard indemnities go to the broker before signature.
Use one rule. If a clause makes you pay without proof of your fault, or more than provable loss, treat it as self-insured unless an endorsement explicitly says otherwise. Then either price that exposure into the deal or negotiate the clause out. Before signing any material contract, have a licensed broker and qualified counsel in the relevant jurisdiction review both documents together.
Questions buyers ask
Does tech E&O cover breach of contract claims at all?
Often yes, when the breach consists of failing to perform your services with reasonable care. Many wordings affirmatively cover breach of contract arising from technology services, then exclude specific items such as guarantees, liquidated damages, service credits and fee refunds.
Will my policy pay SLA credits I owe a customer?
Usually not. Insurers treat service credits as an agreed price reduction, not damages caused by a wrongful act. A few markets offer small sublimits, but most buyers should budget for credits as an operating cost and make them the exclusive remedy for downtime.
Is a liquidated damages clause always uninsured?
Not always. Many policies will pay up to the amount you'd have owed as ordinary damages for negligent performance. The portion above provable loss, or any amount triggered without fault, is typically excluded unless you buy a specific endorsement.
Should my policy limit match my contractual liability cap?
Your limit should at least cover your realistic maximum exposure across your largest contracts, including any super-caps or uncapped carve-outs. A limit below your biggest cap leaves a known gap. One policy limit is also usually shared across all claims in the policy period.
Do customers' insurance requirements in the contract change my coverage?
No. A contract requiring you to carry tech E&O with certain terms doesn't change what your policy says. If a customer requires cover for contractual indemnities or names itself as an additional insured, confirm with your broker that your wording actually provides this before you sign.
Written by the Armorinsurecorp editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.