Liability Cap Reasonableness Review

Liability Cap Reasonableness Review

When to use this

Use this skill when a contract contains a limitation of liability clause and you need to assess whether the cap:

• Is appropriately sized for the contract value and risk profile
• Contains the right carve-outs for high-risk categories
• Is consistent across the indemnification and general liability sections
• Is enforceable in the governing jurisdiction

This is a specialized sub-review. Run alongside [[review-indemnification-balance]] and [[review-msa-deep-review]] for a complete commercial contract review.

Inputs

Cap Structures — Ranked

The following structures are listed in order from most Provider-friendly (lowest exposure) to most Client-friendly (highest exposure):

Reasonableness Factors

Apply these factors to calibrate whether the cap is appropriate:

Factor 1 — Contract Value Scaling

A cap should scale with the value the Protected Party is getting from the deal:

• A cap of 12-month fees on a 5-year, USD 10M TCV contract means the Client can only ever recover USD 2M from a USD 10M deal — that's 20% of total value at risk.
• Rule of thumb: the cap should cover at least the value the Protected Party has a reasonable expectation of recovering if the agreement fails entirely.

Factor 2 — Data Sensitivity

If the contract involves processing of personal data, sensitive personal data, or financially sensitive data:

• The risk of a data breach may dwarf the contract value (GDPR fines can reach 4% of global annual turnover; KSA PDPL fines up to SAR 5M; UAE PDPL fines up to AED 20M)
• Market trend: data breach indemnity and liability arising from privacy violations is increasingly carved out of the general cap entirely
• Flag if: data breach is included within a general 12-month fees cap — this is commercially inadequate for any meaningful data-processing engagement

Factor 3 — IP at Stake

IP indemnification is almost universally carved out from the general liability cap:

• The rationale: a vendor who infringes a third-party patent has exposed the Client to an injunction and royalty claims that may massively exceed the contract value
• An IP cap aligned with the general liability cap effectively gives the vendor unlimited freedom to infringe
• Flag if: IP indemnity is subject to the same cap as general liability

Factor 4 — Length of Contract vs. Cap Period

For multi-year contracts with a 12-month rolling cap:

• Year 1: client has exposure covered by fees paid in year 1
• Year 3: client has only the most recent 12 months of fees available — long tail is unprotected
• Better structure: TCV cap or 2× annual fees to avoid shrinking coverage relative to the full engagement

Factor 5 — Insurance Limits

Where the contract requires the Provider to maintain professional indemnity, cyber liability, or E&O insurance, the insurance limits form a natural floor for what the cap should be:

• If Provider's cyber insurance is USD 5M but the liability cap is USD 500K, the insurance serves no purpose for the Client
• Align: cap should be at least as high as the required insurance limits

Factor 6 — Jurisdiction-Specific Enforceability

Factor 7 — Carve-Out Consistency

The general liability cap should contain carve-outs for specific high-risk categories. Map carve-outs in the cap clause against what is actually covered in the indemnification and other sections:

Standard carve-outs from the general cap (should NOT count against it):

Mismatch flag: cap section uses "gross negligence" but indemnification section uses "willful misconduct only" — creates a gap where gross-negligence IP infringement is still capped.

Anti-Patterns to Flag

Output Format

{
  "cap_structure": {
    "type": "12-month-fees | 24-month-fees | 2x-annual | TCV | fixed-amount | uncapped",
    "amount_described": "<as drafted>",
    "estimated_amount_USD": <number or null>
  },
  "reasonableness_rating": 1-5,
  "recommended_position": {
    "ideal": "<description>",
    "acceptable": "<description>",
    "walk_away": "<description>"
  },
  "carve_out_analysis": [
    {
      "category": "ip | data-breach | fraud | death | confidentiality | ...",
      "status": "carved-out | within-cap | silent",
      "issue": "<if any>"
    }
  ],
  "jurisdiction_enforceability": "<note on governing law>",
  "anti_patterns": [
    { "pattern": "...", "severity": "critical|high|medium|low" }
  ]
}

Reasonableness rating: 1 = severely inadequate (Protected Party barely protected); 3 = market-standard; 5 = very strong (Protected Party well-protected).

Jurisdictional Notes on Market Standards

SaaS / commercial services (global market):

• 12-month fees is the market standard for Provider-side drafting
• Clients routinely push for 2× annual fees or TCV for contracts involving significant data or IP reliance
• IP indemnity: market is converging on uncapped or separate sublimit of 2× annual fees

Construction / FIDIC contracts (MENA):

• FIDIC Red Book / Silver Book: liability cap often linked to Contract Price; exclusions for fraud and wilful misconduct are standard
• UAE construction: courts have historically been willing to reduce disproportionate penalty clauses (Civil Code adjustability)

M&A (Representations and Warranties):

• Seller's liability cap for general reps: typically 20–30% of transaction value
• Seller's cap for fundamental reps (title, authority, taxes): often 100% of transaction value
• Fraud: uncapped by market convention

Related Skills

• [[review-indemnification-balance]]
• [[review-msa-deep-review]]
• [[review-risk-flagging]]
• [[review-unusual-terms-detector]]
• [[draft-msa]]