The Invisible Operative Document/The Order of Precedence
The contract that gets reviewed isn't the one that actually controls. A less-scrutinized document — the SOW, the purchase order, the incorporated policy — governs when the dispute arises. Drafters design this structure deliberately. Responders discover it at the worst possible moment.
Appeared in 22 corpus episodes across multiple industries
On this page
What It Is
The contract the parties negotiate and scrutinize isn’t the one that actually controls when a conflict arises. A less-scrutinized document — an SOW, purchase order, exhibit, or incorporated policy — governs the actual dispute.
Two Readings
The same clause. Two entirely different contracts.
Multiple documents in a contract structure let different teams handle different pieces. The master agreement handles legal terms; the SOW handles commercial terms. The order of precedence clause determines which controls — a legitimate structural choice that keeps the deal organized.
You reviewed the master agreement carefully. Nobody told you that the purchase order signed later — or the exhibit you didn't read — overrides it on the exact issue now in dispute. The document that controls wasn't the one you focused on.
Recognition Signals
Contract language that signals this pattern is present.
- "As set forth in Exhibit A" without reviewing Exhibit A
- Purchase orders that incorporate separate terms by reference
- "In the event of conflict, the SOW controls" buried in the master agreement
- Any document that incorporates another by reference without attaching it
- Order of precedence clauses that reverse the intuitive hierarchy
- "Supplemental terms" or "additional terms" referenced but not attached
The tell: can you name every document that is part of this contract? If not, you haven't found the operative document yet.
What to Do
Know which document you want to control and draft the order of precedence clause explicitly to achieve that result. Ambiguous precedence clauses generate the litigation that explicit clauses prevent. Make the hierarchy visible.
Identify every document incorporated by reference before signing anything. Read them all. Ask explicitly: which document controls in a conflict? Get that answered in writing. Attach all incorporated documents to the master agreement at signing so the record is complete.
Where It Appears
Cross-industry appearances from the LawSnap corpus.
| Industry | How it appears |
|---|---|
| MSA / SaaS | Purchase order terms override master agreement on pricing and liability limits |
| Software Licensing | EULA incorporates separate acceptable use policy that controls actual restrictions |
| Insurance | Declarations page controls coverage; comprehensive policy document is secondary |
| Construction | Prime contract incorporates subcontract by reference; subcontract terms control sub's actual exposure |
| Distribution | Distributor agreement subject to manufacturer's "program terms" updated periodically |
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.