Liability Cap
A liability cap example, how cap formulas work, and when the cap is too low for the risk in the deal.
- The cap amount or formula
- Whether the cap is mutual
- Which claims are carved out
- Whether indemnity obligations sit inside or outside the cap
If this clause already feels aggressive in isolation, upload the full contract and see how it combines with payment terms, liabilities, and exit rights.
Analyze My ContractThe total liability of each party under this Agreement shall be capped at, and shall not exceed, the greater of (a) the total amount of fees paid under this Agreement in the preceding twelve (12) months, or (b) fifty thousand dollars ($50,000). This cap shall not apply to liability arising from a party's gross negligence, willful misconduct, or breach of its confidentiality obligations.
What this clause actually does
A liability cap is the dollar ceiling on what one party can recover if the other side breaches the contract. Caps are often stated as fees paid, fees paid in the prior twelve months, a fixed dollar amount, an insurance amount, or a multiple of fees. The cap is not just boilerplate. It determines whether the contract has enough financial consequence to match the risk.
Why people get burned by this clause
A low cap can make serious failures cheap. If a vendor mishandles data, misses a key transition obligation, or causes operational downtime, a cap limited to a few months of fees may not come close to the actual loss.
What should make you slow down
- The cap is lower than the realistic downside
- The cap applies to confidentiality, data misuse, fraud, or intentional misconduct
- There is no separate treatment for indemnity or third-party claims
- The cap is one-sided in practice even if written as mutual
- The formula is tied to fees paid even when fees are small and risk is large
Where you usually see it
- Vendor agreements
- SaaS terms
- MSAs
- Commercial leases
- Purchase and transition service agreements
What the platform checks in the live contract
- The cap amount or formula
- Whether the cap is mutual
- Which claims are carved out
- Whether indemnity obligations sit inside or outside the cap
- How the cap interacts with excluded damages
What stronger language usually looks like
- The cap is proportionate to the deal's realistic risk
- High-consequence categories have clear carve-outs
- Indemnity and third-party claims are handled expressly
- The formula is easy to calculate
- Insurance coverage and contract exposure are aligned
Definitions worth opening next
Clause pages that share the risk pattern
Articles that go deeper
Common questions about this clause
A reasonable cap depends on the risk. A routine service may use fees paid or twelve months of fees. A data, IP, operational, or transition-heavy contract may need a higher cap or carve-outs for specific high-consequence claims.
Sometimes. If indemnification covers third-party claims, IP infringement, or confidentiality breaches, parties often carve it out or apply a higher cap. The contract should say this directly instead of leaving the sections in tension.
It gives the parties a moving formula tied to the commercial relationship. The problem is that it can be too low if the fees are small but the operational risk is large.
A liability cap is the contract's financial ceiling. The amount, formula, and carve-outs decide whether a serious breach has meaningful consequence. Always read it with indemnification, excluded damages, confidentiality, and insurance requirements.
See how this clause behaves in the real contract.
The clause library gives you judgment. The full review shows how this clause combines with the rest of the agreement, then quotes the exact language, scores the risk, and explains what to push on next.