Order of precedence: the clause that decides which document wins
In short
An order of precedence clause ranks the documents in a contract family, so that when the master agreement and the statement of work disagree, one of them wins by rule rather than by argument. It is the reason a single file is an incomplete unit of review: the same clause can be binding, overridden or irrelevant depending on where its document sits in the stack.
Key takeaways
- A precedence clause ranks instruments; it does not resolve a contradiction inside a single document.
- The same term can be binding under one ranking and overridden under another, with no change to its wording.
- The reviewable unit is the contract family, not the file that happened to be uploaded.
- Most precedence clauses carry an exception for expressly negotiated changes, which quietly inverts the ranking.
An order of precedence clause states which document controls when 2 documents in the same deal say different things. It is a ranking rule, usually one sentence listing the instruments from most to least authoritative, and it exists because a commercial relationship is almost never one file.
The clause is short and its consequences are not. It decides, with nobody renegotiating, whether the termination right in a master agreement survives a statement of work saying the engagement is locked for a year.
The stack a precedence clause is ranking
- The master agreement. General terms intended to outlive any single piece of work.
- The order form or schedule. Commercial specifics — quantity, term, fees, named product — often on its own signature page.
- The statement of work. Deliverables, acceptance and dates, frequently drafted by delivery people rather than lawyers.
- Amendments and addenda. Later in time, usually intended to beat everything above, though the clause has to say so.
- Incorporated documents. Policies and service descriptions brought in by reference, sometimes as a live URL rather than an attachment.
Only the first 4 are usually in the reviewer's hands. The fifth is the one that can change after signature.
Two lines, two answers
Take a master agreement saying either party may terminate for convenience on 90 days' notice, and a statement of work under it saying the engagement may not be terminated before the end of its 12-month initial period. Neither sentence is ambiguous. The answer depends entirely on the ranking.
| Precedence order | Which text governs | What the client is told |
|---|---|---|
| Master agreement first | The 90-day termination right | You can exit any engagement on 90 days' notice, whatever a SOW says |
| SOW first | The 12-month lock | You are committed for the initial period on this engagement |
| Master first, except where a SOW expressly amends it | The 12-month lock, because the SOW names the termination clause it varies | Check every SOW before assuming the exit right survives |
The third row is the common drafting, and the one that defeats naive automation. The ranking is not a fixed list; it is a list with a conditional override, and the condition is a property of the lower document's wording.
The exception that inverts the list
A precedence clause that says the lower document prevails only where it expressly refers to the clause it varies does real work: it stops a delivery team rewriting the liability position in a deliverables table. But the reviewer can no longer answer which document controls from the precedence clause alone. They have to read the lower document for the phrase that claims the override.
The reviewable unit is the family, not the file
This is the engineering consequence, and it is uncomfortable because most review tools are built around an upload. A statement of work reviewed alone can produce a report that is internally correct and practically wrong: every term in it is subject to a document the system never saw.
- Establish the family before analysing anything: which master agreement this document hangs off, which amendments exist, and what is incorporated by reference.
- Find and parse the precedence clause, including its override condition. If there is no such clause, record that — silence is a finding, not a default.
- Resolve conflicts term by term, recording which instrument won and why, so a reviewer can audit the reasoning rather than the conclusion.
- State coverage in the output. If a referenced document is missing, every conflict involving it is unresolved, and the report should say which ones.
Step 4 is the honest part and the one most often skipped. A review that answers confidently from an incomplete family is worse than one that reports a gap, because nothing downstream can tell the difference. The same root shows up in a review that is right about a superseded version.
A clause is not binding because it is written down. It is binding because its document outranks every document that says otherwise.
What precedence changes elsewhere in review
- Definitions. A term defined one way in the master agreement and another in a schedule is a precedence question before it is a drafting question — see defined terms and where their meanings move.
- Indemnities. A narrow indemnity in a SOW can be widened by the master agreement above it, one more reason half an extracted indemnity is worse than none.
- Redlining. Editing the losing document changes nothing, so an edit must name its instrument — and arrive as a tracked revision, not clean text with the history gone.
- Cross-references. Precedence reasoning needs stable clause numbers, and assembly breaks them, as in cross-references that point one clause off.
None of this is unique to legal documents. An operations team reading a rate confirmation without the master carrier agreement behind it has the same problem, which is why the systems that survive run on documents an operation already emits — the argument in our notes on AI in logistics operations. Assembling the family, then reasoning over it, is the work described under AI agents and automation. Siblings sit in contract review and redlining, inside our work with legal teams.
Frequently asked questions
Short answers to the follow-ups this page tends to raise.
What is an order of precedence clause?
It is a clause that ranks the documents making up an agreement, so that a conflict between them is resolved by the ranking rather than by negotiation. A typical clause lists the master agreement, order form, statement of work and any incorporated policies in priority order, and many add an exception for lower documents that expressly amend a named clause.
Does the MSA or the SOW control when they conflict?
Whichever the precedence clause ranks higher, and the answer varies by contract. Many master agreements rank themselves above every statement of work, then carve out an exception where the SOW expressly says which clause it is varying. Read the ranking and the exception together; either one on its own gives the wrong answer.
What happens if there is no order of precedence clause?
The conflict becomes a matter of interpretation rather than a mechanical rule, and the outcome is far less predictable. Record the absence explicitly during review: a missing precedence clause is worth raising in negotiation, particularly where the deal will generate many statements of work drafted by people who never read the master agreement.
- order of precedence
- contract structure
- MSA and SOW
- contract review
The work behind this page
Builds from our portfolio that this page draws on.
Read next
- Defined terms: no clause can be judged without its definitionA capitalised term carries whatever meaning the contract assigns it, wherever that assignment happens to live. Judge the clause without resolving it and you have judged a sentence you have not read.definition
- Third-party paper: why their template is a different job from your ownOn your own template, review is a diff against known positions in known places. On the counterparty's, you have to rebuild the map before you can judge a single clause.definition
- Fallback positions: preferred, acceptable and walk-away, in one ladderA playbook that records only your ideal clause can say the counterparty deviated. It cannot say what to send back, which is the part a negotiator needs.definition
- The liability cap is three fields, and only one of them is a numberThe cap is not a number. It is an amount, a basis that computes the amount, and a list of obligations that sit outside both — and the third one decides how bad the worst day gets.definition
Working on something in this space?
Tell us where you are in a sentence or two. We'll tell you honestly whether we're the right team, and what a sensible first slice of the work looks like.
Start the conversation