How consulting firms review SOWs against a signed MSA

Your MSA got a real review. Two rounds of redlines, a call with their counsel, sign-off from someone senior. Then it goes in a folder, and the paper that actually governs the work starts showing up: SOW after SOW, drafted by delivery leads, signed by a partner who wants the team on site Monday. That is where your negotiated terms get moved, and on a lot of teams nobody is checking.

Why SOWs skip the review the MSA got

The reason a client wants an MSA in the first place is so the next document moves fast. UMass says this to suppliers directly: sign the master agreement once, and after that every campus can attach its own statement of work without renegotiating terms. One contract, multiple projects. Your clients are right to want that, and it saves everybody weeks.

The catch is that the fast lane was built on the idea that a SOW only describes work. It doesn't. A SOW describes work in sentences that are also commitments, and it gets written by the people closest to the delivery promise and furthest from the master agreement.

Scope does not sit still either. PMI's 2023 survey found that even at the organizations it identified as performing better on project success, 28 percent of projects still had scope creep. Scope that moves usually turns into a change order or a fresh SOW, and each of those is another document that can move a term.

The terms a SOW can move without looking like it

You will not find a SOW section called Changes To The MSA. The movement hides in ordinary project language.

The assumptions section is the one worth reading twice. It looks like background and it usually carries conditions: the client will provide test data by a date, a named person stays on the project, the environment will be available in week two. Those become dependencies your MSA never mentioned.

Acceptance is another. A SOW that gives the client thirty days to sign off on a deliverable, with no standard for what sign-off means, has put a gate on your invoice that the MSA payment section says nothing about. Which document controls is a question for a lawyer. Whether anybody noticed before signature is a question about your process, and that is the one you can fix.

Then there is the responsibilities table, where "Provider will maintain" lines get written by somebody describing normal practice rather than making a commitment. Same with personnel language naming individuals, and with fee schedules that quietly introduce a rate card or a travel policy the master agreement doesn't have.

Build the check when you sign the MSA

Decide what you are looking for before the SOWs start arriving, not while one is sitting in a partner's inbox.

When an MSA gets signed, write a delta sheet for that client: the handful of MSA terms a SOW is capable of moving. Six to ten lines is usually plenty. Each line says where the term sits in the MSA, what it currently says, and what a SOW would have to say to change it. Liability cap, acceptance, payment timing, data handling, key personnel, ownership of deliverables. You are not summarizing the agreement, just the parts a SOW can reach.

Every SOW under that MSA gets run against the sheet instead of read cold. A reviewer looking for six specific things can usually do that in ten minutes. A reviewer told to check a SOW "against the MSA" is being asked to reread forty pages, so they skim, and skimming is how this whole problem started.

Running it at volume

In practice, a partner will not hold a signature while somebody reads a twelve-page SOW against a forty-page master agreement. That is the actual bottleneck: at forty SOWs a quarter, the careful version of the check costs more time than the work can absorb.

That narrow job is what AI contract review software is decent at: hold the MSA and the delta sheet, and flag which SOW sections touch a listed term. It will not tell you whether the change is acceptable, and plenty of the time it will be, because a delivery lead traded it on purpose. It just puts the change in front of a person before the signature instead of after. This is the same habit as checking an amendment against the contract's current state rather than the original signed file: review against what you actually agreed to, not against the document you happen to have open.

The number worth counting

Each quarter, count the SOWs you signed that contained language touching a term on the delta sheet. Signed, not caught and sent back.

If that number is zero, the check is not running. If it is half your SOWs, your MSA position and what your delivery teams actually promise have drifted apart, and that is a template problem. More review will not close it.

Try goHeather free and run your next SOW against the master agreement it sits under.

This is legal information, not legal advice; consult a lawyer for legal advice.