How to Redline a Contract: A Step-by-Step Guide (2026)

Redlining is the process of marking up a contract draft so the other side can see exactly what you want to change, what you want to add, and what you want to delete. The word comes from the old habit of editing on paper with a red pen. Today the work is done with tracked changes in a word processor or inside a contract tool, but the goal is the same: make your position clear, make it easy to accept, and keep every version straight. This guide walks through how to do it well, whether you are in-house, at a firm, or running a small business without a lawyer. ## What redlining actually is A redline shows two things at once: the current text and your proposed edits. Insertions appear in one colour, deletions appear struck through, and comments sit in the margin explaining why. When you send a redline back, the other side can accept or reject each change individually. Over a few rounds the document moves from one party's opening draft to a version both sides can sign. A clean redline is a negotiation tool, not just an editing record. It signals how reasonable you are and how much work the other lawyer will have to do to close. ## Before you touch the text Do not start editing on page one. First read the whole draft once, end to end, without changing anything. You need the shape of the deal before you fix the words. As you read, note three things: what is missing, what is one-sided, and what is simply unclear. Then decide your priorities. Not every clause is worth a fight. Separate your points into must-haves (you will not sign without them), wants (you will trade them away for something bigger), and nice-to-haves (raise them, but do not spend capital on them). Knowing this order before you type keeps your redline focused and stops you from turning a routine deal into a war. ## Step-by-step: how to mark up the draft 1. Turn on tracked changes first. Nothing is more damaging than silent edits the other side cannot see. If you are working in Word, switch on Track Changes before you type a single character. In a contract tool, confirm it is capturing versions. 2. Fix the deal points before the boilerplate. Start with price, scope, term, payment, liability, indemnity and termination. These carry the real money and risk. The governing-law and notices clauses can wait. 3. Edit tightly. Change only the words that need changing. Deleting a whole clause and retyping it your way reads as aggressive, even when your version is close to theirs. Surgical edits are easier to accept. 4. Use fallback language, not just deletions. If a liability cap is too low, do not simply delete it. Propose a specific number or a formula. A redline that only strikes out text leaves the other side guessing. 5. Comment on the why, not just the what. A short margin note ("Our policy caps liability at fees paid; happy to discuss a higher figure for the data-breach carve-out") turns a demand into a conversation and usually gets accepted faster. 6. Flag open items you cannot resolve alone. Where you need a business decision or more facts, leave a clear comment rather than guessing. 7. Check cross-references and defined terms last. When you change one clause, defined terms and numbered cross-references elsewhere can break. Read the whole document again to catch them. ## How to write comments the other side will accept Tone decides speed. Three habits help. First, give a reason grounded in policy or risk, not preference: "we cannot accept uncapped liability" lands better than "please change this." Second, offer a landing spot. If you reject their number, propose yours. Third, keep comments short and specific. Long essays in the margin slow the deal and read as lecturing. Remember the person reading your redline is deciding how hard you will be to deal with. A fair, well-reasoned markup earns trust you can spend later. ## Managing versions without chaos Most redlining pain is version pain. A deal can run through six or eight drafts, and a single wrong file sent to signature is a real risk. Protect yourself with a few rules: - Name files with a clear convention: document name, party, date, and version, for example MSA_AcmeCo_v4_2026-03-14.

• Keep a clean and a marked copy of each round. The clean copy accepts all changes; the marked copy shows them against the previous version.
• Compare, do not trust. When a draft comes back, run a document compare against the version you last sent. People accept changes they never flagged, deliberately or not. A compare catches it.
• Lock the final. Before signature, accept all changes, remove every comment, check the compare one last time, then convert to PDF. ## Common mistakes to avoid - Editing with tracked changes off, so your edits are invisible or, worse, hidden.
• Rewriting whole clauses when a small edit would do, which inflames the negotiation.
• Deleting a term you dislike without proposing a replacement.
• Ignoring defined terms and cross-references after an edit, leaving the contract internally broken.
• Sending the wrong version, or sending a draft that still contains your internal comments to the other side.
• Treating every clause as equally important and burning goodwill on boilerplate. ## Doing redlines in one connected workspace The mechanics above assume a stack of separate tools: a word processor for edits, email for sending drafts, a folder for versions, and your own memory for your company's standard positions. The friction is real. You re-explain your fallback positions every deal, you hunt for the latest version, and the risk sits in the gaps between tools. A different model is to keep drafting, understanding, editing, version history and your company's own preferred terms in one AI workspace tuned to how your business contracts. In that model the contract is structured, so an edit like "shorten the notice period to 30 days everywhere" is applied precisely and tracked, each clause carries a plain-English risk view, and every version is kept automatically. Adira is built around that idea, on frontier AI. If you finish a round of redlines thinking your edits, versions and standard positions are scattered across too many places, that is the problem worth fixing. More at Adira. The steps above work with any tool. ## Bottom line Good redlining is less about typing and more about judgement: read first, set your priorities, edit tightly, explain your reasons, and never lose control of your versions. Do that and the other side sees a counterparty who is clear, fair and organised, which is exactly the reputation that closes deals faster. None of this is legal advice; for a high-value or unusual contract, get a qualified lawyer to review your markup before you send it.