---
title: "Failed IT project claims and PI: what is covered"
description: "A late IT project, a withheld invoice and a counterclaim. How the claim is argued, what technology PI does with each demand, and what to do first."
url: "https://www.hammondpi.com/insights/it-project-failure-claims-pi/"
updated: "2026-11-20T06:10:05.445Z"
---

[Home](https://www.hammondpi.com/index.md) / [Insights](https://www.hammondpi.com/insights.md) / The failed IT project: how the claim is argued and what PI covers

Insights for IT consultants

# The failed IT project: how the claim is argued and what PI covers

Most technology claims start the same way. A project runs late, the client stops paying and each side blames the other. The letter that follows mixes several demands, and a technology PI policy can treat each of them differently.

How it startsThe argumentsThe demandsWhat to doBefore you signHow we help

Guidance only. Cover depends on your own policy wording; speak to us about your position.

## How a project dispute becomes a claim

A technology claim rarely begins with a solicitor’s letter. It begins with a missed milestone, a defect list and an invoice the client will not pay. By the time anyone uses the word “claim”, months of emails have been written and positions taken.

The law implies only that a service is performed with reasonable care and skill ([Supply of Goods and Services Act 1982, section 13](https://www.legislation.gov.uk/ukpga/1982/29/section/13)). IT contracts usually promise more: a specification, a go-live date, a system fit for its purpose. A client can then allege breach of contract without showing that anyone was careless.

In [Topalsson v Rolls-Royce Motor Cars \[2023\] EWHC 1765 (TCC)](https://caselaw.nationalarchives.gov.uk/ewhc/tcc/2023/1765) the contract said time was of the essence for the supplier’s delivery dates. Missed go-live dates under the agreed plan entitled the customer to terminate, and damages of over €7 million were reduced to the contract’s €5 million cap.

## How each side argues it

The client says the system does not meet the specification, the dates were missed and it was entitled to stop paying or to terminate. The supplier says the client caused the delay with late data, changed requirements and slow approvals, that the “defects” are change requests, and that the fees are due. Three things usually decide which account prevails.

-   **Documents written at the time.** The specification, change requests, test results and acceptance sign offs carry more weight than anyone’s recollection.
-   **The notice clauses.** In [Disclosure and Barring Service v Tata Consultancy Services \[2025\] EWCA Civ 380](https://caselaw.nationalarchives.gov.uk/ewca/civ/2025/380) the customer lost a claim to delay payments of £1.592 million because it had not first issued the non-conformance report the contract required. The judgment records that most of the supplier’s own delay claims had fallen at its own notice clause.
-   **What was said to win the work.** In [BSkyB v HP Enterprise Services \[2010\] EWHC 86 (TCC)](https://caselaw.nationalarchives.gov.uk/ewhc/tcc/2010/86) the supplier was found to have made fraudulent representations about delivery time when bidding. Bid documents are read as closely as the code.

## One letter, six demands

The letter that finally arrives usually mixes several demands. Separating them is the first job, because a technology PI wording can treat each one differently.

The demands in a failed IT project claim and how technology PI wordings usually treat each

Demand

How technology PI wordings usually treat it

Your unpaid invoices

Not a claim against you, so not the main cover. Some technology wordings can pay fees you agree to waive where that settles a threatened claim larger than the fees.

Refund of fees already paid

Wordings can exclude the return of fees. Check yours before offering money back.

Liquidated damages for delay

Commonly excluded to the extent they exceed the damages the law would award. Part of the demand may be yours.

The client’s own loss from delay or defects

The core of the cover, provided the wording includes breach of contract over deliverables and the duty breached is not more onerous than the law would imply.

The cost of a replacement supplier

Claimed as damages. Insurers will test it against what the law would award and against the liability cap in your contract.

Free rework you have offered

Wordings can exclude the cost of redoing your own work, unless insurers agree it in advance as mitigation of a larger claim.

Liquidated damages deserve particular care. In [Triple Point Technology v PTT \[2021\] UKSC 29](https://caselaw.nationalarchives.gov.uk/uksc/2021/29) the Supreme Court held that delay damages of 0.1% of the undelivered work for each day ran up to termination, even though the work was never finished.

## What to do when the invoice is withheld

1.  Tell us before you chase the debt. A letter before action for the fees usually draws the counterclaim, and wordings can treat a client’s refusal to pay after a complaint as a circumstance that must be notified. We put it to insurers first.
2.  Read the contract’s notice clauses the same day. If relief for client caused delay depends on a notice, send it in the form and to the address the contract requires.
3.  Assemble the record: specification, plan, change requests, test results, acceptance sign offs and the correspondence about delay.
4.  Separate the demands as in the table above, so insurers can see what is likely to be covered and you know early what may not be.
5.  Agree nothing alone. A credit note, a recovery plan or free remedial work offered without insurers’ consent can be treated as an admission.

## Terms that shape the claim before the project starts

Most of the argument above is settled by the contract, long before anything goes wrong. These are the terms we look at first.

-   **Dates.** Whether time is of the essence, and what follows from a missed milestone.
-   **Delay damages.** The rate, any cap on them, and whether they are the client’s only remedy for delay.
-   **Acceptance.** Objective acceptance criteria, and what happens if the client uses the system without signing it off.
-   **Client duties.** What the client must supply and by when, and the notice you must give to claim relief if it does not.
-   **The liability cap.** What it is, and what sits outside it.

Send us the draft before you sign and we will flag the insurance points. [Contract reviews](https://www.hammondpi.com/contract-reviews.md)

## Where a specialist broker comes in

Hammond PI has specialised in professional indemnity since 1990. For a technology business we read the wording itself: the breach of contract cover, the contractual liability exclusion, liquidated damages, unpaid fees and rectification costs. When a project turns into a dispute we put the matter to insurers, gather what they need and stay involved with the claims handler until it is resolved. [How we support claims](https://www.hammondpi.com/claims-support.md)

## Client withholding an invoice?

Tell us before you chase it, so the dispute is notified properly and handled as one matter.

[Speak to a PI specialist](https://www.hammondpi.com/contact.md)[PI for IT consultants](https://www.hammondpi.com/who-we-cover/it-consultants.md)

Related: [PI for IT consultants](https://www.hammondpi.com/who-we-cover/it-consultants.md) · [Claims support](https://www.hammondpi.com/claims-support.md) · [Contract reviews](https://www.hammondpi.com/contract-reviews.md)
