Most revision problems are discovered too late, not because nobody checked, but because the check happened after approval. A client returns a PDF, someone glances at it, it looks familiar, and it gets signed off. Days later, somebody notices a paragraph that was never agreed, a figure that drifted, or a page that went missing. By then the approved version is the one in force, and unpicking it is awkward for everyone. A short, fixed check before sign-off prevents most of this, and it takes about five minutes.
The check has one rule: compare the returned PDF against the version you sent, not against your memory of it. Compare PDF does the comparison page by page at word level, with highlights for added and removed words and counts of what changed. Your job is to walk the highlights, decide on each one, and only then approve. Memory is generous; a highlight list is exact.
Step one: confirm you have the right pair
Before comparing anything, make sure the two files are the pair you think they are. Open both and check the obvious identifiers: the document title, the date in the footer, and the page count. A comparison between a draft and the wrong final version produces a long, alarming list of differences that are really just two different documents. Worse, comparing a returned file against an older draft than the one you sent hides the most recent round of edits inside a pile of older ones.
File names help here, if you use them consistently. Keeping the sent version untouched matters too: never edit your copy of the sent file after sending it, or the comparison will report your own later tweaks as if the other side made them. The sent version is your baseline. Treat it as frozen from the moment it leaves your inbox, and keep it somewhere you will find it again.
Step two: read the counts before the highlights
The counts give you the shape of the revision before you dive into details. A handful of added and removed words suggests a light touch: a few corrections, perhaps one new sentence. Hundreds of changed words suggest a rework, and you should set aside more than five minutes. A large number of removed words with few additions deserves a specific question: what was taken out, and was its removal agreed?
Page distribution matters as well. Changes clustered on one or two pages are usually a focused edit. Changes scattered across every page may mean the document was reformatted or retyped, which can introduce small errors throughout. In that case, read more slowly, even if the similarity score looks high. The counts and the spread together tell you whether you are reviewing a patch or a new document wearing an old document's title.
Step three: work the highlights in page order
Go through the highlights page by page, and sort each change into one of three buckets: expected, acceptable, or query. Expected changes are the ones you asked for, or that the other side told you they were making. Acceptable changes are small fixes you did not request but can live with, such as a corrected spelling or a clarified heading. Everything else goes into query, and nothing in query gets approved until it has an answer.
Pay particular attention to four categories, because they carry consequences out of proportion to their word count. Numbers: prices, quantities, percentages, and account figures. Dates: deadlines, start dates, and notice periods. Names: people, companies, and places, where one changed letter can point at a different party. Obligations: words like "must", "will", and "should", where a single swapped word can soften or harden a commitment. A changed adjective in an introduction rarely matters. A changed number in a payment clause almost always does.
Worked example: a returned freelance brief
The example below is fictional throughout: invented people, an invented project, and invented figures. A freelance designer, whom we will call Tomas Reid, sends a fictional client a six-page project brief for a brochure, using the invented address tomas@example.org for correspondence. The brief states a delivery date, a page count, two rounds of revisions, and a fee. The client returns the brief with tracked-looking changes in the PDF itself, and Tomas runs the five-minute check before replying.
The counts show a modest revision: a small number of added and removed words, spread over three pages. Working the highlights, Tomas finds the expected change first: the brochure grows from eight pages to twelve, which the client had already mentioned. Then he finds two queries. The revision rounds drop from two to one, which was never discussed. And the delivery date moves a week earlier, which clashes with another booking he holds. Both changes sit inside otherwise untouched paragraphs, and both would have been easy to miss in a skim-read. Because the check caught them before sign-off, Tomas can reply with two precise questions instead of discovering the problem mid-project, when the approved brief would already bind him.
Note what the check did not do. It did not tell Tomas whether twelve pages or one revision round is reasonable. It gave him the complete list of changes, in order, so he could apply his own judgement to each one. That division of labour, tool finds, human decides, is the whole point.
Step four: confirm nothing vanished
Additions get noticed more easily than deletions, because new text draws the eye. Deletions are quieter: a paragraph that is simply gone leaves no mark on the page you are reading, only an absence. The removed-word count is your guard against this. If the count is higher than you expected, search the highlights for removed passages and read each one. Ask whether the removal was agreed, and whether anything else in the document still refers to the deleted passage, such as a cross-reference to a section that no longer exists.
Also check the page count. A returned file with fewer pages than the sent version may have lost a page in handling, or an appendix may have been dropped deliberately. Either way, you want to know before approval, not after. If a page is missing, ask about it explicitly rather than assuming it was an accident. Sometimes it was deliberate and sensible; the point is that the decision should be visible.
Honest limitations
This check compares text. It will not catch a changed photograph, a swapped logo, or a re-laid-out table whose words stayed the same. It also needs a real text layer in both files: scanned pages without text must be OCR-processed first, or the comparison has nothing to work with. And it cannot resolve disagreements. When a highlight shows a genuine difference of intent, the fix is a conversation, not a second run of the tool. If the signed document needs a signature placed on it afterwards, Sign PDF handles that step, and if sensitive passages must be removed for real before the file is shared further, Redact PDF removes text rather than covering it.
FAQs
How long does a PDF revision check take?
For a light revision, about five minutes: confirm the file pair, read the counts, then work the highlights in page order. A heavy rewrite takes longer, and the counts will warn you of that before you start, so you can set aside proper review time instead of rushing.
What should I do about a change I did not expect?
Put it in query and ask about it before approving. Do not approve a document with unresolved queries in the hope of sorting them out later: once approved, the document as returned is usually the version that counts, and reopening it is harder than asking one precise question now.
Can this check catch a deleted page or paragraph?
Yes, through the removed-word count and the page count. A missing page shows up as a large removed count and a shorter document. Check the highlights for the removed passage and ask whether its removal was deliberate before you sign off.
Is comparing PDFs the same as comparing text documents?
The idea is the same, but the tool differs by input. Compare PDF works on PDF files at their page locations. For plain text passages, Text Compare is the matching tool. For a general grounding in document comparison, see how to compare documents.
human review pending client designation