Classification Arbitrage/The Definitional Wedge
Categorical distinctions in the contract — what counts as a defect, a covered loss, a billable service — are drawn to exclude situations that would actually trigger a payment or obligation. For the drafter, it’s precision and pricing discipline. For the responder, the definitions exclude exactly the scenarios that actually happen.
Appeared in 32 corpus episodes across multiple industries
On this page
What It Is
Categorical distinctions in the contract — what counts as a “defect,” a “covered loss,” a “billable service,” a “material breach” — are drawn to systematically exclude identical situations that would otherwise trigger an obligation or payment.
Two Readings
The same clause. Two entirely different contracts.
Definitions create precision and limit liability to situations you’ve actually priced for. Clear scope definitions prevent disputes about what’s included. The categories are drawn where they are because that’s the risk you modeled and the exposure you agreed to take.
The definition that seemed neutral at signing excludes exactly the scenarios that actually happen. The distinction between “defect” and “enhancement,” or “covered” and “excluded,” is drawn precisely to eliminate the cases where you’d need to make a claim.
Recognition Signals
Contract language that signals this pattern is present.
- Definition sections that are unusually long or specific
- "Defect" defined to exclude design-related failures or performance degradation
- "Covered loss" with carve-outs that effectively swallow the coverage
- "Material breach" defined so narrowly it excludes breaches that are actually material
- Services defined narrowly, with "additional services" requiring separate SOWs and fees
- "Bug" vs. "feature request" distinctions in software agreements that the vendor controls
The tell: map each definition to the scenario where you’d need to invoke it. If the definition excludes that scenario, you have Classification Arbitrage.
What to Do
Draw definitions to reflect the actual risk you’ve priced for. Definitions that are too aggressive — excluding situations any reasonable party would consider covered — invite disputes and may not hold up. Precision that you can defend is more valuable than exclusions that maximize short-term protection.
Read every definition. Then map each one to the actual scenario where you’d need to invoke it. Ask: does this definition cover the situation I’m worried about? If it doesn’t, negotiate the definition — not the remedy. A well-drawn definition is worth more than a strong remedies clause with a narrow trigger.
Where It Appears
Cross-industry appearances from the LawSnap corpus.
| Industry | How it appears |
|---|---|
| Insurance | Policy defines “occurrence” to exclude the exact events the insured faces |
| SaaS / MSA | Support SLA covers “defects” but not “performance issues” — distinction drawn and interpreted by vendor |
| Employment | Termination “for cause” defined broadly enough to capture what would otherwise be without-cause terminations |
| Construction | Warranty covers “workmanship” but excludes “design” — a distinction that eliminates most real warranty claims |
| Distribution | Exclusivity defined to exclude the exact channels where the market is actually developing |
LawSnap Contract Pattern Library
37 named structural patterns extracted from 107 attorney interviews and MCLE war stories across trucking, healthcare, SaaS, construction, and more. Lawyers across every industry were describing the same traps in completely different vocabulary. We cataloged them.
Browse all patterns arrow_forwardGet notified when new patterns are added.
We're cataloging all 37 patterns from the corpus. One email when new patterns go live — nothing else.
One email per update. No newsletter. Unsubscribe anytime.