How Liability Caps Work in Contracts for UK Edtech Platforms

A liability cap can decide who absorbs the cost when an edtech contract goes wrong. That matters if your platform loses pupil data, a school cannot access lessons during exam season, or a supplier's software outage stops classes from running. Founders often make the same mistakes here: they accept a supplier's standard cap without checking what it actually covers, they assume insurance makes the wording less important, or they focus on price and service levels while missing the exclusions buried in the legal terms.

For UK edtech platforms, liability wording is rarely just legal boilerplate. It affects refunds, claims, data breach exposure, third party IP disputes, and whether a customer can recover anything meaningful if your service fails. It also affects your own risk when you buy hosting, assessment tools, AI products, content licences, white label software or implementation services.

This guide explains how liability caps work in contracts for UK education technology platforms, what a fair cap can look like, which liabilities usually sit outside the cap, and what to check before you sign or accept standard terms.

Overview

A liability cap sets a financial limit on what one party must pay if it breaches the contract or causes certain losses. In edtech deals, the real question is not whether a cap exists, but how it is calculated, what claims it applies to, what losses are excluded, and which liabilities remain unlimited under UK law.

A workable cap should match the real risks in the deal, the fees being paid, the role your platform plays in teaching or assessment, and the sensitivity of the data involved.

• How the cap is calculated, for example annual fees, total fees, or a fixed amount
• Whether the cap applies per claim, per year, or across the whole contract
• Which liabilities are carved out and remain uncapped
• Whether indirect, consequential, revenue or data loss is excluded
• How the cap interacts with indemnities, service credits and termination rights
• Whether the cap matches the practical risk of downtime, security incidents and IP claims
• Whether the clause is likely to be enforceable under UK reasonableness rules

What Liability Cap Contract Education Technology Platforms Means For UK Businesses

A liability cap is a risk allocation tool, not a standard number that works for every contract. For UK edtech businesses, it determines how much legal and commercial exposure sits with you if things go wrong, and how much protection you receive from your own suppliers.

At a basic level, a liability clause usually does three jobs. It sets the cap, excludes certain kinds of loss, and lists liabilities that are not limited at all.

What a liability cap usually looks like

Many edtech contracts state that one party's total liability is limited to a figure linked to fees paid under the agreement. Common formulas include:

• 100 per cent of fees paid in the previous 12 months
• 125 per cent or 150 per cent of annual fees
• Total fees paid or payable over the initial term
• A fixed sum, such as £50,000 or £250,000
• Different caps for different claim types, such as a higher cap for data protection breaches

The right formula depends on the contract. A school paying a modest annual subscription may see little value in a cap set at 12 months' fees if a long outage disrupts timetabling, attendance reporting or safeguarding communications. On the other side, a startup supplier may not be able to accept open ended liability far beyond the contract value.

Why edtech platforms face specific pressure on liability

Edtech contracts often sit close to sensitive functions. A platform may store children's personal data, handle payment information, host lesson content, support remote invigilation, process special educational needs information, or integrate with school management systems. That increases the stakes if the service fails.

Founders also deal with a mixed customer base. You may contract with schools, academy trusts, universities, local authorities, training providers, parents, or commercial education businesses. Each may approach liability differently.

A multi academy trust, for example, may push for stronger data breach protections and higher caps because one incident could affect several schools. A university may focus on research data, accessibility, uptime and intellectual property. A reseller or channel partner may want back to back rights so it is not left exposed to end users while your cap stays low.

What UK law does and does not allow

You cannot simply write any cap you like and assume it will always work. In the UK, exclusion and limitation clauses may be tested for reasonableness, especially under the Unfair Contract Terms Act 1977 in business to business contracts. The exact legal position depends on the parties and wording, but an extreme cap can be challenged if it is not reasonable in the circumstances.

Some liabilities also cannot be excluded or limited in the usual way. Contracts commonly state that nothing limits liability for:

• Death or personal injury caused by negligence
• Fraud or fraudulent misrepresentation
• Any other liability that cannot lawfully be excluded

That wording is standard because the law places limits on contractual freedom in these areas.

Caps, exclusions and carve outs work together

The cap is only part of the clause. A contract may also exclude categories of loss entirely, such as indirect loss, loss of profit, loss of revenue, loss of goodwill, or loss of anticipated savings. That can be just as significant as the cap itself.

