Who is liable when a customer approves a proof with a mistake?

As a general rule, once a customer approves a proof, responsibility for errors that were visible in that proof shifts to them, which is the entire commercial purpose of sign-off. But that shift is not unconditional. It covers what the customer could reasonably have seen and understood in what you sent. A clearer proof does not just speed up approval; it widens the range of errors the approval actually protects you from. This is general information, not legal advice, and the specifics depend on your contract and jurisdiction.

What a sign-off is actually for

A proof approval is a transfer of responsibility. You are saying "this is what we will print," and the customer is saying "yes, print that." From that point, if the delivered job matches the approved proof, an error the customer missed is generally their cost, not yours. That is why shops require approval before committing plates: it converts a shared assumption into a documented agreement about exactly what was to be produced.

The catch: reasonably visible and understood

The protection has a boundary, and it is worth understanding. An approval generally covers what was reasonably reviewable. If a proof was ambiguous, if a critical detail was not shown, or if the customer could not reasonably have understood what they were looking at, the strength of the sign-off weakens. A confident approval of something not understood is legally thinner than it looks: it proves the customer saw a file, not that they agreed to the product. That gap is exactly where disputes live.

Why a clearer proof is a stronger proof

Here is the part that connects liability to format. The more completely a proof shows what will be produced, the harder it is for a customer to argue they could not have seen an error. A flat proof of a folded carton invites the defense "I never saw the base panel." A proof that let them rotate the assembled box removes that argument, because the base was right there to inspect. So a proof the customer could genuinely explore does two things at once: it catches more errors before the press, and it makes the resulting sign-off cover more. See how to document customer sign-off.

What a defensible approval record contains

If a dispute happens, "the PDF was in the email" is a weak position. A strong one records specifics.

• Who approved, by name and with the authority to do so.
• What they approved, tied to a specific version, not just "the latest file."
• When, with a timestamp.
• What they were shown, so it is clear the error was in view.

A proof link that logs the sign-off captures these automatically; an email thread captures them only with discipline.

Set expectations in writing too

Records protect you after the fact; clear terms prevent the argument in the first place. State what the proof does and does not represent, especially on color: an on-screen proof is not a calibrated color guarantee unless a contract proof is produced. A short, plain approval note that names what the customer is confirming is worth more than a long disclaimer nobody reads. Again, this is general guidance; have your own terms reviewed for your jurisdiction.

Related reading

Continue with how to document customer sign-off, the print-proof approval checklist, and how artwork approval prevents reprints. ProofScene is opening early access: join the list.