Amendment and Variation Clauses in India: Why 'In Writing Only' Matters

A variation clause, also called an amendment clause, controls how a signed contract can be changed later. Nearly every commercial contract in India carries some version of the same line: "This Agreement may only be amended by an instrument in writing signed by both parties." Lawyers call this a No Oral Modification clause, or NOM clause. It reads like a locked door. The question that actually matters is different: does an NOM clause stop a later oral or conduct-based change from binding the parties in India? The honest answer is no, not automatically, though it raises the bar for proving a change happened at all. Section 62 of the Indian Contract Act, 1872 lets parties alter a contract by agreement, written or not, unless some other law specifically requires that contract to be in writing. This guide (published by Adira, which builds contract management software, so there is a commercial angle here, but the explanation stands on its own) covers what Section 62 says, what the evidence law does with it, a 2025 Supreme Court ruling that pushed back the other way, and a change-control process that keeps amendments enforceable.

Plain meaning

A variation or amendment clause has two jobs. It confirms the contract can be changed after signing, barely in question since Indian law already permits this by default. And it fixes one method, usually "in writing, signed by an authorised representative of each party," as the only one that counts.

What the clause is really trying to stop is accidental drift. A verbal promise from a sales rep, an email that reads like agreement, a changed practice nobody signed off on, none of that should silently rewrite the deal. Whether it succeeds depends on Indian contract law and evidence law working together, not just on the words printed in the clause.

Who it protects and what triggers it

An amendment clause usually protects the party with more to lose from informal drift, typically the larger or more process-driven counterparty. In a SaaS contract, it protects the vendor from a support agent's email being read as a discount promise. In an EPC contract, it protects the owner from a site engineer's verbal go-ahead being read as an approved scope change with a price tag attached.

It is triggered the moment anyone, including an employee with no authority to bind the company, proposes or acts on a change outside the signed channel: a price discussed over WhatsApp, an email saying "sure, we can push the deadline," or months of invoices issued on a changed basis nobody signed off on.

What to look for

• Does the clause require both writing and signature by a named or ranked signatory, or does it just say "in writing"? An email chain is writing, but not automatically a signed instrument.
• Is there a companion "no waiver" clause, stating that failing to enforce a right once does not waive it for the future? NOM and no-waiver usually travel together, and the case below shows why that pairing matters.
• Is amendment authority reserved to a specific role, such as a named signatory, rather than whoever is on the call that week?
• Does a separate change-order process exist for Statements of Work or Purchase Orders, or does every change run through the slow master-agreement route?
• Does the clause carve out routine items, such as notice-address updates, from the substantive signature bar?

The Indian position: Section 62 and the evidence rule that follows it

Section 62 of the Indian Contract Act, 1872 is titled "Effect of novation, rescission, and alteration of contract." It says:

"If the parties to a contract agree to substitute a new contract for it, or to rescind or alter it, the original contract need not be performed." Source: Section 62, Indian Contract Act, 1872

This is why an NOM clause cannot be airtight in the way it is sometimes assumed to be. Parties keep the basic freedom to alter their bargain by mutual agreement, and that freedom comes from ordinary contract formation, not from anything the clause grants or withholds. Section 62 simply confirms that once altered, the old terms need not be performed, and it says nothing about the alteration itself needing to be in writing. So a later oral agreement, or conduct showing both sides treated the deal as changed, is legally capable of amending the contract, NOM clause or not.

The real limit is evidence, not enforceability. Section 95 of the Bharatiya Sakshya Adhiniyam, 2023, in force since 1 July 2024 and carrying forward Section 92 of the old Evidence Act, generally stops oral evidence from contradicting or varying a written contract's terms. But it carries an explicit exception here:

"The existence of any distinct subsequent oral agreement to rescind or modify any such contract, grant or disposition of property, may be proved, except in cases in which such contract, grant or disposition of property is by law required to be in writing, or has been registered according to the law in force for the time being as to the registration of documents." Source: Section 95, Bharatiya Sakshya Adhiniyam, 2023

