How to draft a master service agreement (MSA): a clause-by-clause guide for India (2026)

What a master service agreement actually does

Think of it this way. A standalone service contract answers one question: what are we doing on this project? A master service agreement answers a different and bigger one: what are the rules every time we do business, no matter what the project is?

That split is the whole point. The MSA carries the heavy, slow-to-negotiate terms: liability, indemnity, intellectual property, confidentiality, payment mechanics, termination, dispute resolution, governing law. These don’t change from project to project. The SOW carries the fast-moving commercial detail: scope, deliverables, timelines, milestones, fees, acceptance criteria. These change constantly.

So when a client wants a fifth project from the same vendor, nobody reopens the indemnity fight. They sign a two-page SOW that references the existing MSA, and the legal framework attaches automatically. For companies running dozens of engagements (IT services firms, marketing agencies, consultancies, manufacturers with recurring suppliers), that’s the difference between a two-day contracting cycle and a two-week one.

Is an MSA legally different from any other contract? No. It’s an ordinary contract that has to satisfy the same essentials as everything else under [STATUTE:contract-1872#section-10] of the Indian Contract Act, 1872: free consent, lawful consideration, competent parties, lawful object. There’s no special “MSA statute” in India. What makes it an MSA is structural, not statutory. It’s built to sit on top of future SOWs.

And that structure is exactly where the drafting risk lives.

MSA, SOW, and the order-of-precedence trap

Picture two documents that are supposed to work together. The MSA says liability is capped at the fees paid in the last twelve months. A later SOW, drafted in a hurry by the delivery team, says the vendor will be “fully responsible for any and all losses.” Which one wins?

If your MSA doesn’t answer that question explicitly, you’ve created a contract that argues with itself. And Indian courts will resolve the ambiguity by reading the documents together and looking for the parties’ intention, which is precisely the uncertainty you signed an MSA to avoid.

The fix is a precedence clause (sometimes called an order-of-priority or conflict clause). It states, in plain terms, which document controls when two of them disagree. There are two defensible approaches, and you have to pick one consciously:

• MSA-controls: the MSA overrides any conflicting SOW term. This protects the carefully negotiated framework from being quietly undone by a junior team member drafting an SOW. It’s the safer default for the party that negotiated hard on the MSA.
• SOW-controls (for project-specific terms only): the SOW overrides the MSA, but only on commercial specifics like scope, fees, and timelines, never on the core legal terms. This gives flexibility where you want it without blowing a hole in liability or IP.

The drafting mistake we see most often is silence: an MSA-plus-SOW structure with no precedence clause at all. Don’t leave it to interpretation. State the hierarchy, and state the carve-outs.

One more structural choice. Should pricing live in the MSA or the SOW? Put commercial rates in the SOW, where they belong, and keep only the payment mechanics (invoice cycle, payment window, interest on delay, currency, taxes) in the MSA. That way a rate change never requires reopening the master agreement.

Six decisions to make before you draft a word

Drafting fails when it starts at clause one and works downward. The clauses are interdependent, and six upstream decisions shape all of them. Settle these first.

First, who are the parties, and is anyone signing for a group? If the client wants its affiliates and subsidiaries to be able to order under the same MSA, that has to be drafted in deliberately, with each affiliate either becoming a party or being defined as an authorised “ordering entity.” Vague references to “the client and its group companies” create enforcement headaches when an unnamed subsidiary tries to invoke the contract.

Second, what goes in the MSA and what goes in the SOW? Draw the line now. Core legal terms in the MSA, commercial specifics in the SOW. Write it down before you start, because the moment you blur it, the precedence problem returns.

Third, what’s your liability appetite? This is a business decision, not a legal one, and it drives the single most negotiated clause in the document. A vendor wants the cap low (fees paid in the last 12 months is the common market position). A customer wants it high, or uncapped for certain breaches. Decide your floor and your walk-away before you draft, because everything in the indemnity clause keys off it.

Fourth, who owns the IP? In a services context, the deliverables created for the client are usually assigned to the client, while the vendor keeps its pre-existing tools, libraries, and know-how (often licensed back to the client to the extent needed to use the deliverable). Under the Copyright Act, 1957, authorship and first ownership don’t automatically pass just because someone paid for the work, so assignment has to be express and in writing. Decide the split now.

Fifth, what’s the governing law and dispute forum? For two Indian parties, Indian law and a named seat of arbitration is the clean default. For a cross-border deal, this becomes a genuine negotiation, and it interacts with enforcement. Decide early because it shapes the entire dispute-resolution section.

Sixth, how does the relationship end? Termination for cause is uncontroversial. Termination for convenience (either party can walk with notice) is a commercial lever that needs a notice period, a wind-down mechanism, and clarity on payment for work in progress. Decide whether you’re granting it, and to whom.

Settle those six, and the drafting becomes assembly rather than invention.

How to draft a master service agreement, step by step

Here’s the sequence that produces a clean, enforceable MSA. It’s deliberately ordered so that each step feeds the next.

1. Map the relationship and fix the structure. Confirm it’s genuinely a recurring relationship (if it’s a single project, you want a standalone contract, not an MSA). Decide the MSA-versus-SOW split and the precedence rule.
2. Draft the definitions and interpretation clause. Define every capitalised term you’ll rely on: “Services,” “Deliverables,” “SOW,” “Confidential Information,” “Affiliate,” “Background IP,” “Foreground IP.” Sloppy definitions cause more disputes than missing clauses.
3. Draft the scope and SOW mechanism. State that the MSA governs all services ordered through SOWs, that each SOW incorporates the MSA by reference, and how an SOW comes into effect (signature, or a defined acceptance process).
4. Draft the commercial-mechanics clauses. Payment terms, invoicing cycle, taxes, interest on delayed payment, and the consequences of non-payment, all keeping rates in the SOW.
5. Draft the risk-allocation core. Representations and warranties, limitation of liability, indemnity, IP ownership and licence, confidentiality, and data protection. This is where most of the negotiation happens.
6. Draft term and termination. Term, renewal mechanism, termination for cause, termination for convenience, suspension, and the survival clause (which terms outlive the contract).
7. Draft the dispute-resolution and governing-law clauses. Negotiation, mediation, arbitration (seat, venue, rules, number of arbitrators, language), governing law, and jurisdiction for any court support.
8. Draft the boilerplate. Assignment, subcontracting, notices, force majeure, severability, entire agreement, amendment, waiver, relationship of the parties, and counterparts/e-signature.
9. Add the precedence, survival, and execution blocks. Confirm the hierarchy of documents, list surviving clauses, and set up the signature and stamping mechanics.
10. Review against the checklist and stamp it correctly. Run the draft against the drafting checklist near the end of this guide, then handle stamp duty and execution.

Notice what’s not in step one: opening a template. Templates are fine as a starting skeleton, but a template you haven’t pressure-tested against these steps is how the Bengaluru vendor from the opening ended up with no liability cap.

The clause-by-clause anatomy of an MSA

This is the core of the document. Each clause below carries a specific legal function, and for the ones that matter most, Indian statute and case law tell you how far you can push.

Definitions and interpretation. Boring, and the most leveraged clause in the contract. Every operative provision later refers back to these terms. If “Confidential Information” is defined narrowly, your confidentiality clause protects less than you think. If “Deliverables” doesn’t capture interim work product, your IP assignment has a gap. Define terms precisely, and add an interpretation sub-clause (headings don’t affect meaning, singular includes plural, “including” means “including without limitation”).

Scope of services and the SOW mechanism. State that the MSA itself creates no obligation to buy or sell anything; obligations arise only when an SOW is signed. Spell out what a valid SOW must contain and how it incorporates the MSA. This is also where the order-of-precedence clause lives. A practical drafting move: attach a blank SOW template as a schedule, so the delivery teams can’t freelance the format.

Term, renewal, and termination. Set the initial term, then choose a renewal mechanism: auto-renewal (rolls over unless someone opts out) or express renewal (ends unless renewed). Auto-renewal favours continuity; express renewal favours control. For termination, separate the two grounds clearly. Termination for cause needs a defined “material breach” and usually a cure period (commonly 30 days). Termination for convenience needs a notice period and a clean exit: what happens to in-flight SOWs, who pays for work done, and how confidential material and data are returned or destroyed.

Fees, invoicing, and payment. Keep rates in the SOW; keep mechanics here. Set the invoice cycle, the payment window, the currency, and who bears taxes. Build in interest on late payment, and if your counterparty is a registered micro or small enterprise, remember the statutory overlay: the Micro, Small and Medium Enterprises Development Act, 2006 caps the payment period (the appointed-day rule under [STATUTE:msmed-2006#section-15], generally 45 days where there’s an agreement) and attaches compound interest at three times the RBI’s notified rate for delay. There’s a tax sting too: under [STATUTE:incometax-1961#section-43B] of the Income-tax Act, 1961 (the Section 43B(h) inserted by the Finance Act, 2023), a buyer can’t claim the deduction for amounts owed to a micro or small enterprise until they’re actually paid within the MSMED timeline. Drafting a generous payment window into your MSA can quietly cost the paying party a tax deduction.

Intellectual property. State who owns what, expressly and in writing, because ownership of created work doesn’t pass by default. Distinguish Background IP (what each side brings in) from Foreground IP (what’s created under the SOW). The market-standard split: Foreground IP in the deliverables assigns to the customer on full payment; the vendor retains its Background IP and grants the customer a licence to use it as embedded in the deliverable. Tie the assignment trigger to payment, so the customer doesn’t own the code before the invoice clears.

Limitation of liability and indemnity: the two clauses that decide the lawsuit

If you draft everything else perfectly and fumble these two, the contract fails at the only moment it matters. So slow down here.

Limitation of liability. This clause caps how much one party can recover from the other, and it usually does two things: sets a monetary ceiling (commonly the fees paid under the relevant SOW in the preceding 12 months) and excludes certain heads of loss entirely (indirect, consequential, loss of profit, loss of data). Under Indian law, a genuine pre-estimate of damages or an agreed cap is enforceable, but you can’t simply name a number and assume the court will hand it over. [STATUTE:contract-1872#section-74] of the Indian Contract Act treats a named sum as a ceiling, not an automatic entitlement: the claimant still has to show that loss was actually suffered.

How strict is that proof requirement? This is genuinely unsettled, and you should know it. The Supreme Court in [CASE:ongc-saw-pipes] took a more relaxed view (where precise proof of loss is difficult, the named sum can guide reasonable compensation), while the later ruling in [CASE:kailash-nath-dda] reaffirmed that compensation under Section 74 requires legal injury and that no damages flow where no loss is shown. The older authority in [CASE:fateh-chand-balkishan] established the foundational principle that the section caps but doesn’t guarantee. The practical drafting takeaway: don’t rely on the cap alone to do your work. Pair it with clear exclusions of loss types, and keep the cap commercially reasonable, because an unconscionably low cap can itself be challenged.

A drafting nuance most templates ignore: carve-outs from the cap. Customers routinely insist that certain breaches sit outside the liability cap entirely (breach of confidentiality, IP infringement, the indemnity obligations, and liability that can’t be limited by law, such as fraud or wilful misconduct). A vendor should resist an open-ended carve-out list, because every item you pull out of the cap is uncapped exposure. Negotiate the carve-outs item by item, and where you concede one, consider a separate, higher super-cap rather than unlimited liability.

Indemnity. An indemnity is a promise to make good a specified loss, usually a third-party claim. It’s governed by [STATUTE:contract-1872#section-124] and Section 125 of the Indian Contract Act, and here’s a trap: the Indian statutory definition is narrower than the common-law concept, covering loss caused by the promisor’s conduct or another person’s. Indian courts have extended it in practice; the Bombay High Court in [CASE:gajanan-moreshwar] held that an indemnity holder can enforce the indemnity before actually paying out, so long as the liability is absolute. Draft the indemnity to specify exactly what’s covered (third-party IP claims, data breaches caused by the vendor, personal injury), the procedure (notice, conduct of the claim, cooperation), and whether it’s capped or sits outside the liability cap. An indemnity with no procedure clause is an invitation to a satellite dispute about who controls the defence.

The interaction between these two clauses is where deals are won and lost. A limitation clause says “my maximum exposure is X.” An indemnity says “but for these specific claims, I’ll cover you fully.” If the indemnity isn’t expressly carved out of (or into) the liability cap, you’ve got two clauses pulling in opposite directions, and a court will have to reconcile them. Reconcile them yourself, in the drafting.

Dispute resolution, governing law, and the arbitration clause

Most MSAs route disputes to arbitration, and most arbitration clauses are drafted on autopilot. Don’t. A vague arbitration clause is worse than none, because it sends the parties to court to argue about how to arbitrate.

Start with governing law and jurisdiction. For two Indian parties, name Indian law as the governing law and a specific city’s courts for any supervisory jurisdiction. The Supreme Court in [CASE:swastik-gases-ioc] held that naming one court’s jurisdiction (with words like “only,” “alone,” or “exclusive”) ousts others, so be explicit about exclusivity.

Then the arbitration clause itself. A clean clause under the Arbitration and Conciliation Act, 1996 fixes five things: the seat of arbitration (which determines the supervisory court and the curial law), the venue (where hearings physically happen, which can differ from the seat), the number of arbitrators (one is cheaper and faster; three is common for high-value deals), the rules (institutional rules or ad hoc), and the language. The seat-versus-venue distinction isn’t pedantry: the Supreme Court in [CASE:bgs-soma-nhpc] and earlier in [CASE:indus-mobile-datawind] held that the named seat carries exclusive supervisory jurisdiction, so getting it wrong relocates your entire dispute. Name the seat expressly.

Two India-specific points worth building in. First, can two Indian parties choose a foreign seat? Yes: the Supreme Court settled this in [CASE:pasl-wind-ge-power], holding that two Indian parties can validly arbitrate at a foreign seat, though that’s a deliberate structuring choice with enforcement consequences, not a default. Second, stamping. An arbitration agreement in an unstamped or insufficiently stamped contract used to be a fatal defect, but the seven-judge bench in [CASE:interplay-stamping] (December 2023) held that an unstamped agreement is inadmissible but curable, and the arbitration clause remains enforceable. So a stamping defect won’t kill your arbitration clause, but it will still cause delay and cost, which is a reason to stamp correctly the first time (more on that below).

Before arbitration, consider a tiered dispute-resolution clause: good-faith negotiation between senior executives, then mediation, then arbitration. There’s a statutory nudge here for commercial disputes that end up in court: [STATUTE:commercialcourts-2015#section-12A] of the Commercial Courts Act, 2015 makes pre-institution mediation mandatory for suits that don’t contemplate urgent interim relief, a requirement the Supreme Court held to be mandatory in [CASE:patil-automation]. A well-drafted escalation clause keeps most disputes out of court entirely.

Executing the MSA: stamping, e-signature, and registration

A perfectly drafted MSA that’s executed wrong is a perfectly drafted problem. Three execution issues trip people up.

Stamp duty. An MSA is a chargeable instrument, and stamp duty is a state subject, so the rate depends on where the agreement is executed and which state’s stamp law applies. There’s no single national figure, and anyone who quotes you “the stamp duty on an MSA in India” without naming a state is guessing. Under [STATUTE:stamp-1899#section-35] of the Indian Stamp Act, 1899 (and the corresponding state Acts), an inadequately stamped instrument is inadmissible in evidence, though the defect is curable by paying the duty and penalty. Check the applicable state schedule, stamp the agreement before or at execution, and if it’s executed in one state but used in another, watch for the differential-duty rule. Don’t treat stamping as an afterthought.

E-signature. Indian law recognises electronic signatures under [STATUTE:it-2000#section-5] of the Information Technology Act, 2000, so an MSA can be validly e-signed. But the First Schedule to the Act excludes certain documents from e-signature (negotiable instruments other than cheques, powers of attorney, trusts, wills, and any contract for the sale or conveyance of immovable property). A standard services MSA isn’t on that exclusion list, so e-signing is fine. If your MSA bundles in anything touching immovable property, though, that part may need wet-ink execution. Match the signature method to the content.

Registration. A plain services MSA generally doesn’t require compulsory registration under the Registration Act, 1908, because it doesn’t create or transfer an interest in immovable property. If your MSA includes a clause that does (say, a licence of premises, or an assignment of immovable property), that component can attract compulsory registration, and an unregistered instrument affecting immovable property has limited evidentiary use. For the overwhelming majority of vendor-services MSAs, registration isn’t required, but check the document for any property-touching clause before you assume so.

Common drafting mistakes that come back to bite

Some errors show up again and again. Here’s what to watch for.

No order-of-precedence clause. We’ve covered why: when the MSA and an SOW conflict and nothing says which controls, you’ve drafted ambiguity into the foundation. This is the single most common structural defect in real-world MSAs.

A liability cap with no exclusion of indirect losses. The cap limits the amount; the exclusion limits the types of loss. You need both. A cap alone still leaves you exposed to large consequential-loss claims up to the ceiling.

An indemnity floating free of the liability cap. If the indemnity isn’t expressly inside or outside the cap, the two clauses contradict each other, and the contradiction surfaces at the worst possible moment, in litigation.

IP assignment with no payment trigger. Assigning deliverables “on creation” means the customer owns the work before paying for it. Tie assignment to payment, or you’ve handed away leverage.

A post-termination non-compete drafted as if Section 27 doesn’t exist. It does, and a blanket post-term restraint is usually void. Drafting one anyway gives the client false comfort and you false confidence.

Boilerplate copied from an unrelated template. The “entire agreement,” “notices,” and “governing law” clauses are where copy-paste errors hide (the wrong city, the wrong governing law, a notice address that doesn’t exist). Read every word of the boilerplate as if it were the operative clause, because one day it will be.

And the quiet one: forgetting that the SOW inherits everything. Every weakness in the MSA replicates across every SOW signed under it. A single bad clause isn’t one mistake. It’s one mistake multiplied by the number of projects.

A practical MSA drafting checklist

Run every draft against this before it goes out. If you can’t tick a line, you have a gap.

• Parties correctly identified, with affiliate/ordering-entity mechanism if needed.
• MSA-versus-SOW split defined, with a blank SOW template attached as a schedule.
• Order-of-precedence clause present, with explicit carve-outs.
• Definitions cover Services, Deliverables, Background IP, Foreground IP, Confidential Information, Affiliate.
• Payment mechanics in the MSA, rates in the SOW, MSME and Section 43B(h) overlay considered.
• IP ownership split (Background vs Foreground), assignment tied to payment.
• Confidentiality clause with duration and carve-outs; data-protection clause forward-compatible with the DPDP regime.
• Limitation of liability: monetary cap plus exclusion of indirect/consequential loss, with negotiated carve-outs.
• Indemnity: scope, procedure, and its relationship to the liability cap all stated.
• Force majeure as an express clause, with notice and prolonged-event termination right.
• Restraint clauses (non-compete/non-solicit) drafted within Section 27 limits.
• Term, renewal, termination (cause and convenience), suspension, and survival clauses present.
• Dispute resolution: tiered escalation, arbitration seat and venue named, governing law and exclusive jurisdiction specified.
• Execution: stamp duty checked against the applicable state, e-signature suitability confirmed, registration need assessed.
• Boilerplate (assignment, notices, severability, entire agreement, amendment, independent-contractor status) reviewed line by line.

That checklist is the difference between a document that sits in a drawer and a document that holds up when a USD 2 million claim lands.

Frequently asked questions

What is a master service agreement (MSA)?
A master service agreement is a contract that sets the standing legal and commercial terms of an ongoing relationship between a service provider and a client, so that individual projects can be ordered through short statements of work without renegotiating the core terms each time. It typically governs liability, IP, confidentiality, payment, termination, and dispute resolution.

What’s the difference between an MSA and an SOW?
The MSA carries the slow-moving legal framework (liability, IP, confidentiality, dispute resolution); the SOW carries the project-specific commercial detail (scope, deliverables, timelines, fees). One MSA usually sits above many SOWs, and each SOW incorporates the MSA by reference.

Is a master service agreement legally binding in India?
Yes. An MSA is an ordinary contract and is binding once it satisfies the essentials in Section 10 of the Indian Contract Act, 1872 (free consent, lawful consideration, competent parties, lawful object). There’s no separate MSA statute; it’s enforced like any other commercial contract.

Does an MSA need to be registered or notarised in India?
A standard services MSA generally doesn’t require compulsory registration under the Registration Act, 1908, because it doesn’t transfer an interest in immovable property. Notarisation isn’t legally required either, though parties sometimes notarise for evidentiary comfort. If the MSA includes a property-related clause, that component may attract registration.

How much stamp duty applies to an MSA?
There’s no single national rate. Stamp duty on an MSA is governed by the stamp law of the state where it’s executed, so the amount varies by state. An insufficiently stamped agreement is inadmissible in evidence under Section 35 of the Indian Stamp Act, 1899 (or the state equivalent), but the defect is curable by paying the duty and penalty.

Can an MSA be signed electronically in India?
Yes. Electronic signatures are valid under Section 5 of the Information Technology Act, 2000. A services MSA isn’t in the First Schedule’s list of excluded documents, so e-signing is enforceable. Documents involving immovable property or negotiable instruments (other than cheques) are excluded and may need wet-ink signatures.

Who owns the intellectual property created under an MSA?
Whoever the contract says, expressly. Ownership of created work doesn’t pass automatically just because the client paid. The market-standard split assigns deliverables (Foreground IP) to the client on full payment, while the vendor keeps its pre-existing tools (Background IP) and licenses them as needed for the deliverable to function.

Can a non-compete clause in an MSA be enforced in India?
A post-termination non-compete is generally void under Section 27 of the Indian Contract Act, 1872. An in-term exclusivity (no working for a direct competitor during the engagement) is usually enforceable. Non-solicitation of employees is unsettled and varies across High Courts, so it should be drafted narrowly.

How should the limitation of liability clause be drafted?
Combine a monetary cap (commonly the fees paid in the preceding 12 months) with an exclusion of indirect and consequential losses, then negotiate specific carve-outs (confidentiality, IP infringement, indemnity, fraud). Under Section 74 of the Indian Contract Act, a capped sum is a ceiling, not an automatic entitlement, so loss still has to be shown.

What happens if the MSA and the SOW contradict each other?
Whichever the order-of-precedence clause says controls. If the MSA has no precedence clause, the conflict is resolved by interpreting the documents together to find the parties’ intention, which creates uncertainty. Always include an explicit hierarchy.

Can two Indian companies choose arbitration outside India in their MSA?
Yes. The Supreme Court held in PASL Wind Solutions v. GE Power that two Indian parties can validly choose a foreign seat of arbitration. It’s a deliberate structuring choice with enforcement implications, not something to drop in casually.

Do I need a lawyer to draft an MSA, or can I use a template?
A template is a reasonable skeleton, but the high-risk clauses (limitation of liability, indemnity, IP, precedence) are exactly the ones templates get wrong or leave generic. For any MSA with meaningful value or risk, have it reviewed by a lawyer, because the cost of review is trivial next to the cost of an uncapped liability claim.

References

Case Law

1. [CASE:bgs-soma-nhpc] – seat of arbitration carries exclusive supervisory jurisdiction.
2. [CASE:energy-watchdog-cerc] – express force majeure clause governs; cost rise is not frustration.
3. [CASE:fateh-chand-balkishan] – Section 74 caps damages, no automatic entitlement.
4. [CASE:gajanan-moreshwar] – indemnity enforceable before actual payment where liability is absolute.
5. [CASE:indus-mobile-datawind] – named seat confers exclusive jurisdiction.
6. [CASE:interplay-stamping] – unstamped agreement inadmissible but curable; arbitration clause survives (7-judge bench).
7. [CASE:kailash-nath-dda] – compensation under Section 74 requires proof of legal injury.
8. [CASE:niranjan-golikari] – in-term exclusivity is a valid restraint.
9. [CASE:ongc-saw-pipes] – Section 74 reasonable compensation where precise proof is difficult.
10. [CASE:patil-automation] – pre-institution mediation under Section 12A is mandatory.
11. [CASE:pasl-wind-ge-power] – two Indian parties may choose a foreign seat.
12. [CASE:percept-zaheer-khan] – post-term restraint void under Section 27.
13. [CASE:swastik-gases-ioc] – exclusive-jurisdiction clause ousts other courts.

Statutes

1. [STATUTE:contract-1872] Indian Contract Act, 1872 – sections cited: 10, 27, 32, 56, 73, 74, 124, 125.
2. [STATUTE:stamp-1899] Indian Stamp Act, 1899 – section cited: 35.
3. [STATUTE:registration-1908] Registration Act, 1908.
4. [STATUTE:it-2000] Information Technology Act, 2000 – section cited: 5; First Schedule.
5. [STATUTE:msmed-2006] Micro, Small and Medium Enterprises Development Act, 2006 – sections cited: 15, 16.
6. [STATUTE:commercialcourts-2015] Commercial Courts Act, 2015 – section cited: 12A.
7. [STATUTE:incometax-1961] Income-tax Act, 1961 – section cited: 43B(h).
8. [STATUTE:arbitration-1996] Arbitration and Conciliation Act, 1996 – sections cited: 7, 11, 34, 37.
9. [STATUTE:dpdp-2023] Digital Personal Data Protection Act, 2023, and DPDP Rules, 2025.
10. [STATUTE:copyright-1957] Copyright Act, 1957.

This article is for informational and educational purposes only and does not constitute legal advice. Drafting a master service agreement involves commercial and legal judgment specific to each transaction, and the law (including stamp duty rates and the phased commencement of the Digital Personal Data Protection Act, 2023) varies by state and changes over time. Consult a qualified advocate before finalising or relying on any agreement.