Master Service Agreement: The Umbrella Contract and the Clauses That Matter

A master service agreement exists to avoid negotiating the same terms twice. The general legal position between two organisations, who bears which risk, who owns what, what happens if things go wrong, is settled once. Individual pieces of work are then agreed in short documents that describe scope, price and timing and incorporate the master terms by reference.

The efficiency is real. A first engagement might take weeks of legal negotiation; the second, under an existing master agreement, can be agreed in a day. The corresponding risk is equally real: because the master agreement contains no scope and no price, it is easy to treat it as a formality, and it will govern every engagement for years.

In software purchases the second row is frequently an order form rather than a statement of work, because the deliverable is access to a product rather than a project. The structural logic is identical: durable terms above, transactional terms below.

Limitation of liability

This caps what one party can recover from the other, commonly by reference to fees paid over a preceding period. Read what is excluded from the cap as carefully as the cap itself, since certain categories are frequently carved out and treated separately. Read also whether indirect and consequential losses are excluded, which is standard and has a specific legal meaning worth understanding rather than assuming.

Indemnity

An indemnity is a promise to cover the cost of specified claims, most often third-party claims relating to intellectual property infringement or to breach of confidentiality or data obligations. Indemnities frequently sit outside the liability cap, so a clause that appears symmetric on the page can be very asymmetric in effect. This is one of the sections where independent legal review earns its fee.

Intellectual property

Two questions need answering: who owns what is created during the engagement, and what happens to the material each side already owned and brought with them. Software vendors normally retain ownership of the product and grant a licence to use it, while material specific to the customer may be treated differently. Ambiguity here surfaces years later, usually when someone wants to leave.

Termination

Distinguish termination for cause, which follows a breach and usually a period to fix it, from termination for convenience, which permits exit on notice without a reason. Note also what happens on termination: what is paid, what is returned, what data is deleted and by when, and which obligations survive.

When a statement of work and the master agreement disagree, something has to decide which one governs. The precedence clause does that in a couple of sentences and prevents a routine inconsistency from becoming a dispute about interpretation.

Either hierarchy can be defended. Master agreement first protects positions that were negotiated by people who understood them, and prevents erosion through project documents. Statement of work first gives flexibility where individual engagements genuinely differ. The choice should be deliberate, and if statements of work are allowed to prevail, the master agreement should say which terms may be varied and which may not.

Most master agreements renew automatically for successive terms unless notice is given, which means terms negotiated for a small first project can still govern a relationship that has grown ten times larger. The dates that matter, effective date, initial term end, renewal date and the notice deadline, belong in a system that reminds the relationship owner in time to act.

One further discipline is worth adopting: keep a single register of which statements of work are live under the agreement. It sounds obvious and is frequently absent, with the result that nobody can answer whether the master agreement is still in force, which is the first question asked in any dispute.

A statement of work describes an individual engagement under the master agreement. An order form performs the same function for product purchases. A data processing agreement covers personal data handling and is usually attached rather than embedded. A purchase order is the buyer's internal authorisation and is not a contract in the same sense, though it may incorporate terms. Nothing on this page is legal advice, and the clauses discussed here are exactly the ones where competent counsel changes the outcome.

Related pages on buying, pricing and evaluating a CRM:pricing, book a demo, features overview, what a CRM is, compare alternatives, and CRM for small business.