How to Compare Two Contract Drafts

An automated redline is a starting point, not an answer. It shows you which characters changed. It does not tell you which changes matter, which are consequential across the rest of the document, or which were slipped in quietly hoping no one would read the schedules. Comparing two drafts well means reading for effect, not just for difference.

Fix the baseline before you compare anything

The first mistake in comparison is comparing against the wrong version. Before generating a redline, confirm which draft is the true baseline — usually the last version both sides agreed to, not simply the last file in your inbox. Note the status of each version: who sent it, when, and whether it was marked as a proposal or as agreed. If you compare a clean draft against an internal working copy, every difference is noise and you will lose the real changes among them.

Read the parts a redline hides

Comparison tools are good at clause text and poor at the places changes actually hide. Look specifically at:

• Definitions. A single altered definition can change the meaning of every clause that uses the term, without any of those clauses appearing in the redline.
• Numbers and figures. Amounts, percentages, notice periods, and dates change meaning entirely while barely registering as edits.
• Schedules and annexures. Substance is often moved here precisely because reviewers skim them.
• Cross-references. A deleted sub-clause can leave references pointing at the wrong place, or at nothing.
• Deletions. Removed protective language is easy to miss because there is nothing left on the page to catch your eye.

Record each change by its effect, not its location

Build a short change table as you go. For every substantive difference, capture three things: what changed, what its effect is on the client, and who needs to decide whether to accept it. "Clause 9.2 — cure period cut from 30 days to 10 — tighter operational risk on the client — decision for [name]." A list of edits is a description. A list of effects and owners is something the deal team can act on.

Separate the substantive from the cosmetic

Not every change deserves the same attention. Distinguish the differences that shift risk, money, or obligation from those that are drafting tidy-ups — renumbering, formatting, harmless rewording. Marking cosmetic changes as such is not busywork; it tells the reader you looked at everything and consciously set the trivial aside, which is what lets them trust your read of the important items.

Close with the open decisions, not the clean file

A comparison is finished only when the unresolved choices have reached the person authorised to make them. The output of a good comparison is therefore two things: the marked-up draft, and a short note listing the substantive changes, their impact, the decision owner for each, and the questions still open. The clean redline is evidence of the work; the decision list is the work.

Done this way, comparison scales to long agreements without becoming a proofreading marathon. The discipline is to read for what a change does, keep the source versions identifiable throughout, and never let an unresolved point pass silently into a signed document. Where the two versions and the change note live in one place — as they do in a workspace like Juniorlawyer — the reviewer spends their attention on judgment rather than on reassembling which file was which.