MSA vs SOW: What Each Covers and Which Signs First
An MSA (master service agreement) holds the legal terms you negotiate once: payment defaults, IP ownership, liability, and how to exit. An SOW (statement of work, or scope of work) holds the specifics of one project: deliverables, timeline, and price. The MSA signs first and stays in place; you attach a new SOW for each project.
This guide shows exactly what belongs in each document, the order to sign them, and when you can skip the split entirely.
Quick summary
- The MSA is the reusable legal framework; the SOW is the per-project detail.
- Sign the MSA first, then attach SOWs under it as new work comes in.
- The split saves you a full contract negotiation on every repeat project.
- For a single one-off job, one combined contract is perfectly fine.
The core difference
Think of the MSA as the rulebook and the SOW as the play. The MSA decides how the relationship works no matter what project you run; the SOW decides what you are actually building this time.
The reason to separate them is efficiency. You negotiate the hard legal terms (liability, IP, payment defaults) a single time. After that, starting a new project is a short SOW rather than another round on indemnity clauses.
What each document covers
| Element | Master service agreement (MSA) | Statement of work (SOW) |
|---|---|---|
| Purpose | Governs the whole relationship | Defines one specific project |
| Payment terms | Defaults: late fees, net terms, deposit policy | The price and schedule for this project |
| IP ownership | Who owns work, and when it transfers | (Inherits from the MSA) |
| Liability and indemnity | Caps and protections | (Inherits from the MSA) |
| Cancellation | Notice period, exit terms | (Inherits from the MSA) |
| Deliverables | Not specified | Exact list, with quantities |
| Timeline | Not specified | Milestones and dates |
| Out of scope | Not specified | Explicit exclusions |
| How often signed | Once | Per project |
Which one signs first
The MSA signs first. It establishes the legal ground rules before any specific work is defined. The first SOW can be signed at the same time as the MSA, but it always sits under the MSA's terms.
For every project after that, you reuse the existing MSA and add a fresh SOW. A clean scope of work is the document that defines deliverables and price, while the MSA quietly keeps doing the legal protecting in the background.
When you do not need both
The two-document split earns its keep with repeat clients. For a single, small, one-off project, it is overkill.
In that case, use one combined agreement that contains both the legal terms and the project scope. You get the same protection without the overhead of two documents for a relationship that may never repeat. The split becomes worth it the moment you expect a second project.
How the SOW protects your margin
The MSA protects you legally, but the SOW protects your profit. It is where deliverables, revision caps, and exclusions live, which is what stops scope creep from quietly eating the project.
Pair a tight SOW with a change-order process and you have the full system: the MSA governs the relationship, the SOW defines the work, and the change order handles anything new.
When the MSA vs SOW split is the wrong choice
If you are a solo freelancer doing small one-off gigs, maintaining a separate MSA and SOW can be more process than the work justifies. Clients can stall on signing a "master agreement" that feels heavyweight for a $2,000 project.
The honest line a competitor will not write: for low-value, infrequent work, the two-document setup can actually slow your sales cycle. Use a single short contract until you have repeat clients or deal sizes that make the legal negotiation worth doing once.
Frequently asked questions
What is the difference between an MSA and an SOW?
An MSA (master service agreement) sets the legal terms that govern the entire client relationship: payment defaults, IP ownership, liability, and cancellation. An SOW (statement or scope of work) defines a single project's deliverables, timeline, and price. The MSA is reused; the SOW changes per project.
Which is signed first, the MSA or the SOW?
The MSA is signed first because it establishes the ground rules. The first SOW can be signed at the same time, but it always operates under the MSA. For later projects, you reuse the existing MSA and add a new SOW.
Do I need both an MSA and an SOW?
Not always. For repeat clients, the split saves you from renegotiating legal terms every project. For a single small one-off job, one combined contract that includes both the legal terms and the project scope is enough.
Can an SOW exist without an MSA?
Yes, but then the SOW has to carry the legal terms itself, which makes it a full contract rather than a project addendum. The cleaner setup is an MSA holding the legal terms with SOWs attached, so each project document stays short.
Related guides:
Ready to streamline your business?
Try Agiled free and see how our all-in-one platform can help you manage your business more efficiently.