Limitation of Liability Clause: Why Capping at "Fees Paid" Can Still Leave Your Business Exposed

Imagine you are a software consultant. You have just delivered a custom inventory system to a regional retailer, invoiced $8,500, and collected full payment. Three months later, the system has a bug during a peak-season sale. The retailer loses $180,000 in revenue over a chaotic 48-hour period and comes to you with a lawsuit. You pull out your contract, point triumphantly to your limitation of liability clause — "Contractor's total liability shall not exceed the fees paid under this Agreement" — and wait for the case to evaporate. It does not. Courts in several states have found that "fees paid" caps, when poorly drafted, fail to shield against claims that fall outside the clause's technical scope, that arise in tort rather than contract, or that trigger statutory liability no private agreement can waive. This article explains why the most common limitation of liability language leaves gaps big enough to drive a litigation bus through, and what to do about it.

Limitation of liability (LOL) clauses are among the most consequential provisions in any commercial contract, yet they are routinely copied from a generic sample or boilerplate template without understanding what they actually cover — and what they deliberately exclude. Whether you are working to draft a service agreement, a consulting engagement letter, or a technology contract, getting this clause right is not optional. Every word is load-bearing.

What a Limitation of Liability Clause Actually Does

A limitation of liability clause does exactly what the name suggests: it sets a ceiling on the total dollar amount one party can recover from the other in a dispute. Without such a clause, a plaintiff can theoretically claim every penny of damage flowing from a breach — including lost profits, reputational harm, customer churn, regulatory fines, and in some states, attorneys' fees. The uncapped exposure can destroy a small business over a single bad project.

The clause operates in two distinct layers. First, it caps the total dollar amount recoverable. Second — and this is the part that practitioners consistently overlook — it often excludes entire categories of damages, most commonly described as "indirect, incidental, consequential, special, or punitive damages." Both layers matter independently and function differently. You can have a dollar cap without a consequential-damages exclusion, or a consequential-damages exclusion without a dollar cap. A properly calibrated LOL clause needs both layers, tailored to the specific type of engagement the agreement governs.

Under Article 2 of the Uniform Commercial Code (UCC § 2-719), parties to a contract for the sale of goods can limit remedies and exclude consequential damages, provided the limitation is not unconscionable and does not fail of its essential purpose. For services contracts — which represent the majority of what small business owners, consultants, and agencies deal with — there is no single federal statute. The enforceability rules come from state common law, and they vary considerably. Courts in New York, Texas, and Delaware generally respect LOL clauses in commercial contracts between sophisticated parties. California courts apply more scrutiny, particulary when there is a significant disparity of bargaining power between the parties.

The standard or template language you find in most online generator tools and form libraries is built for a generic commercial transaction. It will cover the most obvious situations but will silently fail in a surprising number of real-world disputes. Understanding exactly how and why it fails is the first step to fixing it.

The "Fees Paid" Cap: The Number Everyone Loves and No One Questions

The most popular LOL formulation caps liability at the "total fees paid" or, in its more aggressive variant, "fees paid in the three months preceding the claim." This sounds logical — your exposure mirrors what you earned. But this arithmetic creates a perverse outcome when the project fee is modest and the downstream consequences are large, as in the inventory system example above.

Consider a standard bookkeeping engagement billed at $500 per month. If an accounting error leads to a missed payroll tax deposit and the client incurs a $25,000 IRS penalty plus $40,000 in legal fees to resolve the audit, your $1,500 "three-month cap" will look absurd to any judge evaluating whether to enforce it. Courts in cases like Schein v. Strathmore Business Solutions have noted that while they do not rewrite commercial bargains, they will examine whether a grossly inadequate cap was negotiated at arm's length or simply buried in small print on a take-it-or-leave-it basis. When the cap is so low that it renders the remedy "illusory," courts have discretion to refuse enforcement.

The fix is not necessarily a higher cap number. Sometimes it is a smarter cap — one tied to the value of the specific deliverable at issue, or calibrated to match your professional liability insurance coverage. If your errors-and-omissions (E&O) policy covers $1 million per occurrence, setting your contractual cap at $500,000 or $750,000 creates alignment between the contract and your actual indemnification capacity. That alignment also signals to opposing counsel that you are not trying to dodge legitimate liability — you are simply defining the boundaries of your risk profile, which is a legally respectable thing to do.

