How to Redline in Word: Contract Redlining for In-House Counsel

A redline is a message to the other side. It shows what your company wants changed, what it will discuss, and which terms still need a decision. Contract redlining means showing those proposed additions, deletions, comments, and other revisions against an identified version of the agreement so both sides are negotiating from the same text.

In Word, the basic mechanics are straightforward: preserve the original, turn on Track Changes, make the proposed edits and comments in a working copy, run Compare on the version that comes back, and resolve the changes before preparing a clean copy. The harder part is the legal and business judgment layered on top of those steps.

GC AI is an enterprise legal AI software built for in-house teams. 2,100+ legal teams across 45+ countries use it, including the legal departments at Columbia Sportswear, Jasper, and Viant Technology. Our GC AI for Word add-in works inside the document you have open and can propose first-pass redlines and comments against the legal team's Playbook.

Whether a person or the add-in makes the first edit, counsel still reviews the resulting clause, its connected provisions, and any comment that travels with it, then accepts, edits, or rejects the change.

Contract Redlining at a Glance

• A redline shows proposed changes; Track Changes records edits as you make them; Compare shows the differences between two versions.
• Preserve the original and work from a clearly named copy so everyone knows the baseline.
• Use comments to explain material changes, but keep internal fallbacks and escalation limits out of the version sent to the counterparty.
• When a draft comes back, run Compare against the version you sent and read the changed clauses in context before accepting or rejecting anything.
• GC AI for Word can propose first-pass redlines and comments against a Playbook, but the lawyer still decides what should go to the other side.

A redline records a proposal, not the final legal or business decision. The markup shows the language on the table; counsel still decides whether the company can live with it and who must approve any fallback.

Redline vs. Track Changes vs. Blackline vs. Clean Copy

These terms are often used interchangeably, but they refer to different parts of the redlining process.

Term	What it means	When to use it
Contract redline	An agreement showing proposed revisions against an identified baseline	To communicate a negotiation position
Track Changes	Microsoft Word's feature for recording edits as you make them	To create and review proposed changes in the working document
Compare or legal blackline	A comparison of two document versions that displays their differences in a new document	To check a returned draft or reconstruct changes made without tracking
Clean copy	A version with proposed revisions resolved and comments removed or retained on purpose	To read the proposed or agreed text without visible markup
Signature copy	The version the parties have approved for execution	To sign and retain as the final agreement

A clean copy can still contain proposed language. Label the file and the covering message so no one mistakes a proposed clean copy for an agreed execution version. Microsoft's legal blackline instructions explain how Word compares two documents and places the result in a third document without changing either source.

How to Redline a Contract in Word, Step by Step

The overview above shows the full process. The sections below walk through each step in desktop Word for Windows and note the Mac or Word for the web differences that change what you do.

1. Preserve the Original and Make a Working Copy
2. Turn On Track Changes Before Editing
3. Choose the Markup View You Need
4. Make Focused Edits and Add Comments
5. Use Compare to Check Two Versions
6. Check What Each Change Does
7. Accept or Reject Changes Deliberately
8. Create and Inspect the Clean Copy
9. Complete the Handoff

Preserve the Original and Make a Working Copy

Save the file you received without editing it, then create a separate working copy. Use filenames that identify the agreement, the version, and the status:

• Vendor_MSA_v03_Received.docx: untouched file received from the counterparty
• Vendor_MSA_v04_Our_Redline.docx: working copy with your proposed changes
• Vendor_MSA_v04_Proposed_Clean.docx: proposed clean copy with the revisions resolved

Confirm the baseline with the business owner and, where necessary, the counterparty. The latest attachment may differ from the version circulated internally, so keep any existing tracked changes and comments until you know what they represent.

Turn On Track Changes Before Editing

On the Review tab, in the Tracking group, select Track Changes. The dropdown offers For Everyone and Just Mine; choose For Everyone on a negotiation document so no colleague's edit slips in untracked. Make one small edit and confirm that Word marks it before you continue.

The same menu offers Lock Tracking with a password. While tracking is locked, users cannot turn Track Changes off or accept or reject revisions. On a negotiation over the other side's paper, that can complicate the exchange, so leave it unlocked unless your process specifically calls for a protected review record. Microsoft's Track Changes guide covers the controls for Windows, Mac, and the web.

With tracking on, open GC AI for Word. It reads the contract in the document you have in front of you, and the redlines and comments it writes land as tracked changes and margin comments in the same record as yours, against the same baseline.

