[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.
Home / Who we cover / IT and technology consultants
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 specialistSend us your renewal for reviewGet a quote
Your map
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)
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.
Our experience
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.
Who requires PI
No regulator or professional body sets a PI minimum for IT work. The requirement comes from the contract.
| 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), Digital Outcomes 7 (Joint Schedule 3 v1.0, framework RM1043.9), Model Services Contract (version 2.2A, September 2025), Client and agency (IPSE guide, read November 2026). 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.
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
Situations IT consultants face, the risk hidden in each, and the strategy we would follow from the first letter. Choose a scenario.
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
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 lessonAn unpaid invoice after a complaint is an early warning of a claim. Tell us before you chase it.
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
What we aim forThe insurable loss identified and defended, the uninsured contractual element known early, and no breach of the policy conditions.
The lessonLiquidated damages are easy to sign and hard to insure. Show us the clause before you agree it.
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
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 lessonIn a data incident the first email to the client matters as much as the fix. Call us first.
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
What we aim forThe infringement shown to be unintentional, the client’s loss tested, and any recovery against the sub-contractor preserved.
The lessonAn originality warranty is only as good as your control of what goes into the code.
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
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 lessonInsurers accept AI tools that are described and controlled. Surprises are what cause disputes.
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
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 lessonKeep PI running after a contract ends. Claims arrive later than invoices.
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
What we aim forCover holds because the arrangement was presented properly, and whatever recovery the sub-contract allows is kept.
The lessonShow 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.
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.
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
The law implies that a service will be carried out with reasonable care and skill (Supply of Goods and Services Act 1982, 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.
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). 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). 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.
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
£1 million each and every claim
Then check whether defence costs are paid in addition to the limit or use it up, and when the excess applies.
Inside the wording
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Contract and law
[2010] EWHC 965 (TCC)
Off the shelf hotel software recommended by the supplier was not fit for purpose. The supplier’s standard limitation terms failed the reasonableness test.
[2010] EWHC 86 (TCC)
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.
[2021] UKSC 29
Liquidated damages for delay ran up to termination of an unfinished software project. A cap carve out for “negligence” covered careless breach of contract.
[2022] EWCA Civ 440
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.
[2023] EWHC 1342 (TCC)
A limitation clause was read as one aggregate cap for all claims, not a separate cap for each claim. The drafting decides the exposure.
[2023] EWHC 1765 (TCC)
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.
These decisions explain where a professional’s duty lies. They do not decide whether a particular policy responds.
Specialist work
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.
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.
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.
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.
Tell us how access is controlled, logged and reviewed. Insurers ask, and good answers change how the risk is seen.
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
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 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.
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). Or an open source component brings its licence terms into a proprietary product: under the GNU General Public License version 3, 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.
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). Freelancers and sub-consultants
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).
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.
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).
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
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
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.
| 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.
Business changes
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.
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.
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.
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.
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.
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.
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). 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
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.
Tap a situation for the explanation. A general guide only: the answer always depends on the actual wordings.
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 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.
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.
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.
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
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 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). The government’s Model Services Contract expects the public liability policy to include an indemnity to principals clause. The other covers we arrange
Guidance only. Cover depends on your own policy wording; speak to us about your position.
Proposal form
Ask us for the appropriate proposal form, or send us your details when you request a quote.
This form is not available to download at the moment. Call 0333 222 4257 or email [email protected] and we will send it to you.
Beyond the policy
If you receive a complaint or become aware of something that could lead to a claim, email [email protected], or call 0333 222 4257 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.
Review your 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.