Master Services Agreement
Definition
Master Services Agreement
A master services agreement is the umbrella contract that fixes the legal terms governing every engagement between the two parties over time. It describes no work at all — the actual work is defined in the documents that sit beneath it.
The purpose is to negotiate hard once — liability caps, insurance, intellectual property, confidentiality, governance and termination are settled in the master services agreement (MSA), and never reopened for each new piece of work.
Everything commercial and operational moves downward. Scope, deliverables, pricing, service levels and timelines belong in statements of work, so that starting a new engagement takes days rather than months.
The failure mode is leakage — commercial terms creeping into the master document, or legal terms being quietly varied in a statement of work. Both destroy the separation the structure exists to create.
Key takeaways
- The master services agreement carries legal terms only, never scope or price.
- Statements of work and orders sit beneath it and inherit its terms automatically.
- A precedence clause decides which document wins when they conflict.
- Terms varied downward should be explicit, listed and approved, never implied.
How it works
The parties sign one master agreement. Each piece of work is then documented in a statement of work or order that references it, inherits its terms, and adds only the scope, price and timeline specific to that engagement.
Federal ordering practice bounds this structure precisely. Orders placed under an indefinite-delivery contract “shall be within the scope, issued within the period of performance, and be within the maximum value of the contract”.
Those three tests are worth importing wholesale. A commercial order that falls outside the master agreement’s scope, term or value ceiling is not governed by it, whatever the cover sheet claims.
| Term | Belongs in the MSA | Belongs in the SOW |
|---|---|---|
| Liability cap and indemnities | Yes | No |
| Confidentiality and data protection | Yes | No |
| Governance and escalation | Yes | Operational detail only |
| Scope and deliverables | No | Yes |
| Pricing and rate card | Framework only | Actual rates |
| Service levels and credits | Framework only | Measures and targets |
UK government guidance is clear that structure follows risk. The Sourcing Playbook notes that pricing “goes hand in hand with risk allocation”, which is exactly why price sits below the legal terms rather than inside them.
Examples
The structure earns its keep where a relationship will generate repeated, varied work, and adds overhead where it will not. These four cases show both outcomes.
A bank signs one master services agreement with a provider and runs eleven statements of work beneath it over four years. Each new workstream takes two weeks rather than two quarters.
A retailer negotiates an MSA covering three provider entities across two countries. Local annexes handle employment and tax differences without reopening the core terms.
An insurer lets a large statement of work vary the liability cap without flagging it. The variation is discovered during a claim, and the cap that applies is contested.
A small firm insists on a full master services agreement for a single twelve-week project. The legal cost exceeds the project margin and nothing is reused.
Related terms
The contract stack has several layers and they are routinely used as if interchangeable. The entries below separate them by what each document actually decides.
- Statement of work (SOW): the document that defines scope, deliverables and acceptance.
- Contract lifecycle outsourcing: the administration that keeps the stack current and traceable.
- Vendor management outsourcing: the function that governs the relationship the agreement frames.
- Multi vendor outsourcing: arrangements needing one master agreement per provider.
- Procurement outsourcing: the function that negotiates the master terms in the first place.
- Total contract value outsourcing: the value ceiling orders must stay inside.
- Co-sourcing: a shared-delivery model that still sits under a single master agreement.
FAQ
How is an MSA different from a statement of work?
The master services agreement sets legal terms and describes no work. The statement of work describes the work, the price and the timeline, and inherits everything else from above it.
Which document wins in a conflict?
Whichever the precedence clause names, and most master agreements put themselves first. Buyers should check this, because provider templates often reverse it.
Can a statement of work change the liability cap?
Only if the master agreement allows it and the variation is stated explicitly. Silent variation is the commonest structural defect in these stacks.
Does an MSA commit either party to any work?
Usually not. It is a framework, and no obligation to buy or supply arises until an order or statement of work is signed beneath it.
How long should a master services agreement run?
Longer than the work beneath it, often five years or evergreen with a notice period. The point is to avoid renegotiating legal terms mid-relationship.
Is an MSA worth it for a single project?
Rarely. For one short engagement, a standalone contract is cheaper and faster than negotiating a framework nothing else will use.
Compare providers who work from a clear contract stack in the Outsource Accelerator directory.







Independent




