PDF Proofing: 5 Mistakes That Lead to Reprints (and How to Avoid Them)

A reprint rarely happens because someone cannot design. It happens because the wrong file went to the printer, or the right file was never properly checked. PDF proofing is where most of those errors can be caught, and five mistakes cause the bulk of the trouble.

1. Reviewing on the wrong version

Someone sends a PDF by email, someone else comments on an older copy, and the final file mixes both sets of feedback. The printer receives something nobody fully approved.

The fix: keep every version in one place, label it clearly, and let reviewers see only the current one. A tool that holds version history and a side-by-side comparison makes it obvious what changed between rounds. See How to Compare Two Versions of a Proof.

2. Collecting feedback in six places

Comments arrive by email, chat, a marked-up PDF, a phone call and a sticky note. Something always gets missed.

The fix: ask everyone to comment directly on the proof. Pins and drawn markup show exactly where the issue is, so nobody has to describe a position in words. Moving from email to online review is covered in How to Move From Email and PDF Markup to Online Proofing.

3. Letting conflicting feedback through

One reviewer wants the headline bigger and another wants it smaller. If both comments go to the designer, the designer guesses.

The fix: name one person to collate feedback and resolve conflicts before changes go back. In GoProof this is the gatekeeper role.

4. Skipping the colour and print checks

A PDF looks fine on a laptop and wrong on paper. Colours shift, small text fills in, and a logo sits too close to the trim.

The fix: check colour on a calibrated screen where you can, and put print-specific checks on a list that the reviewer ticks off. GoProof can also run a preflight report against your own checklist, which covers content and brief compliance. It is not a technical print preflight for bleed, fonts or resolution, so keep that step in your production workflow. See How to Check Colour Accuracy on a Proof Before Print.

5. No record of who approved what

When a printed run has an error, the first question is who signed it off. If the answer is a chat message from three weeks ago, nobody can be sure.

The fix: approve in the proofing tool so the decision, the person and the time are logged against the version. That record also protects you when a client disputes a change.

A quick pre-press checklist

• The file is the latest version, and older ones are archived.
• All reviewers have finished, and the gatekeeper has merged the comments.
• Every comment is marked as done or deliberately declined.
• Colour, bleed, fonts and image resolution have been checked.
• The approver has signed off in the tool.

For packaging work, see GoProof for print and packaging.

Try GoProof free for 14 days

FAQs