Master Services Agreement (MSA): A Practical Guide

Your company needs a stable vendor for ongoing services — IT support, content, QA, recruitment, payroll processing. You could sign a fresh agreement every time, but that is slow, repetitive and inconsistent. The answer is a Master Services Agreement (MSA): one umbrella contract setting out the standing commercial terms, with each specific piece of work governed by a short Statement of Work (SOW) that plugs into the framework.

The MSA is the backbone of most long-term supplier relationships in India, and it is widely misunderstood. Done well, it lets you onboard a new project in days instead of weeks, because the hard commercial negotiation happens once. Done badly, it is a source of disputes over scope, staffing, liability and termination that surface only when the relationship turns sour.

This guide explains the structure of an MSA, the clauses that actually decide outcomes, and the negotiation points unique to the Indian legal context — grounded in the Indian Contract Act, 1872, the Income-tax Act, 1961 for TDS, and good commercial practice. By the end you will know exactly what to look for before you sign.

How an MSA is structured: the umbrella and the SOWs

The MSA solves a specific problem: recurring services of the same kind, negotiated once. It has two layers:

• The MSA itself: the standing framework — definitions, confidentiality, indemnities, limitations of liability, termination, governing law, and general provisions. These terms apply to every engagement under the MSA.
• The Statement of Work (SOW): one per project. The SOW names the specific services, deliverables, timeline, fees, milestones and project-specific personnel. It references the MSA for all general terms.

The critical rule of construction is specific terms prevail over general terms. When an SOW deliberately deviates from the MSA — say, a higher liability cap for a high-value project — the SOW should expressly say so and, where it does, the SOW controls for that engagement. Unless this hierarchy is stated, courts may treat the two documents as conflicting, and ambiguity is exactly what dispute resolution feeds on.

The scope of services and deliverables

A well-structured SOW is precise about what the vendor must deliver. Repeating the core discipline of good contracts, each SOW should identify:

• the services to be performed, with enough detail to make completion objectively assessable;
• the deliverables and their acceptance criteria;
• the milestones and timeline, including any dependencies on your inputs;
• the fees, whether fixed, time-and-materials, or milestone-linked;
• any service levels — response times, availability, throughput — with credits or remedies for failure.

Without defined acceptance criteria, “completed work” is a matter of opinion and the vendor will invoice on its own view. Specify in the SOW how the vendor’s work is accepted — for example, delivery plus a 10-day review period within which you may reject work that does not conform to the specification, failing which it is deemed accepted. That mechanises acceptance and removes the ambiguity that Section 10 of the Indian Contract Act, 1872 would otherwise leave wide open.

Staffing, sub-contracting and resources

An MSA governs staffing terms more often than any other contract type. The relevant clauses handle:

• Key personnel: identify the vendor’s named resources on a project and require consent before substitution. This prevents the classic bait-and-switch of a senior team at pitch being replaced by juniors once work begins.
• Background verification: for staff who handle your data or systems, require the vendor to conduct and report proper screening, and to comply with your security requirements.
• Sub-contracting: decide whether the vendor may sub-contract, and require consent. If allowed, the vendor must remain fully responsible for its sub-contractors’ performance — the MSA should say the vendor is liable as if it had performed the work itself.
• Resourcing and secondment: where the vendor provides on-site resources, clarify who supervises them daily, who bears costs, and how the engagement can be scaled up or down.

Be careful about the employment boundary. If vendor staff work on your premises under your day-to-day direction, there is a risk — in strict labour-law terms — of the engagement being characterised as employment, attracting provident fund, ESI and gratuity obligations. The MSA should state clearly that the vendor’s personnel are engaged by the vendor and are not your employees, and that the vendor is responsible for all statutory compliance in respect of its staff. As with a consultancy agreement, the substance of the relationship matters: genuine output-based, vendor-managed resourcing is far safer than you micro-managing their daily hours.

Liability caps: the single most negotiated clause

The liability cap is where an MSA is won or lost. A typical formula limits the vendor’s aggregate liability for all claims under the MSA to the fees paid (or accrued) by you in the trailing twelve months (or the contract value), and excludes indirect, consequential, punitive and lost-profit damages on both sides.

These are the clauses you should fight to protect:

