How to Negotiate a Contract: A Free Redline and Email Workflow

Most people freeze at the negotiation stage of a contract, not the reading stage. Reading is a comprehension problem. Negotiating is a workflow problem: what to change, how to say it, how to track what comes back, and when to stop pushing. This guide is that workflow, for someone doing it without a lawyer on every round: pick your must-haves, redline with a reason attached to every change, send a cover email that makes acceptance easy, catch what the other side quietly altered, and know when a clause is worth walking away over. (Adira, which publishes this guide, sells contract review and CLM software; the workflow below works the same whether you ever use it or not.)

Two things matter before you get to tactics. First, in Indian law a redline is not a comment, it is a counter-proposal that legally cancels your right to accept the original draft as-is. Second, a reasoned edit gets accepted far more often than a bare one, because you have done the other side's risk analysis for them. Both shape everything below.

Step 1: sort your changes into must-change and nice-to-have

Before you touch the document, make two short lists. Read the whole contract once first (see How to Read and Understand a Contract for a fast method), then for every clause that bothers you, ask one question: if this clause is enforced exactly as written, what does it cost me, and how likely is that?

• Must-change: clauses where the downside is large or the trigger is common. An uncapped indemnity, a liability cap set below your annual fee, a non-compete that would block your next job, an auto-renewal with a 90-day notice window you will likely miss. These are the hills you negotiate hard on.
• Nice-to-have: clauses that are annoying but low-cost or unlikely to bite. A slightly generous notice period for a routine amendment, a formatting inconsistency, a defined term you would have worded differently. Flag these, but be ready to drop every one of them if the other side pushes back on your must-changes.

Cap your must-change list at three. Send fifteen redlines with equal emphasis and the other side cannot tell what matters to you, so everything gets the same shallow pushback. Send three, clearly prioritised, and you signal seriousness on the things that count. A quick scan for the highest-risk clauses (indemnity, liability cap, IP assignment, termination, auto-renewal) is at How to Check a Contract for Red Flags; use it to build your list before you open the document to edit it.

Step 2: redline with tracked changes, and explain why in every comment

Once you know what to change, make the edit in tracked changes, not a fresh rewrite and not a PDF markup (a PDF comment only flags a problem, it does not change the words; see How to Redline a Contract for the mechanics of doing this properly in Word or, free and without an account, in Weave). Every substantive redline should carry a comment giving the one-line business reason for the change. Not a legal argument, a business one: what you need, and why it is reasonable.

This is not a soft-skills tip, it has a legal basis. Under Section 7 of the Indian Contract Act, 1872, an acceptance is only valid if it exactly matches the offer:

"In order to convert a proposal into a promise, the acceptance must, (1) be absolute and unqualified; (2) be expressed in some usual and reasonable manner, unless the proposal prescribes the manner in which it is to be accepted." Source: Section 7, The Indian Contract Act, 1872 (Indian Kanoon)

Any variation you introduce, however small, means you have not accepted their draft, you have made a fresh counter-proposal, and the original offer is off the table until someone accepts something in full. This is old, settled law: a 1916 Madras High Court judgment cited an earlier Bombay ruling on exactly this point, noting "the letter of the plaintiff promising to send the goods within the time specified by him amounted to a counter-proposal," referring to Haji Mahomed Haji Jiva v. Spinner, (1900) ILR 24 Bombay 510, where the court held that unless acceptance is absolute and unqualified, "the stage of negotiations has not yet passed, and no legal obligation is imposed." Source: Perala Krishnayyan Chettiv vs G. Padmanathan Chettiar, Madras High Court, 1916 (Indian Kanoon)

Practically, every redline you send resets the negotiation, and it stays reset until someone signs off on a version with no open changes. A comment explaining why speeds up that final, unqualified acceptance, because the other side is not guessing at your motive.

A vague comment: on a liability cap clause reading "Vendor's total liability shall not exceed the fees paid in the preceding three (3) months," you highlight it and write "not acceptable."

A comment that gets acted on: same clause, comment reads: "Three months of fees under-recovers our exposure on a 12-month engagement; we're asking for twelve months of fees or the total contract value, whichever is higher, consistent with market terms for a deal this size." This version gives a reviewer on the other side something they can take to their own management and approve without a call.