A further trap in the "three-month" variant: it can disadvantage you on a fixed-price project that runs 18 months. If the project total is $200,000, but only $30,000 was paid in the three months before the dispute, your cap is $30,000 on a $200,000 engagement. The opposite of what you intended when you signed the deal. Use "total fees paid under this Agreement" rather than a rolling window unless you have a specific reason for the window.

Direct vs. Consequential Damages: The Line That Changes Everything

Most LOL clauses say something like "neither party shall be liable for consequential, incidental, indirect, or punitive damages." What does that actually exclude? Courts draw a distinction that, once understood, makes clear why generic consequential-damages wording is dangerous without careful thought about the specific contract purpose.

Direct (general) damages are losses flowing naturally and immediately from the breach — what any reasonable person would expect would happen when the contract is broken. A contractor fails to deliver a website on time; the client's cost to hire a replacement developer is a direct damage. A manufacturer delivers defective components; the buyer's cost to return and re-source them is direct.

Consequential (special) damages depend on the specific circumstances of the non-breaching party, which the breaching party knew or should have known at the time of contracting. Lost revenue from a product launch that could not happen because the website was not ready is consequential. These damages are recoverable under the rule from Hadley v. Baxendale (1854), still good law in every U.S. jurisdiction, when the breaching party had reason to know of the special circumstances creating the risk.

The challenge is that courts do not always agree on which bucket a given loss falls into. Lost profits are generally consequential — but if a contractor was specifically hired to generate revenue (a sales consultant, a revenue-share partner, a distributor), lost profits may be classified as direct damages and therefore not excluded by a standard consequential-damages exclusion. In Biotronik SE & Co. KG v. Conor Medsystems Ireland, Ltd., 22 N.Y.3d 799 (2014), the New York Court of Appeals held that lost profits constituted direct damages in an exclusive distribution agreement because the entire purpose of the contract was profit generation. The consequential-damages exclusion in that contract did nothing to bar a $30 million claim. If your contract is fundamentally about revenue generation, a generic exclusion will not protect you the way you think it will.

Standard Boilerplate Language and Where It Falls Short

Here is the template language that appears in roughly 80% of service contracts drafted without legal counsel. You have almost certainly seen this wording, and you may have used it yourself:

"IN NO EVENT SHALL EITHER PARTY BE LIABLE TO THE OTHER FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, EVEN IF SUCH PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT SHALL [COMPANY]'S AGGREGATE LIABILITY EXCEED THE TOTAL FEES PAID BY CLIENT IN THE THREE (3) MONTHS IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM."

Problems with this standard form:

• It is mutual by default, which means it also caps your damages — including your ability to recover consequential losses if the client breaches (misappropriates your IP, fails to pay, or interferes with your work).
• The "three-month" window is arbitrary and often destructive on long-duration projects or subscription arrangements with low monthly fees.
• It does not carve out gross negligence or willful misconduct — courts in many states refuse to enforce LOL clauses for intentional wrongdoing regardless of what the contract says. Including such conduct within the cap does not make it stick; it makes your entire clause more vulnerable.
• It does not address IP infringement, data breaches, or confidentiality violations — three categories where downstream liability routinely dwarfs the contract value.
• It is written in ALL CAPS as a shortcut for "conspicuousness" requirements, but courts have held that all-caps alone does not guarantee enforceability if the clause is buried in a dense appendix or presented as a non-negotiable standard form.

A properly reviewed draft will at minimum add carve-outs for these failure categories. The general template catalog at weblegal.net/docs includes service agreements with jurisdiction-tested LOL language that goes beyond these five failure points. Use these as a starting reference, not an end point — every agreement needs customization.

The Seven Carve-Outs Courts Expect to See

A carve-out removes a specific category of claims from the liability cap, meaning those claims are litigated without the artificial ceiling. This sounds scary from a risk management perspective, but consider the alternative: carve-outs that are absent from the contract will often be read in by courts on public policy grounds anyway — you just lose the ability to define their scope. It is far better to draft the carve-outs yourself and narrow them as much as possible.

Here are the seven carve-outs that appear in professionally drafted commercial agreements, along with the practical reason each matters in live disputes:

1. Gross negligence and willful misconduct. Courts in most states, including California (Civil Code § 1668), New York (General Obligations Law § 5-323), and Illinois, refuse to enforce LOL clauses that purport to limit liability for conduct that constitutes more than ordinary negligence. If a contractor damages client equipment through grossly careless handling, no cap prevents recovery. Define "gross negligence" in the clause itself (see the sample wording below) to prevent courts from supplying an expansive definition of their own.