Read the two together. Section 62 lets the parties actually alter the deal orally or by conduct. Section 95 lets a party prove in court that this happened, unless the law itself, not just the parties' clause, requires that contract to be in writing, such as a sale of immovable property needing a registered deed under the Registration Act, 1908. An ordinary MSA, SaaS agreement, or supply contract carries no such requirement, so both routes stay open. An NOM clause becomes a serious evidentiary hurdle, not an absolute bar.

A named Indian case: SEPCO v GMR Kamalanga

In SEPCO Electric Power Construction Corporation v GMR Kamalanga Energy Ltd (Supreme Court of India, 2025 INSC 1171, decided 26 September 2025), the EPC contracts for a thermal power project in Odisha carried a strict "No Oral Modification / No Waiver" regime alongside sequenced, notice-driven conditions for testing and payment milestones. The arbitral tribunal read the parties' later conduct as an implied waiver of a notice requirement and awarded SEPCO roughly Rs 995 crore.

The Supreme Court set the award aside, holding that the tribunal had effectively rewritten the contract by inferring a waiver the written NOM and no-waiver clauses were designed to prevent, and that this went beyond the tribunal's mandate under Section 28(3) of the Arbitration and Conciliation Act, 1996, which requires a tribunal to decide according to the contract's terms.

Source: SEPCO Electric Power Construction Corporation v GMR Kamalanga Energy Ltd, 2025 INSC 1171 (Supreme Court of India)

Why this matters: SEPCO does not overturn Section 62, parties can still agree to vary a contract. It shows that in high-value contracts with an explicit no-waiver clause, Indian courts will not let a decision-maker infer variation from conduct alone. Pair an NOM clause with a no-waiver clause naming the rights it protects, and keep your evidentiary story as clean as the clause demands.

Change control for SOWs

Master service agreements almost always sit above one or more Statements of Work or Purchase Orders that carry the real scope, price, and timeline. A variation clause that only covers "this Agreement" often leaves the SOW change process undefined, which is exactly where scope creep happens: a client's project lead emails "can we just add X," a vendor's delivery lead replies "sure," and six weeks later nobody agrees on the extra invoice.

A workable change-control process for SOWs fixes at least four things:

1. Who can request a change. Named roles, not "either party."
2. The form of the request. A written Change Request Form stating the change, its price impact, and its timeline impact.
3. A response deadline. For example, the receiving party must accept, reject, or counter within five business days, after which the request lapses. Silence should end the request, never count as acceptance.
4. How it is recorded. A signed, numbered Change Order, approved by an authorised signatory, that references the original SOW and states expressly that it amends that SOW, and only that SOW.

This keeps the fast conversation, what should we change, separate from the one that actually controls, what did we agree to change, and gives you a version history instead of a WhatsApp thread. Draft this Change Request Form and mark up your own variation clause for free in Weave before it goes to procurement.

Red flags

Normal	Red flag	Why it matters
Amendment requires a signed writing from a named, authorised signatory on each side	"Written notice" alone, no signature or authority requirement	An email from anyone at the company could arguably count as writing
A no-waiver clause sits alongside the NOM clause, naming which rights survive a one-off accommodation	No companion no-waiver clause	One accommodation, such as accepting a late delivery, risks being read as a permanent waiver, and the risk runs both ways, as SEPCO shows
Only a specified role can propose and approve amendments	A vendor reserves a unilateral right to amend, common in SaaS terms as "we may update these Terms at any time"	You agree today to terms the other side can change tomorrow without your signature
Change requests run through a defined SOW or Change Order process with stated deadlines	No defined SOW process; the amendment clause only covers the master agreement	Scope and price changes on the ground have no controlling document behind them
A documented Change Order is signed before work starts	Work begins on a verbal "go ahead" while the Change Order is still pending	You perform on a variation you may not be able to prove happened if there is a dispute
Each amendment is dated, numbered, and the current version is clearly identified	No version control; redlines float over email with no single source of truth	Nobody can say with confidence which version is "the contract" once a dispute starts
Routine notices, such as an address change, are carved out from the substantive threshold	Every change, however minor, is bundled under the same signature requirement	Admin updates get slowed down, which encourages people to skip the process altogether

Bad clause to better clause

Bad: "The Company may amend these Terms from time to time by posting the updated Terms on its website. Continued use of the Service after such posting constitutes acceptance of the amended Terms."

