MSAs and Statements of Work: Structuring Service Contracts in India

By Dushyant Shah, Advocate · Bar Council of Gujarat · Vadodara, India

Published: 9 June 2026

For general informational purposes only. This article does not constitute legal advice and does not create an advocate-client relationship. For advice specific to your situation, please consult a qualified legal professional.

The master service agreement plus statement of work structure has become the standard architecture for services engagements in India — in IT and software development, consulting, marketing, legal support, and outsourced operations. Used well, it lets parties negotiate legal terms once and then contract quickly for each new piece of work. Used carelessly, it produces layered documents that contradict each other. This article explains how the structure works under Indian law and where it goes wrong.

1. The Architecture

The MSA is the standing framework: parties, definitions, confidentiality, intellectual property, representations, indemnity, limitation of liability, termination, governing law, and dispute resolution. It contemplates that services will be described in separately executed SOWs, each of which incorporates the MSA by reference.

Each SOW then covers the engagement-specific commercial matter: scope and deliverables, acceptance criteria, timeline and milestones, fees and payment schedule, key personnel, and any terms unique to that project. Under the Indian Contract Act, 1872 each SOW is a contract in its own right, formed on the terms of the MSA plus the SOW’s specifics.

2. Order of Precedence

The single most important structural clause. When the SOW and the MSA conflict — a different liability cap, a different payment period — which governs? The conventional rule is that the MSA prevails unless the SOW expressly identifies the MSA clause it overrides. This keeps legal terms centrally controlled while allowing deliberate, visible exceptions. Without this clause, later-in-time and more-specific documents tend to prevail under ordinary interpretation principles, which may not be what either legal team intended.

3. Intellectual Property: The Default Surprises People

Under Section 17 of the Copyright Act, 1957, work created by an employee in the course of employment belongs to the employer — but work created by an independent contractor belongs to the contractor unless assigned in writing. Section 19 requires an assignment to be in writing, signed, and to identify the work; assignments silent on duration or territory default to five years and India-only under Section 19(5) and 19(6). A well-drafted MSA therefore includes a present-tense assignment of deliverable IP upon creation or payment, an express waiver-adjacent treatment of moral rights so far as Indian law permits, and a licence back to the provider for its pre-existing tools and reusable components.

4. Service Levels and Credits

Where ongoing services are involved, the SLA schedule defines measurable standards — uptime, response times, resolution times — and attaches service credits to failures. In Indian law terms, credits are liquidated damages under Section 74: enforceable as reasonable compensation without proof of actual loss, but subject to the court’s power to reduce unreasonable amounts. Two drafting decisions matter: whether credits are the sole and exclusive remedy for the failures they address, and at what point persistent failure ripens into a termination right.

5. Personnel, Subcontracting, and Control

Service agreements should state that the provider’s personnel remain its employees — for payroll, statutory contributions (EPF, ESI), and compliance purposes — and address whether subcontracting is permitted. Indian clients increasingly ask for key-personnel clauses and rights of approval over substitutions on critical engagements. Where personnel work on the client’s premises or systems, the agreement should allocate responsibility for workplace compliance and data access controls.

6. Payment Terms and the MSMED Act

If the service provider is a registered micro or small enterprise, the MSMED Act, 2006 overrides contractual credit periods: payment is due within the agreed period (capped at 45 days from acceptance), failing which compound interest accrues at three times the RBI bank rate. Buyers contracting with Indian MSME vendors should build this into their payment operations rather than discovering it in a demand notice.

7. Cross-Border Engagements

Indian service providers frequently contract with foreign clients under foreign-law MSAs. Key India-side considerations include FEMA and RBI reporting for foreign exchange receipts, GST treatment of export of services (zero-rated subject to conditions), permanent establishment risk for the foreign client if control is exercised in India, and the practical enforceability of foreign judgments and awards. An arbitration clause seated in a New York Convention jurisdiction generally travels better than an exclusive foreign court clause, since foreign arbitral awards are enforceable in India under Part II of the Arbitration and Conciliation Act, 1996.

8. Common Failure Points

SOWs signed by project managers without authority, leaving formation open to challenge — delegation limits should be set in the MSA.
Scope described by reference to a proposal deck that conflicts with the SOW — incorporate one document, not several.
Acceptance criteria left as “to the client’s satisfaction”, which is an invitation to dispute; objective criteria and deemed-acceptance timelines are cleaner.
Termination of the MSA without addressing in-flight SOWs — state whether SOWs survive MSA termination or terminate with it.

Frequently Asked Questions

What is the difference between an MSA and an SOW?

A master service agreement (MSA) sets the standing legal terms between the parties — liability, IP, confidentiality, termination, dispute resolution. A statement of work (SOW) is a shorter document issued under the MSA for each engagement, describing the specific services, deliverables, timeline, and fees. The MSA is negotiated once; SOWs are issued as work arises.

Which document prevails if the MSA and SOW conflict?

Whichever the order-of-precedence clause says. The common default is that the MSA prevails except where the SOW expressly states that it amends the MSA for that engagement. Without such a clause, conflicts are resolved by ordinary principles of interpretation, which creates avoidable uncertainty.

Who owns IP created under a service agreement in India?

By default, independent contractors own the copyright in what they create — unlike employees, whose work vests in the employer under Section 17 of the Copyright Act, 1957. A written assignment complying with Section 19 is required to transfer ownership to the client, which is why service agreements should always address IP expressly.

Are service level agreements legally binding in India?

Yes, if incorporated into the contract. Service credits for missed SLAs are generally treated as liquidated damages under Section 74 of the Indian Contract Act — enforceable as reasonable pre-estimates of loss. A well-drafted SLA states whether credits are the exclusive remedy for the failures they cover.