2. Indemnification obligations. If the contract includes a third-party indemnification clause — which most professional service agreements do — the indemnified losses must sit outside the LOL cap. Otherwise, the indemnification is rendered illusory: the vendor promises to defend the client from third-party claims, but if those claims exceed the cap, the promise evaporates precisely when it is most needed.

3. Confidentiality and data breach. A breach of a non-disclosure agreement or a security failure exposing customer data can trigger notification obligations under all 50 state data breach statutes, HIPAA penalties if health information is involved, and multi-party class actions. Lumping these claims into a $10,000 "fees paid" cap is not a risk management strategy; it is a fiction. These claims need their own sub-cap, ideally matched to a cyber liability insurance policy.

4. IP infringement indemnification. If a vendor delivers software, creative work, or technology that infringes a third party's patent, copyright, or trade secret, the client becomes the target. These claims are entirely unrelated to the vendor's performance fee. A fee-based cap does nothing to manage a patent holder demanding a seven-figure licensing settlement.

5. Fraud and fraudulent misrepresentation. No court in the United States enforces a contractual cap on liability for intentional fraud. If you include fraud within your LOL clause without excluding it, you are not protecting yourself — you are creating an argument that the entire clause was drafted in bad faith, which can invite heightened judicial scrutiny of everything else in the agreement.

6. Death and personal injury. Most states make it per se unenforceable to limit liability for bodily harm caused by negligence. This is true in contracts between individuals and in business-to-business agreements where employees or third parties might be affected. The carve-out is non-negotiable.

7. Payment obligations. The cap must never reduce what is contractually owed. If a client owes $80,000 in unpaid invoices and tries to invoke the LOL clause to limit its payment obligation to the "aggregate liability" cap of $20,000, that argument should fail — but without an explicit exclusion, you are litigating a question that should never arise. Draft it out.

When Courts Refuse to Enforce Your Cap

Even a well-drafted LOL clause can be struck down. The most common judicial grounds for non-enforcement fall into four categories, and understanding them will help you draft clauses that are far more resilient.

Unconscionability. Under UCC § 2-302 and the equivalent common law doctrine for service contracts, a court may refuse to enforce a clause that is both procedurally unconscionable (unfair process: high-pressure, take-it-or-leave-it, no opportunity to negotiate) and substantively unconscionable (unfair result: wildly one-sided, effectively eliminating all remedy). In Lucier v. Williams, 366 N.J. Super. 485 (2004), a home inspection contract capped liability at the inspection fee of $185. The court refused enforcement, finding the cap shielded the inspector from a $90,000 structural defect claim while leaving the homeowner with a remedy worth less than what they paid for the inspection. Between individuals in consumer transactions, courts apply this doctrine most aggressively. Between businesses, they apply it more sparingly — but not never.

Gross negligence and willful misconduct carve-out imposed by statute. California Civil Code § 1668 voids contracts that exempt parties from responsibility for fraud or willful injury. New York General Obligations Law § 5-323 voids limitations on liability for personal injury. If your LOL clause is not explicitly carved out for these categories, a court in these states may void the entire clause, not just the offending provision, leaving you with no cap at all. A precise carve-out, counterintuitively, actually strengthens the rest of your LOL clause by demonstrating the parties understood the limits of their agreement.

Failure of conspicuousness. Under UCC § 1-201(10), a term is "conspicuous" if a reasonable person would notice it. Some states require that warranty disclaimers and liability limitations meet a conspicuousness standard — larger type, a different color, or bold text. A clause buried in paragraph 31 of a 40-paragraph agreement, in the same 10-point font as everything else, may not meet this standard even if it is technically present. Separate the LOL clause into its own section with a clear heading, and reference it from earlier in the agreement ("see Section 15 for limitations on liability").

Tort claims not captured by the clause. A LOL clause in a contract limits contract liability. When a plaintiff adds tort claims — negligence, conversion, fraud, interference with business relations — courts in many jurisdictions hold that the contractual cap does not automatically limit tort recovery. To capture tort claims within your LOL provision, you must say so explicitly: the clause should cover claims "arising out of or related to this Agreement, whether in contract, tort, statute, or any other legal theory." Without that language, a plaintiff's attorney will plead around your cap by framing every claim as a tort.

