Statement of Work vs. MSA: What's the Difference?
SOWs and MSAs get used interchangeably in conversation but do very different jobs in a contract stack -- here is how each one works and why the distinction matters when you are reviewing either one.
July 20, 2026 · By ScopeWise Team
Two documents, two jobs
A Master Service Agreement (MSA) sets the general legal and commercial terms that govern a relationship between two parties -- payment terms, IP ownership, liability caps, termination rights, dispute resolution, governing law. A Statement of Work (SOW) defines a specific project: scope, deliverables, timeline, and price. The MSA is the foundation you build once; the SOW is the project you build on top of it. Confusing the two leads to two common mistakes -- negotiating liability terms fresh in every SOW instead of once in the MSA, or assuming a SOW inherits protections the MSA never actually granted.
When you only get a SOW
Not every engagement has an MSA. Smaller vendors and one-off projects often run on a standalone SOW that folds in the legal terms an MSA would normally carry -- liability caps, IP assignment, confidentiality, termination. When that is the case, treat the SOW with the same scrutiny you would give an MSA: those terms are not backstopped by anything else, so if the SOW's liability section is thin or missing, there is no fallback document to catch it.
How they interact once both exist
Once an MSA is signed, each subsequent SOW should reference it and stay inside the boundaries it sets -- adding project-specific scope, deliverables, and price without re-litigating legal terms. The failure mode to watch for is a SOW that quietly tries to change MSA terms (a different liability cap, a different IP assignment) without an explicit amendment. Most MSAs include an order-of-precedence clause for exactly this conflict, but that clause only helps if someone actually checks the SOW against it rather than assuming the MSA automatically wins.
What to check in each
In an MSA: liability caps and carve-outs, IP ownership defaults, termination rights (for convenience vs. for cause), confidentiality duration, and the order-of-precedence clause. In a SOW: deliverable definitions with acceptance criteria, explicit exclusions, timeline and milestones, pricing structure, and whether it references an MSA correctly or silently contradicts one. If a SOW touches liability, IP, or payment terms that differ from its MSA, that difference should be flagged and confirmed as intentional -- not caught after signature.