Ask a shop owner where orders lose time and they will say production. Look at the timestamps and it is almost always approval: the job sat for four days with nothing happening, then got rushed through the press in an afternoon.
Nothing about that is the customer's fault. It is usually the request.
1. Send one proof, not options
Options make approving into a decision with a wrong answer, so people defer it. One proof makes it a yes or a correction, and both are fast. If they genuinely need to choose between two treatments, that is paid design work with its own step.
2. Ask for one unambiguous action
Compare these:
"Let me know if you're happy with the attached and we'll get it in the schedule."
"Approve this proof to lock your Friday delivery. Approve here."
The first is a conversation opener. The second is an instruction with a consequence and a button. Say exactly what you need, exactly what happens when you get it, and exactly what happens if you do not.
3. Make it a one-tap job on a phone
Most approvals happen on a phone, often not at a desk. That means:
- The proof visible without downloading anything.
- No login, or a signed link that needs no password.
- A single large button.
- Garment colour, print size, position and quantity stated next to the image, so there is nothing to go and check.
A PDF attachment that has to be opened, pinched, and replied to is a task. An image with a button is a reflex.
4. Chase automatically
The chase should not depend on anyone remembering. A reminder at 24 hours and another at 72, then it appears on a human's list to call. And every reminder should restate the date consequence, because that is the only part that creates urgency.
The provenance that saves you later
Record which version was approved, by whom, and when. Reprint arguments are almost always about ambiguity, and ambiguity always favours the customer, correctly. A timestamped approval against a specific proof turns a dispute into a fact.
| Change | Effort | Typical effect |
|---|---|---|
| One proof, not options | None | Removes deliberation |
| Explicit ask with a date consequence | None | Largest single gain |
| One-tap mobile approval | Setup once | Removes friction |
| Automated chase | Setup once | Removes forgetting |
What this is worth
If approval is your longest stage, halving it halves your quoted lead time without touching the press. That is the cheapest capacity increase available to a print shop, and it is also what makes a rush fee credible: you cannot charge for speed while your own process loses three days.
Version control is the part shops skip
Most approval disputes are not about whether the customer approved. They are about which version they approved. Three revisions in a day, sent as attachments from two different people, and nobody can say with certainty which artwork the yes referred to.
The cure is dull and total: every revision gets a version number, the proof shown is always the latest version, and the approval is recorded against a specific version rather than against the job. Then the question "what did we agree?" has a one-line answer with a timestamp on it.
| Without version control | With it |
|---|---|
| "You approved it" versus "not that one" | Version 3, approved 14:22, by name |
| Reprint argued over goodwill | Reprint decided against the record |
| Setup checked against whatever was to hand | Setup checked against the approved file |
| Reorders re-proofed from scratch | Reorders reuse the approved version |
What faster approvals are worth in money
Approval delay is capacity you have already paid for and not sold. Take a shop doing 40 jobs a month with an average approval delay of four working days. Cutting that to one recovers three days of elapsed time per job, which shows up as more jobs through the same press in the same month and fewer rushes at the end of it.
The second saving is quieter: fewer reprints. When the setup check is against the exact approved version rather than a printout someone found, the most common cause of a wrong-placement rerun disappears. At the cost of a reprint set out in the QC checklist, removing one a month pays for a lot of process.
Make the approval queue a place, not an inbox
Approvals living in email means the queue is invisible, personal and unmeasurable. Approvals living in a list means anyone can see what is waiting, on whom, and for how long.
The practical setup: proofs sent through the customer portal with one-tap approve or request-change, the approved version and timestamp recorded on the order, an automatic chase sequence, and a single view of everything currently waiting on a customer. Then the daily question at the start of the shift is one glance rather than three people checking their own mail.
Two habits that stop the clock restarting
One point of contact for changes. If two people at the customer can request changes, you will get contradictory ones and a third revision that nobody has approved. Ask who signs off, and copy the rest.
A stated change cut-off. After approval, changes mean a new proof, a new approval and a new date. Say it once at approval time rather than negotiating it later, and the number of after-approval changes falls sharply on its own.
Printer's Friend sends proofs through the customer portal with one-tap approval, records the version and timestamp against the order, and chases on a schedule. Approvals waiting on customers sit in one list rather than in someone's inbox. Where approval fits in the wider path is in the nine stages, and if a customer goes silent entirely, see when a customer ghosts an approval.