A master service agreement (MSA) is a contract that sets the shared legal terms for an ongoing relationship between a buyer and a vendor. It covers things like payment, confidentiality, ownership of work and how disputes are settled. Each new project then gets its own short document, usually a statement of work (SOW), that lists the work, dates and price.
The point is simple: agree on the hard legal terms once, then reuse them. This guide explains what goes in an MSA, how it fits with a SOW, which clauses deserve the most care, and how the US federal government uses a similar idea.
This is general education, not legal advice. Have a lawyer review any contract before you sign it.
What a master service agreement does
An MSA acts as a parent document. It does not usually describe one project. Instead, it sets the rules that every future project will follow.
That brings three benefits:
- Speed. New projects start faster because the legal terms are already agreed.
- Consistency. Every project runs on the same rules for payment, risk and ownership.
- Lower legal cost. Lawyers review the core terms once, not for every project.
MSAs are common with software and cloud vendors, agencies, IT service firms, consultants and long term suppliers. They make the most sense when you expect more than one project with the same vendor.
Sources: Ironclad, "MSA vs SOW: Which One To Use When"; Blueink, "What Is a Master Service Agreement?"
MSA vs SOW: what goes where
The MSA holds terms that rarely change. The SOW holds the details of one piece of work. Mixing the two causes most MSA problems.
| Topic | In the MSA | In each SOW |
|---|---|---|
| Payment | Invoice rules, payment terms, late fees | The price for this project |
| Scope | How new work is requested and approved | The exact tasks and deliverables |
| Timing | Contract length and renewal | Start date, milestones, end date |
| Acceptance | How acceptance works in general | The tests for these deliverables |
| People | Rules on staff and subcontractors | Named roles for this project |
| Risk | Liability caps, indemnity, insurance | Any project specific changes, if allowed |
A useful habit: each SOW should name the MSA it falls under. That makes it clear which rules apply.
Sources: Ironclad, "Differences between an MSA and an SOW"; Dropbox Sign, "Master service agreement vs statement of work"
Key clauses to read closely
Scope and change control
The MSA should explain how new work is added and how changes are approved. Without this, scope can grow without a matching change in price.
Payment terms
Look for when invoices are sent, when they are due and what happens if a payment is late. Terms such as "net 30" are common. Our guide to net 30 payment terms explains the math.
Confidentiality
This clause says what counts as confidential, how it must be protected and how long the duty lasts.
Intellectual property
This clause says who owns what. It should cover materials each side owned before the deal, the new deliverables, and anything licensed rather than sold. Ownership matters most for software, content and design work.
Warranties
Warranties are promises about the work or the product. Check what is promised, how long the promise lasts, and what the fix is if it is broken.
Indemnification
An indemnity says who pays if a third party sues. Typical triggers are a data breach, a claim that the work copies someone else's intellectual property, or negligence. Some lawyers prefer mutual terms, where each side covers its own misconduct.
Limitation of liability
This clause caps how much one side can owe the other. Check the size of the cap, whether it applies to both sides, and which claims sit outside it.
Term and termination
Look for the contract length, renewal rules, notice periods and what happens to data and open work when the contract ends.
Governing law and disputes
This clause names which state's law applies and how disputes are handled, such as in court or by arbitration.
Sources: Blueink, "Key Clauses Every MSA Should Include"; Shperun Law, "Master Service Agreements: Key Clauses You Should Never Skip"; Mercy Corps, sample master service agreement (PDF)
What happens when an MSA and SOW conflict
Sometimes a SOW says one thing and the MSA says another. For example, the MSA may set one payment deadline and a new SOW another.
The answer depends on the contract. Look for a clause called "Order of Precedence," "Conflicts" or "Entire Agreement." Many MSAs say the MSA wins unless the SOW names the exact clause it changes. Do not assume the newest or most specific document wins.
One public example: a 2009 MSA filed with the SEC gave the MSA priority when it could not be reconciled with a SOW. The SOW won only for MSA terms it named as inconsistent.
Sources: Dropbox Sign, "What happens if an MSA and SOW conflict?"; Ironclad, "How MSAs and SOWs work together"
Where SLAs, NDAs and purchase orders fit
An MSA is often one of several linked documents:
- Service level agreement (SLA): sets measurable service targets, such as uptime, and what happens when they are missed. It is often an exhibit to the MSA. See our guide to the service level agreement.
- Nondisclosure agreement (NDA): focuses only on confidential information. The MSA may hold its own confidentiality clause as well.
- Purchase order (PO): the buyer's own document that approves spend. Many finance teams match a PO against the invoice and a receipt before paying.
Sources: Dropbox Sign, "Where do SLAs, NDAs, and purchase orders fit?"
How the federal government uses the same idea
US federal buyers use agreements that work much like an MSA. Two are common:
- Basic ordering agreement (BOA). Under the Federal Acquisition Regulation (FAR), a BOA sets terms for future orders, describes the supplies or services and explains how orders will be priced and placed. The FAR states plainly that a BOA "is not a contract." The contract forms only when an order is placed.
- Blanket purchase agreement (BPA). The FAR describes a BPA as a simple way to fill repeat needs by setting up "charge accounts" with qualified suppliers.
This is a useful lesson for private buyers. A framework agreement and the orders placed under it are two different things. Be clear in your own MSA about whether it commits anyone to buy anything, or only sets the terms if you do.
Sources: FAR 16.703, Basic ordering agreements; FAR 13.303-1, Blanket purchase agreements
A first read checklist
Before you send an MSA to your lawyer, check these points:
- Does it say how SOWs are created, approved and changed?
- Is there an order of precedence clause?
- Are payment due dates and late fees clear?
- Who owns custom work, and who keeps the vendor's tools?
- What is the liability cap, and what sits outside it?
- How can either side end the contract, and with how much notice?
- What happens to your data when the contract ends?
- Which state's law applies?
If you are comparing several vendors, reading their MSAs side by side is part of good due diligence. Exit and renewal terms also change the total cost of ownership of a deal.
Sources: Blueink, "Common Mistakes to Avoid in an MSA"; Dropbox Sign, "What should a master service agreement include?"
Frequently asked questions
What is a master service agreement?
A master service agreement is a contract that sets the shared legal terms for an ongoing buyer and vendor relationship. Each project is then added through a shorter document, usually a statement of work.
What is the difference between an MSA and a SOW?
The MSA sets terms that apply to every project, such as payment rules, confidentiality and liability. The SOW describes one project: the tasks, deliverables, dates and price.
Is a master service agreement legally binding?
Yes, a signed MSA is usually a binding contract for the terms it contains. Whether it obliges anyone to buy anything depends on its wording, so check that point with a lawyer.
Does an MSA need to be signed for each new project?
No. The MSA is signed once, and each new project is added with a new SOW or order that refers back to it.
Can a statement of work override an MSA?
Only if the contract allows it. Check the order of precedence clause, which often says the MSA wins unless the SOW names the exact term it changes.
What is a statement of work?
A statement of work is a document that defines one project under a master agreement. It lists the work, deliverables, milestones, acceptance tests and price.
Sources
- Ironclad, "MSA vs SOW: Which One To Use When." ironcladapp.com
- Blueink, "What Is a Master Service Agreement? Definition, Key Clauses, and Free Template." blueink.com
- Dropbox Sign, "Master service agreements: What they are and how to create one." sign.dropbox.com
- Shperun Law, "Master Service Agreements: Key Clauses You Should Never Skip." shperunlaw.com
- Mercy Corps, sample master service agreement (PDF). prosperglobal.org
- Federal Acquisition Regulation 16.703, Basic ordering agreements. acquisition.gov/far/16.703
- Federal Acquisition Regulation 13.303-1, Blanket purchase agreements. acquisition.gov/far/13.303-1