Of every clause we scan for, unlimited liability is the one with the widest gap between "how it reads" and "what it actually means." It rarely stands out on a skim — it's usually a single sentence buried in a "Limitation of Liability" section that sounds procedural. In practice, it's the clause that decides whether a single dispute can bankrupt you.
Why liability caps exist
A liability cap limits the total dollar amount either party can be forced to pay if something goes wrong — a missed deadline that costs the client revenue, a bug that causes downtime, a data breach, anything that ends up in a claim. Without a cap, "damages" is bounded only by whatever a court decides your mistake actually cost the other side, which can vastly exceed what you were paid.
Step 1: Identify what's currently in the contract
Search the document for "liability," "limitation of liability," "damages," and "indemnif" (catches indemnify/indemnification). Note three things for each hit:
- Is there a cap at all, or is liability unlimited?
- If there's a cap, is it mutual (applies to both parties) or one-sided?
- Are there carve-outs that make the cap not apply in certain cases (e.g., breach of confidentiality, IP infringement, gross negligence)?
Step 2: Decide what cap to ask for
The market-standard starting position for services agreements is a cap equal to fees paid in the trailing 12 months (or total contract value for fixed-term projects). This is the single most common cap we see in fair, negotiated agreements — commonly with carve-outs for gross negligence, willful misconduct, IP infringement, and confidentiality breaches (since those are typically excluded from caps industry-wide).
Step 3: Propose specific language
Rather than asking the other side to "add a cap" in the abstract, propose the actual clause. Something like:
"EXCEPT FOR (A) BREACHES OF CONFIDENTIALITY, (B) INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS, OR (C) GROSS NEGLIGENCE OR WILLFUL MISCONDUCT, IN NO EVENT SHALL EITHER PARTY'S TOTAL LIABILITY ARISING OUT OF OR RELATED TO THIS AGREEMENT EXCEED THE TOTAL FEES PAID OR PAYABLE BY CLIENT TO CONTRACTOR UNDER THIS AGREEMENT IN THE TWELVE (12) MONTHS PRECEDING THE CLAIM."
Note the word "either" — this is the detail that makes it mutual instead of one-sided. If the other side's counter-draft caps only your liability, that's worth flagging explicitly rather than assuming it's symmetrical.
Step 4: Watch for indirect/consequential damages exclusions too
A cap on direct damages doesn't help much if consequential, indirect, or lost-profit damages are still unlimited. Pair your cap request with a mutual waiver of indirect/consequential damages:
"NEITHER PARTY SHALL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE OR DATA, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES."
Step 5: Know when NOT to push
If you're a large agency working with an enterprise client on a $2M contract, the client's legal team likely won't accept a 12-month-fees cap without carve-outs for data breaches or security incidents — and reasonably so. Calibrate the ask to the size and risk profile of the engagement; a freelancer on a $8,000 project has very different leverage (and very different actual risk) than an agency on a multi-year enterprise deal.
Getting a second opinion, fast
If you're not sure whether a specific clause is standard or aggressive, running the contract through Contract Watch gives you a severity-scored breakdown of every liability, indemnification and damages clause, plus a ready-to-send counter-proposal email — before you spend a paid hour of an actual lawyer's time confirming what you could have flagged yourself in under a minute.