Combine vs Compare vs Consolidate: The Three Redline Workflows Legal Teams Confuse
A legal ops lead sends the same NDA draft to four stakeholders: legal, procurement, security, and finance. A week later she has four Word files back, each with a different set of tracked changes. Now she has to produce a single go-forward master.
She opens Word and looks at the Review tab. There is a Compare option. There is also a Combine option. She has heard vendors talk about "consolidating redlines" at a conference. Are these three names for the same thing? Three different things? Which one does she want?
They are three different things, and confusing them is one of the most common reasons multi-reviewer workflows go sideways. This post defines each one, explains when each is the right tool, and is honest about where each one breaks down. We will also be explicit about which of these Clausul supports today and which we do not.
Compare: A vs B, what changed?
Comparison is the simplest workflow in the family and the one most lawyers reach for first. You have two versions of the same document. You want to see what is different between them. You run a comparison tool and you get a third document — the blackline — that shows the additions and deletions inline.
The underlying question compare answers is: "what is different between A and B?" It is not concerned with who made the changes, whether the changes were tracked, or whether the two documents came from the same source. It treats A as the baseline and B as the comparison target and reports the delta.
Word ships a built-in Compare feature (Review tab → Compare → Compare). It works. The reason standalone comparison tools exist — Litera Compare, Draftable, and clausul — is that Word treats every difference equally: formatting noise shows up alongside material edits, moved paragraphs render as delete-plus-insert, and a 60-page contract with 200 differences becomes a manual triage exercise before you can even start reviewing substance.
Use comparison when you have exactly two versions of the same document and you want to know what is different between them. If you have multiple reviewers with separate markups, comparison is the wrong tool — you would have to run it once per reviewer and still be left with the merge problem.
Combine: merge two sets of changes
Word's Combine feature is subtly different from Compare, and the difference matters. Compare looks at two finished documents and asks "what is the difference between these two snapshots?" Combine looks at two documents that both contain tracked changes and asks "how do I merge both sets of changes into one document without losing either?"
The canonical use case is: you send a draft to a reviewer with Track Changes on. They return the file with their edits marked up. You want to fold their edits into your master alongside any edits you already had in progress. Combine takes the master and the reviewer's copy, identifies both sets of tracked changes, and produces a merged document where both are preserved with attribution.
Combine handles two documents at a time. That is by design — the algorithm is a two-way merge. If you have four reviewers, you run Combine three times: master + reviewer 1, then the result + reviewer 2, then the result + reviewer 3. Each step is a fresh invocation and each step is a new opportunity for something to go wrong. This is the workflow most lawyers eventually stop trusting once they try to run it on a real batch.
Consolidate: many reviewers, one master
Consolidation is the category name for what lawyers need when Combine runs out of runway. The workflow is "many-to-one": you have one original draft and multiple reviewed copies, and you want a single master that reflects all the changes with attribution preserved, ideally in a single operation rather than a chain of two-way merges.
The vendors who sell this call it consolidation explicitly. Litera Review is built around this workflow — consolidate changes from multiple collaborators into a single go-forward document. The fact that this is a marketed, paid product category is the market's answer to the question "is Combine enough?" The answer is "no, not at scale."
What consolidation adds on top of repeated Combine operations:
- All reviewers in one pass. You upload the original plus N marked-up copies and get a single consolidated output, not a chain of intermediate merges.
- Attribution preserved. Each change in the consolidated output is tagged with the reviewer who originally made it, so the person merging knows whose change is whose.
- Conflict surfacing. When two reviewers edit the same provision in incompatible ways, the consolidation surfaces the conflict rather than silently picking one. The merger decides what stays.
This is a distinct workflow from comparison. A comparison between the original and one reviewer's copy tells you what that reviewer did. A consolidation tells you what all your reviewers did and gives you a single document to hand forward.
Transfer: negotiated edits onto a new base
Transfer — sometimes called "redline transfer" or carry-forward — is a fourth workflow that the others do not address. The setup: you negotiated edits against version 1 of a draft. The counterparty comes back with version 2, which is not a tracked-change revision of your version 1 but a completely re-based document (their own template, a refreshed draft, a new boilerplate). You need your negotiated edits from v1 applied to the new v2.
Comparison does not solve this: a compare of your v1 against their v2 will show every difference between the two documents, burying your negotiated edits under structural differences. Combine does not solve it either: Combine requires the two documents to share a common base, which is exactly what the refreshed draft has broken.
Transfer works by extracting your individual edits from v1 and matching each one to the corresponding provision in v2 by semantic content rather than by position, then applying the edit in the context of v2's phrasing. The output is v2 with your negotiated edits applied as native Word tracked changes. See our post on transferring tracked changes between documents for the mechanics.
Which one do you actually want?
The short version:
- Two versions of the same document, want to see the delta? Compare.
- Two people edited the same draft, want to fold their changes together? Word's Combine (for two reviewers; painful beyond that).
- Multiple reviewers, want one master? Consolidation. Litera Review is the established product for this.
- Your edits in one document, want to apply them to a different base? Transfer redline.
Using the wrong tool from this list is where most multi-document redline workflows start to leak. Comparing instead of consolidating gives you noise. Combining instead of comparing gives you mis-attributed changes. Comparing instead of transferring buries your negotiated edits under structural drift.
What Clausul supports (and does not)
We build DOCX-native redline transforms, and we are going to be explicit about which of the four workflows above we ship today.
We ship compare. Upload two .docx files, get a blackline with material changes surfaced first, moves detected, and formatting noise sorted out of the way. See the compare page or legal blackline.
We ship transfer. Upload a negotiated source and a new target base, get your edits applied to the new base with semantic matching. See the transfer page or carry-forward redlines.
We do not ship many-to-one consolidation yet. If your workflow is "gather redlines from four reviewers and produce a single master with attribution preserved," Clausul is not yet the tool. For small batches, Word's Combine works. For larger ones, Litera Review is the established product in the space. This is a workflow we may add, but we are not going to claim we ship it until we do.
If consolidation is your primary pain today and you are evaluating tools, tell us — it changes how we prioritise the roadmap.
Frequently asked questions
What is the difference between Combine and Compare in Word?
Word's Compare feature takes two documents and produces a third document showing the differences between them as tracked changes. Combine also takes two documents, but it is designed to merge tracked changes from multiple reviewers — if one reviewer edited a copy with tracked changes on, Combine lets you fold those changes into the master without losing them. The core distinction: Compare is for "what is different between A and B?" Combine is for "merge these two sets of changes into one."
Can Word Combine handle more than two documents at once?
No. Microsoft's guidance is explicit: Combine merges two documents at a time. If you have four reviewers returning four copies of the same draft, you run Combine three times — master + reviewer 1, then the result + reviewer 2, then the result + reviewer 3, and so on. Each step is a new Combine operation. This is the workflow most lawyers recognise as fragile: one mis-click and you have mixed the wrong authorship metadata into the master.
What does "consolidate redlines" mean?
Consolidation is the category name for many-to-one redline workflows: you have an original draft, multiple reviewers have returned marked-up copies, and you want a single go-forward master that reflects all their changes with attribution preserved. Legal-industry vendors market this as a paid workflow category because Word's Combine feature, while technically capable, scales poorly past three or four reviewers.
Does Clausul consolidate redlines?
Not yet. Clausul currently supports two DOCX-native redline transforms: compare (what changed between A and B) and transfer (apply the edits you negotiated in A onto a structurally different target B). Many-to-one consolidation is an adjacent workflow we may add, but we are not going to claim we ship it before we do. For the use case today, Word Combine works for small batches, and Litera Review is the established tool for larger consolidation workflows.
When should I reach for each tool?
Compare when you have two versions of the same document and want to see what changed. Combine (or a consolidation tool) when multiple reviewers have marked up the same draft and you need a single master. Transfer when you have negotiated edits in one document and need to apply them to a structurally different document — for example, when the counterparty switches templates mid-negotiation. The three workflows solve different problems, and using the wrong one generates avoidable work.