A redline contract is a marked-up version of a legal agreement that visually tracks every proposed change between drafts, showing additions, deletions, and comments so both sides can see exactly what shifted from one round of negotiation to the next. It is a working document, not the final contract. Once both parties agree on all terms, the tracked changes get accepted and a clean copy is produced for signature.
The name comes from the old practice of marking up a printed draft with a red pen. Today the term covers any document where edits between versions are tracked and displayed, usually inside a word processor or contract platform. One side sends a draft, the other proposes revisions, and the file goes back and forth until the language settles.
How Redline Markings Work
Redlines rely on a handful of conventions that look nearly identical across the common tools.
- Strikethrough text is language the revising party wants to delete. The original wording stays visible so you can see exactly what is being removed.
- Underlined or colored text is new language being proposed. Most tools display insertions in a contrasting color, often red or blue, so they stand out from the surrounding text.
- Margin comments explain why a change was made. Good negotiators use them liberally on substantive edits.
- Moved-text indicators flag when a paragraph or clause has been relocated within the document rather than deleted and rewritten.
Taken together, strikethroughs and insertions let you reconstruct both versions of any sentence at a glance. If the markup reads “The agreement shall remain in effect for three (3) five (5) years,” the other side is proposing to extend the term from three years to five. That kind of clarity is the whole point of working in redline.
The Tools People Use
Most contract redlining happens in one of three environments, and the tool shapes what you can see.
Microsoft Word Track Changes
Word’s Track Changes feature is the industry standard. When it is on, every edit is recorded and shown as markup, and the other party can accept or reject each change individually. Word also has a Compare Documents feature that takes two versions of a file and generates a third document showing every difference as tracked changes, even if the person who edited the original never turned Track Changes on. That capability matters any time you receive a “clean” revised draft and need to verify what actually changed.
Google Docs Suggesting Mode
Google Docs offers a Suggesting mode that functions similarly. Edits appear as colored suggestions that collaborators can accept or reject. Its real advantage is simultaneous collaboration, with multiple reviewers marking up the same document in real time. It lacks some of Word’s granular comparison features, and many law firms still prefer Word for formal negotiations.
Contract Lifecycle Management Platforms
For organizations handling high volumes of contracts, dedicated contract platforms embed redlining within a broader workflow. These systems maintain clause libraries with pre-approved language, enforce approval chains so junior staff cannot accept risky terms unilaterally, and keep an audit trail across every version. Some encode negotiation policies into playbooks that flag deviations from standard positions automatically. They make sense for legal departments processing hundreds of agreements and are overkill for a one-off business deal.
How to Review a Redline
Reading a redline is not the same as reading a contract. You are doing two things at once: understanding what the document says and evaluating whether the changes from the prior version are acceptable.
Read the Clean Version First
Before diving into the markup, read the document with all changes accepted so you understand what the other party is proposing the final contract to say. Markup is visually noisy, and starting in the tracked view tends to bury the big picture under individual edits. Most word processors let you toggle between All Markup and No Markup views for exactly this reason.
Walk Through Every Marked Change
Switch to the full markup view and move through each change sequentially. Do not skim. The most consequential edits are often buried in dense sections nobody wants to read, like indemnification provisions or definitions. For each change, ask three questions: What did the original say? What does the revision say? Does this shift risk, cost, or obligation toward me?
Check the Definitions Section Closely
This is where most reviewers get burned. A single change to a defined term can cascade through the entire agreement. If “Confidential Information” gets narrowed, every confidentiality obligation in the contract just got weaker. If “Deliverables” gets expanded, your performance obligations may have just grown substantially. When you spot a definition change, search the whole document for every instance of that term to understand the full impact.
Read Every Comment
Margin comments often carry the other side’s reasoning, and that reasoning tells you how hard they will fight on a particular point. A comment saying “this is standard in our industry” signals flexibility. A comment saying “this is required by our board policy” signals a harder line. Comments also sometimes contain questions directed at you, and missing those stalls negotiations.
Formulate Your Response
For each change you have three options: accept it, reject it, or counter with alternative language. Rejecting without explanation invites a repeat fight in the next round. The more effective approach is to accept what you can live with, reject what you cannot, and propose specific alternative wording for everything in between. Leaving your own comments explaining your reasoning speeds up the next round considerably.
Clauses That Deserve Extra Scrutiny
Not every change carries equal weight. A formatting tweak to a header matters less than a one-word edit to an indemnification cap. When time is limited, focus on the provisions where small wording shifts carry outsized consequences.
- Indemnification. Who is responsible for covering the other party’s losses, and under what circumstances. Small wording changes here can shift enormous liability.
- Limitation of liability. Caps on damages and exclusions of consequential or indirect damages. A deleted sentence can mean the difference between capped and unlimited exposure.
- Termination and renewal. How either party can end the agreement, what notice is required, and whether the contract auto-renews. Missed changes to auto-renewal language lock parties into contracts they intended to exit.
- Payment terms. Pricing, payment schedules, late fees, and what triggers a fee increase. Changes to payment timing can affect cash flow more than changes to the dollar amounts.
- Governing law and dispute resolution. Which state’s law applies and whether disputes go to court or arbitration. Being forced into arbitration in a distant jurisdiction is a common surprise parties discover too late.
- Assignment. Whether either party can transfer the contract to someone else. A broad assignment right means you could end up doing business with a company you never agreed to work with.
- Force majeure. What events excuse performance. These clauses get more attention now than they used to, but many reviewers still skip over edits to them.
Traps That Hide Changes
The biggest risks in a redline are rarely the obvious markups. They are the subtle ones.
Edits That Were Never Tracked
Not everyone plays fair. A party may turn off Track Changes, make edits, then turn it back on before sending the file. The result is a redline that shows some changes and hides others. If there is any doubt that all edits are displayed, run Word’s Compare Documents on the version you sent and the version you received. That comparison catches everything, regardless of whether the other side tracked their edits.
Metadata and Leftover Comments
Word documents carry hidden information: the names of everyone who edited them, timestamps, deleted text that is still recoverable, and internal comments that were resolved but not fully purged. Sending a contract with your internal strategy notes still embedded is the kind of mistake that reveals your negotiation position. Before sending anything externally, use your word processor’s document inspector to strip metadata, hidden text, and resolved comments.
Formatting That Masks Substance
Reformatting a paragraph while simultaneously changing a word or two inside it is a common way to make substantive edits harder to spot. When the markup shows an entire paragraph as deleted and reinserted, the instinct is to assume it was cosmetic and move on. Do not. Copy both versions into a comparison tool and verify they are actually identical in substance.
Cascading Definition Changes
A subtle version of the definitions problem is a change in how one defined term interacts with another. If “Net Revenue” is redefined to exclude certain categories, and your royalty is calculated as a percentage of Net Revenue, your compensation just dropped without anyone touching the payment clause itself.
Version Control Across Rounds
Negotiations that run beyond two or three rounds create a version control problem. With five drafts circulating across email threads, it is disturbingly easy for someone to edit an outdated version and undo changes that were already agreed.
Use a clear naming convention for every draft. Something like “Agreement_v3_Redline_2026-01-15” tells everyone which version they are looking at and when it was created. Never name a file “final” unless it truly is, and even then, include a date. Every contract lawyer has a story about three different files all named “FINAL” sitting in the same folder.
Keep internal markups separate from what you send to the other side. Internal comments, where you flag risks for your own team or ask colleagues questions, should never appear in the version you share with the counterparty. The safest approach is to maintain two copies: one with internal notes for your team’s review, and a clean redline showing only the changes you want the other side to see.
Producing the Execution Copy
Once all changes are agreed, someone needs to produce the signing version. Standard practice is to circulate two documents: a clean version with all changes accepted for signature, and a final redline showing every change from the original draft to the agreed version. The redline serves as proof of the negotiation history and lets both parties verify that the clean copy accurately reflects what was agreed.
Before the clean version goes out for signature, run through it carefully. Accept all tracked changes, delete all comments, strip all metadata, and confirm that no hidden markup remains. Then compare the clean version against the final redline one more time to make sure nothing was accidentally dropped or altered during cleanup. This last step feels redundant. It catches errors that would otherwise become disputes.
When to Bring In a Lawyer
Not every contract justifies legal fees for a professional review. Some do. A lawyer’s review is worth the cost if the agreement involves substantial money, a long time commitment, complex compensation structures like equity or performance-based payments, non-compete restrictions that could limit your future career, or indemnification obligations that could expose you to losses well beyond the contract’s face value. The same applies when you receive a redline that is difficult to interpret, when defined terms have been restructured in ways you cannot fully trace, or when the other party has made changes you do not understand and will not explain. A few hundred dollars in legal fees is cheap insurance against signing something that costs far more down the road.