Fix the handoff before changing the tools
Email, WhatsApp and Excel can work well for a small print shop, sign maker or B2B design team. The trouble starts when the person making the product cannot answer three questions: which job is this, which version did the customer approve, and is anything still waiting for a decision?
Look for specific failures: feedback split across two conversations, a replacement logo uploaded after sign-off, or an “approved” spreadsheet row that points to an editable file. More messages are not necessarily the problem. An unclear connection between the decision and the work is.
Start with one job
Take a recently completed order and try to recover its specifications, approved proof and final production file. Any step that requires asking someone to remember is a useful place to improve the process.
Give every job one review record
A shared sheet can be enough. Give each job a stable ID and link to its files instead of scattering attachments across rows and messages. Keep the record in a place the team can access when its usual owner is away.
Minimum information to keep together
| Record | What it answers |
|---|---|
| Job ID and owner | Which order is this, and who resolves questions? |
| Quote and specification revision | What quantity, size, material and scope were agreed? |
| Current proof and revision | Which exact file should the customer review? |
| Named customer approver | Who can give the final decision? |
| Decision, time and evidence | What was approved or sent back for changes? |
| Production file and release status | What may the team actually make? |
Keep commercial acceptance and artwork approval distinct. A customer may accept the quote while still correcting the artwork. Likewise, approving the design does not confirm payment, stock availability or a revised delivery date. Record the checks your business actually requires before release.
Run a five-step proof approval workflow
- 1Confirm the brief. Collect dimensions, orientation, quantity, material, finish and supplied artwork. Identify the person who can approve for the customer. Resolve missing details before presenting a proof as ready for review.
- 2Send a clearly numbered proof. Use a name such as JOB-1042-proof-v2.pdf and show the same job ID and revision inside the proof. State what changed since the previous version and what the customer needs to check. Send one review link through their preferred channel.
- 3Collect one consolidated response. Ask for either approval of that revision or a specific list of changes. If feedback arrives by phone or chat, capture it in the job record and confirm the interpretation with the customer. An emoji or “looks good” may need clarification.
- 4Record the decision against that file. Save who approved, which revision they saw, when they decided and the actual response. Preserve the approved proof. A material artwork or specification change creates a new review revision; do not silently replace the approved attachment.
- 5Release the matching production file. The job owner checks that the production asset corresponds to the approved proof and that other required conditions are met. Keep approval and production release as separate statuses. If the match is uncertain, hold the job and resolve it.
For a service team, the same sequence can cover a brochure, presentation or other deliverable. Replace “production release” with the handoff that matters, such as sending final artwork to the customer or authorizing a supplier.
Be clear about what the proof demonstrates
A layout approval is not automatically a color guarantee. Explain whether the customer is checking wording, placement, dimensions or a physical sample. Adobe notes that the reliability of screen proofs depends on the monitor, color profiles and viewing conditions; agree a suitable proofing method for color-critical work.
For the technical distinction, see Adobe’s explanation of proofing colors.
A revised sign: follow the decision, not the last message
Fictional example—not a client project
A shop is preparing two reception signs under job JOB-1042. The quote specifies 24 × 18 inches. The customer approves proof v2, then sends a corrected phone number by WhatsApp before production starts.
The owner puts the job on hold, records the requested change and issues v3. Version 2 remains in the history with its earlier approval, but it is no longer the version eligible for release. The new message does not itself approve the revised artwork.
The customer reviews v3 and explicitly approves it. The owner then checks the production file against v3, confirms the size and quantity still match the order, and releases the job. If the change also affected material, quantity or price, the commercial details would need their own confirmation.
This can be managed with a sheet, a shared folder and clear ownership. The useful improvement is that nobody has to infer permission from whichever message happens to be newest.
Choose the smallest setup that covers the workflow
1. Keep the tools you have when the record stays clear
A sheet, shared storage and email can be enough when an owner can keep every review current. Use restricted access, separate revisions and a clear release column. Acrobat supports shared PDF links and comments, so you may improve feedback without adding a portal.
Check retention as well as sharing. Google Drive treats PDF and image versions differently from Google documents; preserve the approved version deliberately. If your account includes Drive approvals, verify how its review settings handle edits. Do not assume every change resets approval.
2. Test an existing product when chasing reviews becomes routine
A proofing product may cover annotations and decisions; print-shop software may also cover quoting and scheduling. For example, Printavo lists online quote and artwork approvals. Test a normal job, a revision after approval and a customer using a phone. Check guest access, version history, exports and how your team sees work on hold. Product fit matters more than the length of its feature list.
3. Consider an integration or portal for a specific remaining gap
A custom layer becomes worth evaluating when tested products cannot connect the approved revision to your production system, apply your customer-specific approval rules or limit access correctly. Describe that gap before requesting a build. Include ownership, support and maintenance in the decision. A client portal can connect these steps while your existing accounting and communication tools remain useful.
Before releasing the job, check these six things
- The job ID and current specifications identify the same order.
- The designated customer approver reviewed the current proof revision.
- The decision and its evidence are saved; no requested change is unresolved.
- The approved proof is preserved and older revisions are clearly marked as superseded.
- The production file matches the approval; required commercial and technical checks are complete.
- A named owner has released the job, or recorded why it remains on hold.
Try this on the next few suitable jobs. Record unclear approvals, reopened revisions and time spent finding the right file. Use those observations to decide what needs improving; they are more useful than assuming a portal will save a particular number of hours.
Continue with the part of the process you need
Before a proof exists, a 2D product configurator can help customers explore options and preserve a design request. Visual configuration, price confirmation and approval of the production revision are separate steps.
For broader process mapping, read how to automate manual business processes. For employee-facing job control, see custom internal tools. If approved work needs to become an invoice, the QuickBooks integration overview explains why the accounting handoff needs separate rules.
The linked Adobe, Google and Printavo documentation supports the product capabilities described above. Availability and behavior depend on the product, plan and configuration. The job workflow and checklist are suggested operating practices, not claims about a client implementation.
Sources
If the process still gets stuck
Does one approval handoff still break down?
Describe the job, the tools involved and where the approved file becomes unclear. That gives us a concrete starting point for discussing whether configuration, an integration or a portal fits.
Describe your workflow