What Liability Cap Should A Consultancy Agreement Have?

A fair liability cap in a consultancy agreement is usually the amount that sensibly matches the risk, the fees and the consultant's insurance cover. It's not automatically the total fees, and it's not automatically unlimited.

The more nuanced part is that some liabilities can't be capped at all, and others may need a higher or separate cap depending on the work. If you're negotiating a consultant contract in the UK, the right answer depends on what could realistically go wrong and who is best placed to control that risk.

This doesn't have to turn into a tense negotiation. A clear limitation of liability clause in a service agreement can help both sides understand the commercial deal, price the work properly and avoid an expensive dispute later.

What Is A Liability Cap In A Consultancy Agreement?

A liability cap is a clause that limits how much one party has to pay if something goes wrong under the consultancy agreement. In most consultancy contracts, the cap limits the consultant's financial exposure to the client.

For example, if a consultant gives advice that causes the client to lose money, the client may want to claim compensation. A liability cap sets the maximum amount the consultant may have to pay, subject to any exclusions and the law.

Liability caps are common in professional services because consultancy work can create losses that are much larger than the fees paid. Under a marketing services agreement, a consultant might be paid GBP 5,000 for a campaign strategy, but a failed launch could cost the client far more. A cap helps the consultant avoid taking on open-ended risk that isn't reflected in the price.

From the client's side, the cap shouldn't be so low that the contract is almost meaningless. If the consultant's work is business-critical, you may need a higher cap, stronger remedies or specific obligations around insurance, approval processes and deliverables.

What Liability Cap Is Normal For A Consultant Contract In The UK?

It depends, but common UK consultancy agreement liability caps include a fixed amount, a multiple of fees, the consultant's insurance limit or a tiered structure for different risks.

You'll often see these structures:

• Total fees paid or payable: The consultant's liability is capped at the fees paid under the agreement. This can work for lower-risk work, but may be too low for strategic, technical or regulated projects.
• A multiple of fees: The cap might be 2x, 3x or 5x the fees. This gives the client more protection while keeping the consultant's exposure linked to the contract value.
• A fixed amount: The cap is a set figure, such as GBP 25,000, GBP 100,000 or another negotiated amount. This can be useful where the fee is small but the risk is not.
• Insurance-based cap: Liability is capped at the amount recoverable under the consultant's professional indemnity insurance. This needs careful wording because insurance policies have exclusions, excesses and claims conditions.
• Per claim and aggregate caps: A per claim cap applies to each claim. An aggregate cap applies to all claims together across the contract. Clients usually prefer per claim caps, while consultants usually prefer an aggregate cap.
• Tiered caps: Different types of liability have different caps. For example, general liability might be capped at fees paid, while data protection or confidentiality breaches may have a higher cap.

A sensible cap starts with the commercial reality. Ask what the consultant is being paid, what the client could realistically lose, how much control each side has, and what insurance is available.

Can A Consultant Limit Liability For Negligence?

Yes, a consultant can often limit liability for negligence in a UK consultancy agreement, but there are strict limits and the clause must be reasonable in many cases.

The Unfair Contract Terms Act 1977 is the key law for many business-to-business limitation clauses. Under UCTA, a business can't exclude or restrict liability for death or personal injury caused by negligence. Any clause trying to do that won't work.

For other losses caused by negligence, a limitation clause usually needs to pass the UCTA reasonableness test if it's in standard terms or falls within UCTA's scope. In simple terms, the clause needs to be fair and reasonable having regard to the circumstances when the contract was made.

Factors that can matter include:

• the bargaining power of each party
• whether the client knew about the limitation clause
• whether the client had a real chance to negotiate it
• whether the cap matches the fees, risk and insurance position
• whether the client could have obtained services elsewhere without the same limit

If you're using your standard consultancy terms, don't assume a low cap will automatically hold up. A clause hidden in small print or set at a token amount may be harder to defend, especially if the consultant's work could cause significant loss.

The Consumer Rights Act 2015 may also matter if you're supplying consultancy services to consumers rather than businesses. Most consultancy agreements are B2B, but if consumers are involved, fairness rules and consumer statutory rights need to be handled carefully.

What Liabilities Cannot Be Capped Or Excluded?

