LawSnap Original Research
Contract Pattern Library
37 named structural patterns extracted from 107 attorney interviews and MCLE war stories. Lawyers in trucking, healthcare, SaaS, and construction were all describing the same contract traps — using completely different vocabulary. We cataloged them.
Each pattern has two names: what the drafter calls it, and what the other side is actually agreeing to.
The contract that gets reviewed isn't the one that actually controls. A less-scrutinized document — the SOW, the...
The contract's scope expands beyond what was originally agreed, through mechanisms controlled by the party requesting...
Categorical distinctions in the contract — what counts as a defect, a covered loss, a billable service — are drawn to...
A document incorporated by reference can be rewritten unilaterally after signing. Drafters call it operational...
A remedy or protection in the contract can’t function when you actually need it. For the drafter, it reflects the...
A standard form contract encodes the drafter’s preferred positions on every contested issue, then gets presented as...
A decision that controls payment, performance, or rights sits with a party who faces no deadline and no consequence for...
One party can walk away without meaningful consequence; the other is locked in. Drafters call it flexibility — essential...
About the Corpus
These patterns were identified through 107 attorney interviews and MCLE war stories collected across a dozen industries. The core finding: contract disputes in trucking, healthcare, SaaS, and construction describe the same structural traps — but practitioners in each field had developed entirely different names for them.
This library is original LawSnap research. It is not based on secondary sources. Each pattern is named from the drafter's perspective and the responder's perspective simultaneously, because the same clause reads as two different contracts depending on which side you are on.