MSA vs SOW: how master agreements and statements of work fit together

The split saves time with clients who come back: legal reviews the MSA once, and every later project only needs a one- or two-page SOW. This page is part of our contracts and signatures guides. If you work project by project with different clients, the single-project freelance contract template is usually enough.

What goes in the MSA and what goes in the SOW

When a freelancer needs an MSA

• The client will send you several projects a year, each with its own price.
• The client's legal team is slow, and you don't want to wait for a full contract review on every project.
• You work as a subcontractor for an agency that sends a steady stream of jobs.
• You run a retainer with occasional extra projects on top.

For a single project, or a client you're not sure you'll see again, a single contract with the scope inside it is fewer documents and fewer places for a conflict.

The order-of-precedence clause

Two documents can contradict each other: the MSA says invoices are due in 15 days, a SOW written in a hurry says 30. A contract is an agreement the law will enforce (LII Wex: contract), and when two parts of it disagree, a court looks for what the parties intended. Save everyone the argument with one paragraph:

ORDER OF PRECEDENCE
Each Statement of Work ("SOW") is governed by this Agreement. If a SOW conflicts with this Agreement, this Agreement controls, unless the SOW expressly identifies the section of this Agreement it changes and both parties sign the SOW. Any such change applies only to that SOW.

SOW FORMAT
Each SOW will state: the project name, deliverables and revision rounds, timeline and Client responsibilities, acceptance criteria, fee and payment schedule, and the SOW's start date. A SOW takes effect when both parties sign it.

Mistakes that make the split backfire

• Putting payment terms in both documents with different numbers. Write them once, in the MSA, and let a SOW change them only by naming the section it changes.
• Starting work on a SOW nobody signed. If the client disputes the price later, an unsigned SOW is weak evidence of what was agreed.
• Letting the MSA expire quietly. If it has a term (often one or two years), a SOW signed after it lapses may sit under no general terms at all. Add automatic renewal, or a line saying the MSA keeps governing any SOW still open.
• Copying scope into the MSA. Deliverables that belong to one project end up binding every later one.
• Forgetting acceptance criteria. "Website delivered" invites a fight; "5 pages live on the client's domain, passing the checklist in Appendix 1" doesn't.

Large organizations work the same way. US federal contracting has its own version of the SOW: FAR 37.602 asks agencies to describe the work in a performance work statement in terms of the required results rather than how the work is done, with measurable standards. That is a useful test for a freelance SOW too: could the client check each deliverable off a list without asking you what you meant?

If you sign electronically, the same rules apply to both documents. The federal ESIGN Act and state UETA laws give an electronically signed MSA or SOW the same effect as a paper one, so a quick signature on each new SOW is as binding as the MSA it sits under.

Signing both

Send the MSA for signature once, then each SOW as its own short document. With SoloWOS you can write the SOW's scope and price in Proposals so the client accepts it online, and then send the signed PDF for e-signature, automatically if you choose, when the proposal is accepted. Solo includes 15 signature requests a month for $15/month. For what each part of a SOW should say, see the statement of work template; for clauses that usually sit in the MSA, see limitation of liability and work for hire vs assignment.