A master services agreement is an umbrella contract that sets the legal terms of an ongoing relationship once, so that each individual project only needs a short statement of work describing the actual job. You need one when you expect to work with the same party repeatedly — otherwise you renegotiate liability, payment, and ownership from scratch every time. This guide covers what belongs in a master services agreement, what belongs in the statement of work, and the clauses worth reading closely before you sign either.
A master services agreement (MSA) is a contract that establishes the general legal terms governing all future work between two parties, with the specifics of each engagement set out in separate statements of work.
The structure exists to solve a practical problem. Negotiating liability caps and payment terms afresh for every small project is slow and expensive. An MSA front-loads that negotiation once, then makes each subsequent engagement a one-page document.
You will see the same document called an MSA contract, an MSA agreement, or a master service agreement in the singular. These all name the same instrument. The plural is the more common drafting convention and nothing turns on the difference — what matters is the two-document structure underneath: one master agreement, plus a statement of work for each piece of work done under it.
What a Master Services Agreement Actually Does
The MSA holds everything that stays constant across engagements:
- Liability and indemnification — caps, carve-outs, and who covers whose losses under the indemnity
- Intellectual property ownership — who owns deliverables, and when ownership transfers
- Confidentiality — often removing the need for a separate agreement
- Payment mechanics — invoicing cadence, payment terms, late fees, and dispute process
- Termination rights — how either side ends the relationship, and what happens to work in progress
- Insurance requirements — what cover each party must carry
- Governing law and dispute resolution — which state’s law applies, and whether disputes go to arbitration
None of these change from project to project, which is exactly why they are worth negotiating carefully once. Whatever you agree here governs every engagement that follows, sometimes for years.
MSA vs Statement of Work: What Goes Where
A statement of work (SOW) covers only what is specific to one engagement: deliverables, timeline, acceptance criteria, and price. If a term would be identical on your next project together, it belongs in the MSA. If it describes this particular job, it belongs in the SOW.
The relationship between the two documents is worth understanding precisely. The MSA almost always states that its terms control if an SOW conflicts with it. That single sentence has a significant practical consequence: a favourable term negotiated into an SOW may be unenforceable if it contradicts the MSA. If you need something genuinely different for one project, the MSA usually has to be amended, or the SOW must explicitly state that it overrides the MSA on that specific point.
When You Need a Master Services Agreement
- Repeat engagements. You expect more than two or three projects with the same party.
- Multiple concurrent projects. Several workstreams running at once, each needing its own scope but the same legal terms.
- Ongoing service relationships. Retainers, managed services, or continuous support work.
- Agency or consultancy relationships. Where scope shifts frequently but the commercial relationship is stable.
For genuinely one-off work, an MSA is overhead. A single well-drafted services agreement covering both the legal terms and the scope is faster and easier to read. The same applies to small freelance engagements, where a two-page agreement usually beats a twelve-page MSA plus SOW.
The Clauses That Matter Most in an MSA
The order of precedence clause
This states which document wins when they conflict. Read it before you assume anything negotiated in an SOW will hold.
The liability cap
Check whether the cap applies per statement of work or in aggregate across the entire relationship. An aggregate cap set at the value of your first small project may leave you badly under-protected three years and twenty projects later. This is the most commonly overlooked term in an MSA, and it interacts directly with any uncapped liability carve-outs elsewhere in the document. Read it alongside the exclusion of loss categories that usually sits beside it: a cap limits the amount, while an exclusion removes whole kinds of loss, and consequential damages are the category most often excluded.
The term and survival provisions
An MSA may continue indefinitely, or renew automatically. Check what happens to active statements of work if the MSA terminates — well-drafted agreements let existing SOWs run to completion.
Intellectual property transfer timing
Ownership commonly transfers on full payment rather than on delivery. If you are the client, that means unpaid invoices leave you without rights to work you have received. If you are the supplier, it is your main leverage.
What a Managed Services MSA Needs That a Project MSA Does Not
Most MSA guidance is written for project work: a defined piece of work, delivered, accepted, invoiced. Managed services do not run that way. The service is continuous, the client’s operations depend on it while it runs, and the exit is the hardest part of the relationship. Four terms carry most of the risk in a managed services provider’s MSA, and generic templates handle all four poorly.
The service level agreement, and where its remedies stop
The SLA is usually an attachment rather than part of the MSA body, which makes it easy to negotiate the two separately and miss how they interact. The question to settle is whether service credits are described as the sole and exclusive remedy for missing the service level. Where they are, a client whose operations stopped for a day recovers a percentage of one month’s fee and nothing further, whatever the outage actually cost. Which side that favours depends on which side of the agreement you sit on, but both should know what it says before signing, because it is the term that decides what a bad month is worth.
Aggregate caps under a continuous service
An aggregate cap behaves differently for managed services than for projects. Project work produces discrete engagements, so a cap expressed as the fees paid under the relevant statement of work stays roughly proportionate to the work at risk. A managed service bills continuously, so a cap set at the fees paid in the preceding twelve months moves with the relationship, while one set at the value of the first year does not. Check which of the two you have agreed to, because the wording looks similar and the outcome does not.
Who holds the documentation and the credentials
Runbooks, network diagrams, monitoring configuration, administrative passwords, and accounts opened with third-party vendors on the client’s behalf. Many MSAs never mention any of it, and it becomes the most contested question at termination — precisely when neither side is inclined to be generous. A clause worth having names these artefacts explicitly, says who holds them during the term, and says who receives them at the end.
Transition assistance
This is the obligation to help migrate the service to a successor provider. Where the MSA is silent, cooperation at the end of the relationship is voluntary, and a departing provider has little reason to volunteer. A workable clause states how long assistance lasts, what it covers, and at what rate it is charged. The time to write it is at signature, when neither side expects to need it.
Common Mistakes With Master Services Agreements
Three recur often enough to be worth naming.
- Signing the MSA carelessly because the first project is small. The MSA governs everything that follows, not just the engagement in front of you.
- Letting SOWs drift from the MSA. Over time, project documents accumulate terms that contradict the master agreement and are quietly unenforceable.
- Forgetting the MSA exists. Teams sign SOWs for years without rereading the umbrella terms, including caps that have not kept pace with the size of the relationship.
The pattern underneath all three is that an MSA is negotiated when the relationship is smallest and matters most when the relationship is largest. Its terms are sized to a first project and then govern a book of work many times bigger. Reviewing the MSA when the relationship grows — not only when it starts — is the habit that prevents the problem. A structured vendor contract review covers the same ground.
If the relationship deteriorates, what you can actually do about it depends on the MSA’s remedies rather than the SOW’s promises. The Legal Information Institute sets out what breach of contract means and what remedies follow — and in an MSA structure, those remedies are defined in the umbrella document, not the project one.
ContractClerk reviews master services agreements and statements of work against these terms, flags aggregate caps that look undersized, and highlights where an SOW conflicts with the MSA governing it.
An MSA is a type of contract. What distinguishes it is scope: it sets general terms for an ongoing relationship rather than describing one specific piece of work. The actual work is defined in separate statements of work issued under the MSA.
No, the two work together. The MSA sets the legal terms and the SOW defines the deliverables, timeline, and price for one engagement. You need both, and the MSA usually states that its terms control if the documents conflict.
Many run indefinitely until terminated, while others have a fixed term with automatic renewal. Check what happens to active statements of work when the MSA ends, since a well-drafted agreement allows in-progress projects to run to completion.
Yes, when you expect repeat work with the same party. It removes the need to renegotiate legal terms for every project, which saves time and cost. For genuinely one-off engagements, a single services agreement is simpler.
Only by written amendment agreed by both parties. This is why the aggregate liability cap deserves attention at signature: it is sized against your first project but governs the whole relationship, and revisiting it later requires the other side’s cooperation.
The Bottom Line on MSAs
A master services agreement is a good structure used carelessly more often than it is used badly. Its whole value is that you negotiate the hard terms once — which only works if you actually negotiate them, rather than accepting a template because the first project is worth a few thousand dollars. Read the MSA as though it governs the largest engagement you hope to have with this party, because eventually it will.
This article is general information, not legal advice, and does not create an attorney-client relationship. Contract law varies by state and by situation. For high-stakes agreements, have a licensed attorney review the document.