Master Services Agreements and SOWs

The legal framework

A master services agreement (MSA) with statements of work (SOWs) underneath is the standard way to organise an ongoing services relationship. The MSA sets the legal terms once. Each SOW describes one piece of work. The structure has no special statutory form: it is an ordinary contract. Contract law is largely national in the EU, so the law the parties choose (or that applies without a choice, under the Rome I Regulation) supplies the general rules, together with the rules for the specific type of service.

The MSA carries the terms that should not change from project to project: liability, indemnities, intellectual property, confidentiality, data protection, insurance and termination. Each SOW carries the specifics: scope, deliverables, timeline, acceptance criteria and price. Putting commercial detail in the MSA or legal terms in the SOW creates conflicts. An order-of-precedence clause says which document prevails, usually the MSA on legal terms and the SOW on scope and price.

A mix of EU and national rules shapes the key clauses. Where member states differ, check the law that applies to your contract.

Ownership of deliverables. Copyright is only partly harmonised in the EU, and the transfer of an author's rights is mostly a national matter. In most countries the author starts as owner, and the customer does not own what a contractor creates unless the contract says so. Some countries are strict: a transfer must be in writing and is interpreted restrictively, and each mode of exploitation has to be mentioned expressly, with scope, duration and territory. Exceptions exist, for example the employer's rights in software created by employees, which follow an EU rule. In practice the contract must say whether the customer receives an assignment or a licence. Pre-existing materials and general know-how should be carved out and kept by the provider.

Liability. Limits on liability are national law. Generally, parties may cap liability between businesses, but not for their own intentional fault, and a clause that empties the main obligation of its substance is at risk. How far national law goes beyond that differs. Some countries also let a court strike down a clause that creates a manifest imbalance between businesses, or reduce a manifestly excessive penalty clause.

Data protection. Where the provider processes personal data for the customer, Article 28 GDPR requires a written processing agreement with prescribed content, and subprocessors may be engaged only with the customer's authorisation. This sits alongside the MSA.

Change and unforeseen events. Member states differ on whether a court can adapt or end a contract when changed circumstances make performance excessively onerous. Some have a statutory regime for it. Most MSAs deal with this by contract through a change-control mechanism that varies a SOW in writing without reopening the whole agreement.

In practice

Splitting the work between MSA and SOW

The MSA is negotiated carefully once. SOWs are then agreed quickly by the business teams, within the frame the MSA sets. This is the practical value of the structure, and it is why the MSA should not leave important points to be decided SOW by SOW.

Intellectual property in deliverables

The two common models are assignment, where the customer owns the deliverables outright, and licence-back, where the provider keeps ownership of its tools and grants the customer a licence to use the result. Where a transfer of copyright is intended, the clause should say which rights, for how long and where. A vague clause such as "all IP vests in the customer" may not do what the customer expects.

An example

A logistics company hires a consultancy to build a planning tool under a master agreement. The first SOW covers a prototype. The MSA says the customer owns "all results", and the SOW lists a library the consultancy developed before the project. A year later the consultancy reuses that library for a competitor. Because the MSA did not distinguish between pre-existing materials and project results, and no transfer of specific copyright rights was written down, the dispute turns on interpretation (here under national copyright law that reads transfers strictly). A carve-out for pre-existing materials, with a licence to the customer, and an itemised transfer for project results would have settled it.

Acceptance, renewal and termination

Acceptance criteria in the SOW decide when payment falls due and when a warranty period starts. Automatic renewal with a long notice period can lock the customer in for longer than intended, so notice dates should be recorded and followed.

Frequently asked questions

Can we use one combined contract instead?

For one well-defined project, yes. The MSA-plus-SOW model earns its value when several engagements follow over time, because it removes the need to renegotiate the legal terms each time.

What happens if the MSA and a SOW conflict?

The order-of-precedence clause decides. Without such a clause, a court will interpret the documents together, looking at the common intention of the parties, which is less predictable.

Does the customer automatically own what a contractor creates?

Generally not, although national rules differ. Ownership of copyright and other rights should be dealt with in writing. Without a clear transfer, the contractor may remain the owner and the customer holds at most an implied right of use.

Can liability be capped at the fees paid?

Usually, yes, between businesses in most member states. The cap cannot cover intentional fault, and the usual carve-outs are for data breaches, confidentiality and IP indemnities. Whether a cap is balanced depends on the whole contract.

How this connects

The MSA model is part of our commercial contracts and transactions service. It is drafted with our Document Studio and, when the other side holds the pen, reviewed with our contract review. The wider context is in Commercial Contracts: a Map, and for software engagements in SaaS agreements.