Document structure
MSA vs SOW
A master services agreement, usually shortened to MSA, sets the legal terms that govern a relationship: liability, confidentiality, payment terms, termination. It does not normally commit you to buy anything. A statement of work, or SOW, sits under it and carries the actual scope, price, and dates. Summing both as spend counts the same money twice.
The Vendor Squeezer team. Last reviewed 2026-08-08. General guidance on contract structures, not legal advice, and not a statement about any particular vendor's terms.
What each document does
The split exists so the terms can be negotiated once and reused. Agreeing liability caps and confidentiality obligations is slow; agreeing the scope of the next project should not be. So the MSA is signed once and each engagement adds a short document beneath it.
The consequence for a vendor register is that the MSA is context and the SOWs are commitments. An MSA on its own tells you a relationship exists and on what terms. It does not tell you that any money is committed, and it may sit dormant for years.
| Item | Usually in the MSA | Usually in the SOW |
|---|---|---|
| Liability, confidentiality, IP | Yes | No |
| Payment terms and invoicing rules | Yes | Rarely |
| Scope of work | No | Yes |
| Price and rates | Sometimes a rate card | Yes, the committed amount |
| Dates and duration | A relationship term, if any | The engagement dates |
| Termination rights | Yes | Sometimes additional ones |
Two gaps worth noticing
An MSA with nothing beneath it means one of two things, and both are useful to know. Either the relationship is dormant, which makes it a candidate for review, or there is spend happening that has not been recorded, which is a records gap.
The reverse gap is more serious. A SOW whose MSA you do not hold means the governing terms are unknown: you have the price and the dates, but not the liability position, the termination rights, or the payment terms. That is a commitment whose conditions nobody in the building can state.
Which one carries the renewal clock
Both can have a term, and which one binds is a real question rather than a formality. A common pattern is that the MSA runs for a relationship period while each SOW ends on delivery, so nothing renews and the engagement simply finishes. Another pattern gives the MSA a term that, if it lapses, leaves live SOWs without governing terms.
Read both terms and record which one you are tracking. Guessing produces a wrong date, and a renewal calendar exists precisely so nobody has to guess.
Questions to ask about your own agreement
- 1.Do we hold both the MSA and every SOW under it?
- 2.Which document carries the committed amount, and is it the one being summed?
- 3.Does the MSA itself have a term, and what happens to live SOWs if it lapses?
- 4.Are there MSAs with no SOW beneath them, and is the relationship dormant or unrecorded?
- 5.Does the SOW add termination rights beyond the ones in the MSA?
Common questions
Does signing an MSA commit us to spend?
Usually not. Most master agreements set terms without obliging either side to transact. Some include a minimum commitment, so it is worth checking rather than assuming, but the default structure commits nothing until a SOW is signed.
Should the MSA appear in a spend total?
No, unless it carries a commitment of its own. Include the commitment documents beneath it and keep the MSA linked as context, otherwise the same money appears twice.
Put this against your own vendors
Record the term, the notice deadline, and the exit cost against the vendor once, and the next renewal review starts from an answer instead of a search. Free while in early access.