How to Scope a Service Agreement: MSA-and-SOW in Six Steps

A service relationship that runs longer than a single project should not be governed by a single overstuffed contract. The cleaner architecture is a Master Service Agreement plus per-project Statements of Work. This guide walks through how to scope the split before drafting begins.

This is the operational version of the legal logic. If you want the legal background, see the companion article on MSA vs. SOW structure.

Step 1: Separate the legal frame from the project

The MSA carries standing legal terms: confidentiality, IP, indemnification, liability cap, insurance, payment, termination, governing law, and order of precedence. The SOW carries scope, deliverables, milestones, price, and project assumptions. If a clause does not move project-to-project, it belongs in the MSA.

Step 2: Draft the order-of-precedence clause first

A one-paragraph order-of-precedence clause inside the MSA stops most downstream problems. It says, in substance, that the MSA controls unless the SOW expressly identifies a project-specific item (typically scope, schedule, price, and enumerated assumptions). Anything else in a SOW that conflicts with the MSA does not apply.

Step 3: Calibrate the liability cap to the real risk

Default to a cap tied to total fees paid under the SOW in question. Then add carve-outs for the exposures that should not be capped: confidentiality breaches, IP indemnification, and gross negligence or willful misconduct. A cap with no carve-outs is rarely right; a cap with carve-outs for every category is just an uncapped agreement.

Step 4: Settle IP at the framework level

For most service relationships, the cleanest rule is: the client owns the deliverables; the vendor retains its pre-existing materials and grants a license to use them inside the deliverables. State that once in the MSA and stop renegotiating it on every project.

Step 5: Build a change-order process before you need one

Define the form (short written amendment, signed by an authorized person), the price impact, and the schedule impact. Verbal change requests are the leading cause of fee disputes in service work; a documented change-order template is a one-page fix.

Step 6: Make the SOW boring

A clean SOW is short. It answers four questions: what is being delivered, by when, for how much, and under what assumptions. If the SOW starts negotiating legal terms, it is doing the MSA's job and producing inconsistent legal posture across projects.

When attorney drafting is worth it

DIY service agreements work for single, low-risk engagements. The MSA-and-SOW structure starts paying off when the same parties expect multiple projects, when regulated data is in scope, or when the client's default contract template would quietly transfer IP or remove liability protection.

The firm's flat-fee Service Agreement is $279. For a pure review of a draft the other side has sent, Contract Review is $179 for contracts up to 30 pages.