How to document customer sign-off

To document customer sign-off properly, capture five things together and store them as one record: the named approver and their authority, the exact proof version approved, a timestamp, the stated scope of what approval covers, and the response itself. Any record missing one of those five leaves room for a dispute you cannot close.

What makes a sign-off record strong

The test is simple. Six months from now, with the original people unavailable, could someone open the job and answer "what exactly did the customer agree to, and when?" in under a minute, with evidence? If the answer requires searching a mailbox or asking a colleague what they remember, the record is not strong enough.

The five elements

1. Who approved

Record a named individual, their role and their company — not "the client" and not a shared mailbox. Establish who is authorized to approve at the start of the account or job, and keep that on the customer record. Where several stakeholders review, one named person still owns the final approval; the others are reviewers.

2. What exactly they approved

This is the element most often weak. The record must point to a specific, immutable proof version — version 3, dated and retrievable exactly as it appeared. Not "the artwork", not "the PDF I sent", not a file that has since been overwritten in a shared folder. If the proof can change after approval, the record proves nothing.

3. When

A timestamp, captured automatically. Dates matter for establishing sequence: whether a change request arrived before or after release, whether an approval landed in time for the press slot, whether a later instruction superseded an earlier one.

4. What approval covered

State the scope on the proof, above the sign-off, in plain language — typically that artwork, copy, layout, specification, finishing and quantity have been checked and the job may proceed. State the exclusions just as plainly: that a digital proof represents appearance, placement, materials and finishing, and is not a calibrated contract-color reference unless a contract proof has been supplied. Scope written after the fact is an argument; scope written on the proof is a record.

5. The response itself

Capture the customer's actual decision in a structured form — approved, approved with the listed changes, or new proof required — together with any comments they attached. Free-text email replies are the weakest version of this because they force someone to interpret intent later.

What a complete record looks like

How to capture it in practice

1. Send one canonical proof. A single link that is unmistakably current, rather than attachments that multiply through a thread.
2. Identify the reviewer at delivery. Address the proof to the named approver so identity is established before the decision, not inferred after it.
3. Put the scope statement on the proof. Immediately above the approval action, where it must be passed to approve.
4. Offer structured responses. Approve, approve with changes, or request a new proof — with a comment field, not instead of one.
5. Capture automatically. Identity, version and timestamp recorded by the system, so the record does not depend on anyone remembering to file it.
6. Freeze the approved version. Retain it unchanged; any subsequent edit creates a new version requiring new approval.
7. Confirm back to the customer. A confirmation email restating what was approved and when gives both sides the same record.
8. Attach it to the job. Stored with the job, visible to whoever handles the reorder or the complaint.

Common weak points

• Approval by phone. If it happens, follow up in writing the same day and have the customer confirm.
• Approval by a junior contact. Fine if they are the agreed approver; risky if the invoice goes to someone who has never seen the proof.
• Overwritten proof files. A version that can be edited after approval destroys the record's value.
• "Approved with changes" as a habit. It creates a version that was never actually reviewed. Use it only for unambiguous single corrections.
• Records in one person's mailbox. When they leave or are on holiday, the record is effectively gone.
• Silence treated as approval. Deadline-based auto-approval is commercially tempting and evidentially weak. Chase instead.

Using the record well

A good sign-off archive is worth more than dispute protection. It answers "what did we print last time?" on a reorder, it shows where approvals stall so you can fix the bottleneck, and it lets anyone in the shop see the state of a job without asking. Documentation built only for arguments gets neglected; documentation that makes daily work easier stays accurate.

Related reading

See how artwork approval prevents reprints for the commercial case, the approval checklist for the checks that precede sign-off, and what a proof sheet should contain for the sign-off block itself. On the product side, see customer artwork sign-off and branded proof links.