How to find what changed between two versions of a PDF

A contract goes out. It comes back with a friendly note saying a couple of minor amendments were made. You now have two documents that are ninety-nine percent identical, and the one percent that differs is the only part that matters.

Reading them side by side feels responsible and is remarkably unreliable. Human attention is poor at this task in a specific and well-documented way: we skim familiar text, and a single altered word inside a paragraph we have already read is almost invisible.

Why manual checking fails

The changes that cause problems are rarely dramatic. A deadline moving from thirty days to fourteen. A liability cap losing a zero. Shall becoming may, which converts an obligation into an option. A not inserted or removed.

Every one of those is a few characters inside a paragraph that otherwise reads exactly as you remember. Your eye recognises the shape of the sentence, confirms it is the one you approved, and moves on. That is not carelessness — it is how reading works.

Automated comparison does not read. It compares, character by character, and it has no expectation of what the sentence should say.

What comparison can and cannot see

Text comparison finds differences in the words: insertions, deletions and replacements. That covers the overwhelming majority of what matters in a contract or a report.

What it handles less well is everything that is not text.

• Changes inside images, including a swapped signature or an altered chart
• Formatting changes that alter emphasis without changing words
• Reordering, which can appear as a large deletion followed by a large insertion
• Changes in scanned documents, where there is no text to compare unless OCR has been run
• Metadata and hidden content, which is not on the page at all

The scanned case is the important limitation. If either version is an image, comparison has nothing to work with. Run recognition on both first, and treat the result with appropriate caution, since you are then comparing two imperfect transcriptions rather than the documents themselves.

A reliable process

1. Establish which version is the baseline and which is the revision, and label the files clearly so they cannot be confused.
2. Run the comparison and read every difference it reports, including ones that look trivial.
3. Pay particular attention to numbers, dates, names and the words shall, may, must, will and not.
4. Check the reported changes against the summary you were given, and ask about anything that was not mentioned.
5. Keep both versions and the comparison result, so there is a record of what was agreed and when.

Step four is the one that earns its place. An undisclosed change is a different kind of signal from a disclosed one, and noticing that the list of edits is longer than the list you were told about is often more valuable than any individual edit.

Small habits that make comparison easier

Ask for changes to be tracked in the source document rather than delivered as a fresh PDF. A tracked-changes file tells you exactly what moved and who moved it, and no comparison is needed.

Keep every version rather than overwriting, and name files so the sequence is unambiguous. Comparing version four against version three is straightforward; reconstructing which file was current in March is not.

And when you send a revised document, list your changes honestly. It costs a minute, it builds the kind of trust that makes negotiations shorter, and the alternative is being asked why an unmentioned amendment appeared in clause fourteen.