SOW vs MSA: which document wins when they contradict each other

The two-document structure is standard for a reason: negotiate the legal terms once, then start each new project with a short document about the work itself. It saves everyone weeks.

It also creates a failure mode that a single agreement doesn't have. Two documents can contradict each other, and unless the contract says which one wins, the answer is genuinely unclear — which is the worst possible state for a term you're relying on.

What each document is for

That last row is the whole problem in one line. The MSA gets legal review because everyone knows it matters. The SOW gets signed by whoever owns the project, on the assumption that it's just scope and dates.

Then an SOW says "Supplier's liability under this SOW shall not exceed the fees payable hereunder" and, depending on the precedence clause, it has just rewritten a term nobody meant to reopen.

The order-of-precedence clause

This is the clause that resolves conflicts, and every MSA should have one. The most common formulation is:

In the event of any conflict or inconsistency between this Agreement and any Statement of Work, the terms of this Agreement shall control, except where the Statement of Work expressly identifies the specific section of this Agreement being modified and states the parties' intent to modify it for that Statement of Work only.

Two things make this version work:

• The MSA wins by default. Silence in an SOW never overrides negotiated legal terms.
• Deliberate overrides are still possible, but only by naming the section being changed. That turns an accidental override into an explicit one that someone has to write down on purpose — which means it gets noticed.

The variant to push back on is a bare "in the event of conflict, the SOW shall control." It reverses the protection: every SOW becomes an unreviewed amendment to your master terms.

What counts as a "conflict" is narrower than you think

Precedence clauses only engage when two provisions genuinely conflict — when they cannot both be given effect. A term that is merely additional usually isn't a conflict at all; it just applies.

That distinction matters more than the precedence clause itself. If the MSA is silent on acceptance testing and the SOW adds a 10-day acceptance window, there is no conflict — the SOW term simply governs. Precedence protects you from contradiction. It does not protect you from an SOW adding obligations the MSA never contemplated.

Which means: an order-of-precedence clause is not a substitute for reading the SOW.

The five things to check in every SOW

Even a well-drafted MSA leaves these to the SOW, and they're where SOW-level disputes actually come from.

1. Scope, stated as exclusions too. "Supplier will build X" invites argument about whether Y was included. A short "out of scope" list is worth more than another paragraph of scope.
2. Acceptance criteria. Who decides a deliverable is done, against what standard, within how many days, and what happens on rejection? Without a deemed-acceptance period, a deliverable can sit unaccepted — and unpaid — indefinitely.
3. Change control. How a change to scope becomes a change to fees and timeline, in writing, signed by both sides. Its absence is the single most common source of project disputes.
4. Fees and what triggers them. Fixed fee, time and materials, or milestone-based — and if milestone-based, whether the milestone is tied to delivery or to acceptance.
5. Anything that looks legal. Liability, IP, confidentiality, warranties, indemnities. If a legal term appears in an SOW, someone put it there on purpose. Read it against the MSA section it touches.

Point 5 is the one to make a habit of. A quick search of every SOW for "liability," "indemnif," "warrant," and "intellectual property" takes thirty seconds and catches most silent amendments.

Purchase orders, portals, and the third document nobody counted

The MSA/SOW pair is clean. Reality often adds a third set of terms: the pre-printed conditions on a purchase order, the click-through terms in a vendor portal, or an invoice with payment terms that differ from the contract.

A well-drafted MSA handles this directly:

Any additional or conflicting terms contained in any purchase order, invoice, portal, or other business form shall be void and of no effect, notwithstanding acceptance of such document by either party.

Without that clause, routine operational paperwork can become a competing set of terms, and the resulting analysis is exactly as unpleasant as it sounds.

Getting the structure right from the start

If you're setting up the relationship:

• Negotiate the MSA properly once, and treat that time as amortized across every SOW that follows.
• Put a precedence clause in the MSA that defaults to the MSA and requires named-section overrides.
• Add the purchase-order-terms-are-void clause.
• Make the SOW template short and structural — scope, exclusions, deliverables, acceptance, milestones, fees, change control — with no legal terms section at all. A template with no obvious place to put a liability cap is a template where nobody accidentally puts one.
• Have every SOW reference the MSA by name and date, so the two are provably connected years later.

That last point sounds administrative until an SOW turns up that references "the Master Services Agreement between the parties" with no date, and there are two.

Related reading

The legal terms the MSA should be getting right are covered in five clauses we always flag in vendor MSAs, limitation of liability, explained, and indemnification clauses, explained. For the order to read the whole package in, see how to review a contract without a lawyer.

A disclaimer

This describes how MSA and SOW structures are commonly drafted and where they commonly fail. It is not legal advice and creates no lawyer–client relationship. How a court resolves a conflict between related documents depends on the specific wording and the governing jurisdiction. If two of your documents already contradict each other, that's a question for a lawyer rather than a checklist.