A well-drafted commercial engagement separates the Master Services Agreement from the Statement of Work on purpose. The separation is not administrative convenience. It is a risk-allocation device: the parties agree the ground rules once, in a document they will negotiate hard for four to six weeks, and then attach individual deals to those ground rules in documents they will negotiate in hours.
When the separation is done well, the firm signs one MSA with a supplier and runs twenty SOWs under it over four years. When the separation is done badly, every SOW is a partial re-negotiation of the MSA — the worst of both worlds, and commercially the clearest sign that the drafter did not know which clauses belonged where.
The rule of thumb
Risk lives in the MSA. Deal mechanics live in the SOW. The harder test is where an individual clause sits on that spectrum, because the interesting clauses — IP ownership, warranties, acceptance, termination — live on both sides at once.
| Clause category | Belongs in MSA | Belongs in SOW |
|---|---|---|
| Governing law, jurisdiction, dispute resolution | Always. | Never, unless one SOW requires a different forum for regulatory reasons. |
| Confidentiality, data protection, security | Framework (duration, standards, DPA reference). | Scope-specific overlays only (e.g., PHI handling for a healthcare SOW). |
| Limitation of liability & indemnities | Caps, carve-outs, mutual or one-way — all in the MSA. | Never introduce new liability structures in an SOW. |
| IP ownership | Framework (pre-existing IP, foreground IP default, licence-back). | Category assignment for the deliverables of that SOW — but inside the MSA framework. |
| Warranties | General performance warranties, no-infringement, compliance with law. | Deliverable-specific warranties (acceptance criteria, performance KPIs, uptime SLAs). |
| Acceptance | Default acceptance mechanism (who signs, within how many days, consequences of silence). | The acceptance criteria specific to that SOW’s deliverables. |
| Termination | Termination for convenience, termination for cause, termination for insolvency, transition assistance. | Termination of that SOW only — which may survive MSA termination or expire with it, depending on drafting. |
| Fees, invoicing, tax | Billing mechanics, currency, late-payment interest, withholding. | The fee for that SOW — fixed-fee, T&M, milestones, expenses. |
| Deliverables & timelines | Never. | Always. |
The five clauses commercial lawyers keep putting in the wrong document
1. Intellectual property
The MSA should resolve the ownership default — foreground IP to customer, pre-existing IP retained by supplier, a non-exclusive licence-back to the supplier for residual use. The SOW should do only one thing: assign each specific deliverable to a category from the MSA framework. What SOWs should never do is re-open the ownership question. When they do — “notwithstanding clause 12 of the MSA, the supplier retains ownership of X” — the drafter has re-negotiated the MSA through the side door, usually without the customer’s legal team realising until the next SOW.
2. Acceptance
The MSA should say how acceptance works: the customer has 10 business days to review, silence is deemed acceptance, acceptance can be withheld only for material non-conformity, rejection must cite the failing criterion. The SOW should say what is being accepted: these five deliverables, against these acceptance criteria, at these milestones. Confusing the two leaves the supplier vulnerable to indefinite rejection on one side and the customer bound to accept non-conforming deliverables on the other.
3. Liability caps
Liability caps must sit in the MSA. Every SOW under an MSA should either share a single cap (“the MSA cap is an aggregate cap across all SOWs”) or carry a per-SOW cap that is clearly a sub-cap of the MSA cap. Drafting a fresh liability cap into each SOW without tying it back to the MSA is how a supplier ends up with three SOWs worth US$500,000 each and an MSA that is silent on aggregate exposure.
If a clause will apply identically across every SOW the parties will ever sign, it belongs in the MSA. If it needs to change for each project, it belongs in the SOW. Anything else is a drafting convenience with a hidden cost.
4. Warranties
General warranties — “the supplier warrants that the services will be performed with the due skill and care reasonably expected of a competent professional in the relevant industry” — sit in the MSA. SOW-level warranties are the deliverable-specific overlays: uptime SLAs, performance KPIs, accuracy rates, integration warranties. A well-drafted MSA explicitly permits SOW warranties to supplement, but not contradict, the MSA warranty floor.
5. Termination
Three termination rights sit in the MSA: for convenience, for material breach, and for insolvency. Each must carry its transition obligations — handover of deliverables, return of confidential information, exit assistance periods. SOWs can carry their own termination for convenience if the parties want finer control per project, but material-breach termination should always default to the MSA mechanism. Parallel, inconsistent termination schemes in the MSA and an SOW are one of the most expensive drafting errors in commercial contracting — they produce three-way disputes about which mechanism applies when either could.
The order-of-precedence clause is doing more work than lawyers realise
Every MSA should contain an order-of-precedence clause that tells the reader what happens when the MSA and an SOW conflict. The standard formulation is: “In the event of any conflict between this MSA and a Statement of Work, the terms of the MSA shall prevail, except to the extent that the Statement of Work expressly references the specific clause of the MSA being modified and states that it is intended to modify that clause.”
That qualification — “expressly references the specific clause” — is what protects the MSA from silent erosion through the SOW. Without it, any SOW that mentions a topic covered by the MSA becomes a candidate to override the MSA. With it, an SOW override has to be deliberate, visible, and signed off by the customer’s legal team.
A practical workflow
Firms that negotiate the MSA once and then run many SOWs well have a common workflow:
- The MSA is reviewed by legal. Every SOW is reviewed by commercial, with legal sign-off only on specified triggers (new IP category, new jurisdiction, liability cap change, data category change).
- SOW templates inherit MSA boilerplate. Each SOW begins with a reference clause: “This SOW is entered into under the Master Services Agreement dated [date] between the parties. All terms of the MSA apply except as expressly modified in this SOW.”
- SOW variations are logged centrally. A running list of clauses that have been modified in SOWs — which SOW, which clause, what change — is the single artefact that prevents the MSA from silently eroding.
Closing note
The MSA-SOW architecture only works if the lawyers drafting the SOWs understand that the MSA is the load-bearing document. An SOW that behaves itself leaves the MSA untouched; an SOW that misbehaves rewrites the risk allocation the firm spent weeks negotiating. The test is simple: read the SOW alone, then read the MSA alone. If you can negotiate new SOWs by reading only the MSA, the separation is working. If you cannot, you are signing a series of re-negotiations disguised as Statements of Work.