How to Redline in Google Docs (And Why Lawyers Outgrow It)

Google Docs is fast, collaborative, and free. For internal memos, project plans, and meeting notes, it works well. But when a contract arrives and someone asks you to "redline this," Google Docs starts showing its limits.

This is not a knock on Google Docs. It is a different tool built for a different purpose. Understanding where it works for legal markup, where it doesn't, and when to switch to a dedicated comparison tool saves time and prevents mistakes.

This post walks through how to redline in Google Docs, what the built-in comparison can and cannot do, and where lawyers outgrow it.

How to use Suggesting mode for redlining

Google Docs has a built-in feature that works like Track Changes in Word. It is called Suggesting mode.

Turning on Suggesting mode

1. Open the document in Google Docs.
2. In the top right corner of the document (below the toolbar), find the editing mode button. It defaults to "Editing" (pencil icon).
3. Click it and select "Suggesting."
4. Every edit you make now appears as a suggestion: insertions in colored text, deletions in strikethrough.

Collaborators see your suggestions and can accept (checkmark) or reject (X) each one. Each suggestion shows your name and a timestamp. This is the core redlining workflow in Google Docs.

What Suggesting mode tracks

• Text insertions (shown in colored text)
• Text deletions (shown in strikethrough)
• Some formatting changes (shown as suggestions with descriptions like "Format: bold")

What Suggesting mode does not track

• Table cell changes (edits in tables are tracked poorly or not at all)
• Image insertions, deletions, or replacements
• Style changes (paragraph style, heading levels) in a granular way
• Moved text (shows as deletion + insertion, not as a move)
• Header and footer changes

For simple text markup on a short document, Suggesting mode works. For a 30-page MSA with tables, defined terms, and cross-references, the gaps add up.

How to compare two documents in Google Docs

Google Docs has a less well-known comparison feature. It compares two documents and produces a third document showing the differences.

How to use Compare documents

1. Open the base document (the version you consider "original") in Google Docs.
2. Go to Tools > Compare documents.
3. Select the second document from your Google Drive.
4. Optionally add an attribution label (a name for the comparison).
5. Click "Compare." Google Docs creates a new document showing differences as suggestions.

The output looks like a document with Suggesting mode applied: insertions in colored text, deletions in strikethrough. You can accept or reject each change individually.

What the comparison catches

• Text additions and deletions at the paragraph level
• Basic word-level differences within paragraphs

What the comparison misses

• Formatting-only changes (font, size, color, spacing)
• Table content changes (often garbled or missed entirely)
• Image changes
• Moved paragraphs (shown as delete + insert, not as moves)
• Header/footer differences
• Numbering changes

The comparison also only works between two Google Docs files. If one of your documents is a .docx file, you need to upload it to Google Drive first, which introduces a format conversion step that can itself cause differences.

Five limitations lawyers hit

Google Docs comparison works for simple documents. Here are the five places where legal work outgrows it.

1. No formatting change detection

Contracts use formatting to convey meaning. A heading that gets demoted to body text changes the document structure. Bold text on a defined term signals its first use. Indentation levels distinguish main obligations from sub-obligations. Google Docs comparison does not detect any of these formatting changes. If someone reformats a section without changing the words, the comparison shows nothing. For legal review, this is a blind spot.

2. Tables are unreliable

Many contracts include tables: pricing schedules, SLA matrices, milestone timelines, disclosure schedules. Google Docs comparison handles table changes poorly. Changes within table cells may not be detected, row insertions and deletions may be garbled, and the resulting output can be harder to read than the original documents. If a contract has material terms in tables, Google Docs comparison is not reliable.

3. No change classification

Google Docs shows every change the same way: colored text for insertions, strikethrough for deletions. A comma deletion gets the same visual treatment as a liability cap removal. There is no classification by importance, no filtering by change type, and no way to separate formatting noise from substantive edits. On a 30-page contract with 80 changes, you review all 80 with equal effort or you guess which ones matter.

4. Format conversion artifacts

Most legal documents are exchanged as .docx files. To compare them in Google Docs, you upload them to Google Drive, which converts them from .docx to Google Docs format. This conversion can introduce differences that aren't in the original documents: changed numbering, shifted indentation, lost styles, reflowed tables. When you then compare the two converted documents, the comparison shows conversion artifacts alongside real changes. Separating the two requires reviewing every difference manually.

5. No move detection

When a paragraph is moved from one section to another, Google Docs comparison shows a deletion at the original location and an insertion at the new location. It does not connect the two as a move. In a contract where a clause was relocated (perhaps from the confidentiality section to the general provisions), this matters. Without move detection, the reviewer sees what looks like a deleted clause and a new clause rather than a relocated one. That misreading can lead to unnecessary pushback in negotiation.

When Google Docs is good enough

Not every document needs a dedicated comparison tool. Google Docs works well enough when:

• The document is text-only with no tables. Letters, simple NDAs, term sheets with no pricing grids, and internal policy documents are often text-only. Google Docs catches text changes reliably.
• Both versions are already in Google Docs. If you drafted in Google Docs and the counterparty returned edits in Google Docs, there is no format conversion to worry about. The comparison is between two native files.
• The document is short (under 10 pages). On a short document, even a noisy comparison is manageable. You can review every change individually without needing classification or filtering.
• Formatting differences don't matter. If you only care about whether the text changed (not how it's formatted), Google Docs comparison gives you what you need.
• You are comparing internal drafts. For tracking your own team's edits (not adversarial negotiation), the stakes are lower and the limitations matter less.

