Master Services Agreement vs Statement of Work

A Master Services Agreement and a Statement of Work are two halves of one commercial relationship, and they are deliberately not the same document. The MSA is the framework: negotiated once and then reused, holding the clauses that allocate risk between the two entities. The SOW is the instance: one per engagement, sealed as often as work is bought, and holding the variables — what is being built, by when, for how much.

The division is structural rather than stylistic, and published frameworks show the same shape. The Standard Terms of Common Paper's Professional Services Agreement run Services, Intellectual Property, Privacy & Security, Payment & Taxes, Term & Termination, Representations & Warranties, Disclaimer of Warranties, Limitation of Liability, Indemnification, Insurance, Confidentiality, General Terms and Definitions. Thirteen sections, and not one of them names a deliverable, a date or a price. The work sits outside them, in a separate instrument: "Each SOW together with the Key Terms and Standard Terms will constitute a separate agreement." The same standard describes the instance loosely enough to carry anything commercial: "A SOW may include details about the Deliverables, Fees, or other details about the Services."

The drafting reason for the split is negotiating cost. The framework is reviewed by counsel once and then reused; the instance is issued by delivery staff many times. A liability cap written into a SOW re-opens the negotiation the framework was written to close, and it re-opens it with people on both sides who were not in the original one.

Sequencing is not fixed, and the published guidance is explicit about the common case. Common Paper's Statement of Work page states: "In most cases, people will create a Professional Services Agreement and the first SOW at the same time." The one-to-many shape asserts itself after that first pair: "Once you agree to the Key Terms (i.e., the legal details in the Cover Page), you can issue additional SOWs that leverage the already agreed terms." The instrument Common Paper publishes assumes the framework exists by the time it is used: "This particular SOW is designed to work with an existing Common Paper PSA."

There is no ceiling on the instances: "There is no limit to the number of SOWs that can exist under a single PSA." So the practical pattern is one framework sealed at or before the first engagement, and every engagement after that drafted against a framework already sealed, referenced by name and effective date.

A SOW sealed while the MSA is still in redline is an engagement whose commercial variables are settled and whose framework clauses are not. The scope, the fee and the start date are fixed. The liability cap, the intellectual-property terms and the confidentiality terms are still moving.

A framework that expects instances hanging off it carries a conflict rule, because two documents that both speak to the same subject will eventually disagree. The rule names which one governs.

Common Paper's Professional Services Agreement puts that rule on the instance: "If there is any inconsistency between this SOW and the Agreement, this SOW will control." A second rule handles the framework's own internal parts: "If there is any inconsistency between the parts of the Agreement, the Cover Page will control over the Standard Terms."

Both are drafting choices, made in that form in favour of the later and more specific document. Read on the form's own words, a payment line pasted into a SOW that differs from the framework is the version the form nominates to control. A form ordered the other way would nominate the framework instead, and the same paste would sit subordinate until the framework itself is changed. Which order applies is a question about the text of the particular framework in front of the drafter, not something that can be assumed from the document names.

The concrete failure has two shapes, and small agencies hit both.

The first is a SOW that carries operative commercial terms. A delivery lead copies the last engagement's SOW, edits the scope, and leaves in a payment-terms line, a warranty sentence or a cap on rework that the framework already addresses differently. Nobody notices, because the SOW is reviewed for scope and price and the framework is not reopened. The contradiction surfaces months later, during a dispute about a deliverable, when both sides read both documents for the first time in the same week.

The second is sequencing. A SOW goes out and is sealed while the MSA is still in redline, usually because the client wants a start date and the framework negotiation has stalled on liability. The engagement then runs on a document that incorporates a framework by reference to a file with no effective date, and every clause the SOW leaves out — indemnification, intellectual property, confidentiality, insurance, governing law — is left out while the instrument that would supply it is still unsealed.

Both shapes share one property: they are visible in the file at the moment of sending, and much harder to see afterwards. A SOW that references a framework with a blank effective date is detectable before anyone signs. So is a second copy of a term that already lives upstream.

Clause names and quoted sentences above are taken from the Common Paper Professional Services Agreement standard and its Statement of Work page. Common Paper states: "Common Paper agreements are free to use and modify under CC BY 4.0."

This page describes how these two classes of instrument are structured in one published framework and what OctoDoc's software does with them. It states no rule of law and gives no advice on any particular agreement.

Nobody wants to read the contract. OctoDoc is being built so you do not have to: write a document from a prompt, ask plain-language questions about the one you were sent, and keep every one of them in a single place instead of four accounts and an inbox.

Anyone can check a sealed file with no account.

Unlimited human sends on the paid tier.