Will Your IT Firm's Professional Indemnity Policy Pay for a Failed Project?
A client says your late or buggy implementation cost it millions. Whether your PI or tech E&O policy pays turns on a few words: negligence, contract, fees. Here's how to read them before a claim lands.
The short answer: it pays for your mistakes, not your promises
A client's ERP migration goes live four months late and corrupts its order data. The client withholds the final invoice, demands back the fees it has already paid and sends a letter claiming lost revenue. Your board has one question: will the insurance pay?
Some of it, usually. Rarely all of it. Professional indemnity insurance for IT companies covers legal liability that comes from a professional mistake, meaning a negligent act, error or omission in the work you delivered. It doesn't guarantee that you'll deliver what you sold, on time and on budget. So the claim gets split. Damages caused by negligent work are usually covered. Your fees, contractual penalties and the cost of finishing the job often aren't.
How big each piece is depends on three things: how the policy defines a covered claim, which exclusions it carries and what your client contract says. We take each in turn below, then look at how wordings differ in the UK, the EU, India, Australia and other markets.
Negligence claims versus pure breach-of-contract claims
Insurers sort client claims into two groups, and you need to know which group yours is in.
A negligence claim alleges you didn't use the skill and care a competent IT professional would. You designed a data migration without validation checks, misconfigured access controls or missed a known integration dependency. The client doesn't have to prove you broke a specific promise. It only has to show that your work fell below a professional standard and caused loss.
A pure breach of contract claim alleges you didn't do what the contract said, careless or not. You missed the go-live date. The system misses the agreed response time. Module four never arrived. A failure to perform claim like this can succeed even when every engineer on the project did competent work, because the problem was the commitment, not the care.
Most real disputes are a mix. Late delivery usually gets blamed on bad planning or bad code, and that allegation is what brings the policy into play. Claimants' lawyers know this, so they often plead negligence alongside breach. When you notify, your broker and coverage counsel should make sure the negligence allegations are clearly identified, because that's the part the insurer is there to answer.
The exclusions that decide what gets paid
A policy can have broad insuring clauses and still get cut down by its exclusions. These are the ones that matter most in failed-project claims:
- Contractual liability exclusion. This removes liability you took on by contract beyond what you'd owe under general law. Indemnities, hold-harmless clauses and uncapped promises are the usual targets. Better wordings write cover back in where the liability would have existed without the contract.
- Failure to perform or delay. Common in tech E&O wordings, especially North American and London-market forms. It excludes claims for not delivering on time or to specification, usually with a carve-back where the failure came from a negligent act, error or omission.
- Fee return or restitution. Close to standard everywhere. The policy won't refund fees the client paid you or make up fees the client refuses to pay. Insurers see that money as yours to give back, not as a loss you caused.
- Liquidated damages, penalties and service credits. Usually excluded unless the same amount would have been owed as damages at law.
- Guarantees and warranties. Explicit performance, cost or timing guarantees are typically out.
- Cost estimates. Some wordings exclude claims that a project overran your quoted budget.
- Rectification of your own work. Fixing your own defects is often excluded. Some policies add a limited mitigation-costs extension that pays to stop a bigger claim from developing.
Defense costs are handled separately. Many policies defend the whole claim while coverage is in doubt and allocate costs later. Check whether defense costs sit inside the limit or on top of it. That one detail can decide whether a mid-size claim exhausts your cover.
A worked example: the late ERP rollout
This is a hypothetical. A 60-person consultancy signs an $800,000 fixed-fee ERP implementation with a distributor. Go-live is five months late, and errors in the migrated inventory data cause six weeks of failed shipments. The distributor terminates, hires another vendor and claims $2.4 million. Here's how a typical PI policy with a $5 million limit and a $25,000 deductible would likely treat each part:
| Claim component | Amount claimed | Likely policy response | Why |
|---|---|---|---|
| Return of fees paid | $600,000 | Not covered | Fee return exclusion |
| Liquidated damages for delay | $400,000 | Usually not covered | Contractual penalty, owed only because of the LD clause |
| Replacement vendor's remediation costs | $500,000 | Likely covered | Loss caused by negligent migration design |
| Lost profit from failed shipments | $900,000 | Within policy scope, but may be blocked by the contract | Negligence-caused loss; a consequential-loss exclusion in the contract may defeat this head of claim |
| Defense costs | $150,000–$300,000 | Generally covered | Triggered by allegations of negligence |
On paper, about $1 million of the $2.4 million (the fee refund plus the liquidated damages) stays with the consultancy. Now suppose the contract had capped liability at fees paid and excluded lost profits. The client's recoverable claim shrinks sharply before the insurer is even involved. Your contract sets your real exposure well before the policy limit does.
How UK, EU, Indian and Australian wordings differ
The same failed project can land very differently depending on where the policy was written. The table shows general market tendencies, not rules. Individual insurers often deviate from them.
| Market | Typical insuring basis | Contract claims | Points to watch |
|---|---|---|---|
| United Kingdom (incl. Lloyd's) | Civil liability | Broad; breach of contract can be covered if it arises from professional services | Contractual liability exclusion still removes liability beyond common law; fee return excluded |
| Germany and German-speaking EU | Statutory liability for financial loss (IT-Haftpflicht / Vermögensschadenhaftpflicht) | Claims for performance itself (Erfüllungsansprüche) excluded; damages beyond performance covered | Rework, delay and substitute-performance claims often sit outside the cover |
| France and wider EU | Civil liability (e.g. RC Professionnelle) | Varies widely by insurer | Check cover for contractual penalties and whether jurisdiction limits fit cross-border clients |
| India | Often negligent act, error or omission | Often narrower; pure contractual breach frequently excluded | Large clients may set high contractual PI minimums; limits for domestic and overseas work can differ |
| Australia | Civil liability | Broad, with a contractual liability exclusion | Statutory consumer-law and misleading-conduct claims; confirm whether these are covered |
Elsewhere, including the Gulf states, Singapore and Latin America, larger placements often use London-market or multinational insurer wordings, while local insurers' own forms vary a lot. Some countries also require cover to be written by a locally licensed insurer, with the risk reinsured abroad. Ask for the full policy wording, not a summary sheet, wherever you buy.
The biggest risk for firms selling across borders is a mismatch: a narrow negligence-only wording sitting behind a master services agreement full of performance commitments drafted under another country's law. If most of your revenue comes from foreign clients, ask your broker whether a global program or a London-market tech PI placement fits better than a domestic policy.
Where your own contract undermines your cover
Insurers price PI insurance for software developers on the assumption that you'll only owe what the law would make you owe anyway. Every clause that pushes your liability past that line is exposure you carry yourself. The worst offenders:
- Uncapped indemnities for any breach, not just third-party IP or data claims.
- Liability caps set at a multiple of contract value that exceeds your policy limit, or caps that carve out "data loss" entirely.
- Fitness-for-purpose promises ("the system will reduce processing time by 40%") instead of a duty of reasonable skill and care.
- Liquidated damages with no overall ceiling.
- No mutual exclusion of indirect and consequential loss.
For most mid-size IT firms, the most valuable risk control isn't a bigger limit. It's a contract template that caps liability at around one to two times the fees under the contract, excludes lost profits and limits your duty to reasonable skill and care. Some brokers and insurers will review your standard template at renewal. Ask, because it costs you nothing and shows the underwriter you manage contract risk.
What cover costs and what moves the premium
IT consultant indemnity cover is priced mainly on revenue, type of service, contract size and claims history. The figures below are typical 2026 market ranges. They vary by contract, country and insurer:
| Firm profile | Typical limit | Indicative annual premium (USD) | Typical deductible |
|---|---|---|---|
| Freelancer or micro consultancy, revenue under $1M | $1M | $800–$4,000 | $1,000–$5,000 |
| Software or services firm, $5M–$20M revenue | $2M–$5M | $8,000–$50,000 | $10,000–$50,000 |
| Systems integrator, $50M+ revenue, large implementations | $10M+ (often layered) | $60,000–$250,000+ | $50,000–$250,000 |
Premiums climb fastest for ERP, payments, healthcare and financial-services implementations, for fixed-price work and when a single contract makes up a large share of revenue. Bundling tech E&O with cyber is common and can be cheaper. The catch is a shared aggregate: one data breach can use up the limit you need for a failed project. Confirm pricing with brokers and insurers in your market, since local rates and minimum premiums differ widely.
Red flags to check before renewal
Pull out the current wording and look for these:
- A failure to perform or delay exclusion with no negligence carve-back.
- A contractual liability exclusion with no carve-back for liability that would exist at law anyway.
- A definition of "professional services" that doesn't match what you sell. Managed services, cloud hosting and AI model development are sometimes left out or have to be named specifically.
- No mitigation or rectification-costs extension, or one with a token sublimit.
- Defense costs inside the limit when your typical contract value is close to that limit.
- A retroactive date later than the start of your oldest live client project.
- Territorial or jurisdiction limits that exclude countries where your clients sign contracts or could sue.
- A shared cyber and E&O aggregate with no separate or reinstated limit.
Any one of these can turn a covered negligence claim into a dispute with your own insurer.
What to do the day a client says the project failed
Cover is often lost through how a claim is handled, not because of the wording. Follow this sequence:
- Notify early. PI is almost always written on a claims-made basis. A formal complaint, a payment withheld alongside criticism of your work or a threat of legal action is usually a notifiable circumstance. Late notice is a frequent reason claims get declined.
- Don't admit liability, offer refunds or start free rework without the insurer's consent. Most policies prohibit it.
- Preserve the record. Keep change requests, sign-offs, evidence of client-caused delays and test results. Proof that the client changed scope is often your strongest defense.
- Separate the heads of loss with your broker: fees, penalties, remediation, consequential loss. That shows early which parts are insured.
- Bring in coverage counsel if the insurer reserves its rights on a large part of the claim. A licensed broker or lawyer in your jurisdiction should guide those decisions.
The decision rule is simple. If a client dispute includes any suggestion that your work was technically deficient, notify it. An unnecessary notification costs you close to nothing. Missing a covered claim can cost you the whole loss.
Questions buyers ask
Does professional indemnity insurance cover a project that was simply late?
Usually only if the delay came from a negligent act, error or omission, such as poor design or faulty code. Delay caused by under-resourcing or a missed commitment, with no professional error, is often excluded as a failure to perform. Liquidated damages for the delay are also typically excluded.
Will my insurer refund fees a client demands back?
Almost never. Fee return or restitution exclusions are close to standard across markets, because insurers treat your fees as money you were paid for work, not a loss you caused. The policy may still cover damages beyond the fees, such as a replacement vendor's remediation costs.
Is tech E&O the same as professional indemnity?
They cover the same core risk: liability for errors in professional technology services. 'Tech E&O' is the usual term in North American and some London-market wordings, while 'professional indemnity' is common in the UK, Europe, India, Australia and much of Asia. Wordings differ, so compare the insuring clause and exclusions, not the product name.
How much cover should an IT services firm buy?
Start from your largest typical contract value and your standard liability cap, then add a margin for defense costs if they sit inside the limit. Many clients also set minimum PI requirements in their contracts, and those minimums tend to rise with project size and sector risk. A broker can test your limits against your actual contract portfolio.
Can I fix my own defective work and claim the cost?
Generally not. Rectifying your own work is usually excluded. Some policies include a mitigation-costs extension that pays for fixes that reduce a larger likely claim, typically with insurer consent and a sublimit. Check whether your wording has one before you start rework.
Written by the Auditvault Pro editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.