Step 3: a cover email that frames your changes as standard, not aggressive

Send the redlined document back with an email, never the file alone. The email does two jobs: it tells the reader where to look first, and it frames your edits as ordinary and mutual rather than one-sided, which lowers the reader's guard and speeds up approval. A template that works for most commercial contracts:

Subject: [Contract name], redlines attached, [N] items for discussion

Hi [Name],

Thanks for sending this over. Attached is our redlined version with tracked changes and comments explaining each one.

Most of this is standard for a deal of this shape, we've kept edits minimal and focused on [N] items: [one-line list, e.g. "the liability cap, the renewal notice period, and the indemnity scope"]. Everything else in your draft is unchanged.

Happy to jump on a short call if it's faster to walk through these live. Otherwise, let us know if the attached works and we can move straight to signature.

[Your name]

Naming the exact count of open items tells the reader this is a short, closeable list, not an open-ended fight. And "standard for a deal of this shape" is doing real framing, use it only when it is actually true; an unusual demand dressed up as standard reads as dishonest the moment someone checks a market template.

Step 4: handle counter-redlines, and never trust "no other changes"

Two things can go wrong when the document comes back, and both are common. First, your counterparty may reject your must-change clauses outright with no counter-offer, in which case you decide whether to push again or concede (Step 5). Second, and more dangerous, they may have made changes elsewhere without turning tracked changes on, or accepted their own edits before sending, so the file looks clean but is not the version you sent.

Never assume a returned document only contains the changes called out in the cover email. Run a full compare against the version you sent, every single round, using Word's Compare Documents or Google Docs' compare. A full method for this, including exactly what a diff tool will and will not catch, is at How to Catch Untracked Changes the Other Side Made to Your Contract. At minimum, after every round, Ctrl+F the liability cap figure, the payment amount, and the notice period in both versions: these three are the ones most often quietly nudged.

Keep every round as a separate saved file, named with a version number and date (Contract_v3_2026-09-04.docx), not overwritten in place. That trail is also what shows exactly what was proposed and accepted at each stage if it ever comes to a dispute, since under Section 7 each round is a distinct offer or counter-offer in its own right.

Step 5: know when to concede, and when to walk

Not every must-change item survives contact with the other side. Before your first redline goes out, decide in advance, not in the moment, which of your three must-changes is genuinely non-negotiable and which you would trade away. A rough test: ask "would I sign this contract without that change at all, if the rest is otherwise fine?" If the honest answer is yes, it is not actually a must-change; move it to nice-to-have and stop spending negotiating capital on it.

Walk-away triggers worth setting in advance, specific to Indian practice: an uncapped indemnity covering ordinary breach, not just third-party IP or confidentiality claims; a liability cap paired with an uncapped indemnity, which quietly defeats the cap; a non-compete applied to your post-employment conduct (void for an employee under Indian law in almost every circumstance, so a counterparty who refuses to remove it after you point this out is a signal worth taking seriously); or a counterparty who returns three rounds of redlines with zero explanation for any rejection. Concession is normal on nice-to-haves; a flat, unexplained "no" on a genuine risk item, repeated across rounds, is the signal to bring in a lawyer rather than keep negotiating alone.

This guide is deliberately the mechanics: what to redline, how to word it, how to send it. For the strategy layer underneath, leverage, sequencing your asks, and how a buyer's playbook differs from a seller's, see the Contract Negotiation Playbook.

Red flags during negotiation

Normal	Red flag	Why it matters
Counterparty explains why they rejected a redline	Rejections with no reason, repeated across rounds	You cannot tell if it's a real constraint or just resistance, and you cannot counter-argue what you don't understand
A firm deadline with reasonable notice ("end of week")	"This has to be signed today" pressure, especially late in the week	Time pressure is a classic tactic to stop you reading the final version carefully
Redlines come back with tracked changes on	Clean-looking document with no visible edits after you sent redlines	Edits may have been made and then accepted before sending; always run a compare (Step 4)
Your comments get specific responses	Your comments are silently deleted rather than answered	You cannot tell if an edit was rejected, ignored, or simply lost in a version merge
Both sides' redlines get incorporated into one working draft	Counterparty insists on sending a fresh "clean" copy every round instead of continuing your redline	A clean copy each round makes it far harder to spot what changed between rounds without a full compare
Final version matches what was actually agreed on the call	"We'll sort the final wording after signing" on a disputed clause	Verbal agreements on wording rarely survive intact once someone else drafts the final text

A negotiation-stage clause rewrite, before and after

Take a real IP assignment clause commonly found in vendor and freelance agreements: "All work product created under this Agreement shall belong to the Client." On its own, in India, this line is a trap. Sections 19(5) and 19(6) of the Copyright Act, 1957 fill the silence against the party the clause is meant to protect:

"If the period of assignment is not stated, it shall be deemed to be five years from the date of assignment." (Section 19(5)) "If the territorial extent of assignment of the rights is not specified, it shall be presumed to extend within India." (Section 19(6)) Source: Section 19, The Copyright Act, 1957 (Indian Kanoon)

So a clause silent on period and territory does not assign ownership forever, worldwide; it defaults to five years, India only. A one-line clause like this rarely fixes that.

Bad (what most vendor drafts send): "All work product created under this Agreement shall belong to the Client."

Better (redlined with the fix, and the reason attached in a comment): "All work product created under this Agreement, including all copyright and other intellectual property rights therein, is hereby assigned to the Client, in perpetuity and for all territories worldwide, effective upon creation." Comment: "Adding perpetuity/territory language so the assignment doesn't default to 5 years/India-only under Sections 19(5) and 19(6) of the Copyright Act. This protects both sides from a dispute over scope later."

Naming the statute in the comment shows the other side's counsel you have actually read Indian law, not just copied a template, and gives their reviewer a specific, checkable reason to approve the change quickly rather than escalate it.

A runnable test before you send any round

For every redline, you should be able to finish one sentence: "We need this change because ___," in language a business person, not a lawyer, would accept. If you cannot finish it for a given edit, drop the edit. This keeps your must-change list genuinely short, and means every comment you send already carries its own justification.

US and global contrast

The mechanics translate closely: US negotiation runs on the same tracked-changes-plus-comments workflow, called "blacklining" more often than "redlining" but functionally identical, and "explain the why" holds there too. The legal backdrop differs where it matters most. US courts under the UCC's "battle of the forms" (for sale of goods) are more forgiving of a response that adds minor new terms without treating it as a full counter-offer, unlike the stricter mirror-image rule Indian courts apply under Section 7. And the substance differs: in most US states, non-competes are negotiated over duration and geography because they can be enforceable, while in India that fight is usually about deleting the clause entirely, since it is void against a former employee in nearly every circumstance.

FAQ

How many redlines is too many to send in one round? There's no fixed number, but past 15 to 20 items the other side often cannot process all of it seriously in one pass. Lead with your three must-changes, flag the rest as minor, and be ready to trade the minor ones away.

Should I explain my reasoning in every comment, even for small changes? For must-change items, always. For genuinely minor edits (a typo, a formatting fix), a one-word comment or none at all is fine; save the detailed reasoning for edits you actually intend to defend.

What if the other side says "this is our standard template, we don't negotiate it"? Ask what specifically makes it non-negotiable; a genuine policy reason (a regulatory requirement, an insurer's condition) differs from a reflexive "no." If they cannot explain it and the clause is a real risk to you, that refusal is itself useful information.

Is it normal for negotiation to take multiple rounds? Yes, two to four rounds is typical for a commercial contract with real negotiated changes. What is not normal is a round with no visible change from the prior one, exactly why the compare step (Step 4) matters every time.

Can I redline a contract for free without buying Microsoft Word? Yes. Google Docs supports tracked changes and comments natively, and works for the whole workflow in this guide, no purchase needed.

Do I need a lawyer for every contract negotiation? No, for a routine, moderate-value agreement, a careful non-lawyer following this workflow handles most of it well. Bring in a lawyer specifically when a must-change clause is unusual, high-value, or the other side keeps refusing to move on a genuine risk item without explanation.

---

This guide covers the workflow of negotiating a contract: prioritising changes, redlining with reasons, framing a cover email, and catching what changed between rounds. It does not tell you whether a specific clause is enforceable in your situation, or what a fair market position looks like for an unusual or high-value deal; those depend on facts this guide cannot see. For a contract with real money or real risk attached, get a lawyer to review the must-change items before you sign.