How artwork approval prevents reprints

Artwork approval prevents reprints in two ways: a good proof surfaces mistakes while changing them still costs nothing, and a documented sign-off removes the ambiguity about what was agreed when something goes wrong later. Most shops have the second half in some form. The money is in doing both properly.

Why do reprints happen?

Ask any production manager and the list is remarkably consistent, and remarkably little of it is mechanical failure. The common causes are a typo, a phone number or price that changed, an old logo, artwork that was misjudged on a flat proof, finishing that did not look how the customer imagined it, or the wrong file version going to plate.

What those share is that they were all knowable before the press ran. The press did exactly what it was told. The failure happened upstream, at the moment someone looked at a proof and said yes without really seeing it.

The first job of approval: catching errors early

The cost of a change rises steeply through a job. Editing a file before plating costs a few minutes of prepress time. Catching it on press costs makeready and waste. Catching it after delivery costs the entire job twice, plus freight, plus a missed customer deadline you cannot buy back.

So the practical question is not whether you have an approval step — everyone does — but how much your proof actually reveals. A dense PDF sent as an attachment invites a glance. A proof that presents the product clearly, panel by panel, with specification and finishing stated plainly, invites a real review. Shops that make proofs easier to read get better reviews, and better reviews catch more errors.

This is where reviewing the product rather than the page changes outcomes. Customers are not trained to read a flat die-cut layout. Show them the assembled carton they can turn over, and misjudged panel order, upside-down back panels, artwork crossing a crease and finishing that reads differently than expected all become obvious to a non-print person in seconds.

The second job: making the agreement unambiguous

Even a well-run shop will eventually have a customer say "that is not what I approved." Whether that becomes a ten-minute conversation or a month-long dispute depends entirely on what you can produce.

A strong approval record answers, without argument:

Who approved it — a named individual with authority, not "the client".
What they approved — the exact proof version, retrievable and unchanged.
When they approved it — a timestamp, not a recollection.
What approval covered — artwork, copy, specification, finishing, quantity.
What it did not cover — typically calibrated color, unless a contract proof was supplied.

When all five are on record, the reprint conversation is short. When they are scattered across an email thread, a WhatsApp message and someone's memory, it is not.

What a strong approval workflow looks like

One canonical proof. A single link or file that is unambiguously the current version, so nobody reviews an old attachment.
Explicit versioning. Every reissue increments and is retained. Old versions stay retrievable but are clearly superseded.
A named approver. Established at the start of the job, not at the moment of sign-off.
Scope stated on the proof. What approval authorizes, and the color position, in plain language.
Structured response. Approved, approved with changes, or new proof required — not free-form email.
Automatic capture. Identity, timestamp and version recorded without anyone remembering to file anything.
Production runs against the approved version only. The link between what was approved and what was printed must be traceable.

What approval cannot do

Be honest with yourself about the limits. Approval does not protect you if you printed something other than what was approved, if the file changed after sign-off, if the substrate or finishing was substituted without agreement, or if you promised a color match you had no calibrated basis for. It also does not cover defects that were genuinely invisible on the proof.

And an approval obtained by burying the important detail is worth less than it looks — commercially if not legally. The goal is a customer who understood what they were signing, not a customer who can be shown to have clicked a button.

The commercial upside

Reprints cost more than materials. They consume press capacity that was sold to another job, they push delivery dates, they absorb management attention, and they damage a relationship even when the customer accepts fault. Reducing them is one of the few improvements that helps margin, throughput and customer trust simultaneously — and it needs no capital equipment, only a better proofing step.

Common questions

Does documented approval mean the customer always pays for the reprint?

It means the conversation starts from facts instead of memory. Where the error is genuinely the customer's and the approval clearly covers it, most customers accept that. Where the shop deviated from the approved proof, documentation shows that too — which is fair, and worth knowing quickly.

What if the customer approved without really looking?

That is common, and it is partly a proof design problem. Approvals get rushed when the proof is hard to read. A proof that makes the finished product obvious at a glance gets a more considered review than a dense PDF.

Is an emailed "looks good" enough?

It is better than nothing but weak. It rarely names the version, often sits in a thread with several attachments, and lives in one person's mailbox. Approval tied to a specific proof version in a system everyone can see is much stronger.

Should we still reprint if we are technically covered?

Sometimes yes — for a valuable customer a goodwill reprint can be the right commercial call. Documentation does not force your hand; it just means you are choosing to absorb a cost rather than discovering you have to.

Where do most avoidable reprints actually come from?

In everyday shop experience: text and data errors that survived a rushed review, artwork placement or construction the customer misread on a flat proof, finishing that looked different from what they pictured, and using an outdated file version. All four are addressable at the proof stage.