Some liabilities can't be capped or excluded under English law, and your consultancy agreement should carve these out clearly.

The usual exclusions from a liability cap include:

• Death or personal injury caused by negligence: This can't be excluded or limited under the Unfair Contract Terms Act 1977.
• Fraud: You can't exclude liability for your own fraud.
• Fraudulent misrepresentation: A contract term trying to avoid liability for fraudulent misrepresentation won't be effective.
• Some statutory liabilities: Certain legal duties can't simply be contracted away, especially where legislation says so or public policy is involved.

There are other liabilities that can be limited in some cases, but are often excluded from the general cap as a matter of negotiation. These might include:

• breach of confidentiality
• misuse of personal data
• intellectual property infringement
• non-payment of fees
• deliberate default or wilful misconduct
• breach of restrictive covenants
• specific indemnities

Be careful with phrases like gross negligence. English law doesn't treat gross negligence as a neat, standalone concept in the same way some other legal systems do. If you want higher liability for very serious conduct, the wording should say exactly what conduct is being carved out.

Should Indemnities Sit Inside Or Outside The Cap?

It depends on the risk, but you should decide this expressly because an indemnity can become a major liability if it's uncapped.

An indemnity is a promise to cover a specific loss. In a consultancy agreement, indemnities commonly cover things like:

• third party intellectual property claims caused by the consultant's materials
• losses caused by a data breach or misuse of confidential information
• employment-related claims where the consultant supplies personnel
• claims arising from the consultant's breach of law
• losses caused by subcontractors engaged by the consultant

From the client's perspective, an indemnity can be helpful because it gives you a clearer recovery route for specific risks. From the consultant's perspective, an indemnity can be risky because it may apply more directly than an ordinary damages claim and may not require the same proof of loss depending on the wording.

If you want indemnities to be capped, say so. If you want some indemnities to be uncapped or subject to a higher cap, say that too.

A Practical Example

Say Maya runs a small IT consultancy in Manchester. She's asked to configure a booking platform for a national retailer. Her fee is GBP 18,000, but if the platform fails during a major sales period, the retailer could lose much more.

A cap equal to Maya's fees might feel far too low for the retailer. But unlimited liability could be impossible for Maya to accept, especially if her professional indemnity cover is GBP 1 million with exclusions for some cyber events.

A more balanced approach could be:

• general liability capped at 2x the fees
• data protection and confidentiality liability capped at GBP 250,000
• IP infringement indemnity capped at the amount covered by insurance
• no cap for fraud or death or personal injury caused by negligence
• clear client responsibilities for testing, approvals and timely access

That kind of IT services agreement structure gives the client more meaningful protection for the real risks, while helping Maya price the job and manage exposure.

How Should Insurance Affect The Liability Cap?

Your liability cap should usually line up with the consultant's insurance, but insurance shouldn't be the only thing you think about.

Professional indemnity insurance is often the key policy for consultants. It may cover claims arising from professional negligence, errors, omissions or breach of professional duty. Depending on the work, a consultant may also need public liability, cyber insurance, employers' liability insurance or product liability cover.

When you're checking insurance against a liability cap, look at:

• Policy limit: Is the insurance limit per claim or in the aggregate for the policy year?
• Excess: How much does the consultant need to pay before the policy responds?
• Exclusions: Does the policy exclude cyber incidents, contractual indemnities, insolvency, regulatory fines or certain territories?
• Retroactive date: Does the policy cover past work, or only work after a certain date?
• Run-off cover: Will cover remain available after the project ends, especially for claims that arise later?
• Notification requirements: Does the consultant need to notify the insurer quickly if a claim or circumstance arises?

As a consultant, don't agree to a GBP 2 million liability cap just because you have a GBP 2 million policy. Your insurer may not cover every type of claim, and defence costs may reduce the amount available depending on the policy.

As a client, don't accept an insurance-based cap without understanding what the insurance actually covers. If a claim falls outside the policy, a cap linked only to insurance proceeds may leave you underprotected.

Do Data Protection, IP And Sector Risks Need A Higher Cap?

Often, yes. Data protection, intellectual property and sector-specific risks can justify a different cap because the losses may be larger or harder to control.

Data Protection

