If you've been asked to sign both a Master Service Agreement (MSA) and a Statement of Work (SOW), you're not looking at redundant paperwork — the two documents do different jobs, and the relationship between them is one of the most important things to get right in any services engagement.
What the MSA does
The MSA is the overarching contract. It sets the terms that apply to the entire relationship: liability caps, indemnities, confidentiality, IP ownership defaults, payment terms, termination rights, governing law. It's signed once and typically stays in place for the life of the relationship, covering every project that follows.
What the SOW does
The SOW defines a specific piece of work under that MSA: scope, deliverables, timeline, price, and any project-specific terms. A single MSA can have many SOWs signed under it over time — a new SOW for each new project, without renegotiating the underlying terms each time.
The clause that matters most: order of precedence
The single most important mechanic in an MSA/SOW structure is the order of precedence clause — which document controls if the two conflict. Most MSAs state that the MSA governs unless the SOW explicitly states otherwise for that specific point. Without a clear precedence clause, a conflict between an MSA's liability cap and a SOW's more aggressive terms can become a genuine dispute.
Common mistakes
- Treating the SOW as a fresh contract. If a SOW doesn't reference the MSA, or the two were drafted independently, none of the MSA's protections may actually apply to that specific project.
- Letting a SOW quietly override the MSA. A SOW that includes its own liability or IP language, without addressing precedence, can unintentionally supersede carefully negotiated MSA terms.
- Reusing an old SOW template for a materially different project — scope and deliverables need to be redrafted for the actual work, not copy-pasted from the last one.
When you only get one document
Smaller engagements sometimes skip the MSA/SOW split and use a single "Service Agreement" instead — combining both jobs into one document. That's often fine for simple, one-off engagements, but for anything ongoing or multi-phase, splitting the two makes future work faster to contract and easier to price consistently.
Where this shows up
We review all three documents — see our MSA review checklist, service agreement review checklist, and dedicated SOW review checklist for the scope, acceptance-criteria, and precedence-clause issues we check in each.
For the quick reference version of the clause that decides which document wins, see the order of precedence entry in our legal glossary.
