MSA vs SOW: master service agreement or statement of work?

A master service agreement (MSA) is the contract you sign once at the start of a client relationship, covering payment terms, intellectual property, confidentiality, liability and how disputes get resolved. A statement of work (SOW) sits underneath it and covers a single project: the deliverables, the dates, the acceptance conditions and the fee. You sign one MSA and then issue a separate SOW for every piece of work, which is why the two are nearly always used together rather than chosen between. If the two documents ever contradict each other, the MSA governs, unless the SOW names the conflicting section and overrides it deliberately.

Most of what's written on this runs from the client side: procurement teams and in-house counsel deciding how to manage a vendor, with the agency cast as the thing being managed. Useful enough if you're the one buying. This is the same comparison from the other side of the table, for the agency that issues the paperwork and then lives inside it for a year.

The running example is one client relationship worth $78,500 over twelve months, split across a single master services agreement and three statements of work, at a blended rate of $150 an hour. Every figure below is arithmetic on that example rather than an industry benchmark, so you can substitute your own numbers and the reasoning still holds.

What does a master service agreement cover?

A master service agreement covers everything about the relationship that doesn't change from one project to the next. Payment terms and late fees sit there, along with who owns the work and at what moment ownership transfers, confidentiality obligations in both directions, the cap on each side's liability, insurance requirements, how much notice either party gives before walking away, whether you can subcontract, whether the client can hire your staff, and which state's law applies if it ever gets that far.

What an MSA deliberately doesn't contain is a single deliverable, a single date or a single dollar of fee. That omission is the entire point. Those things change with every project, and the value of the master agreement is that it survives all of them untouched. Once the client's lawyer has read it properly, which is the slow part and frequently takes weeks on a first engagement, the second project can start on a two page document instead of another legal review.

What does a statement of work cover, and how is it different?

A statement of work covers one project and stops there, naming what you're building, what sits outside the fee, when each piece is due, the total fee and the payment schedule. The full contents, and which of those sections actually decide money, are set out in what a statement of work is, so the rest of this page assumes you already know. Writing one well is a separate craft, and the section-by-section version of that job is worth reading before you send your next one.

The cleanest way to keep the two straight is that the MSA answers how the two companies work together, and the SOW answers what's being built, by when, for how much. Anything that would be identical on your next three projects belongs in the master agreement, and anything that would change belongs in the statement of work. That single test resolves most of the drafting questions agencies get stuck on.

A client's procurement team will also ask for a scope of work when they mean a statement of work, and occasionally they genuinely mean the narrower document. The distinction between a scope of work and a statement of work is real but small, and it trips agencies up far more often than the MSA question does.

Which document comes first, and do you always need both?

The MSA comes first, since the SOW refers back to it and inherits its terms. In practice both get signed within a few days of each other on a first engagement, because a client rarely wants to negotiate liability caps before they know what they're buying. What matters is the order written into the documents rather than the order of the signatures, so the statement of work should name the master agreement and its date in its opening paragraph even when the two were signed the same afternoon.

You don't always need both, because a genuinely one-off project with no expectation of repeat work can run on a single agreement with the commercial terms folded in, and plenty of good agencies work that way for years. Our own rule of thumb is that the split earns its keep as soon as either of two things is true: you expect a second project from this client, or the engagement will run longer than about three months. Below that line, one document is less paperwork and no more risk.

The situation that catches agencies out is the opposite one, where the client hands you their MSA and expects you to sign it. Three clauses in a client-drafted master agreement deserve a careful read before anything else. The liability cap is often written as a multiple of the fees paid, and a cap set at fees paid under the relevant SOW in the previous twelve months is very different from an uncapped one. The intellectual property clause frequently transfers ownership on creation rather than on full payment, which quietly costs you the one piece of pressure a late invoice would otherwise give you. The termination clause often lets the client cancel for convenience on short notice, which is survivable only if the SOW says you get paid for work completed and committed up to that date.

What does the split look like across a real client year?

One master agreement and three statements of work is the shape a healthy agency account tends to take. The relationship in our example starts with the MSA, which carries no fee and no dates, and then produces three separate SOWs across the year, each issued under it and each referencing it by date.

