Last verified: June 2026
Picture the last contract you sent back with changes. Both sides traded versions, argued over a few clauses, accepted some edits, rejected others, and signed a clean copy that everyone felt good about. Then a dispute landed eighteen months later, and a clause your team had fought hard to keep turned out to be worth almost nothing.
That gap is the real reason you redline a commercial contract. Not to win edits for their own sake, but to make sure the words you negotiated actually survive contact with an Indian court. Most redlining guides on the internet were written for American or British paper. They teach you to track changes and tighten language. They don’t tell you that Indian law quietly rewrites parts of the contract after you sign it.
Two quick examples show what that means in practice.
A company spends a week negotiating a twenty-four-month non-compete on a departing consultant. Tight drafting, clear geography, real teeth. And under Section 27 of the Indian Contract Act, 1872, that post-termination non-compete is void Percept D’Mark (India) Pvt. Ltd. v. Zaheer Khan, (2006) 4 SCC 227. Every hour spent perfecting it bought nothing. The clause looks enforceable. It isn’t.
Or take liquidated damages. A buyer insists on a fat number, say Rs. 50 lakh, payable if the vendor misses a delivery milestone. Feels like a guaranteed recovery. But Section 74 of the Indian Contract Act treats that figure as a ceiling, not an entitlement. The buyer still has to show that loss actually occurred Kailash Nath Associates v. Delhi Development Authority, (2015) 4 SCC 136. Win the negotiation, and you can still walk into court holding a number you can’t fully collect.
Here’s the thing about redlining in India. It’s two jobs at once. You’re negotiating who carries which risk, and you’re checking that each clause is enforceable as written under Indian statute and Supreme Court precedent. Global redlining advice only teaches the first job. The lawyers who get paid well for contract review have learned the second, and it’s mostly invisible on the page: knowing which clauses to fight, which to accept, and which the law will override no matter what you draft.
This guide gives you all three pieces. The clause-by-clause markup, with sample before-and-after language you can adapt. The Indian enforceability rule sitting behind each clause. And the reply email you send when you return the redline, because how you transmit a markup decides whether the deal closes or stalls. By the end, you’ll redline a commercial contract the way a senior in-house counsel does: fast on the boilerplate, slow and deliberate on the five or six clauses that actually decide who pays when things go wrong.
Redlining a commercial contract means proposing edits to a draft using tracked changes and comments, so the other side can see exactly what you want added, deleted, or reworded before anyone signs. In India, a competent redline does two things at once: it allocates commercial risk and it checks each clause against Indian statute, because provisions like a post-termination non-compete or an inflated liquidated-damages figure can be unenforceable even when both parties agree to them.
The sections below walk through the full workflow, from set-up and clause triage to the markup itself and the email that carries it back to the counterparty. Use the table of contents to jump to the clause you’re stuck on.
How to redline a commercial contract in India: 7 steps
When you receive a draft and need to mark it up properly, work through these seven steps in order.
- Confirm whose paper it is and what leverage you have. The party that controls the first draft controls the defaults, so a redline on the counterparty’s template needs to be more aggressive than edits to your own.
- Turn on Track Changes and run a version compare before you start, so no silent edits slip past you in a draft labelled “clean.”
- Triage every clause into fight hard, accept, or the law decides anyway. Don’t spend leverage on a post-termination non-compete that Section 27 of the Indian Contract Act, 1872 makes void.
- Mark up the risk-allocation clauses first: the liability cap and its carve-outs, indemnity scope, force majeure, and termination remedies. These decide who pays when the deal breaks.
- Fix the India overlay: governing law and arbitration seat (not just venue), stamp duty, MSME payment timelines, and data-protection clauses under the Digital Personal Data Protection Act, 2023.
- Comment every change with a reason and a fallback, not just the edit, so the other side can negotiate against your position instead of guessing at it.
- Send the redline back with a cover email that summarises the material changes, flags your must-haves, and proposes the next step.
Each step is unpacked below, starting with what redlining actually involves and ending with the email templates.
What redlining actually is (and what it isn’t)
Most people use “redline,” “markup,” and “track changes” as if they mean the same thing. They overlap, but the distinctions matter once a negotiation gets serious and you’re juggling five versions of the same document. Get the vocabulary wrong in an email and you’ll confuse the very person you’re trying to negotiate with.
So what is a redline, precisely? It’s a version of the contract that shows your proposed changes visibly: insertions, deletions, and comments, usually in a contrasting colour, so the counterparty can see your edits rather than hunt for them.
Redline, markup, blackline, and clean copy: the vocabulary
A redline and a markup are effectively the same thing in Indian commercial practice: a draft carrying tracked, visible edits. A blackline is the comparison output between two specific versions, generated by software (Word’s Compare tool, or a dedicated comparison engine), and it’s how you catch what changed between, say, the counterparty’s version 3 and version 4. A clean copy has all changes accepted and the markup removed, which is what you circulate for signature once the negotiation closes.
Why does this distinction earn its keep? Because the most common trap in a contract negotiation is a “clean” version that quietly contains changes you never agreed to. If you only ever read clean copies, you’re trusting the other side’s word that nothing moved. Run a blackline against your last version instead, and the document tells you the truth.
Redlining versus reviewing versus negotiating
Reviewing is reading the contract for risk. Redlining is putting your edits on paper. Negotiating is the conversation that follows, where each side defends its changes. They’re sequential, and skipping the review step is where junior lawyers and founders get burned: you can’t redline what you haven’t understood.
In practice, redlining is the written layer of the negotiation. Every tracked change is a position, and every comment is an argument. A well-built contract negotiation checklist tells you what to look for; the redline is where you act on it. The better approach, in our view, is to treat the markup itself as your negotiation strategy made visible, because the counterparty reads your priorities straight off the page.
A question that comes up often: how many rounds of redlining are normal? For a standard commercial agreement, two to four exchanges is typical. More than five usually signals either a genuine commercial gap that email won’t close, or a drafting problem that a fifteen-minute call would solve faster than another round of tracked changes.
Before you touch the document: set-up and three questions
Plenty of reviewers open the file and start editing from clause 1. That’s backwards. The fastest, sharpest redlines come from thirty seconds of orientation before a single change goes in, because the answers reshape how hard you push on everything that follows.
What should you settle before editing? Three questions, and they take less time to answer than it takes to read this paragraph.
The three questions to ask before the first edit
First, whose paper is it, and what’s your leverage? If you’re redlining the counterparty’s standard template, the defaults are built for them, and you should expect to push harder and across more clauses. If it’s your draft coming back with their edits, you’re defending, and the job is to spot what they quietly moved.
Second, what’s your risk posture on this deal? Are you the party giving the indemnity or receiving it, paying or being paid, licensing in or licensing out? The answer flips which way you redline almost every risk clause. An indemnity that’s generous looks very different depending on which end of it you sit.
Third, what’s the deal value and governing law, and which Indian statutes bite because of them? A contract worth more than Rs. 3 lakh can land in a Commercial Court, which triggers mandatory pre-institution mediation under Section 12A of the Commercial Courts Act, 2015 Patil Automation Pvt. Ltd. v. Rakheja Engineers Pvt. Ltd., (2022) 10 SCC 1. If your counterparty is a registered micro or small enterprise, the payment-term rules change entirely. And if the document needs stamping in a particular state, that affects how and when you execute it.
Track Changes, Compare, and catching a hidden redline
The mechanics are quick, and they’re table stakes. In Microsoft Word, switch on Track Changes with Ctrl+Shift+E, and every edit you make is recorded for the other side to see. To expose what changed between two versions, use Review, then Compare, and Word produces a blackline showing every difference. This is how you catch the hidden redline: the edit slipped into a “final” draft that nobody mentioned in the covering email.
Fair warning: never trust a clean copy without comparing it to your own last version. We’ve seen a single deleted word (“not”) in an indemnity clause flip the entire risk allocation, sitting in a document the other side called “just cleaned up for signature.” Word’s Compare caught it in four seconds. A human skim would not have.
For PDFs, you can’t reliably track changes, so convert to Word or use a PDF redlining tool, then send edits in a format the other side can actually work with. Google Docs has its own Suggesting mode, which mirrors Track Changes and is fine for lighter deals, though most Indian corporate practice still runs on Word because that’s what counterparties expect.
Should you redline without a lawyer?
Founders ask this constantly, and the honest answer is: partly. You can triage the commercial terms yourself, the price, the timelines, the deliverables, the termination triggers, because you know your business better than any outside counsel. What you shouldn’t do alone is make the enforceability calls. Whether an indemnity is capped correctly, whether the arbitration seat is right, whether a DPDP clause does what it claims: those need legal eyes.
The mistake we see most often is a founder who redlines hard on price and walks straight past an uncapped indemnity that could swallow the company. Get the commercial points sorted yourself, then have a contracts lawyer pressure-test the risk clauses. That split keeps your legal spend sane without leaving you exposed on the clauses that matter.
Clause triage: fight, accept, or let the law decide
Not every clause deserves your attention, and treating them all as equal is how a redline drags into its sixth round. Senior reviewers sort clauses into three buckets before they negotiate anything, and the third bucket is the one almost everyone misses. Which clauses, then, actually warrant a fight?
The three buckets
The fight-hard bucket holds the clauses that decide who carries risk and money: limitation of liability, indemnity, payment terms, intellectual property ownership, and termination. These are where you spend your leverage, because a bad outcome here costs real money.
The accept-as-standard bucket holds the boilerplate that rarely repays the effort of negotiating: notices, severability, counterparts, entire-agreement clauses, and the like. Read them, sure. But don’t burn goodwill rewriting a notices clause when the indemnity is uncapped.
The third bucket is the one that separates Indian practice from the global guides: the law decides anyway. Some clauses are governed by statute regardless of what the parties write. A post-termination non-compete is void under Section 27 of the Indian Contract Act, 1872 Percept D’Mark. A liquidated-damages figure is only a ceiling under Section 74. Specific performance is now the default remedy under the Specific Relief Act, 1963 as amended in 2018, whatever your termination clause says. Spending negotiation capital on a clause the law overrides is wasted effort, and worse, it gives both sides false comfort.
How to decide accept, reject, or counter
For each clause in the fight-hard bucket, the call is simple in structure even when it’s hard in substance. Accept if the clause sits within your risk tolerance as written. Counter if it’s negotiable and you have a fallback you can live with. Reject outright only when the clause is a genuine walk-away.
The discipline that matters: every rejection needs a stated reason. “We can’t accept unlimited liability; we’re proposing a cap at fees paid in the preceding twelve months” moves the deal. A bare deletion with no comment just invites the other side to put it straight back in. As covered in iPleaders’ guide to the important clauses that form a perfect contract, the clauses worth your time are the ones that allocate risk, and those are exactly the ones where a reasoned counter beats a silent strike.
Clause-by-clause redline playbook: the before-and-after table
This is the heart of it. Below are the five risk-allocation clauses where a redline earns its fee, each with the Indian rule that governs it, a sample before-and-after markup, and the single most important move. One caveat before you use any of this: the sample language is illustrative, not a template to paste blind. Adapt it to your deal, your facts, and your risk posture, and have a lawyer confirm the final wording.
Why these five? Because in fifteen years of contract review, these are the clauses that show up again and again when a deal goes to dispute. Get them right and the rest is mostly housekeeping.
Limitation of liability and liquidated damages
Here’s the rule that surprises people. Indian law draws no distinction between “liquidated damages” and a “penalty.” Under Section 74 of the Indian Contract Act, 1872, where a sum is named in the contract, the court awards reasonable compensation not exceeding that amount, and the named figure works only as a ceiling Fateh Chand v. Balkishan Das, (1964) 1 SCR 515. You still have to show that loss occurred. There’s a genuine, unresolved tension in the case law about how much proof is needed, between the relaxed approach in Oil & Natural Gas Corporation Ltd. v. Saw Pipes Ltd., (2003) 5 SCC 705 and the stricter reading in Kailash Nath, so treat any single liquidated-damages number as an argument you’ll have to back with evidence, not a guaranteed cheque.
For the limitation-of-liability cap itself, the real battleground is the carve-outs. A mutual aggregate cap is standard; what you fight over is what sits outside it.
| Before (risky) | After (redlined) |
|---|---|
| “Neither party shall be liable for any damages arising under this Agreement.” | “Each party’s aggregate liability under this Agreement shall not exceed the total fees paid in the twelve (12) months preceding the claim, except that this cap shall not apply to liability for fraud, wilful misconduct, breach of confidentiality, infringement of intellectual property, or amounts payable under the indemnity at clause [X].” |
The one move: never accept a cap without scrutinising the carve-outs, and never let an indemnity sit uncapped above an otherwise mutual cap unless you intend it to. That asymmetry is where the money leaks.
Indemnity
Indemnity is the clause people copy without reading, and in India that’s risky because the statutory default is narrow. Sections 124 and 125 of the Indian Contract Act define indemnity in terms tied to the conduct of the promisor or another person, language narrower than the all-loss indemnity of common-law practice. Indian courts have read it more generously, allowing the indemnity-holder to recover before actually paying out the loss Gajanan Moreshwar Parelkar v. Moreshwar Madan Mantri, AIR 1942 Bom 302, but that gloss comes from a Bombay High Court decision, not a Supreme Court ruling, so you don’t want to rely on the default. You want the contract to say exactly what it means.
What does a tight indemnity specify? Four things: whether it covers third-party claims only or also direct losses between the parties, what triggers it (a demand, or established loss), who controls the defence and settlement, and whether it sits inside or outside the liability cap.
| Before (risky) | After (redlined) |
|---|---|
| “The Vendor shall indemnify the Customer against all claims, losses and damages.” | “The Vendor shall indemnify the Customer against third-party claims arising from the Vendor’s breach of this Agreement or infringement of third-party intellectual property, subject to the Customer promptly notifying the Vendor, granting sole control of the defence, and the Vendor’s total indemnity liability not exceeding [agreed cap].“ |
The one move: define first-party versus third-party scope explicitly, and decide deliberately whether the indemnity is capped. An open-ended “indemnify against all claims” is a blank cheque, and you’d be surprised how often it’s signed.
Force majeure
Force majeure got a lot of attention after 2020, and a lot of contracts still get it wrong. The Indian position is clear: where the contract has an express force majeure clause, the consequences flow from that clause read with Section 32 of the Indian Contract Act, and Section 56 (frustration) does not apply Energy Watchdog v. Central Electricity Regulatory Commission, (2017) 14 SCC 80. That cuts both ways. A precise clause protects you, but it also confines you to its exact wording, because once you’ve drafted an express clause, you can’t fall back on the general doctrine of frustration when your clause turns out to be too narrow.
And a critical point that Satyabrata Ghose v. Mugneeram Bangur & Co., (1954) SCR 310 settled long ago: a rise in cost or commercial hardship is not frustration. If you want price spikes or supply-chain disruption covered, the clause has to say so.
| Before (risky) | After (redlined) |
|---|---|
| “Neither party shall be liable for delays caused by acts of God or events beyond its control.” | “Neither party shall be liable for delay or failure caused by a Force Majeure Event, meaning [enumerated events: natural disaster, war, government action, epidemic, failure of utilities, and similar events beyond reasonable control], provided the affected party gives written notice within [X] days and uses reasonable efforts to mitigate. Either party may terminate if the Force Majeure Event continues beyond [60] days.“ |
The one move: enumerate the events, add a notice requirement and a duration-triggered termination right, and decide consciously whether price rises are in or out.
Termination and remedies
The Specific Relief (Amendment) Act, 2018 changed the remedies landscape in a way many drafters still haven’t absorbed. Specific performance used to be discretionary; now, under the amended Specific Relief Act, 1963, it’s the rule rather than the exception. The court’s default is to make the breaching party perform, not just pay damages. (The amendment’s prospective application has been litigated, so the exact reach is still settling, but the direction of travel is unmistakable.)
What does that mean for your redline? Termination and remedy clauses now carry more weight, because the counterparty may be able to compel performance you’d rather buy your way out of. So you draft the remedy menu explicitly.
| Before (risky) | After (redlined) |
|---|---|
| “Either party may terminate this Agreement on breach by the other.” | “Either party may terminate on the other’s material breach that remains uncured for thirty (30) days after written notice, or immediately on insolvency or change of control. Clauses [confidentiality, IP, indemnity, limitation of liability] survive termination. The parties agree that damages are an adequate remedy for [X], while breach of [confidentiality / IP] entitles the non-breaching party to injunctive relief.“ |
The one move: spell out the termination triggers, the cure period, what survives, and whether you want injunctive relief available for the clauses where damages won’t make you whole.
Confidentiality and non-compete
Back to Section 27, because this is where contracts routinely promise protection they can’t deliver. A non-compete that bites after termination or after employment ends is generally void in India as a restraint of trade Percept D’Mark. A negative covenant that operates during the term, like an exclusivity obligation while the contract is live, is valid if reasonable Niranjan Shankar Golikari v. Century Spinning & Manufacturing Co. Ltd., (1967) 2 SCR 378. The line is temporal: in-term restraints can stand, post-term ones usually fall.
So how do you actually protect the business? Not with a non-compete. With enforceable tools: a tightly drafted confidentiality obligation, a non-solicitation clause (though be aware that courts are split on how far non-solicits are enforceable, so don’t overstate it), and proper IP assignment.
| Before (risky) | After (redlined) |
|---|---|
| “The Consultant shall not engage in any competing business for twenty-four (24) months after termination.” | “The Consultant shall keep all Confidential Information confidential during and after the term, shall not solicit the Company’s clients or employees for twelve (12) months after termination, and assigns all intellectual property created under this Agreement to the Company.“ |
The one move: strike post-termination non-competes (they give false comfort), and rebuild the protection through confidentiality, non-solicitation, and IP assignment, which Indian courts will actually enforce.
The India overlay: dispute resolution, stamping, payments, and data
Even a perfectly negotiated contract can fail on the things the document doesn’t prompt you to check. These four areas are where Indian statute and procedure quietly decide outcomes, and they’re absent from almost every redlining guide written outside India. Think of this as the layer you add on top of the clause work. What does it cover?
Governing law, jurisdiction, and arbitration seat
Three choices have to line up, and they often don’t: governing law, the court that supervises disputes, and the arbitration seat. An exclusive-jurisdiction clause is valid only where more than one court would otherwise have jurisdiction, and the parties then pick one of them; you can’t confer jurisdiction on a court that has none Swastik Gases Pvt. Ltd. v. Indian Oil Corporation Ltd., (2013) 9 SCC 32. The words “only” or “exclusive” aren’t even mandatory: naming one forum can imply the exclusion of others.
For arbitration, the single most expensive mistake is confusing seat with venue. The seat fixes which courts have supervisory jurisdiction over the arbitration; the venue is just where hearings happen BGS SGS Soma JV v. NHPC Ltd., (2020) 4 SCC 234. A clause that names a “venue” without specifying a “seat” invites exactly the satellite litigation you drafted the clause to avoid Indus Mobile Distribution Pvt. Ltd. v. Datawind Innovations Pvt. Ltd., (2017) 7 SCC 678. (And yes, two Indian parties can validly choose a foreign seat, which PASL Wind Solutions Pvt. Ltd. v. GE Power Conversion India Pvt. Ltd., (2021) 7 SCC 1 confirmed, so cross-border-flavoured domestic deals have more freedom here than people assume.)
| Before (risky) | After (redlined) |
|---|---|
| “Disputes shall be referred to arbitration. The venue shall be Mumbai.” | “Disputes shall be finally resolved by arbitration under the [institutional] Rules, by a sole arbitrator [or three arbitrators], the seat of arbitration being Mumbai, the language being English, and the courts at Mumbai having exclusive supervisory jurisdiction.” |
The one move: write “seat,” name a single seat, use an odd number of arbitrators, and make sure governing law, seat, and jurisdiction tell a consistent story.
Stamping and electronic execution
Stamp duty is a state subject, so the rate and the article depend on which state’s law applies and what kind of document it is. Don’t take a number on faith: check the relevant state schedule. The consequence of under-stamping matters for your redline, because under Section 35 of the Indian Stamp Act, 1899, an insufficiently stamped instrument is inadmissible in evidence, though the defect is curable on paying the duty plus penalty. (Good news on arbitration: a seven-judge Supreme Court bench held in December 2023 that an unstamped arbitration agreement is still enforceable, so a stamping slip no longer kills the arbitration clause In Re: Interplay Between Arbitration Agreements under the Arbitration and Conciliation Act 1996 and the Indian Stamp Act 1899, (2024) 6 SCC 1.)
Electronic signatures need one quick check before you agree to them. Most commercial contracts can be e-signed under Section 5 of the Information Technology Act, 2000, using a digital signature certificate or Aadhaar-based e-Sign. But the Act’s First Schedule excludes certain documents, negotiable instruments (other than cheques), powers of attorney, trusts, wills, and contracts for the sale or conveyance of immovable property, and those still need wet ink.
The one move: confirm the document isn’t on the excluded list, specify the permitted e-signature method and a counterparts clause, and make sure the contract is adequately stamped before execution, not after a dispute starts.
Payment terms and the MSME trap
This one catches large buyers constantly. If your counterparty is a registered micro or small enterprise, the Micro, Small and Medium Enterprises Development Act, 2006 overrides your payment terms. Under Sections 15 and 16, payment must be made within the agreed date or, failing agreement, within fifteen days, and in no case beyond forty-five days. Any longer term is unenforceable to that extent, and interest accrues automatically at three times the RBI bank rate, compounded monthly.
There’s a tax sting too. Under Section 43B(h) of the Income-tax Act, 1961, a buyer is denied the income-tax deduction on amounts owed to a micro or small enterprise unless paid within that MSMED timeline. So a late payment isn’t just a contract problem; it’s a tax cost on your own books.
| Before (risky) | After (redlined) |
|---|---|
| “The Customer shall pay all invoices within ninety (90) days.” | “The Customer shall pay undisputed invoices within forty-five (45) days, or within fifteen (15) days where the Supplier is a registered micro or small enterprise under the MSMED Act, 2006. The Supplier shall notify the Customer of its MSME status and Udyam registration. GST shall be charged in addition; TDS shall be deducted as required by law.” |
The one move: check the counterparty’s Udyam registration, add an MSME-status representation clause, and allocate GST and TDS expressly. (The exact GST e-invoicing threshold and TDS rates change by notification, so confirm the current figures rather than hard-coding them.)
Data-protection clauses after the DPDP Act
This is the freshest moving piece, and it’s easy to overstate. The Digital Personal Data Protection Act, 2023 is law, and its Rules were notified in November 2025, but enforcement is phased. The substantive obligations, consent, notice, data-principal rights, breach reporting, and the duties of significant data fiduciaries, are scheduled to take effect around mid-2027, not in 2026. So a clause asserting present-tense DPDP compliance duties in 2026 is getting ahead of the statute.
What a sensible contract does now is allocate the roles and build in the obligations to switch on as the law comes into force. Where one party processes personal data on the other’s behalf, the clause should set out the data-fiduciary and data-processor roles, processing only on documented instructions, security safeguards, breach-notification cooperation, sub-processor flow-down, assistance with data-principal rights, and deletion or return of data on termination. As iPleaders’ coverage of the Digital Personal Data Protection Act, 2023 explains, cross-border transfer runs on a negative-list model, so the clause should address transfers as well.
The one move: allocate fiduciary and processor roles now, and draft the substantive obligations to apply “as and when in force,” rather than asserting duties that haven’t commenced.
The reply-email playbook: how to send a redline back
Here’s what nobody teaches. The email that carries your redline matters almost as much as the redline itself, because it frames how the other side reads your changes. A bare “see attached” with forty tracked changes reads as hostile. The same redline with a two-paragraph cover note reads as a partner solving a problem. So what does a good transmittal look like?
The cover email: structure and template
A strong cover email does four things: it summarises the material changes, separates must-haves from nice-to-haves, sets a response timeline, and attaches both the redline and a clean copy. That’s it. The goal is to let a busy counterparty grasp your position in ninety seconds without opening the document.
Hi [Name],
Thanks for sending this across. We’ve reviewed and attached our redline (and a clean copy for reference). The edits are mostly minor, but a few are commercially important, so I’ve flagged the key ones below.
Our must-haves: (1) a mutual liability cap at fees paid in the prior 12 months, with carve-outs for fraud, IP, and confidentiality; (2) indemnity limited to third-party claims; (3) payment within 45 days.
Open for discussion: the force majeure list and the notice periods, where we’ve suggested edits but are flexible.
Could you share your comments by [date]? Happy to jump on a quick call if that’s faster than another round.
Best, [Name]
Accept, counter, reject: comment language that moves deals
Inside the document, your comments do the negotiating. The rule that experienced lawyers follow: a comment should state your position, the reason, and your fallback, not just the edit. “Capped at fees paid; happy to go to 1.5x for the IP carve-out” tells the other side exactly where the deal can land, which closes faster than a silent change ever will.
A few patterns worth keeping in your back pocket. To counter: “We can’t accept unlimited liability. Proposing a cap at 12 months’ fees, with the carve-outs noted.” To accept with a condition: “Fine with this clause if we add a 30-day cure period.” To reject: “This is a walk-away for us; happy to explain the commercial reason on a call.” Notice none of them is a bare deletion.
The deadlock email
Sometimes the redlines stop being productive, and you’re trading the same two clauses back and forth. That’s the signal to stop typing and start talking. The deadlock email is short and proposes a different mode.
Hi [Name], I think we’ve narrowed this to two open points: the liability cap and the indemnity scope. Rather than another round of redlines, could we get the commercial leads on a 20-minute call this week to settle both? I suspect we’re closer than the document makes it look.
In practice, one call resolves what three email rounds couldn’t, because tone and intent travel better by voice than through tracked changes. There’s a reason senior dealmakers pick up the phone, and it shows up in how they negotiate a contract effectively: they know when the document has stopped being the right venue.
Redlining etiquette and the hidden-redline rule
A few norms separate professionals from amateurs, and breaking them costs you trust you can’t easily rebuild. Never make a silent change: if you’ve edited a clause, the change should be tracked, and anything material should be flagged in the email. Summarise your material edits up front. Keep version control sane, with clear file names (v1, v2, party initials, date) so nobody loses track of which draft is live. And don’t reopen clauses both sides have already settled, because nothing erodes goodwill faster than relitigating closed points in round four.
The hidden-redline rule deserves its own line, because it’s the etiquette breach that ends relationships. If you bury an unflagged change in a draft you’ve called “clean,” and the other side catches it (they will, if they run a compare), you’ve told them you can’t be trusted with the next ten deals. Don’t do it, and protect yourself by always comparing inbound “clean” copies against your own last version.
Common redlining mistakes that cost Indian companies money
After enough contract reviews, the same expensive errors recur. None of them is exotic. They’re the predictable result of redlining with a global checklist instead of an India-specific one, and each has a price tag. So what goes wrong most often?
The ten that cost the most, in rough order of how often they bite:
- Accepting an uncapped indemnity sitting above an otherwise mutual liability cap, which quietly undoes the cap you negotiated.
- Fighting for a post-termination non-compete that Section 27 of the Indian Contract Act, 1872 makes void, spending leverage on false comfort.
- Missing the counterparty’s MSME status, so your 90-day payment term is unenforceable and you’ve created a Section 43B(h) tax problem.
- Writing “venue” instead of “seat” in the arbitration clause, inviting jurisdictional satellite litigation.
- Under-stamping the contract, leaving it inadmissible in evidence until you cure the duty and penalty.
- Relying on a liquidated-damages figure without preserving the ability to prove actual loss, since under Section 74 it’s only a ceiling.
- Leaving a bare “act of God” force majeure clause that won’t cover the disruption you actually face.
- Making silent or hidden changes, which destroys counterparty trust the moment a compare runs.
- Asserting present-tense DPDP compliance duties that haven’t commenced, instead of an “as and when in force” mechanism.
- Drafting a dispute-resolution clause that ignores the mandatory pre-institution mediation step under Section 12A of the Commercial Courts Act, 2015.
Most of these trace back to a single root cause, which iPleaders’ guide to the common errors to avoid while drafting a commercial contract captures well: treating an Indian commercial contract as if Indian statute were optional. It isn’t. The clause says one thing; the Act says another; the Act wins.
AI and contract-review tools for Indian redlining
Can AI redline a contract for you? Partly, and the honest framing matters here. Tools in the Spellbook, LegalOn, and Luminance class can produce a fast first-pass markup, flag missing clauses, and suggest standard language, which genuinely saves time on the boilerplate. Early signals suggest they’ll keep getting better at the mechanical layer of review.
But here’s the catch for Indian work. These tools are trained largely on US and UK paper, so they miss the things this guide has spent six thousand words on: the Section 74 ceiling, the Section 27 voidness of non-competes, the MSME payment rules, the stamping requirements, the seat-versus-venue distinction. An AI that confidently approves a twenty-four-month post-termination non-compete is worse than no AI, because it gives you false assurance on a void clause.
Two cautions before you lean on them. First, confidentiality: don’t paste a counterparty’s confidential draft into a public AI model, and watch the data-protection implications under the DPDP framework once it’s fully in force. Second, keep a human in the loop on every Indian-law call, because the enforceability judgment is exactly what these tools are weakest at. Use AI to speed the first pass; never let it make the decisions that decide who pays when the deal breaks.
The wider landscape is moving too. A draft Arbitration and Conciliation (Amendment) Bill has been circulated for consultation, though it isn’t law yet, and the DPDP Rules are still phasing in. A contract you redline in 2026 should be drafted with one eye on where the statute is heading, not just where it stands today.
Frequently asked questions
What does it mean to redline a commercial contract?
Redlining means marking up a contract draft with tracked insertions, deletions, and comments so the other party can see your proposed changes before signing. In Indian practice, a proper redline also checks each clause for enforceability under statute, because some provisions are void or capped regardless of what the parties agree.
What’s the difference between a redline and a markup?
In Indian commercial practice they mean the same thing: a contract draft showing visible, tracked edits. “Blackline” is different. It’s the software-generated comparison between two specific versions, which you use to catch exactly what changed between drafts.
Is redlining the same as Track Changes?
Track Changes is the Microsoft Word feature (Ctrl+Shift+E) that records edits; redlining is the practice of using it to propose contract changes. So Track Changes is the tool, and redlining is what you do with it. Google Docs offers the same function through its Suggesting mode.
How do I respond to the other party’s redlines?
Go clause by clause and decide whether to accept, counter, or reject each change, leaving a comment that states your position, your reason, and your fallback. Then return the document with a cover email summarising the material points. A reasoned counter closes faster than a silent re-edit.
How do I send a redlined contract back?
Attach both the redline and a clean copy, and write a short cover email that summarises the material changes, separates your must-haves from your flexible points, and sets a response date. The email frames how the other side reads your edits, so it’s worth two careful paragraphs.
Are limitation of liability clauses enforceable in India?
Yes, a liability cap is generally enforceable, but the carve-outs are where the negotiation lives. An unrealistically low cap can be challenged, and parties typically carve out fraud, wilful misconduct, IP infringement, confidentiality breaches, and indemnity obligations from the cap.
Is a liquidated-damages figure a guaranteed recovery under the Contract Act?
No. Under Section 74 of the Indian Contract Act, 1872, a named sum is a ceiling, not an automatic entitlement, and you still have to show that loss occurred. The case law sets a real tension on how much proof is required, so never treat the number as a certain cheque.
What’s the difference between seat and venue of arbitration in India?
The seat determines which courts have supervisory jurisdiction over the arbitration and the governing procedural law; the venue is merely where hearings physically take place. Always specify the “seat” expressly, because a clause naming only a “venue” invites avoidable jurisdictional disputes.
What governing law should an Indian commercial contract have?
For two Indian parties on a domestic deal, Indian law and an Indian seat are the norm. Two Indian parties can validly choose a foreign seat, but make sure governing law, seat, and exclusive jurisdiction are consistent with each other, since mismatched choices are a common and costly drafting defect.
What data-protection clauses are needed under the DPDP Act, 2023?
Allocate data-fiduciary and data-processor roles, require processing only on documented instructions, and cover security, breach-notification cooperation, sub-processor flow-down, assistance with data-principal rights, and deletion on termination. Because the substantive obligations commence around mid-2027, draft them to apply as and when the law comes into force.
Do I need to pay stamp duty on a commercial contract in India?
Usually yes, and the rate depends on the state and the document type, so check the relevant state stamp schedule. Under-stamping makes the instrument inadmissible in evidence until you pay the deficient duty plus penalty, so stamp it correctly before execution.
What’s the difference between “best efforts” and “reasonable efforts”?
“Best efforts” implies a higher, more demanding standard of obligation than “reasonable efforts,” though Indian courts interpret both contextually. When you’re the obligated party, prefer “reasonable efforts”; when you’re relying on the other side’s performance, push for “best efforts.” It’s a one-word change with real consequences.
Can I redline a contract myself without a lawyer?
You can triage the commercial terms yourself, price, timelines, deliverables, and termination triggers, because you know your business best. But the enforceability calls, indemnity scope, arbitration seat, liability caps, and data clauses, need a contracts lawyer, because that’s exactly where self-drafted redlines go wrong.
How many rounds of redlining are normal?
Two to four exchanges is typical for a standard commercial agreement. Beyond five usually signals a genuine commercial gap or a drafting issue that a short call would resolve faster than continuing to trade tracked changes.
What are the best AI tools for redlining contracts in India?
Tools like Spellbook, LegalOn, and Luminance speed up a first-pass markup, but they’re trained largely on US and UK contracts and miss Indian-specific rules like the Section 74 cap, void non-competes, and MSME payment terms. Use them for speed, keep a human in the loop for every Indian-law judgment, and never paste confidential drafts into a public model.
References
Case law
- BGS SGS Soma JV v. NHPC Ltd., (2020) 4 SCC 234
- Energy Watchdog v. Central Electricity Regulatory Commission, (2017) 14 SCC 80
- Fateh Chand v. Balkishan Das, (1964) 1 SCR 515 (AIR 1963 SC 1405)
- Gajanan Moreshwar Parelkar v. Moreshwar Madan Mantri, AIR 1942 Bom 302 (AIR 1942 Bombay 302; Bombay High Court)
- Indus Mobile Distribution Pvt. Ltd. v. Datawind Innovations Pvt. Ltd., (2017) 7 SCC 678
- In Re: Interplay Between Arbitration Agreements under the Arbitration and Conciliation Act 1996 and the Indian Stamp Act 1899, (2024) 6 SCC 1 (2023 INSC 1066; 7-judge Constitution Bench)
- Kailash Nath Associates v. Delhi Development Authority, (2015) 4 SCC 136
- Niranjan Shankar Golikari v. Century Spinning & Manufacturing Co. Ltd., (1967) 2 SCR 378 (AIR 1967 SC 1098)
- Oil & Natural Gas Corporation Ltd. v. Saw Pipes Ltd., (2003) 5 SCC 705
- PASL Wind Solutions Pvt. Ltd. v. GE Power Conversion India Pvt. Ltd., (2021) 7 SCC 1
- Patil Automation Pvt. Ltd. v. Rakheja Engineers Pvt. Ltd., (2022) 10 SCC 1
- Percept D’Mark (India) Pvt. Ltd. v. Zaheer Khan, (2006) 4 SCC 227
- Satyabrata Ghose v. Mugneeram Bangur & Co., (1954) SCR 310 (AIR 1954 SC 44)
- Swastik Gases Pvt. Ltd. v. Indian Oil Corporation Ltd., (2013) 9 SCC 32
Statutes
- Indian Contract Act, 1872 (sections cited: 27, 32, 56, 73, 74, 124, 125)
- Indian Stamp Act, 1899 (sections cited: 35)
- Income-tax Act, 1961 (sections cited: 43B)
- Specific Relief Act, 1963 (sections cited: 10)
- Arbitration and Conciliation Act, 1996
- Information Technology Act, 2000 (sections cited: 5)
- Micro, Small and Medium Enterprises Development Act, 2006 (sections cited: 15, 16)
- Commercial Courts Act, 2015 (sections cited: 12A)
- Digital Personal Data Protection Act, 2023
Legal disclaimer
This article is for informational purposes only and does not constitute legal advice. For specific legal guidance on redlining or drafting a commercial contract, consult a qualified legal professional.
