---
title: "Professional indemnity broker for IT and technology consultants"
description: "Specialist professional indemnity insurance broker for IT and technology consultants. Hammond PI, PI brokers since 1990. FCA FRN 302911."
url: "https://www.hammondpi.com/who-we-cover/it-consultants/"
updated: "2026-11-20T00:25:30.517Z"
---

[Home](https://www.hammondpi.com/index.md) / [Who we cover](https://www.hammondpi.com/who-we-cover.md) / IT and technology consultants

IT and technology consultants

# Professional indemnity for IT and technology consultants

Technology PI, read clause by clause by specialist brokers. We know where IT claims start: the missed go-live, the withheld invoice, the indemnity in the client’s contract. We know how technology wordings differ on breach of contract, intellectual property and data.

[Speak to a PI specialist](https://www.hammondpi.com/contact.md)[Send us your renewal for review](https://www.hammondpi.com/renewal.md)[Get a quote](https://www.hammondpi.com/quote/?profession=it-consultants.md)

-   **Since 1990**Specialist PI brokers
-   **30+ insurers**Plus specialist agencies and Lloyd’s
-   **4.9 out of 5**From 228 Google reviews
-   **FCA authorised**FRN 302911, independently owned

On this page

-   Your map
-   Our experience
-   Who requires PI
-   Claim scenarios
-   Inside the wording
-   Contract and law
-   Specialist work
-   Your presentation
-   Business changes
-   Cyber and liability
-   Questions
-   Forms and claims

Your map

## The IT and technology consultants map: from your work to the policy and beyond

Your business’s work on one side, the policy on the other. Select a point to see what it connects to, then follow the link to the part of this page that explains it.

Still 3D render (motion off)

### The map, area by area

Each heading below is one area of the map, and the number shows how many points it holds. Open a heading and tap any point: it lights up on the map with everything it connects to, and a short note explains why.

### Practice and business risks 9

-   
-   
-   
-   
-   
-   
-   
-   
-   

### Your terms and framework agreements 7

-   
-   
-   
-   
-   
-   
-   

### Engagements and contracts 5

-   
-   
-   
-   
-   

### Legislation 1

-   

### Policy documents and schedule 10

-   
-   
-   
-   
-   
-   
-   
-   
-   
-   

### Main policy wording 7

-   
-   
-   
-   
-   
-   
-   

### Exclusions and restrictions 1

-   

### Succession, closure and earlier work 4

-   
-   
-   
-   

### Other insurance and final assessment 8

-   
-   
-   
-   
-   
-   
-   
-

Our experience

## Why IT consultants come to a specialist

Two businesses with the same turnover can need very different cover. Advice, bespoke development, systems integration, managed services and contracting through an agency carry different promises. The contract you sign, the liability cap, the client’s dependence on the system, AI tools and offshore developers change the picture again.

Hammond PI has specialised in professional indemnity since 1990. We read the wording itself: how each insurer treats breach of contract, liability assumed under contract, liquidated damages, intellectual property, data and cyber exclusions, sub-contractors and unpaid fees. Then we present your business so insurers underwrite the work you actually do and the contracts you actually sign.

When a problem arises we stay involved. We put the matter to insurers, gather what they need and follow it through with the claims handler.

1.  **The work**Advice, development, integration, support and managed services, and the contract behind each
2.  **What can go wrong**Missed go-lives, defective code, outages, exposed data, ownership disputes and withheld fees
3.  **What the policy must answer**Breach of contract, contractual liability, intellectual property, data, sub-contractors, limits and past work
4.  **How we present it**A clear submission, contracts explained, questions answered and wordings compared across insurers

Who requires PI

## No professional body sets your PI minimum. Your contracts do

No regulator or professional body sets a PI minimum for IT work. The requirement comes from the contract.

PI requirements: Who requires PI

Who

Minimum cover

Excess

After you stop

Other conditions

G-Cloud 15, Government Commercial Agency (formerly Crown Commercial Service)

At least £1 million of PI for Lots 1a, 2a, 2b and 3 (cloud hosting, software and cloud support). Lot 1b, hosting above OFFICIAL, requires at least £50 million. Basis: for a single event or a series of related events and in the aggregate.

No figure set. The supplier bears any excess and cannot recover it from the buyer.

PI must be maintained for at least six years after the End Date.

Insurers of good financial standing and repute. Public liability of £1 million (£20 million for Lot 1b) and employers’ liability of £5 million are also required. Evidence is due at the start and within 15 working days of each renewal. A buyer can add insurances in its order form.

Digital Outcomes and Specialists 7, Government Commercial Agency

Call-off contracts under Lots 1, 3 and 4 need at least £1 million of PI, and the buyer can raise it. Lot 2 suppliers (digital capability and delivery partners) must hold at least £5 million from the framework start. Basis: for a single event or a series of related events and in the aggregate.

No figure set. The supplier bears any excess and cannot recover it from the buyer.

PI must be maintained for at least six years after the End Date.

Public liability to the same figure as PI. Employers’ liability of £5 million unless the supplier has no employees. The supplier must give five working days’ notice before any insurance is cancelled or not renewed.

Government Model Services Contract (contracts over £20 million)

No fixed figure. PI is an additional insurance the authority can require, with the scope and level set for each contract. Basis: set by the authority for each contract.

The supplier bears any excess and cannot recover it from the authority.

Not specified for PI. The authority sets the period of insurance.

Insurers must be of good financial standing and appropriately regulated. Evidence is due at the start and within 15 working days of each renewal. Claims above a set threshold must be reported to the authority within 20 working days.

Client, agency and umbrella contracts

No standard figure. IPSE notes that clients may require a certain level of cover as a contractual requirement, so the insurance clause in each contract sets your minimum for that engagement. Basis: whatever the contract says. Check whether it asks for cover for each claim or in the aggregate.

Whatever the contract says. Check for a maximum excess.

Whatever the contract says. Look for a clause requiring cover to continue after the engagement ends.

Check whose name the policy must be in, whether the client or agency must be noted on it, and what evidence you must provide before you start.

Sources: [G-Cloud 15 (Joint Schedule 3 v1.0, framework RM1557.15)](https://www.gca.gov.uk/agreements/RM1557.15), [Digital Outcomes 7 (Joint Schedule 3 v1.0, framework RM1043.9)](https://www.gca.gov.uk/agreements/RM1043.9), [Model Services Contract (version 2.2A, September 2025)](https://www.gov.uk/government/publications/model-services-contract), [Client and agency (IPSE guide, read November 2026)](https://www.ipse.co.uk/advice/guide-to-freelancer-and-contractor-insurance). Businesses answering to more than one must meet each set of rules.

A minimum is not a recommendation. Many businesses need more, and cover for each and every claim can protect better than an aggregate limit.

Why the minimum is rarely the right limit

A contract minimum is set by the buyer for its own procurement, not for your exposure. Your limit should follow your largest realistic claim: what the client loses if the system fails, the liability cap you agreed in each contract, how many clients one faulty release or one compromised tool could reach, and whether defence costs sit inside the limit. A framework minimum expressed in the aggregate can be used up by one claim.

Claim scenarios

## When a claim arrives: how we would handle it

Situations IT consultants face, the risk hidden in each, and the strategy we would follow from the first letter. Choose a scenario.

### The client stops paying and says the system does not work

The situationYour business is eight months into a fixed price CRM implementation. The client withholds the last two milestone invoices, £90,000 in all, lists defects it says make the system unusable, and warns that its own losses are far higher than the unpaid fees.

The riskTreating it as debt collection. A letter before action for the fees usually draws a counterclaim, and by then insurers may say they should have been told sooner. Technology wordings can list a client refusing to pay after a complaint as a circumstance you must notify.

Our strategy

1.  Notify insurers now as a circumstance, before any demand for payment goes out, setting out the complaint, the defects alleged and the sums the client says it has lost.
2.  Hold back the letter before action. Chasing the debt first can turn a fee dispute into a counterclaim that insurers had no chance to manage.
3.  Assemble the specification, change requests, test results and acceptance sign offs, because the defence usually turns on what was agreed and what the client approved.
4.  Check for an unpaid fees clause. Some technology wordings can pay fees you agree to waive where that settles a threatened claim larger than the fees.
5.  Agree any commercial deal, such as a credit note or free remedial work, with insurers in writing first, so it is not an admission made without consent.

What we aim forThe dispute handled as one matter, the counterclaim defended at insurers’ cost if it comes, and any fee compromise made with insurers’ agreement.

The lesson**An unpaid invoice after a complaint is an early warning of a claim. Tell us before you chase it.**

### Go-live is missed and the client claims liquidated damages and terminates

The situationYour consultancy is integrating a warehouse system for a retailer. Go-live slips by ten weeks. The contract carries liquidated damages for each week of delay. The client serves a termination notice, claims the liquidated damages and says it will recover the cost of a replacement supplier.

The riskAssuming the whole claim is insured. PI wordings commonly exclude liquidated damages and penalties to the extent they exceed what the law would award, so part of the demand may be yours. The contract may also require prompt delay notices that nobody sent.

Our strategy

1.  Notify insurers when the first formal delay letter arrives, not when termination follows, and send the contract, the plan and the correspondence.
2.  Check the contract’s notice clauses at once. Where a notice is a condition of relief, as the Court of Appeal held in a 2025 technology dispute, a late notice can lose the point.
3.  Separate the heads of claim: liquidated damages, the client’s actual loss from delay, and replacement costs. Insurers will look at each differently.
4.  Record client caused delay, such as late data, changed requirements and missed approvals, from documents written at the time.
5.  Do not agree a recovery plan, a credit or extra free work without insurers’ consent, because concessions can be treated as admissions.

What we aim forThe insurable loss identified and defended, the uninsured contractual element known early, and no breach of the policy conditions.

The lesson**Liquidated damages are easy to sign and hard to insure. Show us the clause before you agree it.**

### A change you made leaves a client’s customer data exposed

The situationYour managed service team changes a firewall rule during a migration. A storage bucket holding the client’s customer records is left open for three weeks. The client demands its investigation costs, the cost of notifying customers and an indemnity for any compensation claims.

The riskThree traps. PI wordings can exclude claims arising from breaches of data protection law. The contract indemnity may go further than negligence. And as a processor you must tell the controller without undue delay, which tempts staff into written apologies that read as admissions.

Our strategy

1.  Notify insurers the day the exposure is found, before the client’s formal demand, with the change record and the timeline.
2.  Give the client the facts it needs promptly, as UK GDPR requires of a processor, but keep to what happened and what has been fixed. No apology letters and no acceptance of liability.
3.  Read the data and cyber exclusions against the claim. Cover for a client’s loss from your service failure can turn on a few words, so we raise that with insurers at the start.
4.  Compare the indemnity with ordinary damages. The policy may answer the loss the law would award and leave any contractual excess with you.
5.  Preserve logs, tickets and change approvals, and identify any sub-processor involved, because you remain liable to the client for its failures.

What we aim forThe client kept informed without admissions, the coverage question raised at the outset, and the claim defended on what the change actually caused.

The lesson**In a data incident the first email to the client matters as much as the fix. Call us first.**

### A buyer’s due diligence finds GPL code in the product you built

The situationYou built a proprietary platform for a software client under a contract warranting that the code was original and free of third party restrictions. A buyer’s code audit finds a GPL licensed library compiled into it. The sale price is cut and the client blames you.

The riskOffering to rewrite the module free of charge and conceding the warranty. Technology wordings usually cover intellectual property infringement only where it was unintentional, often exclude patents, and can exclude the cost of redoing your own work.

Our strategy

1.  Notify insurers as soon as the audit finding is raised, with the contract warranty and the audit report.
2.  Establish how the library got in: which developer or sub-contractor added it, what your open source policy said, and whether scanning was in place. Insurers will ask whether it was unintentional.
3.  Separate the client’s claimed loss on the sale from the cost of replacing the library. Rework of your own deliverable may sit outside cover.
4.  Check the sub-contractor’s contract for a right of recovery and tell insurers about it, so that right is not lost.
5.  Agree any remedial work with insurers before starting it, so that it is treated as mitigation and not as an admission.

What we aim forThe infringement shown to be unintentional, the client’s loss tested, and any recovery against the sub-contractor preserved.

The lesson**An originality warranty is only as good as your control of what goes into the code.**

### Code written with an AI assistant carries a flaw into production

The situationYour developers use an AI coding assistant. A generated payment routine with a rounding error passes review and goes live in a client’s billing platform. Six months of invoices are wrong, and the client claims the cost of correcting them and its lost revenue.

The riskThe proposal form said all code was written and reviewed in house, and the client contract banned generative AI without consent. Insurers may question the presentation of the risk, and the client will add breach of contract to negligence.

Our strategy

1.  Notify insurers promptly and be open about how the code was produced. An incomplete account now is worse than the fact itself.
2.  Show the controls that did exist: the AI policy, code review records, test coverage and who approved the release. The claim is about the review, not the tool.
3.  Check the wording and endorsements for any AI exclusion or condition, and the description of your business, before insurers raise them.
4.  Deal with the contract breach separately. Use of a tool without consent may not have caused the loss, and causation is where the defence usually lies.
5.  Correct the presentation at once for the current policy and the next renewal, describing the tools used and the checks applied.

What we aim forThe claim handled as a professional error with the AI use fairly explained, and the presentation of the risk put right.

The lesson**Insurers accept AI tools that are described and controlled. Surprises are what cause disputes.**

### A contractor’s script takes down the end client’s systems

The situationYou contract through your own limited company and an agency. A deployment script you wrote takes down the end client’s trading systems for a day. The client claims against the agency, and the agency passes the claim to your company under the indemnity in your contract. The engagement ended two months ago.

The riskYou let the PI policy lapse when the contract ended, or you assumed the agency’s or umbrella’s insurance covered you. PI is claims made, so the policy in force when the claim arrives is the one that counts, and the indemnity may be wider than negligence.

Our strategy

1.  Identify the policy in force today and its retroactive date. If cover lapsed, tell us at once so we can check what reporting rights remain.
2.  Notify insurers of the agency’s letter straight away and do not reply to the agency or the end client on liability.
3.  Read the indemnity you gave. Insurers usually cover what you would owe in law and not extra liability assumed by contract.
4.  Refuse any deduction from your final invoice until insurers agree, because accepting a set off can be an admission.
5.  Gather the change approval, the test evidence and the client’s own release procedure, which may show shared responsibility.

What we aim forThe claim met by a policy in force, the indemnity confined to what the law would award, and no admission through the invoice.

The lesson**Keep PI running after a contract ends. Claims arrive later than invoices.**

### Your offshore sub-contractor’s module fails and the client sues you

The situationYou are prime contractor for a booking platform. An offshore development house you engaged built the payments module. It fails under load at launch and the client claims its lost bookings from you. Your contract with the developer caps its liability at the fees it was paid.

The riskThe cap you agreed. Wordings can exclude or reduce cover where you have signed away insurers’ right to recover from a third party, and some exclude defects in what a third party supplied. Insurers may also say the offshore work was never disclosed.

Our strategy

1.  Notify insurers and send both contracts: yours with the client and yours with the developer.
2.  Show from the renewal file that the sub-contracting, the country and your code review process were disclosed.
3.  Check how the wording treats sub-contractors and third party deliverables, and whether the developer counts as someone you are responsible for under the policy.
4.  Put the developer on notice of the claim promptly and preserve the recovery, limited as it is, in a way insurers approve.
5.  Defend the client’s claim on its merits: load assumptions in the specification, acceptance testing and the client’s own traffic forecasts.

What we aim forCover holds because the arrangement was presented properly, and whatever recovery the sub-contract allows is kept.

The lesson**Show us your sub-contract terms before you sign. A cap you grant can cost you cover.**

Illustrative scenarios. How any real claim is handled depends on the facts, the policy wording and insurers’ agreement.

### Four things IT consultants should know about PI

The date of the work and the date of the claim are different

A claim today may concern code delivered or a system configured several years ago. PI is written on a claims made basis: the policy in force when the claim is made responds, provided the work falls after the retroactive date and nothing was already notified under an earlier policy.

Year 1Year 2Year 3Year 4Year 5

**System goes live****Fault discovered****Client claims**This year’s policy responds

Claims made cover: the policy in force when the claim is made is the one that responds.

A valid notification of circumstances can connect a later claim to an earlier policy. That is why continuity matters when you change insurers or stop a particular service. [How claims made cover works](https://www.hammondpi.com/insights/professional-indemnity-explained.md)

Breach of contract and negligence are not the same thing

The law implies that a service will be carried out 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: that the system will meet a specification, be fit for purpose and arrive by a date. A client can then claim for breach of contract without proving anyone was careless. A PI policy built around negligence may not answer that. Technology wordings usually add cover for breach of contract over deliverables, then take some of it back for duties more onerous than the law would imply. The contract and the wording need reading together.

A liability cap only protects you if it holds

If a client deals on your written standard terms, a clause limiting your liability for breach must be reasonable ([Unfair Contract Terms Act 1977, section 3](https://www.legislation.gov.uk/ukpga/1977/50/section/3)). In judging a cap, the court looks at the resources you could expect to have and how far insurance was open to you, and it is for you to show the clause is reasonable ([section 11](https://www.legislation.gov.uk/ukpga/1977/50/section/11)). So the cap, the policy limit and the size of the contract should make sense together. A cap may not help where the contract carves out negligence or data, or where a separate indemnity sits outside it.

How your limit of indemnity works

Two unrelated covered claims of £750,000 each come to £1.5 million. Under a £1 million limit in the aggregate, the policy pays up to £1 million for the year in total. Under a £1 million limit for each and every claim, each claim has its own £1 million, subject to the policy’s aggregation wording and other terms.

£1 million in the aggregate

Covered £1mNot covered £500k

£1 million each and every claim

Claim 1 £750k

Claim 2 £750k

The same two claims under an aggregate limit and an each and every claim limit.

Then check whether defence costs are paid in addition to the limit or use it up, and when the excess applies.

Inside the wording

## Twelve clauses that decide IT consultants’ claims

Two policies with the same limit can answer the same claim very differently. These are the clauses we read first, what each means for an IT consultant and what we check.

Insuring clause and “professional business”

What it doesCovers civil liability arising from your professional business, usually defined by the description in the schedule and your proposal.

For an IT consultantIf the description says “IT consultancy” but you also host, resell hardware, run managed services or build AI models, claims from that work may be argued to fall outside it.

What we checkThe business description against every revenue stream, including work that started during the year.

Breach of contract and deliverables

What it doesTechnology wordings usually add cover for breach of contract where software or another deliverable fails to meet a written specification, is materially defective, or breaches statutory terms on quality or fitness.

For an IT consultantThis is the cover standard PI wordings often lack. Without it, a claim that a system simply does not do what the contract promised may not be answered.

What we checkThat the clause is there, what counts as a deliverable, and whether services as well as software are included.

Contractual liability, warranties and indemnities

What it doesExcludes liability you take on by contract that is more onerous than the law would impose, including express warranties, guarantees and undertakings.

For an IT consultantClient contracts often carry fitness for purpose warranties and uncapped indemnities for data and intellectual property. The gap between those and ordinary damages can be uninsured.

What we checkHow wide the exclusion is, any write back for liability you would have had anyway, and the contracts you sign most often.

Liquidated damages, service credits and penalties

What it doesExcludes fines, penalties and liquidated damages, usually to the extent they exceed the damages the law would award.

For an IT consultantDelay damages on implementations and service credits on support contracts are routine. The client’s actual loss may be covered while the agreed sum is not.

What we checkThe exact words, whether service credits are caught, and the caps on these sums in your contracts.

Intellectual property

What it doesCovers infringement only within limits. Wordings commonly exclude patents and trade secrets, and cover other infringement only where it was unintentional.

For an IT consultantReused code, open source components, AI generated output and developers bringing code from a former employer are where these claims start.

What we checkPatent and trade secret exclusions, the unintentional test and who must prove it, and territorial limits for overseas clients.

Cyber and data exclusions

What it doesMany PI wordings exclude loss from viruses, hacking, failure of your own systems and breaches of data protection law, on the footing that those risks belong under a cyber policy.

For an IT consultantFor a managed service provider or developer, a client’s claim often has a security or data element. A broad exclusion can remove the claims you most expect.

What we checkWhether the exclusion applies only to your own systems, and what remains for a client’s claim arising from your services.

Sub-contractors and third party products

What it doesWordings differ on work done by others. Some exclude defects in deliverables supplied by a third party, or a third party’s failure to supply.

For an IT consultantOffshore developers, freelancers, resold software and cloud platforms sit behind most projects. The client still claims against you.

What we checkWho counts as an employee, cover for work you sub-contract, third party supply exclusions and any condition about sub-contractors’ own insurance.

Rights of recovery

What it doesInsurers who pay a claim can pursue whoever caused it. Wordings can exclude or restrict cover where you have contracted that right away.

For an IT consultantAccepting a sub-contractor’s or software vendor’s liability cap, or waiving claims against them, can prejudice your own cover.

What we checkThe recovery clause, and the caps in your sub-contracts and supplier terms.

Rectification, recall and refunds

What it doesWordings can exclude the cost of recalling, replacing, repairing or refunding your own services or deliverables, and claims for the return of fees.

For an IT consultantClients often ask first for free rework or their money back. That cost may fall to you unless insurers agree it as mitigation of a larger claim.

What we checkAny mitigation or rectification costs cover, the consent it needs, and how fee refunds are treated.

Unpaid fees

What it doesSome technology wordings can pay fees you agree to waive, where the client is withholding them and threatens a claim for more than the fees.

For an IT consultantUseful where a counterclaim is larger than the invoice. It usually depends on insurers settling the dispute, and the payment can reduce the limit.

What we checkWhether the clause is included, its conditions and how it interacts with the limit.

Notification, circumstances and aggregation

What it doesCover is triggered by a claim or circumstance notified in the period. Related claims from one originating cause can be treated as one claim.

For an IT consultantA run of complaints, a missed milestone or a withheld invoice can each be a circumstance. One faulty release across many clients may be one claim with one limit.

What we checkWhat counts as a circumstance, the time limits, and the aggregation words read with the limit.

Territory, jurisdiction and governing law

What it doesSets where work may be done, where a claim may be brought and under which law, and can restrict arbitration or adjudication.

For an IT consultantA client contract under New York law, or work delivered from an overseas office, can sit outside a policy written for UK work and UK courts.

What we checkGeographical and jurisdiction limits against every client contract with a foreign law or dispute clause.

[The clause guide: how each part of a PI policy works](https://www.hammondpi.com/clauses.md)

Contract and law

## The contract terms and statutes behind technology claims

### In your contracts

-   **Care and skill, or a result.** The law implies 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)). A specification, a fitness for purpose warranty or a fixed date promises a result, and can be breached without negligence.
-   **Limitation clauses.** On your written standard terms, a clause limiting liability for breach must be reasonable. The court considers your resources and the insurance open to you, and you carry the burden of proof (Unfair Contract Terms Act 1977, [section 3](https://www.legislation.gov.uk/ukpga/1977/50/section/3) and [section 11](https://www.legislation.gov.uk/ukpga/1977/50/section/11)).
-   **Delay and notices.** Liquidated damages can run up to termination even if the work is never finished. Where the contract makes a notice a condition of a delay remedy, missing it can lose the remedy ([Disclosure and Barring Service v Tata Consultancy Services \[2025\] EWCA Civ 380](https://caselaw.nationalarchives.gov.uk/ewca/civ/2025/380)).
-   **Time limits.** A claim on a simple contract must be brought within six years of the cause of action arising ([Limitation Act 1980, section 5](https://www.legislation.gov.uk/ukpga/1980/58/section/5)). Negligence claims for latent damage face a fifteen year longstop ([section 14B](https://www.legislation.gov.uk/ukpga/1980/58/section/14B)).

### Statutes that add liability

-   **Personal data.** A processor needs a written contract with set terms and stays fully liable to the controller for its sub-processors ([UK GDPR, Article 28](https://www.legislation.gov.uk/eur/2016/679/article/28)). Individuals can claim compensation from a processor that breaches its own obligations or acts outside instructions ([Article 82](https://www.legislation.gov.uk/eur/2016/679/article/82)).
-   **Who owns the code.** An employer owns copyright in its employees’ work, but a contractor keeps it unless it is assigned in writing and signed (Copyright, Designs and Patents Act 1988, [section 11](https://www.legislation.gov.uk/ukpga/1988/48/section/11) and [section 90](https://www.legislation.gov.uk/ukpga/1988/48/section/90)).
-   **Consumer software.** Digital content supplied to consumers must be of satisfactory quality, fit for purpose and as described, and those rights cannot be excluded. Content that damages a consumer’s device through lack of care must be put right or compensated ([Consumer Rights Act 2015, Part 1, Chapter 3](https://www.legislation.gov.uk/ukpga/2015/15/part/1/chapter/3)).
-   **Managed services.** The Cyber Security and Resilience Bill would bring medium and large managed service providers into regulation, with incident reports to the regulator within 24 and 72 hours, once it is law and in force ([government factsheet, updated 3 November 2026](https://www.gov.uk/government/publications/cyber-security-and-resilience-network-and-information-systems-bill-factsheets/summary-of-the-bill)).

### Court decisions behind these points

\[2010\] EWHC 965 (TCC)

### Kingsway Hall Hotel v Red Sky IT (Hounslow)

Off the shelf hotel software recommended by the supplier was not fit for purpose. The supplier’s standard limitation terms failed the reasonableness test.

[Read the judgment](https://caselaw.nationalarchives.gov.uk/ewhc/tcc/2010/965)

\[2010\] EWHC 86 (TCC)

### BSkyB v HP Enterprise Services (EDS)

The supplier was found to have made fraudulent representations about delivery time when bidding. What is said to win the work can found a claim.

[Read the judgment](https://caselaw.nationalarchives.gov.uk/ewhc/tcc/2010/86)

\[2021\] UKSC 29

### Triple Point Technology v PTT

Liquidated damages for delay ran up to termination of an unfinished software project. A cap carve out for “negligence” covered careless breach of contract.

[Read the judgment](https://caselaw.nationalarchives.gov.uk/uksc/2021/29)

\[2022\] EWCA Civ 440

### Soteria Insurance v IBM United Kingdom

An exclusion of lost profit, revenue and savings did not exclude wasted expenditure after the supplier’s wrongful repudiation. Exclusion clauses are read for what they say.

[Read the judgment](https://caselaw.nationalarchives.gov.uk/ewca/civ/2022/440)

\[2023\] EWHC 1342 (TCC)

### Drax Energy Solutions v Wipro

A limitation clause was read as one aggregate cap for all claims, not a separate cap for each claim. The drafting decides the exposure.

[Read the judgment](https://caselaw.nationalarchives.gov.uk/ewhc/tcc/2023/1342)

\[2023\] EWHC 1765 (TCC)

### Topalsson v Rolls-Royce Motor Cars

Missed go-live dates under an agreed plan entitled the customer to terminate. Damages of over €7 million were reduced to the €5 million contractual cap.

[Read the judgment](https://caselaw.nationalarchives.gov.uk/ewhc/tcc/2023/1765)

These decisions explain where a professional’s duty lies. They do not decide whether a particular policy responds.

Specialist work

## The work that changes your cover

A one line description on a proposal form leaves the important questions unanswered. These are the areas where we ask most, starting with two that are changing the risk now: AI in your delivery and the security of managed services.

AI generated code and model outputs: who checked it, and who owns it?

Most development teams now use AI coding assistants, and data and AI consultancies deliver models whose outputs clients act on. Your business remains responsible for what it delivers, however it was produced.

-   **Review.** Who reviews generated code, how it is tested and who approves the release.
-   **Ownership.** For a computer generated work, the author is the person who made the arrangements for its creation ([Copyright, Designs and Patents Act 1988, section 9](https://www.legislation.gov.uk/ukpga/1988/48/section/9)). Check what your contract warrants about originality.
-   **Third party rights.** The courts are still working through AI and copyright. In [Getty Images v Stability AI \[2025\] EWHC 2863 (Ch)](https://caselaw.nationalarchives.gov.uk/ewhc/ch/2025/2863) the High Court held the model itself was not an infringing copy, but found limited trade mark infringement in generated watermarks.
-   **Client data.** What client code and data staff may put into external tools, and what the client contract allows.
-   **Security.** The government’s [AI Cyber Security Code of Practice](https://www.gov.uk/government/publications/ai-cyber-security-code-of-practice) sets baseline principles for organisations that develop and deploy AI systems.

For insurance, what matters is the service, the allegation, your controls and the wording. We check for any AI exclusion or condition and describe your use of AI to insurers plainly.

Managed services and security: what if your access is the way in?

A managed service provider holds privileged access to many clients at once. A weakness in your remote tools or a careless change can become every client’s incident, and each will look to its contract with you.

-   **Regulation is coming.** The Cyber Security and Resilience Bill would bring medium and large managed service providers into regulation by the Information Commission, with registration, security duties, incident reports within 24 and 72 hours and a duty to tell affected customers. Smaller providers can be designated as critical suppliers (government factsheets on [the Bill](https://www.gov.uk/government/publications/cyber-security-and-resilience-network-and-information-systems-bill-factsheets/summary-of-the-bill) and [managed service providers](https://www.gov.uk/government/publications/cyber-security-and-resilience-network-and-information-systems-bill-factsheets/relevant-managed-service-providers), updated 3 November 2026).
-   **Standards clients will cite.** The voluntary [Software Security Code of Practice](https://www.gov.uk/government/publications/software-security-code-of-practice) sets 14 principles for software vendors.
-   **The policy.** PI wordings often exclude loss from hacking, malware and failure of your own systems. We check what is left for a client’s claim that your service caused its breach.
-   **Aggregation.** One compromised tool across many clients may be one claim with one limit.

Tell us how access is controlled, logged and reviewed. Insurers ask, and good answers change how the risk is seen.

Client contracts: uncapped indemnities and fitness for purpose

Large clients send their own paper. The clauses that matter for PI are the warranties (fit for purpose, free from defects, compliant with all laws), the indemnities (intellectual property, data protection, confidentiality) and what sits outside the liability cap.

PI is written to answer the damages the law would award. Wordings usually exclude liability assumed by contract that goes beyond that. An indemnity can remove the client’s duty to mitigate and the ordinary rules on remoteness, and an uncapped one has no ceiling at all. Send us the draft before you sign. We will tell you which clauses the policy is likely to follow, which it may not, and what to ask the client to change. [How professional indemnity works](https://www.hammondpi.com/insights/professional-indemnity-explained.md)

Liquidated damages and service credits

Implementation contracts often fix a sum for each week of delay, and support contracts give service credits when availability falls short. Both are agreed in advance and payable without proof of loss, which is why insurers treat them differently from damages. Wordings commonly exclude them to the extent they exceed what the client could have recovered in law.

In [Triple Point Technology v PTT \[2021\] UKSC 29](https://caselaw.nationalarchives.gov.uk/uksc/2021/29) the Supreme Court held that liquidated damages for delay ran until the contract was terminated, even though the work was never completed. We ask what the rates are, whether they are capped, whether they are the client’s only remedy for delay, and how often they have been paid.

Intellectual property and open source licences

Clients expect to own what they pay for and to receive it free of other people’s rights. Three things go wrong. Code is reused from an earlier client. A contractor never assigns copyright in writing, so title stays with the contractor ([Copyright, Designs and Patents Act 1988, section 90](https://www.legislation.gov.uk/ukpga/1988/48/section/90)). Or an open source component brings its licence terms into a proprietary product: under the [GNU General Public License version 3](https://opensource.org/license/gpl-3-0), a modified work that is conveyed must be licensed as a whole under the same licence, with its source code.

We ask about your open source policy, scanning tools, contractor agreements and the warranties you give. Wordings usually limit cover to unintentional infringement and often exclude patents.

Sub-contractors, freelancers and offshore developers

If part of the work is done by a freelancer, an offshore development house or a partner firm, the client’s claim still comes to you. Insurers want to know who does the work, in which country, under what contract, with what insurance of their own, and how you review it before release.

Two contract points affect cover. A cap on the sub-contractor’s liability limits what insurers can recover, and some wordings restrict cover where recovery rights have been given away. And if personal data is involved, you remain fully liable to the client for a sub-processor’s failures ([UK GDPR, Article 28](https://www.legislation.gov.uk/eur/2016/679/article/28)). [Freelancers and sub-consultants](https://www.hammondpi.com/insights/freelancers-and-sub-consultants.md)

Acting as a data processor

Hosting, support, testing with live data and analytics usually make you a processor of your client’s personal data. Processors have direct duties. The ICO can take enforcement action against a processor, individuals can claim compensation from one, and a processor must tell the controller of a personal data breach without undue delay ([ICO, what it means if you are a processor](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/controllers-and-processors/controllers-and-processors/what-does-it-mean-if-you-are-a-processor/)).

Client contracts then add an indemnity for data protection breaches, often outside the liability cap. Many PI wordings exclude breaches of data protection law altogether. We read the two together and tell you where the gap is before a claim finds it.

Contracting through an agency or umbrella company

A contractor working through a personal service company usually signs the agency’s terms. Those terms set the insurance you must hold and can include an indemnity to the agency for claims arising from your work. IPSE notes that clients may require a certain level of cover as a contractual requirement ([IPSE, guide to freelancer and contractor insurance](https://www.ipse.co.uk/advice/guide-to-freelancer-and-contractor-insurance)).

Check three things: that the policy is in your company’s name and not only the umbrella’s, that the limit and basis match the contract, and that cover continues after the engagement ends, because PI responds to claims made while the policy is in force. [Run off cover explained](https://www.hammondpi.com/insights/run-off-cover.md)

US and overseas clients

Software crosses borders easily and contracts follow. We look at the entity you contract with, where the work is done, the governing law and where a dispute would be heard. A policy written for the UK may exclude work outside its geographical limits, claims brought in other courts, claims under foreign law and some arbitrations.

North American clients need particular care. Tell us before you sign a contract under US or Canadian law, or one that requires insurance placed in a particular way, so the territorial and jurisdiction terms can be checked first.

Your presentation

## A proposal should explain the work behind the numbers

An unexplained label can make a modest exposure look broader than it is, while a vague one can hide an important responsibility. Here is how we turn brief answers into a picture insurers can underwrite properly.

Brief proposal answers and what we send instead

What insurers often see

What we send instead

“IT consultancy.”

The split of advice, bespoke development, implementation, managed services, hosting and resale, with the industries you serve.

“We use our standard terms.”

How often you sign the client’s paper instead, the caps you accept, and any indemnity outside the cap.

“We use some contractors.”

Who they are, where they work, their contracts and insurance, and how their code is reviewed before release.

“No AI.”

The tools developers actually use, your policy on client code and data, and the review every release gets.

“Largest contract £150,000.”

What that system does for the client, what a failure would cost it, and the cap and delay damages agreed.

“No claims.”

Withheld invoices, credit notes, service credits paid, projects terminated early and complaints, with their current status.

Illustrations of common answers, not statements about particular clients.

### How we handle your renewal

1.  **You send what you have**Schedule, wording, endorsements, last proposal and your renewal date.
2.  **We find what needs explaining**Activity split, largest contracts, caps and indemnities, client industries, sub-contractors, AI use, overseas work and any fee dispute.
3.  **We approach suited insurers**From more than 30 insurers, specialist agencies and Lloyd’s, chosen for the work you do.
4.  **We compare the wordings**Cover, clauses, excess and limits side by side, with the differences explained.

Business changes

## When your business changes, the insurance needs reviewing

### A much larger contract

A contract several times your usual size brings higher insurance requirements, tougher indemnities and bigger delay damages. Send us the draft before you bid, not after you win.

### Adding managed services

Moving from projects to hosting, support or managed security changes the risk from one deliverable to continuous responsibility. The business description and the cyber exclusions need checking.

### Contractor to company

When a personal service company grows into a business with staff and sub-contractors, the policy needs to cover their work, and the retroactive date must carry across.

### Buying or selling

Decide who answers for past projects. A buyer’s policy may not cover the seller’s earlier work, and an acquired codebase brings its own ownership and licence history.

### Changing insurer

Tell the outgoing insurer about any dispute, complaint or withheld invoice first, disclose it to the new insurer, and carry the retroactive date across unchanged.

### Stopping or going permanent

Claims arrive after the work ends. Government frameworks require PI for at least six years after the contract end date, so plan run off cover into closing the company.

[Run off cover explained](https://www.hammondpi.com/insights/run-off-cover.md)

We are closing our contractor company. Do we still need PI?

Usually, yes. PI responds to claims made while a policy is in force, so a claim arriving after you stop is only covered if cover is still running. Software faults can surface years after delivery, and a contract claim can generally be brought for six years ([Limitation Act 1980, section 5](https://www.legislation.gov.uk/ukpga/1980/58/section/5)). G-Cloud and Digital Outcomes contracts require PI for at least six years after the end date. Run off cover keeps protection in place for past work. [Run off cover explained](https://www.hammondpi.com/insights/run-off-cover.md)

Alongside your PI

## Cyber and public liability cover to consider alongside your PI

PI answers claims about your professional work. It is not built to restore your own systems after an attack, or to pay for injury or damage at a client’s site. Technology businesses hold privileged access and client data, and government frameworks ask for public liability by name, so we recommend considering both.

### Which policy responds?

Tap a situation for the explanation. A general guide only: the answer always depends on the actual wordings.

SituationPICyberPublic liability

Ransomware locks your own systems and you cannot serve clientsNot built for itBuilt for itNot built for it

Incident response, forensic help, restoring data and lost income are cyber covers. PI does not pay to get you working again, though clients may claim against you for the interruption to their service.

A release you deployed takes a client’s system downBuilt for itNot built for itNot built for it

A client’s financial loss from your work is what technology PI is for, subject to the contract terms and the wording. Cyber and public liability are not designed for it.

An attacker uses your remote access to reach clients’ networksMay respondBuilt for itNot built for it

Cyber cover is built for the investigation, the response and often the liability. Clients may also claim under your PI, where the answer depends on the wording’s cyber exclusion. The two policies need reading together.

Your engineer damages equipment in a client’s server roomNot built for itNot built for itBuilt for it

Accidental injury and physical damage at someone else’s premises are public liability risks. PI wordings usually exclude property damage unless it flows from negligent advice or design.

Hardware you supplied overheats and causes a fireNot built for itNot built for itBuilt for it

Damage caused by goods you sold is a products liability risk, normally arranged with public liability. PI wordings usually exclude the sale and supply of goods.

Built for itMay respondNot built for it

Cyber cover explained: the response, the recovery and the liability

-   **Incident response.** A breach coach, forensic investigators and lawyers from the first call.
-   **Restoration and interruption.** Rebuilding your systems and data, and the income lost while you cannot work.
-   **Extortion.** Specialist handling of ransomware demands, within the law.
-   **Liability.** Claims and regulatory costs following a breach of data you hold.

For a technology business the line between cyber and PI needs care, because your services are themselves digital. We check which policy would respond to a client’s claim that your service caused its incident.

Public and products liability explained

Public liability covers injury to people and damage to property arising from your business, such as an engineer’s accident on a client’s site. Products liability covers injury or damage caused by goods you supply, such as hardware.

Buyers ask for it by name. G-Cloud 15 requires public liability of at least £1 million alongside PI, and employers’ liability of £5 million ([Government Commercial Agency, G-Cloud 15](https://www.gca.gov.uk/agreements/RM1557.15)). The government’s Model Services Contract expects the public liability policy to include an indemnity to principals clause. [The other covers we arrange](https://www.hammondpi.com/other-covers.md)

[The other covers we arrange](https://www.hammondpi.com/other-covers.md)

## Questions every firm asks

- [I am retiring. What happens to my PI?](https://www.hammondpi.com/insights/questions/#cq-1)
- [Does using AI invalidate my PI?](https://www.hammondpi.com/insights/questions/#cq-5)
- [Does my policy cover a freelancer or consultant who works for us?](https://www.hammondpi.com/insights/questions/#cq-9)
- [A client wants our liability cap raised to match our PI limit. Does that affect cover?](https://www.hammondpi.com/insights/questions/#cq-15)

[See all common questions](https://www.hammondpi.com/insights/questions.md)

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

## Guides for IT consultants

[Professional indemnity explainedGuide](https://www.hammondpi.com/insights/professional-indemnity-explained.md)[Fair presentationGuide](https://www.hammondpi.com/insights/fair-presentation.md)[The clause guideGuide](https://www.hammondpi.com/clauses.md)[Sole trader or limited companyGuide](https://www.hammondpi.com/insights/sole-trader-or-limited-company.md)[Run off coverGuide](https://www.hammondpi.com/insights/run-off-cover.md)[Freelancers and subconsultantsGuide](https://www.hammondpi.com/insights/freelancers-and-sub-consultants.md)[Claims supportGuide](https://www.hammondpi.com/claims-support.md)

Proposal form

## Prefer to fill in a form?

Ask us for the appropriate proposal form, or send us your details when you request a quote.

Beyond the policy

## Claims support and contract reviews

If you receive a complaint or become aware of something that could lead to a claim, email [claims@hammondpi.com](mailto:claims@hammondpi.com), or call [0333 222 4257](tel:03332224257) if it is urgent or sensitive. We report the matter, follow up with the insurer and explain updates. If a deadline is near, follow the notification instructions in your policy immediately. Do not admit liability before speaking to us.

Before you sign, send us the master services agreement, statement of work, framework order form or agency contract you have been asked to accept, with the liability cap, indemnities, warranties and insurance clause highlighted. We can flag insurance points to discuss with you and, where needed, your insurer. Your solicitor can advise on the legal effect. A review cannot guarantee cover for a claim.

[Claims support](https://www.hammondpi.com/claims-support.md)  ·  [Contract reviews](https://www.hammondpi.com/contract-reviews.md)

Review your cover

## Let a specialist read your PI cover

Send us your current schedules, wordings, endorsements and renewal information. Tell us about your largest contracts, the caps and indemnities you have agreed, sub-contractors, AI use and any fee dispute. We will tell you where the cover fits your business, where it does not, and what we would change.

[Speak to a PI specialist](https://www.hammondpi.com/contact.md)[Send us your renewal](https://www.hammondpi.com/renewal.md)[Get a quote](https://www.hammondpi.com/quote/?profession=it-consultants.md)

-   Your schedule, policy wording and endorsements
-   Renewal date and your last proposal form
-   Your split of work and largest contracts
-   Your standard terms and any client contract signed
-   Sub-contractors, offshore developers and AI tools used
-   Fee disputes, complaints and anything that needs explaining
