How to Compare Two Contract Versions Before You Sign

Negotiation is done, the envelope looks clean, and you are about to click Sign by eye. You still need to know how to compare two contract versions before signing when the vendor says they just accepted Track Changes: name the last agreed file and this execution copy, accept leftover markup, run Word Compare into a third document, then stop the click if anything unexpected moved.

In August 2026, Soren — ops, 24-person UK B2B — has a vendor MSA — a master services agreement vendors hang order forms on, after three redline rounds. Friday 16:40 the AE sends DocuSign: clean execution copy, legal already accepted everything. Soren still has the last agreed Word file with the 30-day notice they fought for. He has never run Review → Compare. Typical mistake — the hidden risk: treating a page with no red ink as last agreed.

A clean copy is not a security control — it is a new file. Clausul (February 2026) has no published industry statistic; practitioners report a mismatch in roughly one in ten to fifteen execution copies. Most misses are quiet: a stale number, a zombie clause, a definition that lost a carve-out.

Disclaimer: Checkory provides AI support, not legal advice. Consult a qualified lawyer for binding decisions.

Which two files are you actually comparing?

Last agreed is the file from the final round both sides approved — not the redline before that, not Soren’s internal comments, not a random Agreement_v4_final_CLEAN. This file is the DocuSign they just sent. Write both names and dates on one line before anyone opens the envelope.

If you cannot find last agreed, stop. Who owns it: the person who sent the last outbound “we agree” file, or the shared matter folder. How you assembled that packet — the exact file set that will be signed — is in how to prepare a contract packet for first-pass review. This page only asks whether this signature file matches it.

• Do: write two filenames and dates before DocuSign.
• Do not: open the envelope and “just check page 1.”

Why accept leftover markup before you run Compare?

Eyeballing two PDFs misses shall versus may and a one-cell price. Open copies. Accept All Changes in both files, save, then Review → Compare → Compare two versions (legal blackline). Original is last agreed. Revised is this execution file. Show changes in a new document.

Microsoft Support: the blackline is a third new document; the sources stay unchanged. If either file still has tracked changes, Word warns and can treat them as accepted — dirty inputs lie. LexDraft (June 2026): Compare is not Combine. Reverse Original and Revised and every insert becomes a delete. More >>: keep insertions, deletions, moves and tables; uncheck formatting; word level; New document.

DiliTrust: redline is the conversation; blackline is the audit. Read All Markup. Vaquill: their attached redline only shows what they chose to track. Never write results into Original or Revised.

• Do: generate your own Compare from the two saved files.
• Do not: trust their attached redline, Combine two reviewers, or scroll two PDFs.

Which numbers do you scan first — dates, caps, notice, definitions?

Do not start at page 1. Scan the change count, then search the blackline for figures, day-counts, shall versus may, and defined-term edits. A one-word “not” or a 30-to-15-day flip is a High flag — wording a human must verify before anyone signs — even if the rest is fonts.

Clausul on efficient compare: Word Compare is usually enough under about ten pages; it fails on template restyles, pricing tables and files past thirty pages. Never skip Compare because they said “minor comments only.” Empty of content changes → go to the stop-signature step. A wall of red from a new template: keep formatting off and still finish tables and xrefs.

• Do: read All Markup and triage dates, caps, notice and definitions first.
• Do not: drown in fonts and skip the 30-to-15 flip.

How do you check exhibits and tables cell by cell?

Word often paints a pricing schedule as deleted and reinserted, so a £175 versus £150 cell hides in the wreckage. List every table, schedule and exhibit — an attached schedule or appendix — in both files. Same count and columns? Then open last agreed and this file side by side on pricing, SLA and milestones.

Clausul on tables: a row insert, delete or merge is unreliable. Cross-check body versus schedule. In practice, body “£10,000” versus table “£12,000” is a content miss. A new template may re-letter exhibits — treat that as substance.

• Do: walk pricing, SLA and milestone cells one by one.
• Do not: treat a whole-table red blob as “just formatting.”

What breaks when they renumber after cleanup?

Compare cannot verify that “Section 12.1” still points at the right target. If the target renumbers and the pointer text is unchanged, Compare shows nothing. Exhibit letter shifts — a new Exhibit C — break “Schedule C.” This step is manual even when the blackline looks short.

Clausul on cross-references: list added, deleted or renumbered sections, then search the execution copy for each “Section”, “Schedule” and “Exhibit”. Open the target. Hunt orphans. Spellbook: the returned clean copy is the diligence step — check no undisclosed language was added, then check the pointers.

• Do: search every moved section number before Sign.
• Do not: treat renumbering as formatting.

When do you stop the signature if the clean copy drifted?

Zero unexpected content change means you may proceed to sign the clean file — not the still-redlined one. Any unexpected delta stops the click. Email one factual line: “Section 7.3 in the execution copy shows 15 days; the last agreed file shows 30. Please correct and resend.” Signature binds the drifted file.

LegalClarity: do not sign a still-redlined file. If every delta favours them, or a negotiated point reverted, escalate to counsel — a qualified lawyer, not the chatbot. New boilerplate that was not in last agreed goes back. How you got to last agreed is how to redline a vendor contract before signing — this page is only the pair check.

Success bar: two named files, a Compare empty of unexpected content or a written catch, and a decision — send back, escalate, or sign the clean file. Workflow: name the pair → Accept then Compare → triage dates, caps, notice, definitions → tables cell by cell → xref audit → stop Sign if drifted. After the blackline, Checkory can run a first-pass — a first machine pass that extracts clauses before a human reads every page — on the execution PDF. A human still owns the pair.

• Do: send one factual catch and wait for a corrected file.
• Do not: click Sign because “we already agreed.”