MSA vs Statement of Work: How the Two Documents Fit

A master service agreement and a statement of work are two halves of one contract. The MSA is negotiated once and holds the legal terms that do not change from project to project: payment mechanics, intellectual property, confidentiality, warranties, indemnity, liability limits, and termination. Each statement of work is signed per project and holds what changes every time: scope, deliverables, schedule, and price. It fails when the two documents disagree and nobody decided in advance which one wins. This post covers what belongs in each, and how to handle the conflict.

What belongs in the master service agreement

The MSA is the legal framework, and it should be complete enough that a statement of work can be two pages. In our contract drafting and negotiation practice, an MSA typically covers the following, each drafted to apply to every future SOW without modification:

• Definitions, including “Services,” “Deliverables,” and “Statement of Work,” so every SOW uses the same vocabulary
• Payment mechanics: invoicing cadence, due dates, late fees, expense reimbursement, disputed invoice procedure, and taxes
• Intellectual property: who owns deliverables, what is licensed, and how each party’s background IP is protected
• Confidentiality, data protection, and security obligations
• Warranties, indemnification, limitation of liability, and insurance requirements
• Term, termination rights, effect of termination, and survival
• Dispute resolution, governing law, assignment, notices, and the rest of the general terms

The MSA should not contain a price, a delivery date, or a description of a specific project. Those belong in the SOW, and putting them in the MSA means amending the MSA every time the work changes. The full list of clauses an MSA should cover tracks our post on which clauses every business contract needs.

What belongs in each statement of work

A SOW describes one engagement in enough detail that both sides know what done looks like. It should identify the MSA it falls under by date and title, then state the scope of services, the deliverables with acceptance criteria, the schedule with milestones, the fees and the pricing model (fixed, time and materials, or milestone-based), the personnel or roles assigned, and any assumptions and customer dependencies the price relies on.

The SOW is also the right place for project-specific terms that genuinely differ from the MSA default: a different payment schedule for a fixed-fee build, a specific service level for a managed service, or a named key person who cannot be replaced without consent. When a SOW needs to override an MSA term, it should say so expressly, naming the MSA section it modifies. A SOW that silently restates legal terms creates the conflicts described next.

Which document controls when they conflict

Every MSA should contain an order of precedence clause. The usual rule is that the MSA controls over any SOW, except where a SOW expressly states that it is overriding a specific MSA provision for that project only. That rule protects carefully negotiated legal terms from being undone by a hastily drafted SOW.

Some customers push for the opposite rule, that the SOW controls. Be careful with it. If the SOW controls generally, then any legal-sounding sentence that finds its way into a SOW, such as “vendor shall be liable for all damages arising from delay,” overrides the MSA’s limitation of liability for that project. If you must accept SOW precedence, limit it to commercial terms such as scope, schedule, and fees, and state that MSA provisions on liability, indemnity, IP, and confidentiality cannot be modified except by a signed amendment to the MSA.

Where no precedence clause exists, courts try to read the documents together, and where that fails they look to which was signed later and which is more specific. That analysis is unpredictable, and it is how a scope dispute becomes a lawsuit handled by our commercial litigation and dispute resolution team instead of a conversation.

Change orders and scope creep

Scope changes are inevitable, and the SOW should say how they happen. A change order procedure requires any change in scope, schedule, or price to be documented in writing, signed by authorized representatives of both parties, and attached to the SOW. Without it, the vendor performs extra work on verbal requests, the customer refuses to pay for work it never formally ordered, and both sides are partly right.

The procedure should also say who can sign. Naming the authorized signers in the SOW, and requiring that changes above a stated amount be signed by someone senior, keeps the paper trail aligned with the money.

Common MSA and SOW mistakes

The errors we see most often are structural. A SOW gets signed before the MSA is final, so the project runs under no legal terms at all. A SOW references an MSA by a title or date that does not match the executed version, which is a gift to the party that later wants to disclaim it. Work starts on an unsigned SOW, and the fee dispute that follows has no signed scope to anchor it. An MSA is terminated while SOWs are still running, and the MSA never said whether outstanding SOWs survive or end with it.

Sign the MSA first. Reference it precisely. Require a signed SOW before work starts, with a short-form SOW template for small projects so the requirement does not slow anyone down. State in the MSA that termination of the MSA does or does not terminate active SOWs, and what happens to work in progress either way. When reviewing a counterparty’s MSA before signing, the steps in how to review a contract before you sign it apply, and CLP’s contract review and executive counsel team handles that review for clients with high SOW volume.

When the MSA and SOW structure is worth it

Use the structure when you expect more than one project with the same counterparty, when projects vary in scope or price, or when you want sales and delivery teams to be able to launch work without a legal review every time. For a single, one-off engagement, a standalone services agreement that combines both documents is simpler. The negotiation approach is the same either way, and our post on how to negotiate a business contract covers the positions worth holding in the MSA itself.

If your company signs statements of work regularly and the master agreement behind them is outdated, missing, or silent on precedence, Capitol Law Partners can draft an MSA and SOW template that your team can run without friction. Schedule a consultation.

This article is for informational purposes only and does not constitute legal advice. No attorney-client relationship is formed by this communication.

Attorney Cagatay Ersoy. Practical strategy for founders, investors, and growing companies.

Need help with this topic? See our MSA and statement of work drafting page or schedule a consultation.