How to Redline a Contract in Word: Step-by-Step Guide

Redlining a contract in Word is a 5-step process: save a clean working copy, turn on Track Changes (Ctrl+Shift+E on Windows, Cmd+Shift+E on Mac), edit with visible markup, customize the markup view, then review and finalize. Get the steps right — plus the hidden features that protect you from the kind of metadata mistakes that cost real deals.

A few months back, I sat in on a call where a senior counsel walked through her redline of an MSA, accepted what she thought was an isolated change, and accidentally pulled in seven other modifications she hadn't reviewed. The vendor's lawyer caught it on the next pass — politely. The CISO on the call did not look amused.

That's the version of contract redlining most people don't talk about. The mechanics in Microsoft Word seem simple. Track Changes on, type, send. But the ways those mechanics break — disappearing redlines, accidentally-accepted changes, metadata leaks that expose your negotiation strategy, version control chaos across five drafts — are exactly where deals quietly fall apart.

According to Contract Nerds' 2025 poll, 91% of contract negotiators still use Microsoft Word's Track Changes as their primary redlining tool. And per World Commerce & Contracting research, poor change management during redlining contributes to 71% of contract disputes. So yes — Word is the standard. And yes, most people are using it slightly wrong in ways they don't notice until something goes sideways.

This guide walks through how to redline a contract in Word the right way — every step, every shortcut, every hidden feature, plus the strategic mistakes that cause real legal and security exposure. By the end you'll know how to do this cleanly, even on a complex multi-party deal.

Let's get into it.

What does it mean to redline a contract?

Redlining a contract means marking up proposed changes — additions, deletions, and edits — so every party in the negotiation can see exactly what's being modified. The term comes from the old practice of using a red pen to strike through text on printed contracts during negotiation. In modern legal practice, it refers to any method of tracking and displaying document changes, with Microsoft Word's Track Changes feature being the dominant tool.

A "redlined version" or "redline" is the marked-up copy showing proposed changes — added text typically underlined, deleted text struck through, and comments in the margin. The clean, agreed-upon final copy is called the execution version.

Worth noting upfront: redlining isn't just markup. It's the legal record of how meaning evolved between drafts. Every accepted change is a piece of mutual assent. Every rejected one is a position staked out. Treating it casually is how you end up in a dispute six months later about whether a sub-processor was actually approved or whether someone forgot to reject a quietly-inserted indemnity carveout.

The five-step process to redline a contract in Word

This is the workflow we use internally and recommend to every customer's legal team. Five steps, in order. No skipping.

Step 1 — Save a clean working copy with a clear file name

Before you do anything else, save the inbound document as a new file with a versioned name. Don't redline directly on the file your counterparty sent.

Use a naming convention that includes the document name, version number, the party doing the edits, and the date. Something like:

MSA_v2_Cyberbase_Edits_2026-05-08.docx

This sounds boring. It's the difference between sending the right draft to the right person at the right time and accidentally executing on a version everyone thought was superseded. Clio's 2026 redlining guide calls this out as one of the top sources of redlining errors — multiple parties working on multiple files without a single source of truth.

While you're at it: store the file in a shared location everyone on your side has access to. Email attachments are the worst possible version control system. SharePoint, OneDrive, Google Drive, your CLM — anywhere with audit history beats a thread of Outlook attachments.

Step 2 — Turn on Track Changes

This is the actual mechanical core of redlining in Word.

Keyboard shortcut: Ctrl + Shift + E on Windows, Cmd + Shift + E on Mac.

Menu path: Click the Review tab in the ribbon → click Track Changes in the Tracking group. The button highlights when it's on.

Once enabled, every insertion, deletion, and formatting change you make from that point forward is recorded — color-coded by author, with timestamps. Insertions show as underlined colored text. Deletions show as strikethrough. Formatting changes appear in balloons in the right margin (more on those in Step 4).

