Most legal teams have a documented position on indemnity caps. The standard language is well-known: mutual indemnification, capped at fees paid in the twelve months preceding the claim, with carve-outs for gross negligence, willful misconduct, and IP infringement. The position exists in some version of a playbook. Attorneys know it.
And yet non-standard indemnity structures consistently make it to signature. Not because the attorneys are wrong about what the standard is, but because indemnity provisions in counterparty paper are written to obscure the deviation from that standard until you are reading carefully. This post is about the specific structural variations that evade standard playbook checks, and why most playbooks are not configured to catch them.
The Problem Is Not Your Cap Amount — It Is the Cap Structure
When a playbook says "indemnity capped at 12 months of fees," it is addressing cap amount. That is the right thing to address. But sophisticated counterparty paper increasingly structures indemnity caps in ways where the amount is technically compliant while the exposure is meaningfully different.
Consider these variations, all of which can appear while the stated cap amount matches your playbook:
Asymmetric caps by obligation type: Vendor paper frequently sets a low cap — sometimes as low as direct fees paid — for most indemnification obligations, while including a separately structured, effectively uncapped indemnification for the vendor's IP infringement claims against you. The seller is capped; the buyer's IP-adjacent obligations are not. On a quick read, the cap language looks present. On a careful read, it applies to only a subset of the indemnification obligations.
Fee-paid period definitions: "Fees paid in the 12 months preceding the claim" sounds standard. Look at how the period is calculated. Some vendor forms define the reference period as the 12 months before the event giving rise to the claim rather than the claim itself. On a multi-year agreement where fees escalate, this distinction can meaningfully change the cap floor. Others calculate from the date of the agreement rather than from the claim — which on a new contract means the cap applies against fees that have not yet been paid, and so the effective cap at month one is zero.
Aggregate versus per-claim caps: Your playbook may specify an aggregate cap without specifying whether it applies across all claims in the agreement term or resets annually. Vendor paper written to favor the vendor often includes an aggregate lifetime cap on indemnification. If you have a ten-year supply agreement with annual fees, a lifetime aggregate cap equal to one year's fees is materially different from what an annual reset would produce.
Mutual versus unilateral language that reads mutual: Indemnification provisions often use "each party shall indemnify the other party" framing that appears mutual. Read the definitions. If "Losses" is defined differently for each party — or if the triggering events for indemnification are specified asymmetrically in a way that practically benefits one side — the mutuality is formal rather than substantive.
Why Playbooks Miss These Variations
The deeper issue is that most playbooks specify approved positions on the headline terms of a clause without specifying all of the structural elements that determine what the headline term actually means. A playbook position that says "cap at 12 months fees, carve-outs for IP and gross negligence" is correct as far as it goes. It does not give a reviewer enough specificity to flag asymmetric IP carve-outs, fee calculation period games, or aggregate-versus-per-claim questions.
This is partly a playbook maintenance problem. Indemnity structures that sophisticated counterparties use today are more varied than they were when most playbooks were written. The playbook was accurate when drafted; it has not kept pace with the range of structures in current market practice.
It is also a review-time problem. Evaluating indemnity cap structure completely — checking mutuality, carve-out asymmetry, fee period definition, and aggregate versus per-claim — requires reading three to five different defined terms in addition to the indemnification section itself. Under volume pressure, that complete evaluation does not happen on every agreement.
We're not saying the solution is to write longer playbooks. More detail in a PDF that gets consulted occasionally does not fix the problem. The playbook needs to be actionable at review time, not comprehensive in the abstract.
Building Indemnity Checks That Actually Work
The practical response is to decompose your indemnity cap position into specific checkable elements rather than a single summary position. For each vendor agreement where indemnification applies, a reviewer should be able to confirm or flag:
- Is the cap mutual, or does it apply asymmetrically to one party's obligations?
- Is the fee reference period calculated from event, claim date, or agreement start?
- Are any indemnification obligations (particularly IP indemnification) excluded from or separately capped under the stated limit?
- Is the cap aggregate across the term, or does it reset on an annual basis?
- Do the carve-outs for gross negligence and willful misconduct apply to both parties or only to one?
This is five distinct checks, not one. When we design playbook rules in Repovyn for indemnity cap review, we treat each of these as a separate clause attribute to be matched against the counterparty's language. A contract can pass the headline check — cap amount present, carve-outs present — and still have a HIGH flag on asymmetric IP exclusion or a REVIEW flag on fee period definition.
The value of that decomposition is not that it tells the attorney what decision to make. An asymmetric IP indemnification structure might be entirely acceptable given the nature of the vendor relationship and the IP at stake. The value is that the decision gets made consciously rather than by omission.
The IP Indemnification Carve-Out Specifically
IP infringement carve-outs deserve separate treatment because the language patterns are particularly varied and the potential exposure is asymmetric.
Standard market practice calls for the vendor to indemnify the customer against third-party IP infringement claims arising from the vendor's product or deliverables. This indemnification is typically excluded from the overall cap — meaning the vendor's IP indemnification obligation is uncapped. That structure is normal and appropriate: it protects the buyer from a scenario where the product they licensed turns out to infringe a patent and they face a claim from a third party they had no role in creating.
Vendor paper sometimes flips this. The vendor's IP indemnification obligation remains uncapped or is capped very high. The customer's indemnification obligation for customer-provided materials — content, data, specifications the customer gave the vendor — is also uncapped or capped high. This looks like symmetry. But if the customer-provided materials are broad (all data provided to the platform, all specifications for deliverables), the uncapped customer-side obligation is a significant exposure, particularly in data-intensive vendor relationships.
Playbooks that specify "IP indemnification excluded from cap" without specifying which party's IP indemnification, and under what triggering conditions, leave this structural variation invisible.
Practical Configuration for High-Volume Review
For teams reviewing 50-plus vendor agreements per quarter, the overhead of applying the five-element check above manually to every indemnification clause is not realistic. The realistic target is consistent first-pass flagging: flag every contract where the indemnification structure deviates from the decomposed baseline, and route those deviations to attorney review.
Consider an in-house legal team at a growing SaaS company processing vendor agreements for infrastructure vendors, data providers, and professional services firms. The company has a standard MSA template and a playbook position on indemnity. When we looked at a representative sample of counterparty-form agreements that team had signed, roughly 40 percent had at least one of the five structural variations described above — asymmetric caps, fee period quirks, aggregate-versus-annual ambiguity. Most had been accepted without flagging because the headline cap amount and carve-out list matched the playbook at a surface level.
The fix was not to negotiate every deviation. Many were accepted as a business decision after conscious review. The fix was to make sure the decision was made with full information rather than by a reviewer who had focused on the cap amount and moved on.
Indemnity cap language is familiar enough that it creates a false sense of completeness. You see the cap. You see the carve-outs. You move to the next section. The structural variations are designed — often deliberately — to look like standard language until you pull them apart. The playbook that catches them is the one specific enough to require the pulling apart.