What is wrong: the amendment right sits with one party only; "continued use" as acceptance means silence binds the other side; there is no notice period, no requirement to flag what changed, and no right to object or exit first.

Better: "Either party may propose an amendment to these Terms by written notice to the other party's designated contract owner, describing the proposed change and its effective date. No amendment is effective unless signed by an authorised representative of each party, except that amendments the Company proposes to standard Terms applicable to all customers take effect if the Company gives Customer at least thirty (30) days' written notice before the effective date and Customer does not terminate under Clause [Termination] before that date. No failure or delay by either party in enforcing any right under this Agreement operates as a waiver of that right."

What changed: amendment is no longer unilateral by default; a notice-and-object window replaces silent "continued use"; a named contract owner replaces "posting on a website"; and a no-waiver sentence closes the exact gap SEPCO turned on.

How it interacts with related clauses

• Entire agreement clause. Says the written contract is the whole deal, superseding prior negotiations. It does not stop a future amendment, so read the two together so nobody argues it also blocks a Section 62 variation.
• Notices clause. The written form an NOM clause demands is only as reliable as the delivery rules in the notices clause. An email may or may not count as valid written notice, depending on how notices are defined there.
• Governing law and dispute resolution. Which law and forum apply changes how strictly a decision-maker reads your NOM clause, as SEPCO's Indian-seated arbitration shows.

US and global contrast

Under the US Uniform Commercial Code, Section 2-209(2), for goods contracts, an NOM clause is generally binding by statute:

"A signed agreement which excludes modification or rescission except by a signed writing cannot be otherwise modified or rescinded." Source: UCC Section 2-209, Cornell Legal Information Institute

Even there, Section 2-209(4) lets a failed written modification work instead as a waiver, so US goods law reaches a similar compromise from the opposite direction: strict on paper, flexible through waiver. England reached the same place through Rock Advertising Ltd v MWB Business Exchange Centres Ltd (2018), where the UK Supreme Court upheld an NOM clause against a purely oral variation. India has adopted neither rule outright. Section 62 keeps the freedom to vary orally open by default, and SEPCO shows the real contest here plays out over evidence and waiver, not over whether the clause is valid.

FAQ

Does a "no oral modification" clause make an oral change to a contract unenforceable in India? Not automatically. Section 62 of the Contract Act lets parties alter a contract by agreement, written or not, unless some other law requires that contract to be in writing. An NOM clause raises the evidentiary bar though; a party relying on an oral variation still has to prove one happened.

What is the difference between an amendment clause and a variation clause? None in substance. Both terms are used interchangeably for the provision governing how a contract may be changed after signing.

Can conduct alone amend a written contract in India, with no written document at all? In principle, yes, if both sides' conduct shows they agreed to the change. But SEPCO v GMR Kamalanga (2025) shows the Supreme Court will not let a decision-maker infer that agreement from conduct where the contract has an explicit no-waiver clause protecting the right in question.

Is a SaaS clause that says "we may update these Terms" enforceable in India? It can be, but a unilateral amendment right held by one party only, with no notice period and continued use standing in for consent, is a red flag rather than a settled rule. It depends on the exact wording, the notice given, and, for consumer-facing terms, on fairness rules under consumer protection law.

Does amending the master agreement automatically change a Statement of Work under it? Not usually, and it should not. Keep the variation clause and the SOW's change-order process separate, and state clearly which document a signed change modifies.

What proof do I need if I want to rely on an oral or email-based variation later? Contemporaneous, dated evidence that both sides intended the change: an email confirming the new term, invoices issued and paid on the new basis, or minutes of a meeting where both authorised signatories agreed. Section 95 of the Bharatiya Sakshya Adhiniyam lets you prove a subsequent oral modification, but a court still has to be persuaded, on the facts, that it happened.

This guide explains how variation and amendment clauses work under Indian law, and what the Contract Act, the evidence law, and one recent Supreme Court case actually say. It does not tell you whether a specific email, conversation, or course of conduct has legally varied your contract, that depends on the exact facts and wording, and is not legal advice. Talk to a lawyer before you rely on an unsigned change, or challenge one.