If you're working on a contract that absolutely cannot have untracked changes — and honestly, most negotiated agreements fall into this category — use Lock Tracking. Click the dropdown arrow under Track Changes → select Lock Tracking → set a password. This prevents anyone from disabling Track Changes without the password, even by accident. Volody's 2026 guide covers this in depth, and I'd treat it as standard practice for any deal worth more than a small fee. Choose a strong password, share it only with authorized editors, and log it somewhere you can find again. Forgetting it can lock you out of editing functions on that document.

Step 3 — Edit with visible markup and use Comments to explain reasoning

Now you actually redline. Type your edits as normal — Word handles the rest.

Two practical disciplines that separate good redliners from sloppy ones:

Use Comments to explain your reasoning. A comment costs nothing and saves your counterparty from guessing why you struck through a clause. Highlight the relevant text → click New Comment in the Review tab (or Ctrl + Alt + M on Windows, Cmd + Option + A on Mac). Write a one-sentence rationale. "Removing per our DPA — vendor cannot train on customer data." "Tightening notification window from 72 hours to 24 hours from discovery."

The other side will read your comments before they look at the redline. A clear comment can save days of back-and-forth and head off the "what did you mean by this?" emails that bloat negotiation cycles.

Make substantive changes first; cosmetic ones last. Don't waste your first pass on capitalization fixes and Oxford comma debates. Get the liability cap, the breach notification window, the indemnification scope, the data protection terms, and the termination clauses correct first. The other side cares about substance. A redline that's 80% formatting changes makes you look unfocused and dilutes your real positions.

Step 4 — Customize the markup display so you can actually see what's happening

Word offers four markup display modes, and most people never change the default. Big mistake.

In the Review tab, find the Display for Review dropdown:

• Simple Markup — clean view with red lines in the margin indicating where changes exist. Good for high-level review.
• All Markup — every edit, comment, and formatting change visible inline. Use this for active redlining and serious review.
• No Markup — hides all changes visually. This does NOT remove the changes. It only hides them. If you send the file in this view, the recipient can switch back to All Markup and see everything.
• Original — shows the document before any tracked changes.

For contract review, use All Markup. Always.

You can also filter what shows. Click Show Markup → toggle Insertions and Deletions, Formatting, Comments, or filter by Specific People. On a multi-party negotiation where five reviewers have edited the same draft, filtering by reviewer is the difference between a cogent review and a migraine.

One detail almost nobody knows: you can move your tracked changes from inline markup into balloons in the right margin. Click Show Markup → Balloons → Show Revisions in Balloons. For complex redlines, this dramatically improves readability. Inline markup makes long edits illegible; balloons let you read the original text clearly while still seeing the proposed changes.

Step 5 — Review changes, accept or reject each, then finalize the clean version

When the redline lands back in your inbox after the other side has marked it up, you have three choices for each change: accept, reject, or counter (negotiate further with your own redline on top).

Use the Next and Previous buttons in the Changes group of the Review tab to step through each modification one at a time. Accept keeps the change. Reject discards it.

Here's where I have to flag the single most dangerous button in Microsoft Word.

Avoid "Accept All Changes" unless you've personally reviewed every single edit. Per the American Bar Association via Justee's 2026 redlining analysis, failing to review accepted changes is one of the most common causes of contract disputes. I've seen senior attorneys accept all changes on a document that had a quietly-inserted clause they hadn't seen — and only catch it on the execution version a week later. By then, the deal had momentum, the relationship was warm, and walking back a quietly accepted change felt like an accusation. They paid for that change for the next three years.

Review every change. One at a time. No exceptions on a deal that matters.

A second pitfall most people don't realize: when you click the Reject button on a counterparty's proposed redline, the text reverts silently to the original — with no record that a change was just rejected. Nada Alnajafi at Contract Nerds calls these "disappearing redlines", and they're one of the most common transparency failures in modern contract negotiation. The other side glances at your response, sees their text apparently restored to its original form, and assumes you accepted everything. Only on close inspection do they realize you rejected a key clause.

