Master Service Agreement (India)

Introduction

Master Service Agreements decouple commercial terms (in Statements of Work) from legal architecture (in the MSA itself). Done right, the MSA is signed once and every subsequent engagement runs on an SOW that takes a day to negotiate. Done wrong, every project re-litigates limitation, IP and termination — friction that kills delivery and trust.

When to Use This Prompt

• Recurring B2B services across multiple projects or SOWs.
• Customer or provider requires standardisation across business units.
• Engagements involve transfer of intellectual property or personal data.
• Long-term relationship with billing and renewal cycles.

Statutory & Case-Law Backdrop

Indian Contract Act, 1872 — formation, free consent, consideration, limitation of liability (Section 73-74). Sale of Goods Act / Services — implied warranties. Information Technology Act, 2000 — Section 43A on sensitive personal data. Digital Personal Data Protection Act, 2023 — consent, fiduciary obligations, cross-border transfer. Arbitration and Conciliation Act, 1996 — institutional vs ad-hoc arbitration. Section 9 and 17 for interim relief.

The Prompt

Paste into ChatGPT, Claude or Gemini. Replace every bracketed placeholder with your specific facts before generating.

Draft a Master Service Agreement between [SERVICE PROVIDER] and [CUSTOMER] governed by Indian law, structured to support multiple Statements of Work (SOWs).

Inputs:
- Nature of services: [IT / CONSULTING / MARKETING / OTHER]
- Pricing model: [TIME & MATERIAL / FIXED-PRICE / MILESTONE / RETAINER]
- Term and termination notice: [PERIOD]
- Liability cap: [FEES PAID IN PRECEDING 12 MONTHS / OTHER]
- Indemnity scope: [IP, CONFIDENTIALITY, DATA]
- Seat of arbitration and governing law: [CITY, INDIA]

Structure: parties, recitals, definitions, services and SOW framework, payment and invoicing, taxes and TDS, IP (background, foreground, deliverables), confidentiality, data protection (DPDP Act 2023), warranties, indemnity, limitation of liability, term and termination, force majeure, dispute resolution (arbitration under Arbitration and Conciliation Act, 1996), governing law, miscellaneous. Provide an SOW template as Schedule 1.

Anatomy of the Draft

Why the prompt is built the way it is — section by section.

Common Mistakes to Avoid

• ×MSA-SOW conflicts left unresolved by absence of an order-of-precedence clause.
• ×Confusing 'seat' and 'venue' of arbitration — BALCO (2012) and BGS SGS Soma (2019) make this consequential.
• ×Indemnities without scope, cap, or carve-out — practically unenforceable.
• ×Ignoring DPDP Act obligations where personal data flows are involved.

Frequently Asked Questions

Final Thoughts

An MSA is judged by its ability to handle the bad day. Build the liability cap, the IP grant and the dispute clause for the lawsuit you hope never to file.