Small Business
MSA vs SOW: How the Two Documents Fit Together
By FixMyContractLast updated Sep 27, 20266 min read
A master services agreement (MSA) sets the general rules for a working relationship — how invoices are paid, who owns the work, who carries the risk, how either side can leave. A statement of work (SOW) describes one specific project under those rules — what will be delivered, by when, for how much. You usually sign the MSA once and a new SOW for each project.
Freelancers, agencies, contractors and small businesses on either side of the table meet this pair all the time. The two documents are usually read together, so a gap or a clash between them can matter as much as anything inside either one.
What goes in each document
| Topic | Usually in the MSA | Usually in the SOW |
|---|---|---|
| What is delivered | A general description of the services | The specific deliverables, quantities and formats |
| Timing | How long the relationship lasts | Dates and milestones for this project |
| Price | Rates, invoicing and payment timing | The fee or budget for this project |
| Acceptance | The general process for approving work | The criteria for this project's deliverables |
| Ownership of work | Who owns what is created, and when | Anything specific to this project, such as licensed tools |
| Confidentiality | The duty for the whole relationship | Rarely repeated |
| Liability and indemnity | Caps and who covers which claims | Rarely — and worth noticing if it is there |
| Ending the deal | How the MSA ends, and what happens to open projects | How this project can be stopped or changed |
The SOW itself is explained in the glossary entry for scope of work — "scope of work" and "statement of work" often name the same document. Other names you may see for it: work order, order form, project schedule or task order.
How the two fit together
- The MSA is the frame; each SOW plugs into it. A new project usually needs only a new SOW that refers to the MSA, not a new contract.
- An SOW without an MSA stands alone. If there is no MSA, the SOW usually carries the payment, ownership, liability and exit terms itself; where it does not, those questions can be left open.
- An MSA without an SOW usually has no work in it. Signing an MSA usually commits nobody to a project yet. The obligations to deliver and to pay usually start with the SOW.
- One document usually names which wins. This is often an "order of precedence" sentence. Some MSAs say the MSA wins over any SOW; others let an SOW change the MSA if it says so expressly. It usually decides what happens when the two disagree.
- The documents usually list each other. The MSA's entire agreement clause often says which documents make up the contract. A common check is whether the SOWs are on that list.
What to check in the MSA
- Order of precedence. Which document wins in a conflict, and whether an SOW can override the MSA.
- Payment mechanics. When invoices are due, what starts the clock, and what happens when a payment is late. The SOW sets the amount; the MSA usually sets the rules.
- Ownership of work. Whether ownership passes on delivery or on payment, and whether tools you already had stay yours. This applies to every future SOW at once.
- Liability cap. What the cap is measured against. A cap tied to "fees paid under the applicable SOW" can be much smaller than one tied to all fees under the MSA, and the difference grows with every project. See limitation of liability.
- Ending the MSA. If either side ends the MSA, the question is whether open SOWs end too or run to completion, and what is paid for work already done. See termination for convenience.
- Changes to the MSA itself. Whether the other side can update its terms by notice, or only by a document you both sign.
What to check in each SOW
- It points to the right MSA. The name and date usually match the MSA that was signed.
- Deliverables are specific. Named items, quantities and formats — not an outcome such as "a modern website."
- What is out of scope. A short list of what the project does not include can prevent common arguments later.
- Acceptance. How long the client has to review, and what happens if it says nothing. See deemed acceptance.
- Changes. How extra work is priced and approved — usually a written change order. See scope creep.
- Anything that changes the MSA. If the SOW adds a new liability, ownership or payment term, the question is whether the MSA lets it override the general rules.
A realistic example
A small design studio signs an MSA with a retailer, then three SOWs over a year. The MSA caps the studio's liability at the fees paid under the SOW that gave rise to the claim. The third SOW is a small one. A problem on that project could be capped at that SOW's fee — a very different picture from a cap on everything the retailer has paid under the MSA.
FAQ
Do I need both an MSA and an SOW? Not always. A one-off project often uses a single agreement that covers both the rules and the work. The pair makes most sense when the same two parties expect more than one project.
Which one do I sign first? Usually the MSA, then the first SOW. Sometimes both are signed together. A common check is that each SOW refers to an MSA that has actually been signed.
Can an SOW change the MSA? Usually only if the MSA allows it. The order-of-precedence sentence usually decides whether the MSA or the SOW wins when they disagree.
Both documents, side by side
FixMyContract reads the MSA and the SOW one at a time and shows how each reads from your side and what people usually ask to change. We review the documents you were sent rather than draft them; where a report shows alternative wording for a clause, it is generic text to start a discussion, not a finished clause.
👉 Check a service agreement free — your first analysis is free, no card, no deadline to use it.