• Carve-outs to the cap: breach of confidentiality, infringement of third-party intellectual property, fraud or wilful misconduct, and death or personal injury caused by negligence should not be absorbed by the cap. Unlimited (or higher-capped) liability for these is standard.
• Mutual exclusion of consequential damages: both parties typically exclude each other’s loss of profits, data and goodwill. This keeps the risk profile predictable.
• Set-off: agree in what circumstances your payments to the vendor may be withheld or set off against valid claims. Absent a clause, unilaterally withholding payment invites a breach-of-contract claim.

Set the cap in alignment with risk and insurability. If the vendor is a small firm insuring its professional services exposure, an uncapped MSA will simply be rejected or priced in. A cap equal to a multiple of quarterly fees is a reasonable middle ground that keeps the vendor insurable while compensating you meaningfully if performance fails.

IP, confidentiality and data in the MSA

Because the MSA covers many engagements, its IP and confidentiality provisions must be written to survive across every SOW:

• IP ownership: the MSA should state that deliverables — software, designs, content, documents — become or remain your property upon payment, while the vendor retains ownership of its pre-existing tools and licences them back to you for use of the deliverables. This mirrors the carve-out discipline discussed for software outsourcing, and it is essential for an MSA covering recurring production work.
• Confidentiality: a broad clause protecting both parties’ confidential information, surviving termination (typically three to five years, or indefinitely for trade secrets), and requiring the return or destruction of materials on end of the relationship.
• Data protection: where the vendor processes personal data, require compliance with the Digital Personal Data Protection Act, 2023, the Information Technology Act, 2000 and its Rules, and with reasonable security practices, and oblige the vendor to assist you in meeting your compliance duties.

Keep the IP and confidentiality definitions in the MSA itself rather than buried in individual SOWs. Since a single MSA may govern a dozen SOWs, a standalone, robust set of general terms saves you from renegotiating IP on every project.

Termination, transitions and the exit plan

An MSA must answer the question every long-term relationship eventually asks: how does it end, and what happens to the work in progress? Cover:

• Term: an initial period (typically one to three years) with automatic renewal subject to notice (usually 30 to 90 days).
• Termination for convenience: either party’s right to terminate on written notice, subject to a defined notice period reflecting the length of the engagement.
• Termination for cause: immediate termination for material breach that is not cured within a defined period (15 to 30 days), or for insolvency, fraud or sustained failure to meet agreed service levels.
• Transition-out obligations: the vendor’s duty to hand over work products, documentation, data and IP, and to provide reasonable transition assistance at an agreed rate. A defined transition period (say 30 to 90 days) prevents you from being held hostage by a departing vendor.

Both plain-English clarity and the mechanics of Sections 62 to 67 of the Indian Contract Act, 1872 (which deal with obligations of parties when a contract is rescinded) make a written, unambiguous termination clause essential. Ambiguity over what remains due at termination is among the most common MSA claims.

Taxes, invoicing and Indian compliance

Finally, build the payment mechanics around Indian compliance realities. State in the MSA that:

• invoices carry the vendor’s GSTIN and comply with GST invoicing rules where applicable; and
• you deduct TDS on payments as required — for service providers, generally under Sections 194C or 194J of the Income-tax Act, 1961 — and issue the relevant certificates.

And specify the governing law and dispute resolution. For a vendor operating in India, Indian law with courts at your principal place of business, or arbitration under the Arbitration and Conciliation Act, 1996 with a stated seat, gives you a predictable forum. Set these once in the MSA so every SOW inherits them, and you will never again negotiate jurisdiction in a hurry against a deadline.

Master services agreement FAQ

Q: What is the difference between an MSA and an SOW?
A: The MSA sets the standing commercial, legal and liability terms for the whole relationship; each Statement of Work details one specific project’s services, fees and timeline and refers back to the MSA for general terms.

Q: What should a Statement of Work include?
A: Services, deliverables and acceptance criteria, milestones, fees, project-specific personnel, and any service levels. Where an SOW deliberately changes an MSA term, say so expressly so the specific term prevails.

Q: Is it normal for the vendor to limit its liability?
A: Yes. Most MSAs cap liability at the fees paid, with standard carve-outs for confidentiality breach, IP infringement, fraud and personal injury. Negotiate the cap and carve-outs carefully.

Q: Who owns the work product produced under an MSA?
A: It should be you, on payment, via an IP assignment, with the vendor’s pre-existing tools carved out and licensed back to you. If the MSA is silent, ownership may stay with the vendor under Section 17 of the Copyright Act, 1957.

Q: Can the vendor replace its staff without consent?
A: Only with your consent if the MSA names key personnel and prohibits substitution. Always include a key-personnel clause to prevent an unapproved drop in the quality of delivery resources.