When to switch to a dedicated tool

Switch to a dedicated comparison tool when any of these apply:

• The source documents are .docx files. If both parties are working in Word, compare the .docx files directly rather than converting to Google Docs first. The conversion step loses information and introduces artifacts.
• The contract has tables. Pricing schedules, SLA tables, disclosure schedules, and asset lists need reliable table comparison. Google Docs does not provide it.
• The comparison has more than 20 changes. At that volume, you need change classification or filtering to review efficiently. Without it, you are reading 20+ changes of unknown significance in order.
• You need to detect formatting changes. If the counterparty might have changed styles, numbering, indentation, or font properties, you need a tool that detects these differences.
• It's an adversarial negotiation. When the counterparty's edits are not friendly suggestions but strategic moves, you need a comparison you can trust completely. "Probably caught everything" is not sufficient.

A practical workflow for mixed environments

Many teams use Google Docs for internal work and Word for external exchanges. Here is a practical workflow for handling both.

When you draft in Google Docs but exchange in Word

1. Draft and collaborate in Google Docs using Suggesting mode for internal edits.
2. When ready to send externally, export as .docx (File > Download > Microsoft Word).
3. Review the exported .docx for conversion artifacts before sending.
4. When the counterparty returns their marked version, compare the two .docx files using a dedicated comparison tool.
5. Do not convert the returned .docx back to Google Docs for comparison. Compare in the native format.

When both parties use Google Docs

1. Use Suggesting mode for the first round of edits.
2. If you need a clean comparison between versions, use Tools > Compare documents.
3. Review the comparison output for completeness. Check tables and formatting manually if the document includes them.
4. For high-stakes or complex documents, export both versions as .docx and compare using a dedicated tool for a more reliable result.

The key principle: compare in the format that the documents will be exchanged in. If the final contract will be signed as a Word document, compare Word documents. If both parties are genuinely working in Google Docs end to end, use Google Docs comparison with an awareness of its limitations.

The bottom line

Google Docs Suggesting mode is a serviceable redlining tool for simple, text-only, internal documents. Google Docs Compare documents is a basic comparison feature that works for straightforward cases. Neither is built for the demands of legal contract review: table comparison, formatting detection, change classification, and move detection are missing or incomplete.

If you are a lawyer who works primarily in Google Docs, you are not doing anything wrong. But when a 30-page MSA arrives as a .docx and the partner asks you to "compare this against last week's version and flag what changed," Google Docs is not the right tool. Export the files, compare them in a tool built for the job, and spend your time analyzing the changes rather than worrying about whether you caught them all.

If you want a comparison tool that handles .docx files natively, classifies changes by importance, and filters formatting noise from substantive edits, try Clausul.

Frequently asked questions

Can you redline a contract in Google Docs?

You can track changes using Suggesting mode (the pencil icon in the top right, or Edit > Suggesting). Every edit you make appears as a colored suggestion that other users can accept or reject. This works like Track Changes in Word and is adequate for simple edits to short documents. Google Docs does not have a built-in Compare Documents feature equivalent to Word Compare, so if you receive two separate files and need to see the differences, you need a separate comparison tool.

How do I compare two documents in Google Docs?

Google Docs has a basic comparison feature under Tools > Compare documents. It compares the current document against another Google Docs file and produces a new document showing the differences as suggestions. The comparison is text-only: it does not detect formatting changes, does not handle tables well, and does not classify changes by type or importance. For simple text documents it works. For contracts with structured formatting, tables, and defined terms, the output is often incomplete.

Why do law firms use Word instead of Google Docs?

Three main reasons. First, the legal industry standardized on Word decades ago, and most contracts, court filings, and regulatory documents are exchanged as .docx files. Second, Word has more sophisticated formatting, numbering, and styles support that legal documents rely on (automatic paragraph numbering, cross-references, fields). Third, Track Changes in Word embeds change metadata (author, date, change type) that many legal workflows depend on. Google Docs Suggesting mode tracks fewer details. These factors create switching costs that keep most firms on Word even when Google Docs would be sufficient for general business documents.

Is Google Docs Suggesting mode the same as Track Changes?

Conceptually yes, practically no. Both record edits so reviewers can accept or reject them. But Track Changes in Word records more metadata (author name, exact timestamp, change type including formatting changes, moves, and table edits). Suggesting mode in Google Docs records text insertions and deletions but does not track formatting changes, does not track moved text as moves, and has limited support for table change tracking. For simple text edits, the difference is negligible. For complex contract markup with formatting, tables, and cross-references, Track Changes captures more.

Can I convert a Google Doc to Word for redlining?

Yes. File > Download > Microsoft Word (.docx) exports the document as a Word file. The export preserves most text and basic formatting, but complex elements like automatic numbering, custom styles, headers/footers, and cross-references may not convert cleanly. If you are working on a document that will eventually be exchanged as a .docx, it is better to work in Word from the start. If you draft in Google Docs and convert to Word for redlining, always check the exported file for formatting artifacts before comparing.

What is the best way to compare a Google Doc and a Word document?

Export the Google Doc as a .docx file (File > Download > Microsoft Word), then compare the two .docx files using a dedicated comparison tool. This gives you the most accurate comparison because both files are in the same format. Comparing a live Google Doc against a Word file directly is not supported by most tools. The export step adds a minute to the workflow but avoids format-mismatch issues that cause false positives in the comparison output.

---