Choose the Markup View You Need

Under Display for Review, Word offers four views:

• Simple Markup shows a line in the margin and hides the detail.
• All Markup shows detailed tracked changes. Use Show Markup to confirm Insertions and Deletions and All Reviewers are selected, and turn Comments on when you want the discussion displayed alongside the edits.
• No Markup previews the text with the revisions applied and leaves them unresolved.
• Original shows the earlier text and keeps the tracked changes and comments in the file.

Begin and end in All Markup, where GC AI's proposed edits sit alongside your own and you read both together. Use No Markup briefly to read a heavily redlined sentence without the visual clutter, then switch back. Word for the web offers Simple Markup and All Markup.

Make Focused Edits and Add Comments

Change only the language needed to state the company's position. Keeping the edit focused makes the negotiating point easier to see and reduces the chance of disturbing defined terms, qualifications, or language both sides accept.

Select the clause and type the change you want in plain language. GC AI for Word redlines a selected clause or the whole contract, so the scope of the ask sets the scope of the markup.

On the liability cap worked through below, an illustrative ask reads:

Move this cap to a 12-month fee look back, keep the existing exceptions intact, and stay close to the counterparty's sentence.

What comes back is a tracked change on the measurement period and a margin comment with the reason, and you read that comment as a negotiation choice before it travels.

GC AI’s Easy Prompt expands a short instruction into a fuller legal one, and the Skill Library holds the asks your team reuses.

Add a comment when the recipient needs the reason for a material change or an answer to a specific question. A useful external comment names the concern and offers a path to agreement; “Please revise” leaves the counterparty guessing.

Hayley McAllister, Senior Counsel and Head of Commercial Legal at Jasper, describes using GC AI to refine a comment she has drafted herself:

Sometimes I will just go ahead and draft what's in my brain as a comment… and I'll use GC AI to refine what I've said, add context, and ask, 'Did I miss anything here?'

Keep the internal ceiling in the internal record. The two notes on the same clause might look like this:

• External comment, in the redline: “We propose a 12-month lookback to reflect a full year of fees. We are open to discussing the cap's exceptions on a call.”
• Internal note, in the issue list or a comment tagged INTERNAL that you delete before sending: “Approved fallback is 24 months. Escalate to the GC if they push for 6 or remove confidentiality from the exceptions.”

Use Compare to Check Two Versions

Compare is the easiest way to see what changed between the version you sent and the version that came back. In desktop Word:

1. On Review, select Compare, then Compare two versions of a document (legal blackline).
2. Choose the version you sent as the Original document and the returned version as the Revised document.
3. Show the changes in a New document, then select OK.

If formatting changes create too much noise, open More and turn Formatting off. Word for the web does not have Compare, so run this check in desktop Word.

If several internal reviewers created separate marked-up copies, Word's Combine command can merge those revisions, but that is a separate task from comparing the counterparty's return.

You can also ask GC AI for Word to summarize the counterparty's changes and comments first. That gives you the shape of the return before the line-by-line review, but still run Compare because it catches textual differences whether or not the other side used tracking.

Compare tells you what changed. The next question is what each change does.

Check What Each Change Does

To decide whether a change matters, read the comparison alongside the working document and look for revisions that affect:

• Who owes an obligation or receives a right.
• A deadline, notice period, price, payment formula, or liability calculation.
• A definition, exception, cross-reference, or order-of-precedence provision.
• An exhibit, schedule, signature block, or incorporated policy.
• A termination right, survival obligation, data return promise, or transition duty.

Then read the complete resulting clause. A deletion can change an exception even when the remaining sentence looks polished, and a changed defined term can affect every section that uses it.

GC AI for Word can issue spot the returned draft for risks and ambiguities. Use that list to narrow where you look, then check each flagged clause against the text and its connected provisions. Keep an issue list for anything unresolved: the clause, the proposed position, the business owner, the approval status, and the next action.

Accept or Reject Changes Deliberately

On the Review tab, use Next with Accept or Reject to work through the revisions. The main trap is deletions: accepting a tracked deletion removes that text from the working document. GC AI's proposals move through the same pass as the counterparty's, so you decide on each of them before the file goes anywhere.

Leave proposals pending in the negotiation redline while the counterparty still has to evaluate them, and resolve them in a separate copy when you prepare a clean version.

Microsoft's accept-and-reject guide explains why the clean-copy step matters: choosing No Markup hides changes temporarily, and they become visible again the next time someone opens the document.