Splitting the year into three documents rather than one large one buys you something specific. Each statement of work can be finished, paused or disputed without freezing the other two, so a disagreement over a retainer deliverable in September doesn't stall a website launch that's already paid 70 percent of its fee. Each one also carries its own acceptance conditions, which means the brand work can be signed off and closed while the build is still running.

What happens when the MSA and the statement of work disagree?

The MSA wins by default, because the SOW is issued under it and inherits its terms. This matters more than it sounds, since the conflicts that actually occur are boring ones. Your master agreement says net 15 and the SOW your project manager wrote says net 45. The MSA caps included revisions at two and SOW-02 promised three. In each case the client's finance team will read the master agreement and act on it, and your project manager's promise quietly evaporates.

The fix is a carve-out clause, written specifically rather than vaguely. A line saying the SOW controls in the event of conflict is close to worthless, because that line is itself in conflict with the MSA on the question of which document controls, so the version that works names the section by number.

Two sentences, two section numbers, and the ambiguity is gone. Plenty of templates note that order of precedence matters without ever writing the clause that settles it.

Does a mid-project request become a change order or a new SOW?

A change order, in almost every case where the request touches work an existing statement of work already describes. It's the question agencies actually have, and the paperwork usually answers it with one vague line. The client asks for a fourth revision round in week seven, or two more page templates, or a booking integration that was never mentioned. None of those needs a new contract, and all of them need a price.

A written threshold turns that judgment into an administrative step. Ours is that anything under roughly fifteen percent of the relevant SOW fee, and which moves final delivery by no more than a week, gets handled as a priced change order under the existing document. On SOW-02 that's $5,100, which covers most of what week seven produces. Anything larger gets its own statement of work, with its own dates, acceptance conditions and payment schedule, because at that size it's a project rather than an adjustment.

The reason to write it this precisely is arithmetic rather than legal caution. Three unpriced additions of about twelve hours each on the website build come to 36 hours, or $5,400 at the blended rate, against a margin of $10,200 if you priced that $34,000 project at thirty percent. Over half the profit disappears into three conversations that each felt too small to invoice for, which is the pattern behind what scope creep costs an agency across a year.

Naming the approver in the clause matters as much as naming the threshold. A change approved by a junior coordinator who wasn't authorized to spend $5,100 is a change you may end up eating, and one named email address in the SOW is what makes an approval trail hold up when that question arrives. The mechanism on the agency side is a standing form rather than an email thread, and a change request form with the impact already priced is what turns the clause from a paragraph into a habit.

A threshold agreed in advance turns a negotiation into an administrative step.

Is a statement of work legally binding on its own?

Generally it needs something around it, because on its own an SOW describes work rather than creating obligations between named parties with agreed terms. It carries weight once it references a signed master agreement, or once it contains the commercial terms itself. You will see it stated flatly that a statement of work is legally binding, with no qualification attached. Read past that.

None of this is legal advice, and we're not a law firm. We build software for agencies, so treat the clause language above as a starting point to take to a lawyer in your own jurisdiction rather than as something to paste into a live contract unreviewed. The audit trail our own product produces isn't court-proof either, and we've never claimed otherwise. It's obviously better than a Slack message, which is what most agencies are relying on today.

Two clauses to add to your SOW template, and one thing to say at kickoff

Start by adding the order of precedence clause to your standard statement of work template, with the master agreement named by date and any carve-outs named by section number. It takes ten minutes on a document you'll reuse for years, and it removes the single most common conflict between the two documents.

Then put a real change control clause into the same template, with a named approver and a stated threshold rather than a general statement that changes will be discussed. Decide the percentage now, while nothing is at stake, because deciding it in week seven with a frustrated client on the phone produces a worse number every time. If you'd rather start from a document that already has the commercial terms filled in, a complete statement of work with real figures in place saves you the blank page.

Last, tell the client about both clauses at kickoff instead of letting them discover the second one in week seven. Explaining that changes are welcome, priced within three days and approved by one named person is a reassuring thing to hear at the start and an unwelcome surprise later, which is why explaining the change rule at kickoff does more for your margin than any clause you can draft.

Frequently asked questions