If the consultancy involves personal data, the UK GDPR and the Data Protection Act 2018 matter. The contract should deal with whether the consultant is a processor, controller or joint controller, and include the required processor terms where needed.

A data breach can lead to investigation, notification costs, third party claims, operational disruption and reputational damage. The Information Commissioner's Office can also take enforcement action. A private contract can't stop a regulator from acting, although the parties can allocate financial responsibility between themselves where lawful.

For higher-risk data projects, you might use a separate data protection cap rather than folding everything into a low general cap.

Intellectual Property

If the consultant creates reports, designs, code, training materials or brand assets, the agreement should say who owns the IP and what licences apply. A liability cap won't fix unclear ownership wording.

Clients often ask for IP infringement indemnities where the consultant supplies original materials or software. Consultants should check whether the indemnity covers third party materials, open source software, client-supplied materials and changes made by the client after delivery.

Regulated And High-Risk Sectors

The right cap may be different if the consultancy work touches a regulated or sensitive sector, including construction consultancy or employment compliance, such as financial services, healthcare, construction, education, cybersecurity or employment compliance.

For example, under a consultancy agreement, a brand consultant preparing a logo concept may have a different risk profile from a cybersecurity consultant reviewing a payment platform. The fee might be similar, but the potential consequences are not.

What Should A Limitation Of Liability Clause Include?

A good limitation of liability clause should be clear, tailored and easy to apply when a dispute happens.

At a minimum, think about including:

• The main cap: State the amount or formula clearly, such as a fixed amount or a multiple of fees paid.
• Whether the cap is aggregate or per claim: Avoid leaving this open to argument.
• Excluded liabilities: List liabilities that aren't capped, including those that can't legally be capped.
• Higher-risk categories: Set any separate caps for confidentiality, data protection, IP or indemnities.
• Losses that are excluded: For example, loss of profit, loss of revenue, loss of goodwill or indirect losses, if commercially appropriate.
• Insurance obligations: Require suitable insurance, evidence of cover and prompt notification of relevant claims.
• Client responsibilities: Make sure the client must give accurate information, approvals and access on time.
• Mitigation: Require both sides to take reasonable steps to reduce losses if something goes wrong.

Be careful with simply excluding consequential loss. Under English contract law, that phrase can have a narrower technical meaning than many people expect. If you want to exclude specific types of loss, spell them out.

Also make sure the limitation clause works with the rest of the agreement. Payment terms, termination rights, warranties, service levels, acceptance processes, confidentiality and IP clauses all affect the risk picture.

Common Mistakes To Avoid

The most common mistake is treating the liability cap as a standard number rather than a commercial risk decision.

Watch out for these issues:

• Using the same cap for every project: A low-risk advisory job and a business-critical systems project shouldn't necessarily have the same cap.
• Forgetting UCTA reasonableness: A very low cap in standard terms may be challenged if it's not reasonable.
• Making everything unlimited: This may feel protective for the client, but it can make the deal uninsurable or unaffordable.
• Ignoring insurance exclusions: A policy limit isn't the same as guaranteed cover.
• Leaving indemnities unclear: If an indemnity sits outside the cap by accident, the consultant may be taking on more risk than intended.
• Not matching the cap to the scope: If the scope is vague, it's harder to manage liability because nobody is completely sure what the consultant promised to deliver.
• Relying on a generic template: Templates often miss the risk details that matter most for your project, especially around data, IP and sector-specific obligations.

The best negotiations usually start with the actual risk. What could go wrong? Who can prevent it? What would it cost to fix? Is the risk insured? Once you answer those questions, the cap becomes much easier to discuss.

Key Takeaways

• A liability cap in a consultancy agreement should match the fees, risk, bargaining position and insurance cover.
• Some liabilities can't be capped, including death or personal injury caused by negligence, fraud and fraudulent misrepresentation.
• Indemnities should clearly say whether they're inside the cap, outside the cap or subject to a higher separate cap.
• Data protection, IP and regulated-sector work often need extra attention and sometimes a different cap.
• Insurance is a useful guide, but you still need to check exclusions, excesses, aggregate limits and run-off cover.
• A tailored limitation of liability clause can protect both sides and make the consultancy relationship clearer from day one.

If you'd like help with your consultancy agreement, liability cap wording, indemnities or insurance alignment, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.