How to Review a Master Services Agreement (MSA) in India

A Master Services Agreement, usually just called an MSA, is the umbrella contract that sets the rules once, so the parties do not have to renegotiate liability, IP ownership, confidentiality, or payment terms every time they start a new piece of work. The actual work, what gets delivered, by when, for how much, lives in separate Statements of Work (SOWs) or Order Forms signed under the MSA. Most disputes over an MSA are not about the MSA itself. They are about what happens when an SOW says one thing and the MSA says another, and the contract never says clearly which one wins. Adira, which publishes this guide, makes contract review and CLM software, so we have a stake in you getting good at reading MSAs. Everything below still holds if you never touch our product; if you just want to mark up one MSA by hand, Weave (Adira's free browser tool) lets you do that without an account.

What an MSA actually does, in plain terms

Think of an MSA as the constitution and the SOW as the legislation passed under it. The MSA fixes what should not change deal to deal: IP ownership, liability caps, confidentiality, termination, governing law, and dispute resolution. The SOW (or, in a subscription context, an Order Form) fixes what does change: scope, deliverables, milestones, fees, and the term of that specific engagement. This split exists because renegotiating indemnity and IP language for every new project is slow; sign the MSA once, and each engagement becomes a one or two page SOW that plugs into the framework already agreed.

The trap is treating the MSA as boilerplate you skim once and never revisit. An MSA signed three years ago, for a relationship that has since grown from a small pilot to a multi-crore program, is still the document governing liability on today's SOW, whether or not anyone re-read it before the last three SOWs were signed.

The precedence clause: the one line that decides who wins a conflict

Every MSA needs an order-of-priority clause, and a surprising number either omit one or word it so vaguely it decides nothing. The clause typically reads something like: "In the event of a conflict between this Agreement and any Order Form or SOW, the terms of this Agreement shall prevail, except that the Order Form or SOW may expressly vary a specific provision by referencing the section it is varying."

Three things make this clause actually work:

• A stated order. MSA over SOW, or SOW over MSA, is a real commercial choice. Most MSAs put the MSA on top for risk terms (liability, IP, confidentiality) and let the SOW control commercial terms (price, scope, deadlines).
• An explicit variance mechanism. Without a line letting an SOW deliberately override a named MSA clause, sales and delivery teams negotiate a client-specific liability cap directly into an SOW with no legal review, then argue later about whether that clause was even allowed to exist.
• A defined document stack. Where amendments, addenda, purchase orders, and SOWs are all in play, list them in order. Silence invites each side to argue for whichever reading favours them once the dispute has already started.

A test you can run right now: open your MSA and search for "conflict" or "precedence." If nothing comes up, that is not a neutral gap. It means the order of priority on your next dispute gets decided by a judge or arbitrator applying general interpretation principles, not by anything you agreed to.

Clause by clause: what to check, and where to go deeper

Skim the whole document for these, then go deep on the ones that apply to your deal. Each links to a full explainer.

• Scope and SOW mechanics. Does the MSA define what an SOW is, how it gets executed, and what governs work that starts before one is signed?
• Fees and payment. The MSA sets mechanics (invoicing, currency, late-payment consequences); the SOW sets price. See payment terms in Indian contracts for how net-30/45/60 works, and why the MSMED 45-day rule below can override it.
• IP ownership. Assignment or licence, and split from pre-existing "Background IP"? See our IP assignment explainer: silence on duration and territory does not default to permanent, worldwide ownership.
• Confidentiality. Mutual or one-way, survival period after termination, and standard carve-outs. See our confidentiality explainer.
• Warranties. Standard service-level promises versus a disclaimer broad enough to exclude basic fitness for purpose. See our warranty clause guide.
• Indemnity. Who pays for third-party claims over IP infringement, data breach, or on-premises injury. See our indemnity explainer on how an uncapped indemnity can swallow a liability cap whole.
• Limitation of liability. The cap, and its carve-outs (fraud, gross negligence, confidentiality, IP indemnity are common exclusions). See our limitation of liability explainer.
• Term and termination. Fixed term or auto-renewal, and termination for convenience versus for-cause only. See our termination for convenience explainer.
• Data protection. If personal data moves through the engagement, the MSA needs a clause on Data Fiduciary/Processor roles, security safeguards, and breach notice under the DPDP Act, 2023. See our DPDP explainer.
• Force majeure. Listed events or a general "beyond reasonable control" test, a notice window, and a termination right if the event runs long. See our force majeure explainer.
• Dispute resolution. Arbitration versus courts, seat, venue, and governing law. See our arbitration explainer and governing law explainer.

India notes: three things a generic MSA template gets wrong

Stamping. An MSA is an instrument, and in most Indian states, commercial agreements attract stamp duty under the applicable state Stamp Act (or the Indian Stamp Act, 1899, where the state has no separate Act). Rates are state-specific and move with state budgets, so check the schedule for the state of execution, not the rate from a previous deal. Skipping this does not make the contract vanish, but Section 35 of the Indian Stamp Act says an instrument chargeable with duty "shall [not] be admitted in evidence for any purpose... unless such instrument is duly stamped." A seven-judge Supreme Court bench settled the biggest uncertainty here in In Re: Interplay Between Arbitration Agreements under the Arbitration and Conciliation Act, 1996 and the Indian Stamp Act, 1899 (13 December 2023): non-stamping makes an instrument inadmissible in evidence, a curable defect, not void. Get the MSA properly stamped at signing; do not treat a missing stamp as a free exit, and do not assume an unstamped MSA is worthless either.

The MSME 45-day rule can override your payment clause. If your provider or subcontractor is a registered micro or small enterprise under the MSMED Act, 2006, Section 15 caps how long you can take to pay them regardless of what the MSA says: where a period is agreed in writing, "in no case [shall it] exceed forty-five days from the day of acceptance." Miss it, and Section 16 imposes compound interest, with monthly rests, at three times the RBI-notified bank rate, "notwithstanding anything contained in any agreement between the buyer and the supplier." An MSA that sets a blanket net-60 or net-90, without checking supplier MSME status per SOW, silently exposes the buyer to this override. Our payment terms explainer covers this, and the Silpi Industries Supreme Court case on when registration has to exist, in full.

Personnel non-solicit clauses need to restrain conduct, not people. MSAs routinely bar either side from hiring the other's staff during the engagement and for a period after. Section 27 of the Indian Contract Act, 1872 says "every agreement by which any one is restrained from exercising a lawful profession, trade or business of any kind, is to that extent void," subject only to a narrow goodwill-sale exception. A non-solicit worded to restrain the company from actively poaching, not any individual's freedom to move jobs, sits outside what Section 27 targets. In Wipro Ltd. v. Beckman Coulter International S.A. (Delhi High Court, 11 July 2006), the court upheld a two-year mutual employee non-solicit between distributor and principal on exactly that reasoning, and because it carved out unsolicited applicants and general job postings. Separately, Gujarat Bottling Co. Ltd. v. Coca Cola Co., (1995) 5 SCC 545, confirmed that a restraint operating only during the subsistence of a contract, as most MSA non-solicits do, is not caught by Section 27 the way a post-termination restraint can be. Read our non-solicitation explainer for the full breakdown.

Red flags table

Normal	Red flag	Why it matters
Clear precedence clause naming MSA or SOW as controlling	No precedence clause, or one that just says "read together"	Every SOW-vs-MSA conflict becomes a fresh argument after the dispute starts
SOW template attached, showing exactly what fields it can fill in	No SOW template; each one drafted from scratch by whoever closes the deal	Inconsistent SOWs quietly override MSA protections without legal review
Liability cap stated as a multiple of fees paid, with named carve-outs	Liability cap silent, or "as per applicable law"	Silence does not create a favourable default; it often means uncapped exposure
Indemnity scope limited to specific triggers (IP infringement, confidentiality breach, gross negligence)	Broad "indemnify for any and all losses arising from this Agreement"	Effectively swallows the liability cap through the back door
Termination for convenience with defined notice for both sides	Termination for convenience only in one party's favour	The weaker-notice party absorbs all transition risk when the relationship ends
IP clause states assignment, duration, territory, and covers derivative works	IP clause just says "assigns all IP" with no period or territory	Silence on duration defaults to 5 years, and territory to India only
Payment clause checks supplier MSME status and honours the 45-day cap	Blanket net-60/net-90 with no MSME carve-out	Sections 15 and 16 of the MSMED Act override contrary contract terms
Non-solicit worded as a restraint on hiring conduct, with an unsolicited-applicant carve-out	Non-solicit broad enough to bar an individual from working in the industry	Risks being read as an unlawful restraint of trade under Section 27
Stamp duty paid per the state of execution	No record of stamping, or state of execution left blank	Unstamped instrument becomes inadmissible in evidence, delaying enforcement

Bad clause versus better clause: the precedence clause

Bad: "This Agreement, together with any Statements of Work executed hereunder, constitutes the entire agreement between the parties."

What is wrong: it says the documents together form the agreement, but never says what happens when they conflict. It reads as complete but decides nothing on the one question that actually causes disputes.

Better: "In the event of any conflict or inconsistency between the terms of this Agreement and the terms of any Order Form or Statement of Work executed hereunder, the terms of this Agreement shall prevail, except with respect to scope of work, deliverables, fees, and delivery timelines, which shall be governed by the applicable Order Form or Statement of Work. Any Order Form or Statement of Work purporting to vary a specific provision of this Agreement (other than scope, deliverables, fees, or timelines) shall be effective only if it expressly identifies the section being varied and is signed by an authorised signatory of both parties."

What changed and why: naming the winning document by default closes the silent gap. Carving out scope, fees, and timelines as SOW-controlled matches how these documents are actually used, commercial terms change per engagement, risk terms should not. The final sentence closes the loophole where a sales-negotiated SOW quietly overrides liability or IP language without legal ever seeing it.

The MSA review checklist

Run through this in order, on any MSA before signature.

1. Is there a precedence clause naming a clear winner for MSA-SOW conflicts?
2. Is there an SOW template attached, or a defined SOW execution process?
3. Does the liability cap have a stated number, with carve-outs explicitly listed?
4. Does the indemnity clause list specific triggers, not "any and all losses"?
5. Does the IP clause state assignment (not licence), duration, and territory?
6. Is confidentiality mutual, surviving termination for a stated period?
7. Does the payment clause account for MSME suppliers and the Section 15 cap?
8. Is termination for convenience available to both sides, on comparable notice?
9. Does a data protection clause exist if personal data will flow either way?
10. Is the agreement stamped correctly for the state of execution?
11. Is any personnel non-solicit worded as a restraint on hiring conduct, not on any individual's right to work?
12. Does the dispute resolution clause name a seat, venue, and governing law?

How this connects to SOWs and Order Forms

An MSA review is incomplete without checking what gets signed underneath it. For project-based delivery, see our guide to reviewing a Statement of Work for deliverables, acceptance criteria, and change orders. For recurring subscription or services relationships, see our guide to reviewing an Order Form or Purchase Order, since the fields that matter there (term, auto-renewal, per-seat pricing) differ from a project SOW.

US and global contrast

US-style MSAs look structurally similar, master agreement on top, SOWs or work orders underneath, but two things differ. US MSAs often rely on "work made for hire" language, vesting IP in the client automatically for qualifying work; Indian law has no general equivalent, so a merely re-titled US template often leaves IP ownership weaker than intended. And US non-compete enforceability varies heavily by state (California voids most employee non-competes outright, others enforce them if reasonable), while India runs off one central statute, Section 27, applied consistently across states.

FAQ

Does every services engagement need a separate MSA, or can we just use one long contract? For a single, one-off engagement, a standalone services agreement is often simpler. An MSA earns its complexity when you expect multiple engagements with the same counterparty, since it lets you negotiate risk terms once and reuse them.

Who normally drafts the MSA, the client or the vendor? Either, usually reflecting negotiating leverage: larger clients often issue their own template, smaller ones sign the vendor's standard MSA. Whoever drafts it tends to build in favourable defaults, especially on liability caps and indemnity scope, so read it as written in the other side's interest.

If the MSA and a signed SOW conflict and there is no precedence clause, who wins? A court or arbitrator applies general interpretation principles, which can include treating the more specific, later-dated document as controlling on the point it addresses. That is not a reliable substitute for saying so directly in the MSA; do not rely on an interpretation you have not actually negotiated.

Can an MSA be terminated while SOWs under it are still active? Only if the termination clause says so. A well-drafted MSA states explicitly whether MSA termination automatically ends all active SOWs, or whether they run to their own completion date regardless.

Does an MSA need to be signed by both parties' authorised signatories, or can a manager sign it? It should be signed by someone with actual authority to bind the company, typically confirmed by a board resolution or power of attorney for larger commitments. One signed without that authority can be challenged later as not properly executed, exactly when a dispute makes it matter.

We are a small business signing our first MSA with a large enterprise client. What should we check first? Start with the liability cap and indemnity scope, since large-client MSAs are often drafted with the smaller vendor absorbing disproportionate risk. Check the precedence clause next, then IP ownership if you expect to reuse your own tools or frameworks across other clients.

This guide explains how MSAs are generally structured under Indian law and the specific statutory points, stamping, MSMED payment timelines, and Section 27, that most templates get wrong. It is not legal advice, and it does not tell you whether your specific MSA is enforceable, properly stamped, or safe to sign in your situation. For that, especially before a high-value or long-term engagement, have a lawyer review the actual document.