Compare two versions of a contract and catch every change that matters

Word processors compare text character by character. That works for small edits in the same file, and breaks down quickly in real negotiations:

• Renumbered sections. A new clause 4 shifts every later number, and the comparison flags hundreds of changes that are not real.
• Moved text. A limitation moved from Section 9 to an exhibit appears as one deletion and one insertion, far apart.
• Different files. You have a signed PDF and their new Word draft, or a scan and a typed copy.
• Meaning without wording. "Thirty (30) days" became "one month"; "shall" became "may". Small in characters, large in effect.

An AI comparison works at the level of meaning: it lines up clauses by topic rather than by position and reports what changed in substance, with the page in each version.

1. 1Name both files clearly. "MSA our version v4" and "MSA counterparty draft 2026-10". The names appear in every citation.
2. 2Use the right baseline. Compare against the last version you sent, not the first draft. Otherwise you re-review changes already agreed.
3. 3Include exhibits that changed. Pricing schedules and data processing exhibits often carry the most important edits.
4. 4Check scans. If one version is scanned, it is read with OCR. Make sure key pages are legible.

1. 1Add both versions to one space and open compare documents.
2. 2Choose the topics to compare. Start with a standard set (below), and add topics specific to the deal.
3. 3Run the comparison. You get a table with one row per topic and one column per version, each cell with its citation to the page.
4. 4Read every row marked as changed. Click both citations to see the passages side by side.
5. 5Ask follow-up questions. "Does the new version still exclude confidentiality breaches from the cap?" in the same thread, with citations to both files.
6. 6Write the change list. One line per substantive change: clause, old position, new position, page in each version, your recommendation.
7. 7Export the table to XLSX or CSV if counsel or the business owner works in a spreadsheet.

• Limitation of liability. The cap amount, the multiple of fees, the period it is measured over and every carve-out.
• Indemnities. Who indemnifies whom, for what, and whether the indemnity is capped.
• Term, renewal and termination. Auto-renewal, notice periods, termination for convenience and the effects of termination.
• Payment terms. Days to pay, late fees, price increases on renewal, currency.
• Data protection and confidentiality. Use of data, subprocessors, breach notification periods, return or deletion on exit.
• Service levels and remedies. Uptime commitments, credits, and whether credits are the sole remedy.
• Assignment and change of control. Whether either party can assign the agreement, and what happens on acquisition.
• Governing law and disputes. Law, venue, arbitration.
• Definitions. A changed definition of "Confidential Information" or "Fees" changes every clause that uses it. Always compare the definitions section.

• Watch modal verbs. "Shall" to "may", "will" to "will use reasonable efforts to" are substantive.
• Watch qualifiers. "Material", "reasonable", "without undue delay" all soften an obligation.
• Watch cross references. A clause may be unchanged while the section it refers to has changed.
• Treat silence as a change. If a clause present in your version is missing from theirs, the comparison shows it with the passage from your version and no matching passage in theirs. Removal is often the most important edit.

Each statement in the comparison carries a citation that has been checked in code to exist on the cited page and contain the quoted text, so you are never sent to a page that does not say what the table claims.

ChatDocument compares 2 to 5 documents at once. That helps when you want to see your template, your last draft and their latest draft side by side, or the same clause across several supplier agreements. A comparison counts as 3 questions on any plan. For pulling one set of terms from many signed agreements, extract contract terms to Excel is the better method.

Keep the output short. For each substantive change:

• Clause and topic, for example "9.2 Limitation of liability".
• Our version, with page.
• Their version, with page.
• Impact in one sentence.
• Recommendation: accept, reject, or counter with specific wording.

A list like this lets counsel spend time on the five changes that matter instead of rereading forty pages. For the wider review process, see AI contract review.

Here is how a typical review runs on a software services agreement that came back from a customer's procurement team.

1. 1Baseline. You upload your version 4, the one you sent two weeks ago, and their returned draft. Both are named with the date.
2. 2First pass. You compare the standard topics. The table shows changes in four rows: liability, payment terms, termination and data protection. The other rows are marked unchanged, each with the passage from both versions so you can confirm in a click.
3. 3Liability. Their version raises the cap from twelve months of fees to twenty-four and adds data breaches to the carve-outs. Both passages open highlighted on their pages.
4. 4Payment. Days to pay moved from 30 to 60. A follow-up question confirms the late fee clause was deleted, citing your version and showing no matching passage in theirs.
5. 5Termination. A new right to terminate for convenience on 30 days' notice appears in their draft. You ask whether a refund of prepaid fees is mentioned, and the answer cites the exact sentence.
6. 6Data protection. Breach notification changed from "without undue delay" to "within 24 hours". Small in words, significant in operations.
7. 7Change list. Four lines, each with both page references and a recommendation, go to counsel and the account owner the same afternoon.

The document review that used to fill an afternoon becomes a focused discussion of four points.

Who should see the comparison

• Counsel needs the change list and both citations for each change.
• The business owner needs the commercial impact: price, payment, termination.
• Security or IT needs the data protection and service level rows.

Sharing the answer by link keeps the citations attached, so each reader can open the passages without asking for the files.