An MSA (Master Service Agreement) sets the legal ground rules for an ongoing business relationship, and a SOW (Statement of Work) defines the specifics of each individual project done under that relationship. Compared side by side, the MSA handles the heavy legal provisions once — liability, indemnification, intellectual property, confidentiality — so you don’t renegotiate them every time a new project starts. The SOW then describes what’s actually being built or delivered, on what timeline, and for how much money. Think of the MSA as the constitution and each SOW as a specific law passed under it.
You use both when you expect multiple projects with the same vendor or client. You use a single standalone contract only when the engagement is a one-off with no realistic chance of follow-on work.
The Core Distinction
An MSA is designed to stay in force for the entire relationship, often years. Its provisions are evergreen: they don’t change based on whether the next project is a website redesign or a six-month consulting engagement. Once it’s signed, subsequent projects can move from handshake to signed SOW in days instead of weeks, because the heavyweight legal terms are already settled.
A SOW is the opposite. It’s self-contained, project-specific, and short-lived. It inherits every protection in the MSA and adds the operational detail that makes the project executable. When the project ends or a new one begins, a new SOW gets drafted and signed without touching the MSA. Your legal team negotiates the MSA. Your project managers run the SOWs.
What the MSA Locks In
The MSA is where you settle the terms that would be painful to renegotiate repeatedly. The provisions below are the ones that carry the most weight in a typical professional services relationship.
Indemnification
Indemnification determines who pays when something goes wrong and a third party comes after one of you. A provider typically agrees to cover losses if the work product infringes someone else’s intellectual property, or if a provider’s employee causes injury on the client’s premises. Clauses can be one-sided or mutual; mutual is more common when both sides contribute work that could create third-party liability. Most clauses carve out an exception: no indemnification is owed when the loss resulted from the other party’s own negligence or willful misconduct. This is one of the most negotiated provisions in any MSA, because a single lawsuit from an outside party can otherwise swallow the economics of the whole engagement.
Intellectual Property Ownership
Who owns the work product? If the MSA doesn’t answer this clearly, you’ll fight about it later. Many agreements designate deliverables as “work made for hire,” which under federal copyright law treats the hiring party as the author and copyright owner from the start.
There’s a trap here. The work-for-hire doctrine has real limits when the provider is an independent contractor rather than an employee. For contractors, a work qualifies as work-for-hire only if it falls into one of a specific set of categories and both parties sign a written agreement saying so.1Office of the Law Revision Counsel. 17 USC 101 Definitions Custom software and marketing strategy don’t fit neatly into those categories. When the work doesn’t qualify, the MSA needs a separate IP assignment clause transferring copyright ownership to the client. Without that assignment, the provider keeps ownership of what they created, even if the client paid for it.2Office of the Law Revision Counsel. 17 US Code 201 – Ownership of Copyright
Confidentiality
Confidentiality provisions function as a built-in NDA covering the whole relationship. The MSA defines what counts as confidential information, who can access it, and how long the obligation lasts after the relationship ends. Standard carve-outs apply to information that was already public, was independently developed, came from a third party without restriction, or was ordered disclosed by a court. If the parties signed a standalone NDA earlier, the MSA’s confidentiality section usually supersedes it, so the MSA’s protections should be at least as strong.
Limitation of Liability
Liability caps control the maximum financial exposure each party faces. In professional services, the common approach is capping total liability at the total fees paid under the contract, or at the fees paid during the preceding twelve months for ongoing engagements. Some agreements use a fixed dollar amount or a multiple of fees. Equally important is what types of damages are excluded. Most MSAs contain a mutual waiver of consequential damages — lost profits, lost business opportunities, reputational harm — because neither party wants exposure to speculative downstream losses. Courts don’t always draw the line between direct and consequential damages the same way, so listing specific categories being waived is safer than relying on the label alone.
Termination
MSAs address two flavors. Termination for convenience lets either party walk away for any reason, typically with 30 to 90 days’ written notice. Termination for cause applies when one party materially breaches and fails to cure the problem within a specified period, often 10 to 30 days after written notice. The MSA should also spell out what happens to pending work and unpaid invoices on termination, since those loose ends create most of the post-termination disputes.
Force majeure, dispute resolution procedures, and governing law also live at this layer. They’re handled once in the MSA and then stay settled for every project that follows.
What the SOW Nails Down
The SOW is where the project becomes real. Four elements do most of the work.
Deliverables and Specifications
The SOW describes exactly what the provider will produce, with the technical specifications and performance standards the deliverables must meet. Vague descriptions are the single biggest source of scope disputes. “Build a website” is not a deliverable. “Deliver a responsive website with 15 pages, CMS integration, and WCAG 2.1 AA accessibility compliance” is a deliverable.
Timeline and Milestones
Milestones break the work into phases with specific due dates: an initial design mockup by one date, a working prototype four weeks later, a final deliverable two weeks after that. These dates matter because payment is often tied to them, which creates natural accountability on both sides.
Pricing and Payment Terms
The SOW locks in compensation. Fixed-fee works best when the scope is well defined and unlikely to change; the client pays an agreed total regardless of hours. Time-and-materials works better when requirements are uncertain or expected to evolve, often with a not-to-exceed cap to protect the budget. Milestone-based payments split the difference: the client releases a percentage of the fee as each milestone is completed, keeping cash flowing to the provider while giving the client checkpoints to confirm the work is on track.
Acceptance Criteria
Acceptance criteria define how the client determines whether a deliverable meets specifications: what testing will occur, when, and how long the client has to review before the work is deemed accepted. If a deliverable fails testing, the SOW should describe a revision process with a defined cure period. Without acceptance criteria, you end up in a gray zone where neither party can say with confidence whether the project is done.
How the Two Documents Interact
The MSA and SOW operate as a single contractual framework, but they need a rule for what happens when their terms collide. That rule is called an order-of-precedence clause. Standard practice gives the MSA priority on legal matters (liability, indemnification, IP ownership) and the SOW priority on project-specific details (deliverables, timelines, pricing).
Example: if the MSA sets a 30-day payment window but a particular SOW says payment is due within 15 days of milestone completion, the MSA’s term controls unless the SOW explicitly states it is overriding that provision. The parties can deviate from the MSA on a project-by-project basis, but only when they do so deliberately and in writing. Accidental conflicts default to the MSA. Contracts without a clear precedence clause invite litigation, because a court has to guess which document the parties meant to follow.
When to Use Both vs. a Single Contract
Use an MSA plus SOWs when you expect an ongoing relationship involving multiple projects. Once the MSA is negotiated, spinning up a new project is fast because you’re only drafting a SOW. For companies that regularly engage the same vendors or consultants, the efficiency savings compound over time.
A standalone contract combining legal terms and project details in one document can work for a single, small engagement with no expectation of future work. The risk is that the relationship continues anyway, and you end up renegotiating the legal terms every time, or worse, operating under terms that were tailored to a different project entirely. If there’s any realistic chance of repeat work, the MSA/SOW structure pays for itself.
Managing Scope Changes
No project survives first contact with reality exactly as planned. Requirements shift, clients discover new needs mid-project, and technical obstacles force workarounds. The question isn’t whether scope will change; it’s whether the change gets documented before work starts or argued about after it’s done.
The mechanism is a written change order, sometimes called a SOW amendment. It describes the new or modified work, adjusts the timeline if needed, states the cost impact, and requires both parties’ signatures before anyone lifts a finger. This can feel bureaucratic until you’ve been on the wrong end of a provider who performed $40,000 in extra work “because the client asked for it” with no documentation.
Scope creep — the gradual expansion of project requirements without formal approval — is the silent budget killer in service engagements. Poor requirements gathering at the outset is usually the root cause. When the original SOW is vague, every clarification risks becoming a scope expansion. A tightly written SOW combined with a clear change-order process is the best defense: specify who can request changes, how cost impacts are evaluated, and that no out-of-scope work begins without written authorization.
One Boundary: When Goods Are Part of the Deal
Most MSA/SOW arrangements govern professional services, but some engagements involve delivering physical goods alongside services, such as a technology integration that includes hardware. When goods are involved, the Uniform Commercial Code’s implied warranties come into play. The implied warranty of merchantability requires that goods meet baseline quality standards for their ordinary use.3Cornell Law Institute. Uniform Commercial Code 2-314 – Implied Warranty Merchantability Usage of Trade The implied warranty of fitness for a particular purpose applies when the seller knows the buyer is relying on their expertise to select suitable goods.4Cornell Law Institute. Uniform Commercial Code 2-315 – Implied Warranty Fitness for Particular Purpose These warranties exist by default unless the contract explicitly disclaims them, so an MSA covering mixed goods-and-services work should address whether UCC warranties apply or are waived.