Owner's Contracts The clauses that decide what happens when it goes wrong.

Owner's Contracts

CONTRACT STRUCTURE

Master Service Agreement vs. Statement of Work: Which Document Governs

By Baruch Mackliff · · 6 min read

An MSA carries the legal terms and an SOW carries the work, but when the two documents disagree it is the order of precedence clause that decides.

Somebody sent you two documents and asked you to sign both. One is a master service agreement. The other is a statement of work, and in a couple of places it says something different from the first one. So which document wins?

The master service agreement sets the legal relationship. The statement of work sets the job. Where the two disagree, an order of precedence clause decides, and that clause is usually a short paragraph near the back of the MSA that nobody reads because it looks like housekeeping. If there isn't one, you are left arguing about how two documents read together, and that argument is expensive to have.

Read the precedence clause first. Before the scope, before the price, before anything else in either file. It is four lines long and it is the most consequential text in the stack.

What each document is carrying

The MSA is built to outlive the work. You sign it once and it sits there for years while projects come and go. It holds the terms that do not change from job to job: who owns what gets made, what stays confidential, how you invoice and when you get paid, who defends whom if a third party sues, the ceiling on what either side can owe, which state's law applies, and what notice ends the relationship.

The SOW is built to be thrown away. It describes one piece of work and then it is finished. Scope. Deliverables. Dates. Price and how the price is calculated. Who supplies the materials, the site access, the approvals. What "accepted" means, and how many rounds of review are included before extra work starts getting billed as extra work.

Written well, the two barely touch.

Written the way most of them actually arrive on a Tuesday afternoon, they overlap in four or five places, and every overlap is somewhere the documents can contradict each other. The overlaps are predictable. Payment timing shows up in both because the person writing the scope document was trying to be helpful. Ownership of the work shows up in both because the client's template assigns everything to the client and your scope document carves out the tools you already owned. Change control shows up in both because the MSA describes one process for approving extra work and the SOW describes a different one.

The precedence clause and its four shapes

The MSA controls. Anything in a statement of work that conflicts with the master agreement is void to the extent of the conflict. This is the most common shape, and it is the one that quietly kills the terms you thought you had won. You negotiated net thirty into the SOW. The MSA says net forty-five. The MSA wins, and you do not have net thirty.

Take a shop invoicing 24,000 dollars a month under that agreement. Fifteen extra days of float against a monthly run rate of 24,000 dollars leaves roughly 12,000 dollars of your money parked in somebody else's account at any given moment, permanently, for as long as the relationship runs. You are financing your customer for free, and you started doing it by skipping a paragraph about paragraph order.

The SOW controls. The specific document beats the general one. That sounds fair and it is dangerous in the opposite direction, because now every scope document anyone signs can rewrite the master terms. A project manager who accepts an uncapped indemnity inside a scope document has amended your MSA, and nobody escalated it because nobody believed a scope document could do that.

Split by subject. The better drafting. The MSA controls on legal terms, the SOW controls on scope and money, and the clause names which subjects sit where. If you are the one writing the agreement, write it this way.

Silence. No precedence clause at all. Now the answer depends on which document was signed later, on whether the SOW says it is subject to the MSA, on whether a court treats the specific term as what the parties really meant, and on the governing law. Courts do not all resolve this the same way. Treat silence as a defect to fix rather than a question to answer.

The statement of work that amends the master agreement

Search every SOW you are handed for one word: notwithstanding.

"Notwithstanding anything to the contrary in the Agreement" is a precedence override hiding inside a scope document. It flips whatever the MSA says, for that one sentence, and it usually sits under a heading like Assumptions or General, three pages past the part anyone read out loud.

The other hiding place is the assumptions block itself. Assumptions look like project notes. They are doing contract work. An assumption that the client will deliver final content within five business days is load bearing, because the schedule and your exposure for late delivery both hang off it. When the content arrives three weeks late and the deadline slips, that line decides whether the failure is yours or theirs.

And watch for a SOW that attaches terms of its own. A vendor order form with fine print on the reverse is a third document in the stack, and it has opinions about which document wins.

What terminating one of them actually does

Most master agreements let either side end a single SOW without ending the MSA, and end the MSA without automatically ending the statements of work already running under it. Find out which way yours goes, because the two failure modes are opposites.

If the MSA survives the end of every SOW, you have a dormant agreement with live obligations inside it. Confidentiality keeps running. The restriction on hiring their people keeps running, where that is enforceable at all. Eighteen months later somebody issues a fresh SOW under the old MSA, and you are bound by terms you last looked at in a different market.

If terminating the MSA kills every open SOW with it, then a routine cleanup of a stale vendor file can stop work in progress on a project you still need finished. That happens more often than it should.

The clause that settles most of this is the survival clause. It lists the sections that keep operating after the paper is dead. Confidentiality belongs there. So does ownership of delivered work, payment for work already performed, and indemnity for harm that already happened. So does the limitation of liability. If the liability cap is not listed as surviving, you have an uncapped tail on claims that show up after termination, which is exactly when most claims show up.

One more clause earns its space here: the one saying each SOW is a separate and independent contract. That is not decoration. It decides whether a fight on one project lets the client stop paying on the other four, and whether your stumble on a single job counts as a breach of the entire relationship. Independent statements of work contain the damage. Linked ones spread it.

Reading the pair in the right order

Precedence clause. Survival clause. Termination. Then the liability and indemnity sections of the MSA. Only after that, the SOW, and read the SOW with the MSA open beside it, hunting for every place the scope document speaks about something the master agreement already settled.

Anywhere both documents speak, decide which one you want to win and then make the precedence clause say so in plain words. "The payment terms stated in each Statement of Work control over Section 4 of this Agreement" is one sentence, and it is worth more than most of the negotiating that happens over scope language.

A precedence clause you wrote yourself is the cheapest insurance in the file.

And if precedence runs to the statement of work, then every scope document your team signs from now on is a chance to rewrite your own liability cap by accident. That is the one to put a process around.

Common questions

Which one do I sign first, the MSA or the SOW?

Sign the master service agreement first, because the statement of work is meant to hang off it. A scope document signed before any master agreement exists is a standalone contract with almost no legal terms in it, so the default rules of the governing state fill every gap. If a client hands you both at once, read them as a single document and make sure the SOW names the MSA by date.

Can a statement of work override the master service agreement?

Only if the order of precedence clause allows it, or if the SOW carries override language of the kind that begins with the word notwithstanding. Absent one of those two, the master agreement usually controls and the conflicting term in the scope document is void to the extent of the conflict. Check precedence before you rely on anything you negotiated into a SOW.

Do I need a new MSA for every project?

No. A master agreement is designed to stay in place while statements of work come and go underneath it. Redo the MSA when the commercial relationship changes in a way the old terms never contemplated, such as work in a new state or a job carrying far more exposure than anything you had signed before.

More on this