For an edtech platform, broad exclusions can create real gaps. If your customer's main harm from an outage is lost enrolment income, disrupted teaching hours, or the cost of emergency workaround services, a generic exclusion may remove much of the practical claim value even where the headline cap looks acceptable.

Carve outs are equally important. These are liabilities left outside the cap or subject to a higher cap. Common examples in edtech contracts include:

• Data protection breaches
• Confidentiality breaches
• Intellectual property infringement claims
• Deliberate default or wilful misconduct
• Payment obligations

This is where founders often get caught. A clause may say liability is capped at annual fees, but an indemnity for IP infringement may sit outside the cap entirely, or a data breach claim may have its own much higher cap.

Legal Issues To Check Before You Sign

Before you sign a contract, the main job is to map the legal wording against the real failure points in the service. If the clause does not reflect how your product is used in schools or by learners, the number on the page may give false comfort.

1. How the cap is calculated

The first question is simple: what is the actual cash value of the cap? A cap based on fees paid in the previous 12 months can be very low in year one, especially where there is a pilot, discounted onboarding, or phased rollout.

Ask for the clause to be tested against likely scenarios, such as:

• A two week platform outage during term time
• A breach affecting pupil records
• An IP claim over third party content or software
• Failed implementation work requiring replacement suppliers

If the likely claim value is far above the cap, the clause may not be commercially sensible.

2. Whether the cap is aggregate or per claim

An aggregate cap means all claims across the contract count towards one total pot. A per claim cap resets for each claim. The difference can be dramatic.

An aggregate cap may be workable for a low risk software tool. It can be a problem where the contract covers several services, multiple schools, large data volumes or a long term implementation. One early claim could use up the full amount and leave no meaningful cover for later issues.

3. Which liabilities are uncapped or have a separate cap

Do not stop at the main limitation clause. Check indemnities, data processing terms, IP clauses, confidentiality wording and payment provisions. These often contain hidden liability positions.

In edtech contracts, you should review whether separate treatment applies to:

• UK GDPR and Data Protection Act 2018 breaches
• Security incidents involving children's data
• Third party claims that your platform infringes copyright, database rights or trade marks
• Breach of confidentiality around school records or assessment materials
• Refund obligations and prepaid subscription fees

If you are the supplier, make sure a higher cap for one area does not accidentally create uninsured exposure. If you are the customer, make sure your main practical risks are not trapped inside a very low general cap.

4. Whether loss of data is excluded

Many software contracts exclude loss of data, corruption of data, or restoration costs. That is a serious point for education technology platforms.

If your platform stores attendance records, coursework, pastoral notes, exam information, or learner progress data, a blanket data loss exclusion may gut the value of the contract. Sometimes the issue can be narrowed so the supplier is not responsible for all possible downstream consequences, but still accepts liability for restoration costs, breach response and direct remediation where the supplier caused the problem.

5. Service credits are not a full remedy

Some providers point to service credits for downtime and say that should be enough. Usually it is not. Service credits are a commercial mechanism, not a complete substitute for liability rights.

Check whether service credits are the exclusive remedy for missed service levels. If they are, your business may be stuck with a small account credit even where the real loss is much larger.

6. Insurance does not fix bad drafting

Insurance matters, but it does not automatically align with the contract. A founder may think a cyber policy or professional indemnity policy covers the risk, only to find the contract goes further than the policy, or the policy has exclusions and conditions.

Before you accept the provider's standard terms, compare the contract against your insurance position and seek a legal review if needed. Check:

• Whether the policy covers contractual liabilities of the type assumed
• Whether limits are high enough for the cap or carve out
• Whether children's data, cyber incidents and regulatory investigations are included
• Whether subcontractor failures are covered

7. The clause must fit the customer type

A school procurement team may accept a market standard SaaS cap more readily than a local authority or university buying a mission critical system. The same product can justify different positions depending on use case, data, and dependency.

A reading app used for optional home revision raises different risk questions from a safeguarding communication platform or online exam tool. The contract should reflect that.

Common Mistakes With Liability Cap Contract Education Technology Platforms

The most common mistake is treating the liability cap as a single number instead of a whole risk structure. Founders often negotiate hard on fees and miss the wording that decides who pays for real damage.

Accepting annual fees as the default cap without pressure testing it

