SOW vs MSA: what's the difference and why it matters

If you're negotiating vendor or client agreements, you'll often see two documents: a Master Service Agreement (MSA) and a Statement of Work (SOW). They serve different purposes, and the relationship between them matters more than most teams realize.

What the MSA covers. The MSA is the framework agreement. It sets the general terms: liability caps, indemnification, IP ownership, confidentiality, termination rights, governing law, and dispute resolution. It's meant to be negotiated once and applied to multiple engagements.

What the SOW covers. The SOW is the engagement-specific document. It defines what's actually being delivered: scope, timeline, deliverables, milestones, pricing, and acceptance criteria. Each new project or phase typically gets its own SOW under the same MSA.

Why the split matters. The MSA-SOW structure saves time. You negotiate the hard stuff (liability, IP, termination) once, then scope each project quickly with a new SOW. But this only works if the documents are consistent and the SOW doesn't silently override the MSA.

Conflict clauses. Check which document controls when they disagree. Most MSAs include an "order of precedence" clause — typically the MSA governs unless the SOW explicitly states otherwise. If the SOW says it takes precedence, a vendor can rewrite your carefully negotiated liability cap or IP terms in a two-page scope document. Read the precedence clause and know what you're signing.

Common gaps between MSA and SOW:

• Payment terms in the SOW that differ from the MSA (net-30 vs net-60, milestone-based vs monthly).
• IP ownership assumed in the SOW ("all deliverables are work-for-hire") without matching language in the MSA.
• Acceptance criteria missing entirely — leading to disputes about whether the work is "done."
• Change order process not defined — leaving scope creep unmanaged.

Practical advice. When you receive an MSA and SOW together, review the MSA first — that's where the risk lives. Then check the SOW for consistency: does it reference the MSA? Does it conflict on price, IP, or payment? Is there a clear process for changes?

If you're reviewing contracts regularly and want to spot these gaps quickly, try a free risk analysis or see how it works.