MSA vs SOW

A master service agreement (MSA) sets general terms; a statement of work (SOW) describes the specific work. Errors in the hierarchy between them are the most common source of scope disputes.

What is the difference?

A Master Service Agreement (MSA) is the "parent document": liability, IP, payment terms, confidentiality — the generic rules that apply to all future engagements. A Statement of Work (SOW) is per project: scope, deliverables, rates, timeline.

Example

MSA between consultancy X and client Y: 60-day payment terms, liability capped at 12 months of fees, IP assigned to client, confidentiality 5 years.
SOW 1 under this MSA: "AI strategy assessment, 8 weeks, €65,000, deliverables 1-3, two consultants."
SOW 2 under the same MSA: "Implementation, 6 months, time-and-materials, cap €180,000."

When it matters

Any vendor with whom you do multiple projects. Without an MSA you renegotiate liability with every SOW. Without a clear hierarchy, every dispute becomes a debate about which document controls.

Common pitfalls

No "order of precedence" clause — when MSA and SOW conflict, which wins?
SOW modifies MSA terms — legally often invalid without a formal amendment.
SOW without MSA reference — legally standalone, missing all the safety nets.
Expired MSA — SOWs under a lapsed MSA run on unprotected ground.

How GuardPilot flags this

The Contract Management agents map every SOW to its parent MSA, flag SOWs arriving without MSA reference, and warn when an MSA expires while active SOWs still run under it.