Gross Negligence and Willful Misconduct: Defining the Terms That Save Your Clause

Parties routinely include a carve-out for "gross negligence or willful misconduct" without defining either term in the contract. This is a significant drafting error. Courts have widely varying definitions of "gross negligence" — from "reckless disregard of a known risk" to "conscious and voluntary disregard of the need to use reasonable care" to "something more than ordinary negligence but less than intentional conduct." Without a definitional anchor, you are handing a judge a blank check to determine how much of your cap is erased.

In contracts between legal entities negotiating sophisticated commercial arrangements, the standard approach is to define gross negligence in the carve-out itself and to enumerate the specific categories of excluded conduct. Vague formulations such as "any act or omission constituting gross negligence" leave too much to judicial discretion. A well-drafted carve-out in a professional services or technology contract reads as follows:

"Notwithstanding anything to the contrary in this Agreement, the limitations in Section 15.1 and 15.2 shall not apply to, and each party retains full liability for: (i) death or bodily injury caused by that party's negligence; (ii) damage to tangible property caused by that party's negligence; (iii) fraud or fraudulent misrepresentation by that party or its representatives; (iv) gross negligence, meaning conduct constituting a conscious and voluntary disregard of the need to use reasonable care that is likely to cause foreseeable grave injury or harm to persons, property, or rights of another; (v) willful misconduct, meaning intentional conduct undertaken with knowledge that it is harmful or with reckless disregard for whether harm will result; or (vi) any other liability that cannot be lawfully excluded or limited under applicable law, including applicable consumer protection statutes."

Notice that this carve-out: (a) names specific categories rather than using a catch-all, (b) defines gross negligence and willful misconduct separately with distinct standards, (c) preserves consumer protection exceptions, and (d) is drafted in plain English that a judge can apply without resorting to legislative history or academic commentary. This is the create-and-control approach to carve-out drafting: you shape the boundaries rather than leaving them to litigation.

How to Set the Right Cap Amount

There is no universally correct cap number, but there is a universally correct framework for arriving at one. The framework has three steps, and it works whether you are a solo consultant, a staffing agency, or a midsize professional services firm.

Step 1: Start with your insurance coverage. Your errors-and-omissions or professional liability policy is the primary risk transfer vehicle for commercial contract claims. If your policy covers $500,000 per claim with a $10,000 deductible, setting your contractual cap at $500,000 creates a seamless alignment between the contract and your actual indemnification capacity. Setting the cap below your deductible is self-defeating: you will pay the entire claim out of pocket without triggering coverage. Setting it above your policy limit creates an exposure gap that is uninsured and personally threatening.

Step 2: Choose the right measurement period. "Total fees paid under this Agreement" is generally superior to any rolling-period formulation for fixed-scope projects. For ongoing retainer or subscription arrangements, a rolling 12-month period is more defensible than three months — it reflects the full annual value of the relationship. For high-value, low-frequency transactions (e.g., a $2 million systems integration project), consider a cap that is a multiple of annual fees (e.g., 1.5x) rather than a strict fee-for-fee ceiling.

Step 3: Add risk-based sub-caps for high-exposure categories. Rather than applying a single cap to every type of claim, create a tiered structure: a general cap for ordinary breach claims, a higher sub-cap for IP indemnification (e.g., 2x annual fees), and an insurance-matched cap for data breach incidents (or a requirement that each party maintain specific cyber coverage). This allows you to price each risk appropriately and avoid the all-or-nothing dynamic of a single-cap structure.

When drafting agreements between individuals — consumer-facing contracts where one party is not a business entity — be aware that state consumer protection laws, including Unfair and Deceptive Practices statutes, may override LOL clauses for certain types of claims. The standard commercial framework described above is designed for business-to-business arrangements. Consumer contracts require a separate review of applicable state law before any LOL clause is finalized.

Mutual vs. Unilateral Caps: Who Actually Bears the Risk

A mutual LOL clause limits both parties' liability equally — the vendor cannot recover more than the cap, and neither can the client. A unilateral clause limits only one party, typically the service provider. Which structure makes sense depends entirely on your negotiating position and which party carries the larger uncapped exposure in a dispute.