A cap at 100 per cent of annual fees is common, but it is not automatically fair. If your platform supports thousands of users across a trust, annual fees may bear little relationship to the impact of a data incident or service failure.

That does not mean every deal needs a huge cap. It means the cap should be tested against the service and the likely losses.

Ignoring the exclusions because the cap looks high enough

A contract can advertise a generous cap and still remove most useful claims through exclusions. Loss of revenue, loss of profits, wasted spend, loss of data and indirect loss can significantly narrow recovery.

Before you rely on a verbal promise that the supplier will "make things right", read the excluded loss wording carefully. If the clause strips out the losses your business is most likely to suffer, the headline cap may not help much.

Leaving indemnities outside the cap without realising

Indemnities deserve special attention because they can shift risk more aggressively than ordinary breach claims. An indemnity for IP infringement, data misuse, or third party claims may sit outside the general cap.

That can be appropriate in some deals. It can also create a major imbalance if one party gives broad indemnities but receives only a low capped remedy in return.

Assuming supplier terms are non negotiable

Many startup founders think large software vendors never move on liability. In practice, some do, especially where the customer can explain the education context clearly.

Useful negotiation points may include:

• A higher cap for data protection and confidentiality claims
• A separate cap for IP infringement claims
• A minimum fixed cap rather than a fees only formula
• Clarification that direct remediation costs are recoverable
• Removal of wording making service credits the sole remedy

Forgetting subcontractors and integrated tools

Edtech products often rely on third party cloud hosts, video tools, AI services, content libraries, payment processors or identity verification providers. If your customer contract gives strong commitments but your supplier contract has a much lower cap, you may carry the gap yourself.

This back to back problem is common in white label and reseller arrangements. Your upstream and downstream positions should be compared before you sign.

Using the same cap across every contract

A standard template helps, but one cap does not suit every deal. A pilot with a tutoring business is different from a long term arrangement with a university or public sector body. The right drafting may vary depending on data sensitivity, user numbers, revenue model, integration depth and whether the platform supports core educational operations.

Missing the reasonableness issue

A very low cap may look attractive if you are the supplier, but extreme drafting can create enforceability risk and damage the deal. A customer may push back hard, procurement may stall, or the clause may later face challenge.

A more balanced clause often serves the business better than a position that looks strong on paper but is hard to defend commercially.

FAQs

Can a UK edtech platform exclude all liability in its contract?

No. Some liabilities cannot be excluded as a matter of law, such as death or personal injury caused by negligence and fraud. Other exclusions may also be subject to reasonableness requirements, particularly in business to business contracts.

What is a typical liability cap for education technology contracts?

There is no single market standard, but common positions include 100 per cent to 150 per cent of annual fees, total fees over the term, or a fixed sum. The right amount depends on the service, the data involved, the customer type and the likely loss if things go wrong.

Should data protection liability sit outside the cap?

Not always, but it often gets separate treatment. Some contracts leave data protection claims uncapped, while others apply a higher specific cap. The better approach depends on the scale of data risk, the parties' insurance and bargaining position.

Are service credits enough protection for outages?

Usually not on their own. Service credits can help for minor service level failures, but they may be poor compensation for major disruption. Check whether the contract still allows termination rights, damages claims or other remedies for serious breaches.

Do indemnities count towards the liability cap?

Sometimes yes, sometimes no. You need to read the contract carefully because indemnities are often carved out of the general cap or given a separate cap. Never assume they follow the main limitation wording automatically.

Key Takeaways

• A liability cap sets the maximum financial exposure under a contract, but the real position depends on the cap formula, excluded losses and uncapped carve outs.
• For UK edtech platforms, liability clauses should reflect practical risks such as pupil data breaches, downtime during term, implementation failures and IP claims.
• Annual fees are a common cap measure, but they may be too low where the service is business critical or handles sensitive education data.
• Check whether the cap is aggregate or per claim, and whether indemnities, confidentiality breaches or data protection liabilities sit outside it.
• Service credits and insurance do not replace careful contract drafting.
• Supplier and customer contracts should be reviewed together so you are not exposed to a back to back risk gap.
• Before you sign, pressure test the clause against real scenarios and make sure the wording is commercially sensible as well as legally enforceable.

If you want help with supplier contracts, customer terms, data protection risk allocation, indemnity wording, or contract drafting, you can reach us on 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.