Create and Inspect the Clean Copy

To create a clean copy without losing the negotiation record, preserve the negotiation redline and save a separate copy. Resolve the remaining revisions to the intended text, turn off tracking, and remove the comments that should not travel with the clean version.

Reopen the clean copy and check:

• Party names, dates, amounts, and defined terms.
• Cross-references, tables, exhibits, and schedules. Search for “Error! Reference source not found.” and refresh the fields (select all, then F9) after you accept changes that moved clauses.
• Page breaks, numbering, headers, footers, and signature blocks.
• Comments and hidden revisions.
• Whether the document still contains tracked changes or review metadata.

On Windows, File, then Info, then Check for Issues, then Inspect Document surfaces revisions, comments, document properties, and hidden content. Run it on a copy, because Word cannot always restore removed data. Word for Mac has no Document Inspector, so on a Mac, resolve the changes and delete the comments by hand, then check the file's properties for author and revision data before you send. Microsoft's Document Inspector guide explains the process.

Complete the Handoff

Before sending the next draft, reopen the outgoing redline and clean copy and verify that they reflect the same proposed deal. Confirm that the redline identifies the correct baseline, then make the covering message do five things:

• Name the agreement and the version.
• Identify the attached files.
• State whether the clean copy contains proposed or agreed language.
• Summarize the material open points.
• Ask for the next action and the response needed, with the turnaround you expect.

For signature, compare the execution text against the last approved version and investigate each unexpected difference before anyone signs.

What If the File Is a PDF, Locked Document, or Google Doc?

To keep conversion errors from looking like negotiated changes, preserve the original before converting or copying anything. If the counterparty sends a PDF or scan and the negotiation needs Word redlines, obtain or create an editable .docx only when permitted, then compare the converted text with the source before editing. Pay special attention to tables, definitions, cross-references, headers, and signatures.

If the file is read-only or protected, do not work around the restriction. Ask for an editable copy or permission to create one, then label the original and working copy separately.

A similar manual redlining process works in Google Docs. Google calls its tracked-edit equivalent Suggesting mode: additions and deletions appear as suggestions that the document owner can accept or reject.

GC AI can connect to Google Docs through Agent Connectors, but that is different from the native redlining workflow in GC AI for Word. If you want to use the Word add-in, download the current Google Doc as a Microsoft Word file, name that download as the baseline, and inspect comments, formatting, and tracked changes after the conversion.

How to Read the Redline That Comes Back

A returned redline can contain changes that are easy to miss but materially change the deal. Run Compare against the version you sent rather than against an earlier draft, then look for three things:

1. Untracked edits: A change made with tracking off shows up in Compare even though it was not marked in the returned file. Treat it as a proposal and ask about it; do not assume intent.
2. Changed definitions and broken carve-outs: One edit to a defined term can affect every clause that uses it, and a renumbered section can break an exception central to your position.
3. Deletions that change the deal: A struck sentence is a proposal. If you accept that tracked deletion, Word removes the language from the working text.

Here is what the third problem looks like on the liability cap in the example below. You sent a 12-month lookback with three exceptions to the cap, and their return accepts the 12 months but strikes the confidentiality exception.

Your prior language:

...provided that the foregoing limitation shall not apply to (a) a party's breach of Section 8 (Confidentiality), (b) Supplier's obligations under Section 11 (Indemnification), or (c) a party's gross negligence or willful misconduct.

Their redline: (a) Supplier's obligations under Section 11 (Indemnification), or (b) a party's gross negligence or willful misconduct.

No comment accompanies it. Reject the deletion if confidentiality must remain outside the cap; rejecting that revision keeps the original confidentiality exception in the working text. Add the external comment that explains why, and keep the point on the issue list until the other side answers it.

Contract Redlining Example: A Liability Cap

This simplified example assumes the customer's approved position is a 12-month fee lookback. It shows the mechanics; the position is one example.

Original language:

Supplier's total aggregate liability under this Agreement will not exceed the fees Customer paid Supplier under this Agreement in the 6 months preceding the event giving rise to the claim.

Illustrative redline:

Supplier's total aggregate liability under this Agreement will not exceed the fees Customer paid Supplier under this Agreement in the 12 months preceding the event giving rise to the claim.

Illustrative external comment:

We propose a 12-month lookback to reflect a full year of fees where that payment history exists. We will address the cap's exceptions separately.