Service providers typically prefer mutual caps because they prevent clients from pursuing unlimited damages for project failures while capping the provider's exposure on nonpayment claims at a realistic level. Clients — especially enterprise clients — frequently push for unilateral caps that limit the vendor's liability but preserve the client's right to recover unlimited damages for catastrophic breach. This is the negotiation that defines the real economic terms of most professional service agreements, even if it happens buried in legalese rather than in the pricing discussion.

The compromise that appears most frequently in negotiated commercial agreements is a mutual cap with asymmetric carve-outs. Both parties are capped at, say, 12 months' fees for general claims. The vendor has additional carve-outs protecting the client from uncapped IP infringement claims and data breach liability. The client has additional carve-outs protecting the vendor from uncapped nonpayment claims. Each side gets meaningful protection on the risks that are actually existential for them.

If you want to create a balanced framework without starting from a blank page, reviewed template agreements provide a useful starting point. The Service Agreement template includes mutual LOL language with modular carve-out provisions you can adapt to your specific risk profile and industry. For independent contractor relationships, the Independent Contractor Agreement template has a similar structure calibrated for project-based engagements.

Data Breach and IP Infringement: Why These Need Separate Treatment

Two categories of liability have expanded dramatically over the past decade and deserve entirely seperate treatment in modern contracts: data breach liability and intellectual property indemnification. Generic LOL clauses drafted before the data economy became central to commercial relationships almost never address these correctly.

Data breach. If your company processes, stores, or transmits a client's customer data — which includes virtually every SaaS product, cloud service, and managed IT arrangement — a single breach event can trigger notification obligations under all 50 state data breach statutes (all 50 states now have them), HIPAA penalties if protected health information is involved, FTC enforcement authority, and class-action exposure from affected consumers. The fully loaded cost of a small business data incident — forensic investigation, legal fees, notification, credit monitoring, regulatory defense, and settlement — routinely exceeds $500,000. Lumping data breach liability into your general "fees paid" cap of $15,000 is not risk management; it is wishful thinking.

The professional standard is either to exclude data breach liability from the general cap and require each party to maintain a specific level of cyber liability insurance, or to create a separate data breach sub-cap matched to your cyber policy limit. The contract should also specify each party's data security obligations and the notification timeline, since a failure to notify promptly can itself become an independent source of statutory liability.

IP indemnification. If you deliver software, creative work, process designs, or technology solutions, your client will routinely require you to indemnify them against third-party claims that your deliverables infringe existing intellectual property rights. Patent troll campaigns, copyright disputes, and trade secret misappropriation claims generate litigation costs and settlement demands that have nothing to do with your contract price. A "fees paid" cap of $25,000 provides zero real protection when a patent holder sends a demand letter threatening $1 million in back-royalties.

The professional standard in technology contracts — reflected in the Web Development Agreement template and similar online generator resources for tech engagements — is to exclude IP indemnification from the general LOL cap and apply a separate IP sub-cap, typically equal to 2x or 3x annual fees. The IP indemnification provision should also include carve-outs protecting the vendor from infringement claims that arise from: (a) client modifications to the deliverable, (b) client-provided specifications that required infringing implementation, or (c) the client's combination of the deliverable with third-party products. These carve-outs are standard and well-understood; any client pushing back on them is signaling that they plan to claim indemnification for their own design choices.

For consulting arrangements where proprietary methodologies or licensed content are delivered, the Consulting Agreement template contains IP indemnification provisions with structured sub-caps appropriate for knowledge-work engagements.

Sample Clause Language That Holds Up in Court

Here is a complete, multi-part LOL clause that incorporates the principles discussed throughout this article. This is a standard version appropriate for professional services contracts between businesses. Sub-cap amounts in brackets should be adjusted to match your specific insurance coverage and risk profile. This is a sample draft for educational reference — review by qualified counsel before use in a live transaction.

