Approving the first print proof without a costly reprint
- 12 hours ago
- 3 min read
Introduction
A printer sends a proof, the client glances at it on a phone, replies "looks great", and two thousand brochures arrive with a wrong phone number on the back. Nobody wants to pay for the reprint and both sides have a reasonable case.
The proof stage exists precisely to prevent this, and it fails constantly because it is treated as a formality rather than as the point where responsibility transfers. Getting it right is mostly about being explicit — about what a proof is, what it does not show, and what approval actually means.
1. Approving the first print proof is where responsibility transfers
Both sides should understand that, and usually only one of them does. Close that gap explicitly.
Say what approval means in plain words
Approval means it goes to press as shown and that changes afterwards cost money. State it in the same message as the proof, every time. Keep the wording consistent.
Get it in writing, not verbally
A phone call is not a record. One line of written confirmation against a named, dated proof is what settles a dispute later.
2. Tell them what to check
Clients look at the design. The errors are almost never in the design. Point them at the details instead.
Give them a short, specific checklist
Phone numbers, email addresses, prices, dates, spelling of names, the web address. Six things, listed, take two minutes and catch nearly everything. Put them in the email body.
Ask for a second pair of eyes
Suggest somebody who has not seen it before reads it. Authors cannot proofread their own copy and everybody believes they can. Say it as a standard request.
3. Be clear about what a proof does not show
This is where most disagreements actually originate. Set the expectation in advance.
Colour on a screen is not colour on paper
A monitor is backlit and a press is not. If colour matters, offer a hard proof and say plainly why the screen version cannot be relied on.
Stock, finish and trim
Paper weight, coating, how a fold sits, how much bleed is lost at trim. A digital proof shows none of this, and clients assume it shows everything.
4. Handle the technical issues before proofing
Do not let a file problem become a colour argument.
Resolution, fonts, bleed and colour space
Flag low-resolution images and missing bleed at the file stage, in writing. A logo that will print soft needs raising before approval, not after.
Show the trim and safe margins on the proof
Mark them clearly. Text too close to an edge is the single most common avoidable fault.
5. Make the process easy to follow
Friction in proofing produces careless approvals. Make the ask obvious.
One proof, one clear request, one deadline
Not four versions in a thread. Say which is current and what you need back, and give a date tied to the press slot. Explain what happens if it slips.
Explain the cost of changes at each stage
What a change costs before plates, after plates, and after printing. Clients check far more carefully once they know.
Conclusion
The proof is the moment responsibility transfers, so say so explicitly: approval means it goes to press as shown, changes afterwards cost money, and confirmation needs to be in writing against a named, dated proof.
Tell the client what to check, because errors are almost never in the design — give them six specific items like phone numbers, prices, dates and the web address, and ask for a fresh pair of eyes. Be explicit that a screen cannot show colour, stock, finish or trim loss, raise resolution and bleed problems at the file stage rather than afterwards, mark the trim and safe margins, and send one current proof with one deadline and the cost of changes at each stage.
.png)



Comments