Current to October 25, 2026
The terms described in this article are typical, but no two agreements are identical. Before you sign, have your contract reviewed by the right professionals, which may include your lawyer, your insurance broker and your accountant.
A limitation of liability clause caps or excludes what one party must pay if a contract goes wrong. Ontario courts generally enforce these clauses. When a party tries to avoid one, the court asks three questions:
- Does the clause, read in the context of the whole contract, cover this claim and this loss?
- Was the clause unconscionable when the contract was made?
- Is there an overriding public policy reason not to enforce it?
A serious breach, sometimes called a “fundamental breach,” does not cancel the clause on its own.
- A cap limits how much can be recovered. An exclusion removes whole categories of loss. Most clauses use both.
- Name the losses you mean to exclude. Labels like “indirect” and “consequential” do not settle the question.
- A cap needs a complete formula: the amount, the period, the scope and whether it applies per claim or in total.
- Carve-outs and indemnities decide how much the cap is really worth. Review them as closely as the cap itself.
- Data, intellectual property and third-party claims rarely fit a general cap. Give them their own treatment.
- Insurance should support the cap, not define it.
- Ontario businesses can agree to shorten the time to sue, but only with clear wording.
- Defined terms, cross-references and survival language often decide whether the clause works when it is needed.
What Is a Limitation of Liability Clause?
A limitation of liability clause sets, in advance, the most each party will pay if the contract is breached or a named event happens. It is a risk allocation tool, not boilerplate.
Most clauses combine several of these tools:
- Liability cap. A maximum amount one party can be required to pay. It can be a fixed dollar figure or tied to the fees under the contract.
- Damages exclusion. A list of loss types that cannot be claimed at all, such as lost profits or loss of data.
- Separate caps. Different limits for different risks. A higher limit for a specific risk is often called a “super cap.”
- Carve-outs. Claims removed from the cap or the exclusions, such as fraud or a breach of confidentiality.
- Basket or deductible. A threshold that losses must exceed before a claim can be made.
- Exclusive remedy. A rule that a set remedy, such as repair, replacement or a service credit, is the only remedy for a defined failure.
- Warranty disclaimer. A statement that the only promises about the product or service are the ones written in the contract.
- Shorter claim period. A deadline for bringing a claim that is shorter than the law would otherwise allow.
Together, these terms affect pricing, insurance and who absorbs the loss if the deal fails. Each one is explained in more detail below.
Why Businesses Use Liability Limits
The clause decides who absorbs the loss when something goes wrong, and each side wants that line in a different place.
- The supplier’s concern. A supplier may earn $100,000 in fees for work that touches a much larger customer operation. Without a limit, one failure could expose it to losses many times the value of the contract.
- The customer’s concern. The customer may rely on the supplier for a critical system, sensitive data or intellectual property. A very low cap would leave the customer carrying almost all of the cost of the supplier’s failure.
The table shows where those interests usually pull apart.
| Issue | Supplier’s goal | Customer’s goal |
|---|---|---|
| Maximum exposure | Predictable liability tied to the contract value | Recovery in proportion to the harm a failure is likely to cause |
| Lost revenue or profit | Exclude unpredictable business losses | Keep recovery where those losses are the likely result of a failure |
| Data incident | Limit exposure and match it to cyber insurance | A higher cap for response costs, claims and regulatory exposure |
| IP infringement | Keep the indemnity within a manageable limit | Real protection against third-party claims |
| Service failure | Offer repair, credits or re-performance | Keep termination and damages if the remedy fails |
| Insurance | Limit liability to available coverage | Avoid making insurance the only measure of recovery |
The strongest clause is not the most one-sided one. It is the clause that allocates foreseeable risk on purpose and can be applied without a lawsuit.
How Ontario Courts Decide Whether to Enforce the Clause
Ontario courts generally enforce a limitation clause as written. The clause survives unless the party trying to avoid it wins on one of three questions.
The Supreme Court of Canada set out those questions in Tercon Contractors Ltd. v. British Columbia (Transportation and Highways), 2010. A court works through them in order:
Tercon Contractors Ltd. v. British Columbia (Transportation and Highways), 2010 SCC 4, [2010] 1 S.C.R. 69
What happened. The Province of British Columbia ran a request for proposals for a highway project. Its terms said no bidder could claim compensation “as a result of participating” in the process. The Province then awarded the work to a bidder that was not eligible to bid. Tercon, an eligible bidder, sued.
What the court decided. A five to four majority held that the clause did not cover the Province’s own breach of the bidding rules, so Tercon recovered its damages. All nine judges agreed on the three-question framework and rejected “fundamental breach” as a separate rule.
Discussion point. The Province lost because of how its clause was worded, not because the court thought the clause was unfair. If you rely on a limitation, make sure its wording reaches the kind of breach you are worried about.
1. Does the Clause Apply to This Claim?
The first question is whether the clause’s words reach the breach, the claim and the loss in dispute. If they do not, the clause does not help the party relying on it.
Courts answer this in a practical, common-sense way. They read the contract as a whole, in light of the objective circumstances both parties knew about when they signed (Sattva Capital Corp. v. Creston Moly Corp., 2014).
Small drafting choices therefore matter. Disputes often turn on questions like these:
- Type of claim. Does “all claims” include negligence or misrepresentation?
- Which fees. Do “fees paid under this agreement” include fees under every statement of work?
- Type of loss. Is lost revenue a direct loss in this transaction, or an excluded one?
- How often the cap applies. Does it apply per claim, per event or in total, and do related incidents create one cap or several?
- Defence costs. Do they count against the cap?
- Indemnities. Is an indemnity inside or outside the cap?
- Remedies. Is a remedy described as exclusive truly the only one available?
- Carve-out scope. Does a carve-out for “gross negligence” also catch ordinary negligence?
- Survival and protected parties. Does the clause survive termination, and does “supplier” include affiliates and subcontractors?
Standard form contracts get slightly different treatment on appeal. When the wording is not negotiated and is used across many deals, its interpretation is usually a question of law (Ledcor Construction Ltd. v. Northbridge Indemnity Insurance Co., 2016). In practice, that means an appeal court can more readily correct a trial judge’s reading of the clause.
Sattva Capital Corp. v. Creston Moly Corp., 2014 SCC 53, [2014] 2 S.C.R. 633
What happened. Sattva was owed a finder’s fee, payable in Creston shares, for introducing a mining property. The parties disagreed about which date set the share price. The answer changed the number of shares Sattva received by millions.
What the court decided. The arbitrator read the agreement as a whole, in light of its commercial setting, and sided with Sattva. The Supreme Court restored that award. It held that interpreting a contract means applying legal principles to its words, read in light of the surrounding circumstances. That makes it usually a question of mixed fact and law.
Discussion point. A court will not read your liability clause in isolation. Your defined terms, the fee schedule and the deal’s commercial purpose all shape what the clause means. Check them together before you sign.
2. Was the Clause Unconscionable When It Was Made?
A party can try to escape a clause by showing it was unconscionable, meaning so unfair when the contract was made that a court should not enforce it. Between businesses, this argument rarely succeeds.
The Supreme Court has said unconscionability requires two things:
- Inequality of bargaining power. One party could not adequately protect its own interests when the contract was made.
- An improvident bargain. The result unduly favours the stronger party or unduly harms the weaker one.
A difference in size is not enough by itself, especially where both businesses had access to advice. The argument has more force where:
- The clause is hidden. It is buried in non-negotiable standard terms.
- Its effect is unclear. One party could not reasonably understand what it meant.
- No real remedy is left. It leaves one party with no practical way to recover anything.
Timing matters. The court looks at the bargain when it was made. A bad result later does not make the original deal unconscionable.
Uber Technologies Inc. v. Heller, 2020 SCC 16, [2020] 2 S.C.R. 118
What happened. An Ontario Uber driver started a class action. Uber’s standard form driver contract required every dispute to go to arbitration in the Netherlands, with substantial up-front fees.
What the court decided. The Supreme Court held the arbitration clause unconscionable. It found inequality of bargaining power for three reasons:
- The contract was not negotiated.
- There was a large gap in sophistication between the parties.
- A driver could not be expected to understand what the clause meant.
It also found an improvident bargain, because the fees and travel made it practically impossible to bring any claim.
Discussion point. Uber involved an individual on a take-it-or-leave-it form, not two businesses at the table. Still, if you use standard terms with smaller customers or suppliers, keep your limits clear, visible and commercially reasonable. A clause that leaves the other side with no real remedy is the one most at risk.
3. Is There an Overriding Public Policy Reason?
Only in rare cases will a court refuse to enforce a clause that applies and was fairly made. Tercon treats public policy as a narrow exception.
The party trying to avoid the clause must show a public policy concern that outweighs the strong public interest in enforcing contracts. It is not a way to rewrite a deal that turned out badly.
Does a Fundamental Breach Cancel the Clause?
No. A serious breach does not, by itself, cancel a limitation clause that otherwise applies.
Courts used to apply a doctrine called “fundamental breach.” If one party’s breach deprived the other of substantially the whole benefit of the contract, the party in breach could lose the protection of its exclusion clause. That made outcomes hard to predict.
The Supreme Court moved away from that rule in Hunter Engineering Co. v. Syncrude Canada Ltd., 1989, and Tercon confirmed the change. Instead of asking whether the breach was fundamental, a court now asks:
- Coverage. Does the clause clearly cover this breach?
- Validity. Was the clause validly agreed to?
- Enforcement. Is there a recognized reason not to enforce it?
Hunter Engineering Co. v. Syncrude Canada Ltd., [1989] 1 S.C.R. 426
What happened. Syncrude bought gearboxes for its oil sands conveyor system from two suppliers, Hunter and Allis-Chalmers. Both contracts were governed by Ontario law. The gearboxes failed because of a design defect after the written warranties had expired.
What the court decided. Allis-Chalmers’ contract expressly excluded any other warranties or conditions, including statutory ones. The Supreme Court enforced that exclusion even though the failure was serious. Hunter’s contract did not exclude the statutory conditions, so Hunter remained liable.
Discussion point. The two suppliers sold similar goods, and the same defect caused the loss. The only difference was the wording of their contracts. Clear exclusion language protected one supplier. Its absence left the other liable.
The Main Building Blocks and How They Work
Each part of a limitation clause does a different job. This section explains how each one works and what to watch for.
Excluded Losses: “Indirect” and “Consequential” Damages
List the specific losses you mean to exclude. Labels alone do not settle what is excluded.
Contracts often exclude “indirect, incidental, special, exemplary, punitive or consequential damages.” In plain terms, losses fall into two groups:
- Direct losses. The immediate cost of the breach, such as fixing the defect.
- Indirect or consequential losses. Knock-on effects, such as sales lost while a system was down.
Where the line falls depends on the contract and on what the parties expected, which is why it is so often disputed.
Lost profit shows the problem. Profit lost through general damage to reputation may be treated differently from profit the customer would have earned directly from the very work the supplier was hired to do. Do not assume every lost profit is indirect.
A clearer clause names the excluded losses. Common examples are:
- lost profits and lost revenue;
- loss of anticipated savings or business opportunity;
- loss of goodwill;
- loss or corruption of data;
- business interruption; and
- the cost of replacement products or services.
If a category should stay recoverable for a particular obligation, say so expressly.
What happened. A vendor runs the platform a customer uses to complete its sales. The contract excludes all lost revenue and profit. The platform fails during the customer’s busiest season. Fixing the system costs little, but the customer loses a season of sales. The vendor argues that the customer’s main loss is excluded.
Lesson: before accepting a blanket revenue exclusion, ask whether lost revenue is the most likely result of a failure. A negotiated sub-cap for that loss is often a better fit than excluding it entirely.
Liability Caps
A cap is only as good as its formula. Common structures include:
- a fixed dollar amount;
- fees paid during the previous 12 months;
- fees paid or payable under the relevant statement of work;
- total fees under the agreement;
- a multiple of annual fees;
- available insurance proceeds; or
- separate caps for different risks.
Whatever the structure, a complete cap answers these questions:
- Which fees? Fees paid, payable, invoiced or earned.
- Over what period? The measurement period, such as the previous 12 months.
- Across what scope? The whole agreement, or one statement of work.
- How often? Per claim, per event, per year or in total.
- Related claims. Whether claims arising from the same facts count as one.
- Costs. Whether defence costs, interest and legal fees count toward the cap.
- Each party. Whether the cap applies to each party separately.
- Early claims. What happens if a claim arises before much has been paid.
The last question catches many customers. A cap of “fees paid in the preceding 12 months” gives the customer almost nothing if the failure happens early in the relationship. A fixed minimum, or a “greater of” formula, solves that problem.
What happened. A customer signs a three-year software agreement. Liability is capped at the fees paid in the previous 12 months. Six weeks in, the implementation fails badly. The customer has paid only a small deposit. The contract’s total value is substantial, but the supplier argues the cap is limited to the deposit.
Lesson: use a minimum cap, include fees payable, or use a different formula during implementation.
Enter your own numbers to see how much a claim could recover under different cap formulas. The figures shown are only an illustration.
Baskets and Deductibles
A basket is a threshold that losses must exceed before a claim can be made. There are two common types:
- Once losses pass the threshold, only the amount above it can be recovered.
- The threshold works like an insurance deductible.
- Once losses pass the threshold, the full amount can be recovered from the first dollar.
- Recovery is still subject to the cap.
Baskets are common in business purchase agreements. They also work for service-level, warranty and other recurring claims. Whichever type you use, the contract should say:
- Adding claims together. Whether separate claims can be combined to reach the threshold.
- Related claims. Whether claims arising from the same facts count as one.
Carve-Outs and Super Caps
A carve-out removes a specific claim from the general cap or from the damages exclusions. Every carve-out you add reduces what the cap is worth.
Common carve-outs include:
- fraud or fraudulent misrepresentation;
- wilful misconduct or gross negligence;
- breach of confidentiality;
- privacy or data security incidents;
- intellectual property infringement;
- indemnity obligations;
- unpaid fees;
- bodily injury, death or property damage; and
- liabilities that cannot lawfully be limited.
A carved-out claim does not have to be uncapped. It can be:
- Uncapped. No limit applies.
- Inside the general cap. It shares the main limit, but escapes the damages exclusions.
- Under a super cap. A higher, separate limit applies to that risk.
- Limited to insurance. Recovery is capped at available insurance proceeds.
Two cautions apply to every carve-out:
- Keep them targeted. If every confidentiality, data, IP and indemnity claim is uncapped, the general cap may protect almost nothing.
- Define the conduct. Phrases such as “gross negligence,” “wilful breach” and “recklessness” invite disagreement. If certain conduct should have a special consequence, describe that conduct and its effect as precisely as you can.
Exclusive Remedies
Only call a remedy exclusive if you mean it to replace the ordinary remedies under the contract. An exclusive remedy clause makes one remedy, such as repair, replacement, service credits or re-performance, the only remedy for a defined failure.
A workable exclusive remedy clause addresses:
- Scope. Which failures it covers.
- Process. How and when the remedy must be requested.
- Success. Whether the supplier must actually fix the problem, or only try.
- Failure. What happens if the remedy is unavailable or does not work.
- Termination. Whether termination rights remain available.
- Exceptions. Whether fraud, confidentiality, data or IP breaches fall outside it.
Warranty Disclaimers
A warranty disclaimer limits the promises about a product or service to the ones written in the contract. It typically addresses:
- merchantability or acceptable quality;
- fitness for a particular purpose;
- uninterrupted or error-free performance;
- compatibility with other systems;
- results from using a service; and
- statements made in proposals, demonstrations or sales discussions.
For the sale of goods, Ontario’s Sale of Goods Act implies certain conditions into the contract, such as that goods match their description. Section 53 lets the parties exclude those implied conditions by express agreement.
Two cautions apply:
- Match the disclaimer to your warranties. It makes no sense to promise detailed performance in one section and appear to disclaim it in another.
- Know its limits. A disclaimer does not reliably protect against fraud, negligent misrepresentation, statutory rules that cannot be excluded, or pre-contract statements that the contract itself adopts.
Earthco Soil Mixtures Inc. v. Pine Valley Enterprises Inc., 2024 SCC 20
What happened. Pine Valley bought topsoil from Earthco for a City of Toronto project. Earthco recommended new testing before delivery, but Pine Valley was in a hurry and took the soil without it. The contract said that if Pine Valley did not test, Earthco would not be responsible for the soil’s composition. The soil did not drain as required, and Pine Valley sued under the Sale of Goods Act condition that goods match their description.
What the court decided. A majority of the Supreme Court held that the clause was an “express agreement” that excluded the implied condition. The clause needed no special formula of words. Read in context, it had to show a clear agreement to exclude that liability, and it did.
Discussion point. If you sell goods in Ontario and want to exclude statutory conditions, say so plainly in the contract. If you are the buyer, read the risk-shifting terms before you waive a test or inspection.
Shortened Claim Periods
Ontario businesses can agree to a shorter deadline for bringing claims, but the wording must be clear.
The Limitations Act, 2002 sets a basic two-year limitation period for most claims. Section 22 lets the parties to a “business agreement,” meaning one where no party is a consumer, vary or exclude that period.
A short contractual deadline can end a claim before a party knows it has one. Treat it as part of the liability package and read it alongside the cap.
How the Clause Works With Indemnities
State whether each indemnity sits inside or outside the cap. Without clear wording, the parties may argue about whether an indemnity is a separate payment obligation or simply damages governed by the cap.
An indemnity is a promise by one party to cover specific losses or third-party claims suffered by the other. For each indemnity, the limitation clause should choose one of these treatments:
- General cap. The indemnity shares the main limit.
- Separate cap. The indemnity has its own limit.
- Uncapped. No limit applies.
- Exclusions. Whether the consequential damages exclusion applies to it.
- Split treatment. Whether direct claims and third-party claims are treated differently.
The indemnity section should also set out the claims process:
- Notice. When notice of a claim must be given.
- Defence. Who controls the defence and picks counsel.
- Settlement. Whether a settlement needs consent.
- Defence costs. Whether they count against the cap.
- Limiting the loss. Whether the indemnified party must take reasonable steps to reduce its loss.
- Shared fault. How the indemnified party’s own conduct affects what it can recover.
What happened. A services agreement has a reasonable general cap. In another section, the supplier agrees to indemnify the customer for “all losses arising from any breach of this agreement.” The limitation clause does not say whether it applies to indemnities. After a service failure, the customer frames its claim as an indemnity claim and argues it is uncapped.
Lesson: state expressly whether each indemnity is subject to the general cap, a super cap or no cap.
Third-Party Claims
Treat third-party claims separately, because they can involve losses the contract excludes between the two parties. Two decisions matter most:
- Which losses are covered. A contract may exclude lost profits between the parties but still require the supplier to indemnify the customer if a third party wins a lost-profit award against it. If that is the intent, say so.
- Who the limit protects. The limit may need to cover parent companies, subsidiaries and affiliates, officers and directors, employees, agents, subcontractors, and licensors or hosting providers. If people who are not parties to the contract are meant to benefit, name them and explain how the contracting party can enforce the limit on their behalf.
Data and Cybersecurity Risk
A general cap tied to one year of fees rarely reflects the cost of a data incident. A single incident can trigger investigation and restoration costs, notification costs, business interruption, third-party and customer claims, regulatory proceedings and reputational harm.
Common approaches include:
- Data super cap. A separate, higher limit for data breaches.
- Insurance-linked cap. A cap tied to cyber insurance limits.
- Deliberate misuse. Uncapped liability for intentional misuse of data.
- Type of information. Different treatment for personal information and other confidential information.
- Customer-caused incidents. Exclusions for incidents caused by the customer’s own systems or instructions.
Whichever approach you choose, coordinate the liability clause with the security schedule, privacy obligations, incident response duties and cyber insurance requirements.
Intellectual Property Risk
Treat different kinds of IP risk differently. IP provisions should separate:
- infringement of a third party’s rights;
- misuse of the customer’s IP;
- ownership disputes between the parties;
- open-source software issues;
- materials the customer supplies; and
- changes or combinations the supplier did not authorize.
An IP indemnity usually includes a defence process and fallback options if the product infringes. The contract should settle three points:
- Fallback options. Getting a licence, modifying or replacing the product, or ending the affected service with a refund.
- Exclusivity. Whether those options are the customer’s only remedies.
- The cap. Whether the IP indemnity sits under the general cap or a separate super cap.
Insurance
Insurance should support the agreed allocation of risk, not replace it. The contract should address:
- the types of policy required;
- minimum limits;
- deductibles or self-insured retentions;
- additional insured status, where appropriate;
- coverage after the work ends or the contract terminates;
- requirements for claims-made policies;
- notice of cancellation or material change; and
- certificates or other proof of coverage.
Be wary of a clause that says “liability is limited to available insurance proceeds.” Three things can shrink or eliminate that recovery:
- Denial. The insurer can deny coverage.
- Exhaustion. Other claims can use up the policy limit.
- Defence costs. Legal costs paid by the policy can reduce what is left.
If insurance is meant to set the cap, the contract has to deal with each of these. Your insurance broker can tell you how your policy would actually respond.
What Is Usually Negotiable?
Almost every part of the clause is negotiable. How far you can move it depends on the deal, each party’s alternatives and which party controls the risk.
A supplier usually has more leverage when it offers a standardized, low-cost service to many customers on uniform terms, or cannot get insurance for open-ended liability.
A customer usually has more leverage when:
- The deal matters to the supplier. The contract is strategically important or brings in substantial revenue.
- The supplier controls key assets. It holds sensitive data or runs critical systems.
- The customer cannot protect itself. It has no practical way to limit the damage from a failure on its own.
- Third parties are exposed. The supplier’s conduct could create liability to others.
- Standards are promised. The supplier has agreed to specific security or performance standards.
Common compromises include:
- a general cap equal to 12 months of fees;
- a higher cap for data, confidentiality or IP claims;
- uncapped liability for fraud or deliberate misconduct;
- a minimum dollar floor for claims early in the term;
- a narrower lost-profit exclusion;
- recovery of direct replacement and remediation costs;
- service credits that are exclusive only for minor service-level failures;
- defence costs outside the cap, with settlement amounts inside it; and
- separate caps for each statement of work.
Common Red Flags
| Red flag | Why it matters | Better approach |
|---|---|---|
| Cap based only on fees already paid | An early claim may face a cap close to zero | Add a fixed floor, or include fees paid and payable |
| “All indirect or consequential losses” with no examples | What is excluded stays uncertain | List the excluded losses |
| Every indemnity is uncapped | The general cap may do very little | Set caps by type of indemnity |
| Liability limited to insurance proceeds | Coverage can be denied or used up | A fixed cap backed by insurance, not defined by it |
| One-sided limits buried in standard terms | Raises interpretation and enforceability risk | Clear, visible and commercially defensible wording |
| No rule for related claims | Several incidents may multiply the cap | Define how claims are grouped |
| Service credits are the only remedy for every failure | A major outage may leave no real remedy | Limit exclusivity to defined service-level failures |
| Broad data carve-out | A minor incident may create unlimited liability | A targeted super cap with conduct-based exceptions |
| Indemnity and limitation sections conflict | The parties may litigate whether the cap applies | An express clause saying which section governs |
| No survival clause | Claims after termination become uncertain | State which limits and remedies survive |
| Undefined “gross negligence” carve-out | The parties may disagree about the conduct required | Define the standard or describe the conduct |
Drafting Recommendations
These steps follow the order in which a clause is usually built: understand the risk, set the limits, then check how they fit with the rest of the contract.
- Map the risks first. Identify the realistic losses from performance, data, IP, third-party claims and regulatory obligations before choosing a cap.
- Complete the cap formula. Set the amount, period, scope, how claims are grouped and how defence costs are treated.
- Separate direct and third-party claims. Decide how each is treated, and say so.
- Name excluded losses. Do not rely only on legal labels.
- Target the carve-outs. Decide whether each risk is uncapped, under the general cap or under a super cap.
- Read related clauses together. Review warranties, indemnities, insurance, termination rights and service levels as one package.
- Plan for failed remedies. State what happens if repair, replacement or re-performance does not work.
- Protect the intended group. Name affiliates, employees, agents and subcontractors where appropriate.
- Make major limits visible. Do not hide important restrictions in schedules or hyperlinks.
- State what survives. Liability limits, indemnities, confidentiality and dispute terms often need to outlast termination.
- Check mandatory law. Do not try to exclude liabilities that cannot legally be limited.
- Test with real numbers. Work out what you could actually recover under realistic failure scenarios before you sign.
Before You Sign: Liability Clause Checklist
Run through this checklist before you sign. Tick each item once you have confirmed it in your contract.
Five Common Mistakes
- “Treating the clause as boilerplate, when it is often one of the most valuable terms in the contract.”
- “Copying the limitation from an earlier deal instead of fitting it to this deal’s risks.”
- “Agreeing to a cap number without a period, a scope or a rule for related claims.”
- “Letting a broad indemnity quietly bypass a carefully negotiated cap.”
- “Assuming a serious breach will let you escape the clause later.”
Frequently Asked Questions
Usually, yes. Courts start with the words the parties agreed to. Under Tercon, a court asks whether the clause covers the claim, whether it was unconscionable when the contract was made, and whether an overriding public policy reason prevents enforcement.
It can, but that depends on the wording and the contract as a whole. If the clause is meant to cover negligence, say so expressly rather than relying on a general phrase like “all claims.”
There is no standard formula. A reasonable cap reflects the contract value, the losses a failure is likely to cause, which party controls the risk, the insurance available and the consequences of failure.
No. It depends on the contract and the nature of the loss. If lost profits or revenue matter to the deal, deal with them expressly in the contract.
It can, but the result is unpredictable. The insurer can deny coverage, defence costs can use up the policy, and several claims can compete for the same limit. A fixed dollar cap is usually more predictable.
Not necessarily. The customer often wants uncapped protection, because an infringement claim can stop it from using an essential product. The supplier often wants a super cap and control of the defence. The right answer depends on the technology, any third-party materials, the contract value and the insurance.
Uncapped liability is not the only option. The parties can use a separate super cap, treat deliberate misuse differently from a negligent incident, assign responsibility according to who controls the systems, and match the cap to cyber insurance.
No. A serious breach does not automatically cancel a clause that otherwise applies. The court still asks whether the clause covers the claim, whether it was unconscionable and whether public policy prevents enforcement.
It can, if the contract clearly says so. The safer approach is to state whether termination rights remain available when repair, replacement, re-performance or service credits do not fix the problem.
Only in limited cases. Unfairness alone is not enough. Unconscionability requires inequality of bargaining power and an improvident bargain, both judged when the contract was made. Tercon also allows a narrow public policy exception.
Related Articles
Primary Sources
This article gives general information about Ontario and Canadian law, current to October 25, 2026. It is not legal advice and does not create a lawyer-client relationship.
Do not rely on it in place of advice from a qualified Ontario lawyer who knows your agreement, the parties, your industry and your circumstances.
Whether a limitation of liability clause is enforceable, and what it does, depends on its wording, the contract as a whole, the circumstances in which it was made, applicable legislation and the facts behind the claim.
Forgione Deal and Corporate Counsel · Burlington · Mississauga · Oakville · Vaughan · Toronto