Getting artwork approved without the email ping-pong
Published 30 August 2026
Nearly every remake a sign shop swallows starts the same way: somebody approved something, and nobody can prove what. This guide is about the process rather than the software — how to run proofs so an approval is a record instead of a recollection, and so the version that got signed is the version that got made.
The problem is versions, not people
Nobody sets out to approve the wrong file. It happens because a proof went out on Tuesday, a change went out on Thursday, and the customer replied “happy with that” to whichever email was nearest the top of their inbox. Both parties are being reasonable and the shop still remakes the sign.
The fix is to make every proof a numbered version and to make approval belong to a version rather than to a conversation. If v2 exists, an approval of v1 must not release anything. That single rule removes most of the category.
- Number every proof and keep the old ones
- Approval attaches to a version, never to a thread
- Re-issuing resets approval — always
- Never accept “yep looks good” against an unnumbered file
Get every page ticked, not the set
A six-page wayfinding set approved with one yes is six assumptions. In practice the customer read page one carefully, skimmed pages two to five and missed that the level-three plate says Level 2. Page-by-page sign-off costs the customer thirty extra seconds and turns a blanket yes into six real decisions.
It also changes the conversation when something is wrong later. “You approved it” is an argument. “Page four, version two, approved on the 14th” is a fact.
- One tick per page, not one per set
- Spell-check names, numbers and levels before sending — the customer will not
- Record who approved, on which version, and when
Make it easy or it will not happen
The most common reason a proof sits unapproved for four days is not indecision — it is that the customer could not open it, could not log in, or could not work out how to say yes. Every login you require is a day added to the job.
Send a link that opens anywhere, on a phone, with no account. Let them mark up what is wrong directly on the artwork rather than describing it in prose. “Move the logo left a bit” is three emails; a circle and an arrow is none.
- No account, no app, no password reset
- Works on the phone they are actually holding
- Markup on the artwork beats description in an email
- Chase once, politely, and record that you chased
Decide what “approved with changes” means before it happens
This is the one that catches shops out. A customer approves “with a couple of small tweaks” and the job releases to the floor because the status says approved. The tweaks are in a comment nobody read, and the sign is made wrong — to an approval that technically existed.
Approved with changes is not an approval. It is a request for another version. The safe rule is that it never releases production on its own: a person reads the notes, makes the change or decides it is immaterial, and releases the job deliberately — with their name against that decision.
- “Approved with changes” must not auto-release
- A human reads the notes and releases deliberately
- Record who released it, not just that it was released
- If the change is material, issue a new version and start again
Gate production, and be able to un-gate it
The approval is only worth having if something depends on it. Production should not be able to start on an unapproved job — not as a note on the job bag, but as a rule the board enforces. Shops that rely on everyone remembering discover the exception on the day it costs a sheet of acrylic.
Equally, approvals get given in error — by the wrong person, on the wrong job, in a hurry. Being able to withdraw one and put the job back to waiting is not an admission of sloppiness; it is the difference between catching a mistake in the morning and building it by lunchtime.
- An unapproved job cannot release — enforced, not advised
- Withdrawal should be possible, and recorded
- Preflight the file on upload, before anyone reviews it
- Keep the approval on the job, where the maker will see it
Frequently asked questions
- Is an email approval legally enough?
- In practice a dispute turns on what can be shown, not on what was meant. An email saying “looks good” with no version reference and no attachment is weak evidence; a timestamped approval against a specific numbered version, with the file attached to it, is strong. Neither is legal advice — but one of them ends the argument in about a minute.
- How many proof rounds should we include?
- Say the number in your terms, and make it a real number — two rounds is common. Unlimited rounds are not generous, they are unpriced labour, and the customers who use them most are rarely the ones paying the most. Charge for rounds beyond the included ones and most jobs settle inside two.
- The customer will not respond. What now?
- Chase once, in writing, with the delivery date attached to the silence: approval by Thursday keeps the install date, after that it moves. Then record that you chased. The point is not to be forceful — it is that “we never heard back” has a date on it when the customer later asks why their sign is late.