Core contract clause | Contract risk guide

Unlimited Liability Clause: Risks, Examples, and How to Detect It

This guide explains unlimited liability clause in plain English so you can spot red flags fast - even if you're not a lawyer. Use it to scan your contract, find the wording, and know what to negotiate.

Fast scanPlain-English outputHighlights risky wording
AuthorX

Direct answer

The unlimited liability clause dictates that one party guarantees payment for all losses, regardless of the actual amount owed or incurred. This clause shifts the financial burden of loss entirely onto the signing party, often without a defined ceiling on damages, which means your potential liability skyrockets based on the contract's definition of 'loss'. It fundamentally changes the economics because it dictates that one party must cover all liabilities stemming from the other party's actions or obligations.

Quote

"The secret of getting ahead is getting started."

- Mark Twain (attributed)

Quote

"When you see a good move, look for a better one."

- Emanuel Lasker

Related stats (business contracts)

9.2%
Average contract value erosion (2014 benchmark)
8.6%
Average today (WorldCC + Deloitte update)
~3%
Best performers (benchmark range)

Sources: World Commerce & Contracting + Deloitte (via Legal Dive).

BrieflyGo contract risk report preview screenshot
Example report: high/medium/low bars plus a highlighted red flag snippet.
Chart showing contract value erosion benchmarks
Illustration: why better limits, notice rules, and definitions reduce financial surprises.

Why it's risky (specific outcomes)

Financial
concrete
  • A $100,000 project can result in a $500,000 liability claim if the clause applies without limitation.
  • $25,000 upfront fees become potentially exposed to an unlimited liability claim.
  • The actual cost of loss shifts from the counterparty to the signing party's balance sheet.
Legal
concrete
  • The standard for 'unlimited' coverage is often the key differentiator.
  • It creates a risk where the indemnified party has no defined ceiling on their obligation.
  • Jurisdictional traps arise when the jurisdiction demands full payment for damages.
Operational
concrete
  • It imposes an immediate, unquantifiable burden on daily operations, requiring constant cash flow allocation to cover potential liabilities.
  • The workflow gets stalled because operational teams must account for every possible loss scenario defined in the clause.
  • Approval requirements become bottlenecked by the need to calculate and assign liability exposure.
Long-term
concrete
  • Over time, this clause dictates a perpetual risk profile, compounding the cost of initial errors.
  • It sets a precedent where one party has no cap on their financial exposure.
  • The relationship degrades because the counterparty sees an infinite potential for claim.

Red flags to look for

Search your contract for these phrases. Each one can change costs, leverage, or your ability to exit a bad deal.

Red flagcheck

'without limitation' is the classic trigger.

Action: ask for a limit, a clear definition, and a written notice/dispute window.

Red flagcheck

indemnity obligation" signals the core requirement."

Action: ask for a limit, a clear definition, and a written notice/dispute window.

Red flagcheck

hereby agrees to pay for all losses" specifies the mechanism. "sole discretion" often indicates a dangerous clause."

Action: ask for a limit, a clear definition, and a written notice/dispute window.

Red flagcheck

indemnification" requires careful scrutiny of the defined scope."

Action: ask for a limit, a clear definition, and a written notice/dispute window.

Red flagcheck

exceeding the agreed liability cap

Action: ask for a limit, a clear definition, and a written notice/dispute window.

Red flagcheck

suggests a failure in structure.

Action: ask for a limit, a clear definition, and a written notice/dispute window.

Red flagcheck

The term 'unlimited' means the party must cover everything, regardless of the stated exposure.

Action: ask for a limit, a clear definition, and a written notice/dispute window.

Real example (what you can lose)

  • Who: A small tech consultancy firm signing a 1-year service agreement with an established corporate client for a software deployment project.
  • What they signed: A company signing a Master Services Agreement where one party has to pay for all losses incurred by the other party under specified conditions.
  • What went wrong: The trigger occurs when the 'unlimited liability' clause is paired with a 'pay for all losses' provision, meaning any loss calculated exceeds the initial agreed fee structure.
  • What they lost: The specific outcome is that the signing party must cover $150,000 in potential liabilities, even if actual costs were only $50,000.

How to identify it

Where to look

Look for 'Section 8 (Indemnification)' or 'Exhibit B (SOW)' where liability limits are defined.

What indicates danger
  • No cap (or cap excludes key claims).
  • Consequential/indirect damages included.
  • Indemnity covers broad events you can't control.

Action checklist

How to protect yourself

Tap a card for details
01Add a clear liability cap (e.g., fees paid in the last 12 months).
Use this as a negotiation checkpoint. Ask for narrower wording, measurable limits, and a written exception before you sign.
02Exclude consequential/indirect damages explicitly (lost profits, downtime).
Use this as a negotiation checkpoint. Ask for narrower wording, measurable limits, and a written exception before you sign.
03Broad indemnity language can make you pay for third-party claims you didn't cause.
Use this as a negotiation checkpoint. Ask for narrower wording, measurable limits, and a written exception before you sign.
04Negotiate: ask for a narrower scope and clear definitions.
Use this as a negotiation checkpoint. Ask for narrower wording, measurable limits, and a written exception before you sign.
05Limit: add caps, thresholds, and clear notice windows.
Use this as a negotiation checkpoint. Ask for narrower wording, measurable limits, and a written exception before you sign.
06Remove: delete one-sided language where possible.
Use this as a negotiation checkpoint. Ask for narrower wording, measurable limits, and a written exception before you sign.
07Use AI: upload the contract to spot risky wording fast.
Use this as a negotiation checkpoint. Ask for narrower wording, measurable limits, and a written exception before you sign.

Upload your contract and detect liability & damages risks instantly using AI.

BrieflyGo scans contracts and highlights risky wording in plain English so you can decide what to accept, what to negotiate, and what to avoid.

No legal jargon overload. Fast scan. Clear red flags.

FAQ

Is this type of clause legal?

Often yes - but legality depends on your location, the exact wording, and the context. Even a legal clause can still be a bad deal for you.

Can it be changed in the draft?

Yes, many clauses can be removed or narrowed. If the other side won't remove it, ask for limits, exceptions, or a trade-off (price, term, scope).

Who benefits from it?

Usually the party with more power in the negotiation. The clause often shifts risk away from them and onto you, especially when it's broad or one-sided.

When does it become dangerous?

When it's broad, has no clear limits, applies after termination, or is tied to large money. It's also risky when the contract has vague definitions or hidden cross-references.

Never sign without understanding every clause.

BrieflyGo reviews your contracts in plain English — instantly.

Try for free →