When someone sends you "the latest version" of a document, it is natural to look for the changes they told you about, tick them off, and get to work. That is exactly the moment something can slip through. The change note tells you what the sender meant to change. It does not tell you what else changed by accident.
What Happened
A client sent us an updated version of a document we build their email campaign from. The note listed the changes and said to build from this file only. We checked, and only some of the promised changes were in it. The note also pointed to a section as a landmark, and that section was not in the file at all.
The first clue was the file size. The new version was meant to add content, yet it came back slightly smaller than the old one. Comparing the two versions side by side showed why: a whole section of instructions was in the older copy and gone from the new one.
Nobody did anything wrong on purpose. The client had simply exported from a copy of the document that had already lost that section. It is the kind of mistake anyone makes.
Why it mattered: the missing section was the only written guide for one personal line that goes into the first email of the campaign. That campaign was set up to send on its own, with no one approving each email. Building from the new file as instructed would have quietly removed the rules for something that goes out to many people, with nothing in place to catch it.
The Check We Now Use
Every time a client sends a revised version of a document we work from, we run through the same short routine.
Check the new file's size against the old one first. More content coming back smaller means something was removed.
Put both versions side by side and compare the whole text, not just the parts they said they changed.
Treat the change note as a claim to confirm, not a full list of what is different.
If something is missing, name it, and reassure them you still hold the older copy.
One more clue is worth knowing on its own: if the note mentions a section that is not in the file, they almost certainly edited a different copy than the one they sent. Telling them that helps them find the right one.
Looking for Additions vs Checking the Whole Thing
Only checking what they said they changed
- You confirm the new parts arrived
- You trust "nothing else moved"
- Anything removed by accident goes unnoticed
- The work gets built from an incomplete file
Checking the whole document
- The file size flags a problem in seconds
- A side by side comparison shows what left, not just what arrived
- Missing sections are named before any work starts
- The client finds their right copy with no stress
Confirming the additions arrived tells you nothing about what left. That one idea is the whole lesson.
Word Documents Hide More Than You Think
A Word document does not really store pages. It is one long stream of text, and the page count is worked out by whatever program opens it. In this case, the file's own details claimed it was a single page, while Word showed far more. So asking "did you check every page?" is not quite the right question.
To be sure nothing was missed, we check more than the main body of text:
- Footnotes, endnotes and comments
- Tables and text boxes, which a quick search can skip over
- Headers and footers
Then, to prove it end to end, we turn the document into a PDF in Word, pull out the text on every page, and check that each piece of it matches what we read from the file. When nothing on any page is left unmatched, that is proof, not a guess.
A small trap: automatic list numbers and words split across lines in a PDF can look like differences when they are not. Ignore stray numbers and rejoin split words before you compare, or you will chase problems that are not there.
When to Use This Check
- Any document a client sends that you build work from, every time a new version arrives.
- Especially when that work runs on its own with no person approving each step, because there is no second chance to catch a missing rule.
- Any time a note says "nothing else changed".
Common Questions
How do I check what changed in a revised document?
Start by comparing the file size with the previous version. If the new version is supposed to add content but comes back smaller, something was removed. Then compare the full text of both versions side by side, not just the parts the sender said they changed. Confirming the additions arrived tells you nothing about what left.
Can I trust the change note someone sends with a new version?
Treat it as a claim to check, not a full description. People often export from the wrong copy of a document. It is an ordinary mistake and nobody is to blame, but the note can still be wrong. A quick comparison of the two versions settles it.
What should I do if something is missing from a revised document?
Do not quietly build from the shorter version. Stop, tell the sender exactly what is missing, and let them know you still hold the older copy so they do not worry about getting it back. If their note mentions a section that is not in the file, say so, because it usually means they edited a different copy than the one they sent.
Key Takeaways
- A revision that adds content but comes back smaller has lost something. Checking the size takes seconds.
- Compare the whole document, not just the changes you were told about.
- A change note is a claim to check. Wrong copies get sent all the time, and nobody is to blame.
- A note that mentions a section missing from the file usually means a different copy was edited.
- Never quietly build from the shorter version. Stop, name what is missing, and reassure the client you have the older copy.