The Customer Said “Approved.” What Exactly Was Approved?
Customer approval is useful only when the business can identify the exact proof, specification, quantity, material and revision that the approval covers. Ambiguous approval creates avoidable disputes and rework.
The short answer
A customer approval is useful only when the business can identify exactly what object and revision the customer accepted. “Approved” should connect to the proof, artwork, specification, sample, material or other decision it covers, together with the approver and time.
Ambiguous approval creates risk because sales, prepress and production may each believe a different version is authorized.
How this connects to the pillar
The wider change-control model is covered in The Customer Changed the Job Again. How Do You Keep Specs, Cost and Production Aligned?. Approval is the point where a customer decision becomes an operational instruction.
Approval is not one universal event
Different jobs require different approvals.
A customer may approve:
- artwork content;
- digital proof;
- physical proof;
- color standard;
- material;
- dieline;
- structural sample;
- finishing effect;
- packing configuration;
- quantity;
- change request.
The business should define what each approval means.
An artwork approval should not automatically be interpreted as acceptance of every technical specification.
Identify the object being approved
The approval record should point to a specific object.
Examples:
- artwork revision B;
- proof file with a controlled ID;
- signed sample;
- substrate specification;
- physical mock-up;
- revised quantity.
This eliminates the phrase “the customer approved it” as a substitute for evidence.
Record who approved it
The customer's approver may matter.
Some organizations require a designated brand, quality or purchasing contact to authorize specific elements.
If approval comes from a different person, the account team should know whether that authority is acceptable.
The printing company does not need to manage the customer's organization for them, but it should follow the agreed approval path.
Time matters
A customer may approve a version and then send another revision later.
The chronology should be clear.
If the later message changes the approved object, the previous approval may no longer authorize production.
The job history should show which approval was current at production release.
Distinguish approval from acknowledgement
A customer replying “received” is not the same as approval.
Likewise, silence after a proof deadline may or may not constitute approval depending on the commercial agreement.
Define the approval language and process clearly enough that account teams do not make inconsistent assumptions.
Control approvals received in email and messaging apps
Customers use the channels convenient to them.
The solution is not necessarily to force every customer into a portal.
The operational requirement is to capture the relevant approval back into the controlled job record.
A screenshot or email can be retained as evidence, but it should link to the exact job and version.
Handle conditional approval explicitly
Customers may approve with conditions:
- “approved if barcode is corrected”;
- “approved subject to color match”;
- “approved for sample only”;
- “approved except one language line.”
Conditional approval is not the same as clean production release.
The condition should remain visible until it is resolved and revalidated.
Connect approval to production release
Production release should check whether required approvals are complete.
The exact rule depends on the risk of the job.
For some work, artwork approval may be enough. Other packaging may require structural, material or compliance approval as well.
The release gate should reflect the real customer requirement.
Preserve approval after job completion
Approval evidence becomes valuable during:
- customer complaint;
- invoice dispute;
- repeat job;
- regulatory inquiry;
- internal root-cause review.
Do not let the evidence disappear in one employee's mailbox.
The job history should preserve the decision for an appropriate retention period.
Measure approval behavior
Useful indicators include:
- jobs waiting for customer approval;
- approvals received after planned release date;
- jobs released with conditional approval;
- revisions after customer approval;
- complaints where approval evidence was unclear;
- jobs started before required approval;
- average approval cycle time;
- customer segments with repeated late approval.
These measures help distinguish internal delay from customer decision delay.
ACC and Jupiter context
Jupiter connects printing and packaging job information across estimating, specification, production and delivery. Customer approvals become more useful operationally when they are tied to the exact job revision they authorize, rather than stored as isolated communication. Explore Jupiter for printing and packaging.
Operational review point
Take five recent jobs where approval was important.
Ask a person who was not involved originally to identify:
1. what was approved;
2. which version;
3. who approved it;
4. when;
5. whether there were conditions;
6. whether the approval was still current when production started.
If the answers require searching personal inboxes, the job record is not yet self-explanatory.
Define approval expiry when appropriate
Some approvals remain valid indefinitely for the same specification.
Others may need reconsideration after a material, artwork or process change.
The business should define what kind of revision invalidates the prior approval.
This prevents users from carrying an approval forward to a job that is no longer equivalent.
Make approval status visible to planning
Planning should know whether a job is genuinely releasable or still waiting for the customer.
If approval status is hidden in account-management communication, planners may reserve capacity for work that cannot yet run or release work too early.
A visible approval state makes customer delay part of schedule evidence.
Separate commercial approval from technical sign-off
A customer may approve appearance or content while internal technical teams still need to confirm manufacturability.
The two approvals should not be confused.
A structural sample can be commercially accepted but still require final process validation. Likewise, a technically sound design may still lack customer content approval.
Production release should reflect all required decisions.
Define what happens when the approver changes
Customer organizations change staff.
If the agreed approver leaves or delegates responsibility, update the approval path.
Do not assume that any contact with the customer domain automatically has authority for high-consequence approval.
Account management should keep the authorized relationship current.
Make sample approval traceable
Physical samples introduce a challenge because they cannot be linked only by file name.
Use a controlled sample ID, date, revision or other method so the approved physical object can be identified later.
If several samples are circulated, record which one became the production reference.
Capture rejected proofs as useful evidence
Rejected proofs show what changed before release.
Keeping the rejection reason can improve prepress quality and customer communication.
Repeated rejection for the same issue—wrong language, missing copy, dieline mismatch—may indicate a weak upstream briefing process.
Review approval delays separately from internal delays
If a job misses schedule because customer approval arrived late, make that cause visible.
This supports better capacity planning and more accurate customer discussions.
Otherwise internal teams may be measured against a date that became impossible before production was authorized.
Keep approval evidence accessible without exposing customer data unnecessarily
The operational job record should show that approval exists and identify the approved object. Supporting communication can be retained according to the company's privacy and retention rules.
The goal is operational traceability, not indiscriminate storage of every conversation.
A clear reference to the approval is often more useful than a large archive of unrelated email.
Define internal escalation for unclear approval
When the customer's message is ambiguous, employees should know who can decide whether production may proceed.
That may be account management, quality, technical management or another authorized role.
A controlled escalation is safer than allowing each operator or planner to interpret the customer's intent differently.
Use approval cycle time in capacity planning
Jobs awaiting customer approval can occupy future capacity without being truly executable.
Track the expected approval date and release risk.
Where customer approval is chronically late, avoid overcommitting constrained resources based on unapproved work or build an explicit planning rule for that uncertainty.
Review approval quality, not only speed
A fast approval is not useful if the wrong version was presented.
Measure whether the proof package was complete and whether revisions after approval were caused by missed information.
This helps improve the briefing and proofing process rather than simply pushing customers to respond faster.
Frequently asked questions
Does every job need formal customer approval?
No. Approval requirements depend on the job, customer agreement and risk. The business should define what requires approval.
Can email approval be valid?
Yes, if the business accepts that method and the email clearly identifies the relevant object or revision. Capture it in the job history.
What if the customer approves and then changes the artwork?
Treat the later change as a new revision and determine whether new approval is required before production.
Should conditional approval release production?
Only if the business has a controlled rule for the condition. Do not let an unresolved condition become invisible.