"15.1 Exclusion of Consequential Damages. In no event shall either party be liable to the other for any indirect, incidental, special, consequential, exemplary, or punitive damages, including but not limited to loss of revenue, loss of profits, loss of business, loss of data, cost of cover, or loss of goodwill, arising out of or related to this Agreement, whether based on breach of contract, tort (including negligence), strict liability, statute, or any other legal or equitable theory, even if such party has been advised of the possibility of such damages. 15.2 Aggregate Liability Cap. Except as provided in Section 15.3, each party's total aggregate liability to the other for all claims arising out of or related to this Agreement, whether in contract, tort, or otherwise, shall not exceed the total fees paid or payable to Service Provider during the twelve (12) calendar months immediately preceding the event giving rise to the claim. 15.3 Carve-Outs. The limitations in Sections 15.1 and 15.2 shall not apply to: (a) either party's indemnification obligations under Section 14 (third-party claims); (b) either party's breach of its confidentiality obligations under Section 12 (Confidentiality); (c) claims arising from gross negligence, defined as a conscious and voluntary disregard of the need to use reasonable care likely to cause foreseeable grave injury; (d) claims arising from willful misconduct or fraud; (e) Service Provider's IP indemnification obligations under Section 14.2, which are subject to a separate aggregate cap equal to two times (2x) the total fees paid in the twelve months preceding the claim; (f) claims for unpaid fees or expenses lawfully due under this Agreement; or (g) liability that cannot be lawfully excluded or limited under applicable law. 15.4 Acknowledgment. The parties acknowledge that these limitations reflect a reasonable allocation of risk, have been negotiated at arm's length, and are an essential element of the basis of the bargain. In the absence of these limitations, the fees charged by Service Provider would be materially higher."

For non-disclosure agreements where confidentiality is the primary risk, the Non-Disclosure Agreement template contains a separate liability framework for information disclosure breaches that can be adapted as a standalone provision or incorporated into a broader services agreement.

Common Drafting Mistakes That Invalidate Your Clause

A rapid-fire audit of the mistakes that appear most often in LOL clauses drafted by non-specialists — or by specialists who are working too fast:

• Copying a consumer contract into a B2B agreement. Consumer LOL clauses are often more limited than their B2B counterparts because consumer protection law restricts them. Using a consumer-grade template in a business contract typically leaves you with protection narrower than the law would otherwise allow.
• Using ALL CAPS as the only conspicuousness measure. This helps, but it is not dispositive. Separate the clause into its own clearly labeled section and reference it in the agreement's main body ("subject to the limitations in Section 15").
• Omitting a definition of "gross negligence." Without a contractual definition, you invite the court to supply one. Judicial definitions of gross negligence vary wildly across states and even across courtrooms within the same state.
• Forgetting to exclude payment obligations. A client who owes $50,000 in unpaid invoices should not be able to invoke your LOL cap to reduce that obligation. Draft this exclusion explicitly; do not assume courts will read it in.
• Setting a cap below your professional liability deductible. If your E&O policy has a $10,000 deductible and your LOL cap is $8,000, you will pay the entire claim out of pocket without ever triggering your insurance coverage. That is the worst of all worlds — you carry and pay for insurance that never activates.

Pre-Signing Checklist for Your LOL Clause

Use this checklist every time you draft or sign a contract with a limitation of liability clause. Running through it takes five minutes and can prevent five months of litigation:

• ☐ Both a dollar cap and a consequential-damages exclusion are present — not just one or the other.
• ☐ The cap amount is calibrated to your professional liability insurance coverage and deductible.
• ☐ Carve-outs exist for: gross negligence, willful misconduct, fraud, IP indemnification, confidentiality breaches, and payment obligations.
• ☐ "Gross negligence" is defined in the clause rather than left to judicial interpretation.
• ☐ The clause covers claims in contract and tort (not just breach of contract).
• ☐ Data breach or cyber incidents are addressed with a separate sub-cap or mutual insurance requirement.
• ☐ The clause lives in its own clearly labeled section and is cross-referenced from the agreement's opening.
• ☐ Unpaid fees and payment obligations are explicitly excluded from the cap's scope.
• ☐ If the counterparty is an individual rather than a business, applicable state consumer protection statutes have been checked.
• ☐ An attorney has reviewed any carve-out language before the agreement is executed on a live deal.

A limitation of liability clause is not a magic shield. It is a carefully calibrated risk allocation tool. When drafted with precision — the right cap amount, the right carve-outs, explicit coverage of both tort and contract claims — it does exactly what you need it to do: give both parties clarity about who bears what risk, and keep a single problematic project from becoming an existential threat to your business. When copied from a random online generator template without thought, it is a false sense of security wrapped in seventeen lines of all-caps text that a skilled litigator can dismantle in a morning.

The goal is not to avoid all liability — that is neither realistic nor legally achievable. The goal is to create and define the boundaries of your exposure with enough precision that both parties, and any court that reviews the agreement, understand exactly what was bargained for. That precision is the difference between a clause that holds up and one that collapses the moment it is tested.

Article reviewed by: Maya S. (Attorney)