Your SOW’s exclusivity clause is probably void — and your MSA didn’t save you
The MSA-and-SOW structure only protects you if the two documents are wired together correctly. A post-term exclusivity clause in an SOW can be void under Section 27 of the Indian Contract Act, and a missing order-of-precedence clause can let a campaign SOW quietly override your master IP protections. Here is how the hierarchy is supposed to work.
By Sumit Kumar
An enterprise brand signs a multi-year Master Service Agreement (MSA) with a talent firm. For the festive season it issues a Statement of Work (SOW) that includes an exclusivity clause: the creator “cannot promote any competitor for 12 months.” Two months after the SOW expires, the creator — needing income — signs with a competitor. The brand sues for an injunction.
The court declines. The 12-month post-term exclusivity is an unreasonable restraint of trade, void under Section 27 of the Indian Contract Act, 1872. And because the MSA contained no “order of precedence” clause tying the documents together, there was no master-level protection to fall back on. The brand loses the injunction, the creator is gone to a competitor in peak season, and the payment is now disputed.
The MSA-and-SOW structure is the right structure. It just only works if the two documents are wired together correctly — which copy-paste Word templates almost never are. This post explains the hierarchy and the two clauses that make it hold.
What the MSA-and-SOW hierarchy is for
The standard commercial pattern is a two-tier structure:
- The MSA sets the foundational, durable terms: confidentiality, IP ownership, dispute resolution, indemnities, governing law. You negotiate it once.
- The SOW sets the tactical, per-project terms: this campaign's deliverables, timeline, fee, and any campaign-specific conditions. You issue many SOWs under one MSA.
The point of the split is leverage and consistency: you fight the hard legal battles once at the MSA level, then move fast on each campaign without re-litigating IP and confidentiality every time. That only holds if the SOW genuinely inherits the MSA — which is where most setups quietly break.
Two places Indian contract law bites
Two statutory realities shape what these documents can and can't do.
Section 27 — restraint of trade. The Indian Contract Act voids agreements that restrain someone from exercising a lawful profession or trade. Post-term exclusivity — preventing a creator from working with competitors after the engagement ends — is the classic trip-wire. Reasonable in-term exclusivity (during the campaign) is generally fine; a broad post-term lock-out is generally void. A brand relying on a 12-month post-term clause is relying on something a court will strike.
Specific Relief Act, 1963 — and its personal-volition limit. The 2018 amendment made “specific performance” (forcing a party to actually perform, rather than just pay damages) the rule rather than the exception. But Section 14 still bars specific enforcement of contracts that depend on the “personal qualifications or volition of the parties.” A creator contract that promises a particular creative style is exactly this kind of personal-volition obligation — so you cannot force a creator to produce the content; you're left with damages. A contract written as if you can compel performance is built on a remedy you don't have.
The two clauses that make the hierarchy hold
1. An order-of-precedence clause. This is the clause whose absence broke the opening scenario. It states explicitly which document wins when the MSA and an SOW conflict — typically the MSA governs on legal/IP/confidentiality terms, the SOW governs on commercial/operational specifics. Without it, a hastily drafted SOW can accidentally override a hard-won MSA protection — for example, an SOW that re-defines IP assignment in passing, undercutting the master IP clause you negotiated for months.
2. Terms drafted to what's actually enforceable. In-term exclusivity, scoped and reasonable — not blanket post-term lock-outs that Section 27 voids. Remedies framed around damages and defined liquidated amounts for non-delivery — not specific-performance language that Section 14 won't grant for a creative obligation. The contract should promise what a court will actually back.
Why the Word-template approach fails
The root cause is that SOWs get produced by copying last quarter's SOW and changing the names, fees, and dates. Each copy is an opportunity to (a) carry forward an unenforceable clause that was never tested, and (b) introduce a term that silently conflicts with the MSA, because no one is checking the SOW against the master document. Every SOW feels like a fresh negotiation precisely because the relationship between master terms and campaign terms was never standardised.
The fix is a contract-lifecycle approach that treats the SOW as a child of the MSA — inheriting its protections, validated against it, with an order-of-precedence checker that flags when an SOW term would undermine a master clause.
In-term vs post-term is the line that decides if exclusivity survives. Asking a creator not to promote a direct competitor during a campaign is generally a reasonable, enforceable restriction. Asking them not to do so for 12 months after the campaign ends reaches past the engagement into their livelihood and runs into Section 27. If exclusivity matters to the brand, the durable version is a reasonable in-term clause plus a defined first-right or notice window — not a long post-term lock-out that reads strong and enforces to nothing.
What SutraOS does about this
A two-tier contract structure only protects you if the documents actually hold together — which is exactly what breaks when contracts live in scattered Word files. SutraOS exists to keep the master terms and the per-campaign terms working as one, so each campaign agreement inherits the protections you negotiated once instead of quietly undercutting them — and an exclusivity clause that reads strong doesn't enforce to nothing when it counts.
Contract law, and what courts will actually back, keeps evolving. Keeping the platform's agreements current with it — so you're never leaning on last year's template — is our job. SutraOS exists so the legal scaffolding around a creator deal is something you can trust by default, not audit line by line.
If you're a brand or agency operator who has watched a SOW exclusivity clause evaporate in court — or feared one would — SutraOS is built around exactly this kind of structural contract risk, and it's live today. Set up your workspace whenever you're ready, or book a walkthrough through the design-partner program.
Ready to make this someone else’s problem?
SutraOS is live. You can sign up and set up your account today — self-serve, no waitlist — and run your first compliant campaign. Want it hands-on? The design-partner program adds white-glove onboarding for your first campaigns and direct input on the roadmap.
Share or discuss this post: