redlining

Redlined agreement received: how to read it, sort the changes and reply

Nisha VarenkarCommercial contracts writer10 min read

Written by Nisha Varenkar A redlined agreement is a draft contract that comes back to you with the other side's proposed changes marked on it: their deletions struck through, their insertions underlined or coloured, and their comments in the margin. It is a proposal, not a contract. Nothing in it binds you until both sides agree the final text and sign. This page is for the person on the receiving end, the lawyer, founder or contracts manager who has just opened a redlined agreement from a customer or supplier and needs to work out what changed, what to accept, and how to reply without losing track of the deal. If you are the one making the markup, our step-by-step guide on how to redline a contract covers that side. ## Reading the marks before you read the words Redlines in contracts follow a few common conventions. Word's Track Changes is the usual source, though some counterparties send a comparison report or a marked-up PDF. Learn to read each kind of mark first, because each needs a different response. | Mark | What it means | Your first question | | --- | --- | --- | | Struck-through text | They want this wording removed | What protection or obligation disappears with it? | | Underlined or coloured text | They want this wording added | Does it add a duty for you, or remove one for them? | | Margin comment | A question, an explanation or an internal note left by mistake | Is it addressed to you, and does it need an answer? | | Moved text (shown as moved, or as a deletion here and an insertion there) | A clause has been relocated | Was anything changed inside it on the way? | | Formatting change | Bold, numbering, heading level, spacing | Does the change alter structure, such as a heading becoming body text? | | Changed defined term | A word in the definitions clause has been edited | Which other clauses use this term? | Read the comments before the text changes. Counterparties often explain their reasoning in a comment ("our insurer requires this"), and that explanation changes how you respond. Comments sometimes also reveal internal discussion the other side forgot to delete. You should not rely on such a slip, but it tells you something. ## A sample redlined contract clause, and how to read it Here is a short, invented example of a limitation of liability clause after the supplier's markup. Struck text is shown as struck and inserted text in bold. > 11.1 Except for liability arising from fraud, breach of confidentiality, breach of data protection obligations or death or personal injury caused by negligence, each party's total liability under this Agreement shall not exceed two times the fees paid by the Customer in the twelve (12) three (3) months preceding the claim.

11.2 Neither party shall be liable for loss of data, howsoever arising. What has happened, in plain terms: 1. The carve-outs for confidentiality and data protection breaches have been removed. Those breaches would now fall under the cap.

  1. The cap has dropped from two times twelve months of fees to one times three months, roughly an eighth of the original figure on a steady monthly fee.
  2. "Paid by the Customer" narrows the base: fees invoiced but unpaid at the time of the claim no longer count.
  3. The new 11.2 excludes data loss entirely. For a software or data-processing supplier, that may be the single largest risk in the deal. Four separate changes in two sentences, and only one of them (the cap amount) is the kind people notice on a quick read. This is why every mark deserves its own line in your review. ## Accept, counter or reject: sorting every change Once you can see all the changes, sort each one into one of three piles. Doing this explicitly, rather than reacting clause by clause as you read, keeps the reply consistent. | Pile | When a change belongs here | What you send back | | --- | --- | --- | | Accept | Clarifies wording, fixes an error, or moves risk in a way you can live with | Accept the tracked change; no comment needed | | Counter | The concern is fair but the wording goes too far | Reject their text and propose your own, with a one-line reason | | Reject | Moves material risk to you with no balancing benefit, or conflicts with your policy | Reject, restore the original, and explain briefly | Two rules help. First, decide the piles before you start typing the reply. Second, look for linked changes: a supplier that narrows its liability cap and also removes your termination right for repeated failure has made one combined move, and it should be answered as one. For the liability clause above, a reasonable counter is to keep the data protection carve-out, offer twelve months of fees as the cap, and accept a narrower data-loss exclusion limited to loss caused by the customer's own systems. Our page on limitation of liability fallback positions sets out typical steps. ## Changes that do not show up as tracked changes The most important habit on the receiving side: never trust that the tracked changes show everything. Changes can be made without tracking for several reasons, most of them innocent. Someone turned tracking off to fix formatting and forgot to turn it back on. Someone accepted all their own changes before sending to make the document cleaner. A schedule was replaced with a fresh copy. A template field updated itself. The fix is simple and takes two minutes. Keep the exact file you sent. When the redlined agreement comes back, run a comparison between your sent version and their returned version. Microsoft's legal blackline instructions explain that Word accepts any existing tracked changes before comparing, so the result shows the full net difference between the two files, whether or not the other side tracked each edit. Anything in the comparison that is not in their tracked changes is a silent change, and you should raise it. Check these places in particular: - Definitions, especially any term that was widened or narrowed.
  • Schedules, annexures and order forms attached as separate files.
  • Headers, footers and the signature block, including party names and company numbers.
  • Numbers written in both words and figures; one may have changed and the other not.
  • The governing law and dispute resolution clause. If the counterparty sends a PDF instead of a Word file, ask for the Word version. If they refuse, use a comparison tool that handles PDF against Word, and check the result carefully because PDF comparisons produce more noise. ## Who needs to see which changes A redlined agreement rarely belongs to one person. Before replying, route each change to whoever owns the risk it moves, and give them a deadline. - Finance should see anything touching payment terms, price increases, currency, set-off, late-payment interest and the liability cap expressed as a multiple of fees.
  • The business owner of the relationship should see service levels, deliverables, acceptance tests, exclusivity and termination rights. They know whether the supplier can actually meet a 99.9 uptime promise, or whether the customer will ever use the right to audit.
  • Security or data protection should see data processing terms, breach notification windows, sub-processor rules and where data may be stored.
  • Insurance or risk, where you have that function, should see indemnities and any change to the insurance clause, because an indemnity your policy does not cover is a promise paid from your own balance sheet.
  • Tax should see withholding, gross-up and stamp duty clauses when the deal crosses borders. Send each reviewer only the clauses they own, with the relevant marks, rather than the whole document. People review a two-page extract within a day; they leave a forty-page draft for a week. There is also a judgment call about when to stop writing and start talking. If the redlined agreement changes more than a handful of commercial points, or if you see the same theme across many clauses (the supplier is pushing all risk back to you), a thirty-minute call with the other side usually achieves more than another round of markup. Use the issues list as the agenda. ## Replying with a clean issues list On anything longer than a few pages, send two things back: your own markup of their redlined agreement, and a short issues list. The list lets both sides see the open points in one place and often settles half of them on a single call. | No. | Clause | Their proposal | Our position | Proposed compromise | | --- | --- | --- | --- | --- | | 1 | 11.1 cap | One times three months of fees paid | Two times twelve months of fees | Twelve months of fees payable | | 2 | 11.1 carve-outs | Remove confidentiality and data protection | Keep both | Keep both; data protection subject to a separate higher cap | | 3 | 11.2 data loss | Total exclusion | Delete | Exclude only loss caused by Customer systems | | 4 | 14.2 termination | Delete repeated-failure right | Keep | Keep, triggered by three failures in six months | Keep the list factual. The reasons belong in one short sentence each; long arguments slow everything down. Before you send, remove your own internal comments from the file. Microsoft's Document Inspector guidance shows how to find and remove comments, revisions and hidden text, and suggests working on a copy because removed data may not come back. ## Keeping every round of the deal in order By round three, most deals have a version problem. A few habits prevent it. - Use one naming pattern for every round, for example Supply-Agreement_v4_Supplier-markup_14Nov.docx, then v5_Our-reply.
  • Never edit the counterparty's file directly without saving a copy first; you need the untouched file for your silent-change check.
  • Keep track changes on for every edit you make. Word's Track Changes help also describes Lock Tracking, which stops others in your team switching it off.
  • Record what was agreed on each call in the issues list, with the date, so the next draft reflects it.
  • At signing, compare the execution copy against the last agreed draft once more. Our guide on contract version control goes further on naming and locking drafts. ## Where Adira helps when a redline comes back Adira works on the document itself. Open the counterparty's returned draft in Adira and its Document Intelligence Dashboard marks each position as favourable, neutral or unfavourable to your company, and lists red flags, missing clauses, key dates, obligations and monetary terms, which is a fast way to see where the redlined agreement now leaves you. To prepare your counter-proposals, Clause-Level Editing accepts plain-English instructions such as "restore the data protection carve-out in the liability clause", makes the change and shows you a diff of exactly what it altered. Notebooks let your team annotate the draft before the internal call, and you can export the result to Word or PDF. Adira is not marketed as a two-file comparison product, so run the silent-change check against your sent version in Word Compare or a comparison tool. Plans are published, from USD 89 per seat per month on annual billing for the Practice plan (minimum three seats), with a 7-day free trial at adiralaw.com.

Frequently asked questions

Is a redlined agreement legally binding?
No. A redlined agreement is a proposal showing suggested changes. It becomes binding only when both parties agree a final version and sign it, or otherwise clearly accept it under the law that governs the contract.
How do I find changes the other side did not track?
Keep the exact file you sent and compare it with the returned file using Word legal blackline or a comparison tool. Anything in the comparison that does not appear in their tracked changes is an untracked edit you should raise.
Should I accept all the tracked changes and then edit?
No. Accepting everything removes the record of what they proposed. Work change by change, accepting, rejecting or countering each, and keep the untouched original for your comparison.
What should an issues list contain?
One row per open point: clause number, their proposal, your position and a proposed compromise, each in a short phrase. Keep reasons to one sentence and record what is agreed on each call.
Can Adira show what the counterparty changed between two files?
Not for that step. Adira reviews a returned draft for favourable and unfavourable positions and returns a diff of its own clause-level edits; it is not marketed as a two-file comparison product, so use Word Compare or a comparison tool for the silent-change check.
Was this useful?

See how Adira drafts in your voice and reads contracts from your side.

Explore the showroom

Working through a contract like this? Weave is Adira’s free tool to read, mark up, and connect any contract in your browser — no account needed.

Try Weave — free

Book a demo

See Adira on your own contracts

A 30-minute walkthrough with our team. Tell us a little about you, then pick a time that suits you.

Prefer email? [email protected]