The fix: instead of clicking Reject, manually strike through the counterparty's proposed text using the backspace key (with Track Changes still on). This creates a visible strikethrough record that your reviewer can see — preserving the audit trail and signaling exactly what you didn't agree to.

Once all changes have been resolved, save the marked-up version (your "redline" copy) for your records. Then create the execution version by clicking the dropdown under Accept → Accept All Changes and Stop Tracking. This produces the clean copy ready for signature.

The hidden Word features that protect you from costly mistakes

The five steps above will get you 80% of the way there. The features below are what separate amateur redliners from senior contract negotiators.

Compare two documents (a.k.a. the "blackline")

Sometimes the other side sends you a "clean" version after their internal edits — without Track Changes on. Now you have no idea what they changed.

Word's Compare tool generates a blackline document showing the differences between any two versions, regardless of whether either had Track Changes enabled.

Click Review → Compare → Compare. Select the original document and the revised document. Word generates a third document showing all differences in tracked-changes format.

This is non-negotiable for legal teams. Always compare the latest version you receive against the version you last sent. Especially if you've gone through three or more rounds. Comparing the wrong versions — say, Draft 5 against Draft 3 instead of Draft 4 — means you miss everything that changed in the intermediate round. That's how silent modifications make it into execution versions.

A "blackline" is the legal industry's term for this comparison output. Some lawyers use "redline" and "blackline" interchangeably; technically a redline is the actively-tracked working document, while a blackline is the after-the-fact comparison between two versions.

Inspect Document and clean up metadata before you send

This one is critical and almost universally underused.

Word documents carry hidden metadata: author names, edit timestamps, prior reviewer comments, deleted text fragments, embedded file paths, the works. When you send a redlined contract to a counterparty, all of that travels with it — including, sometimes, the internal commentary your team wrote about them.

Before sending any contract externally:

• Click File → Info → Check for Issues → Inspect Document.
• Run all checks. Word will report on hidden text, document properties, comments, revisions, and personal information.
• Remove anything you don't intend the recipient to see.

The ABA Model Rules of Professional Conduct have ethics opinions warning lawyers about metadata leakage in redlined documents. It's not just a courtesy — it's a professional responsibility issue for legal teams. And it's a security issue for everyone else.

Track changes by author color

When multiple reviewers are working on the same document, the default Word colors can become indistinguishable. Customize per-reviewer colors via File → Options → Trust Center → Trust Center Settings → Privacy Options → uncheck "Remove personal information from file properties on save" if it's enabled (this preserves authorship metadata you actually want to keep visible internally).

For external versions, re-enable that option to scrub author names before sending out.

The five mistakes that turn redlining into legal exposure

I've seen each of these cost real deals. Avoid them.

Mistake 1 — Accepting all changes without review. Already covered. The most dangerous button in Word.

Mistake 2 — Comparing the wrong versions. Always compare sequential versions (v3 vs v2, not v3 vs v1). Skipping a round means you miss everything that changed in the intermediate draft.

Mistake 3 — Mixing clean drafts with redlined versions in the same workflow. If your team is working from both a clean draft and a redlined version simultaneously, you'll lose changes. Designate one source of truth — the redlined version — and consolidate all edits there.

Mistake 4 — Disappearing redlines via the Reject button. Strike through manually with backspace instead of clicking Reject. Preserves the audit trail. Signals your position clearly to the other side.

Mistake 5 — Sending a document with metadata you didn't mean to share. Inspect Document before every external send. Especially for redlines that include internal team comments about the counterparty.

What to actually look for when you redline

The mechanics of Track Changes are the easy part. Knowing what to redline is the hard part — and it's where security teams have to be in the room, not just legal.

In SaaS contracts specifically, the clauses where breach-of-contract risk concentrates are well known: limitation of liability, breach notification timing, sub-processor management, SLA enforcement, indemnification scope, and AI-specific obligations. I've written a dedicated breakdown of breach of contract in SaaS agreements that walks through each of those in detail.

Two general principles that apply to almost every contract redline:

First, the limitation of liability clause is the single highest-leverage thing you'll ever redline. Vendors typically cap exposure at 12 months of fees paid. On a $400K SaaS deal that holds 2 million customer records, that math doesn't work in your favor — the cap is $400K against breach exposure that runs into the hundreds of millions. Push for "supercap" categories (data breach, gross negligence, willful misconduct, IP infringement) that sit outside the cap or at 3x–5x the regular cap.

Second, breach notification timing is almost always written in the vendor's favor. Most vendors propose 72 hours from "confirmation." Push for 24–48 hours from discovery — and define discovery clearly. The difference between confirmation and discovery can be weeks, and your own regulatory clocks won't wait.

When Word alone stops scaling

Here's the thing about redlining manually in Word. It works fine for a handful of contracts a quarter. It breaks down completely once your volume crosses about 30–50 contracts per quarter, or once your team can't reliably enforce a consistent playbook across multiple reviewers.

Most legal and security teams hit that wall and don't realize it. They keep redlining manually, the cycles get longer, the deal velocity drops, and senior reviewers start spending weekends on first-pass review instead of strategic negotiation.

This is where AI-native contract redlining changes the math.

The category split is worth understanding. AI add-ons for Word — tools like Spellbook, Juro's AI Review Agent, Wordsmith — sit inside the Word document and flag clauses against a playbook in real time. Useful, especially for legal teams that want to keep working in Word.

Then there's AI-native redlining — what we're building at Cyberbase. The difference: AI-native systems weren't bolted onto Word or a CLM. They were designed from the ground up assuming the AI does the heavy lifting on first-pass review, the playbook stays current automatically, and security teams co-own the negotiation alongside legal — not as after-the-fact reviewers.

Our customer Augment Code is a useful proof point. Across their contract program, our Context Engine helped save 743 hours of senior legal and security review time across 155 contracts at a 13:1 ROI. Their team didn't get smaller. They got faster — and the contracts that actually deserved senior judgment got it, because the routine pattern-matching was handled by the AI before anyone opened the document.

That's the version of contract redlining I want every legal and security team to have access to. Not an assistant. An AI-native function that takes your playbook, your historical positions, and your risk tolerance, and applies them consistently across every contract that hits your queue.

Want a human-led layer first?

Some teams aren't ready to go AI-native on day one. They want experienced humans driving the contract review process while they build muscle memory. Fair.

Our partner firm YSecurity, provides advisory and vCISO services with deep contract-review experience. Jon McLachlan — our Chief Security Officer and YSecurity's founder — has personally negotiated hundreds of these agreements as an enterprise CISO. Worth a conversation if you want a human-led process that matures into AI-native over time.

Get started

Three concrete moves you can make today:

First, audit your last five contracts against the five mistakes section above. Specifically: did anyone Accept All Changes without reviewing? Are there metadata fragments in any external version? Were sequential drafts compared correctly? You'll usually find at least one issue worth flagging to your team.

Second, host your SOC 2 reports, security policies, and DPAs on a free Cyberbase Trust Center. It's the single best way to reduce DDQ ping-pong and accelerate your sales motion. Most competitors charge $6K–$15K per year for the equivalent. We don't. Setup takes about 30 minutes — no credit card.

Third, if you'd like to walk through how AI-native redlining changes the math for your team — including how the Context Engine learns your playbook from your historical contracts — grab 15 minutes on the calendar. Founders run those calls personally. No SDR layer.

The redlining hygiene you build this quarter compounds for years. Worth getting right.

Ready to redline smarter?

Spin up a free Trust Center in 30 minutes — no credit card required. Most competitors charge $6K to $15K per year. We don't.
→ Try Cyberbase free

Want to walk through your contract redlining workflow with me? Grab 15 minutes — founders run these calls personally. We'll look at your highest-volume contract types and where AI-native redlining can compress your cycle time.
→ Book a 15-minute call

Need a human-led advisory layer first? Our partner firm YSecurity provides vCISO and contract-review services led by Jon McLachlan, who has negotiated hundreds of enterprise SaaS agreements as a CISO.