The edit changes the measurement period. It leaves open which claims sit outside the cap, whether the fee base covers the full agreement, and whether “paid” should include “payable.” Those are separate negotiation questions, and the exceptions are where the returned redline above tried to move the deal.

Before sending the markup, check the cap against the indemnity, confidentiality, data, warranty, and remedy provisions. The contract may allocate the same risk in more than one place, and the limitation of liability clause is where those allocations meet.

Contract Redlining Best Practices From the In-House Seat

Nada Alnajafi's ten rules of contract redlining etiquette, published on Contract Nerds in 2021, are the canonical list for the negotiation itself: comments on each redline, one exchange before a call, tracked changes on at all times, a clean and verified final. The five below are the ones that belong to the in-house seat, where the counterparty is one audience and the business owner is the other.

1. Name the baseline, the pen holder, and the turnaround: The covering message says which version you marked, who holds the pen next, and when you expect the return. Missing any of the three creates avoidable delay and version confusion.
2. Send one file set per turn: One redline against a named baseline and one clean copy labeled proposed. A second attachment an hour later with a small fix creates two baselines and a reconciliation nobody planned for.
3. Consolidate before you send: Procurement, security, finance, and the business owner each get one chance to comment before the redline goes out, and the counterparty receives one position per turn. Playbooks are where those settled positions live afterward, captured once from your templates and your negotiated agreements, so the next redline starts from the standard the team has agreed on.
4. Accept theirs, show only yours when that is your team's convention: If your process calls for it, accept the counterparty's changes you agree with and return a draft that shows only your edits, so the other side reads one set of changes.
5. Hand the business the right copy: Give the business owner the clean copy labeled proposed, the open points in plain language, and the decision you need. Keep the negotiation redline available to legal and the team members who need to review it.

How GC AI Redlines a Contract in Word

McAllister, introduced above, described building Jasper's playbook from recurring contract issues and sample comments rather than starting with a finished rule set. Her redlining advice is especially useful:

GC AI feels like having an assistant or another brain that I can dialogue with, and with redlining, it does a much better job if I say, 'let's work with what's already there and be a little more surgical.'

A Playbook matters because it tells GC AI which positions are preferred, which fallbacks are approved, and which issues require escalation. A vague or incorrect standard can produce consistently unhelpful redlines.

GC AI runs the liability-cap example above in three steps:

1. Run your MSA Playbook against the document: The pre-built Playbooks cover NDAs, DPAs, and MSAs, and you can build a contract playbook from your own templates and negotiated agreements. Write each position from the seat you negotiate in because the same cap reads differently for the customer and the supplier.

   Example Playbook position:

   Limitation of liability: cap at fees paid in the 12 months before the claim, with exceptions limited to breach of confidentiality, the IP indemnity, and gross negligence or willful misconduct. Fallback: a 24-month cap if the exceptions stay intact. Escalate if the counterparty removes confidentiality from the exceptions or proposes an uncapped indemnity.

2. Read the flagged clauses in Word: The proposed language arrives as a tracked change with a comment explaining the reason. In this example, the six-month lookback and missing confidentiality exception are the points to review. The AI contract redlining walkthrough covers a full Playbook pass clause by clause.

3. Verify and decide: Read the flagged clause with the indemnity and confidentiality sections, accept or edit an approved fallback, and reject anything that overreaches.

Here's how our GC AI for Word add-in reviews and redlines a contract inside Word:

GC AI does not set the company's risk appetite, invent a fallback nobody approved, or decide whether a novel term is worth the commercial trade. A polished edit can still be wrong for the business or conflict with another clause, which is why approval stays with counsel.

Our Easy Edit feature runs similar document editing in GC AI's web app. Open the document beside the chat, ask for a revision in plain language, and review the proposed tracked changes before accepting or rejecting the set.

If you are choosing the software, compare contract redlining software on Word integration, Playbook depth, and citations before price. If you want the first read before you open the file yourself, the AI review of a Word document workflow starts from the same Track Changes baseline.

GC AI's Prediction: Redlining Gets Faster, Judgment Stays With Counsel

The core redlining discipline does not change: work from a known baseline, make proposed changes visible, compare every return, and decide deliberately what to send. Software will take on more of the mechanical comparison, issue spotting, and first-pass language, but the position, the commercial trade, and the final approval remain legal decisions.

The practical test is simple: open a contract your team has redlined before, run the Playbook against it, and compare the proposed changes with the ones your lawyer made by hand.