Which Artwork Version Is Approved—and How Do You Stop the Wrong One Reaching Press?
Artwork version errors can survive quotation, proofing and prepress if approval status and file lineage are unclear. Printing teams need one controlled version chain from customer revision to production release.
The short answer
The safest artwork process is one where the production team never has to guess which file is current. Each customer revision should move through a controlled lifecycle from receipt to internal review, proof, customer approval and production release, with older versions preserved for history but clearly marked as superseded.
The problem is not that companies have too many files. It is that file name, folder location and approval status can become three different versions of the truth.
How this connects to the pillar
The broader change-control model is covered in The Customer Changed the Job Again. How Do You Keep Specs, Cost and Production Aligned?. Artwork version control is one of the most visible places where a small revision can affect the whole job.
File names are not approval control
Teams often build naming conventions such as FINAL, FINAL2, APPROVED or NEW.
Those labels help people navigate, but they are not enough to prove production authority.
A file called “final” may later be replaced. A customer may approve a PDF that is not the same file sent to plate output. A local copy may remain on a workstation after the shared version changes.
The approved production version should therefore be represented by controlled status, not only by naming.
Preserve lineage from customer file to production output
A useful artwork history shows the relationship between:
- original customer artwork;
- internal correction or prepress version;
- proof version;
- customer-approved version;
- final production output.
The business may use different systems to create and render these files.
What matters is that the lineage is understandable.
When a customer asks which version was printed, the team should not need to reconstruct the answer from email timestamps.
Separate review status from customer approval
Internal prepress review and customer approval are different decisions.
Prepress may confirm technical suitability while the customer confirms content and appearance.
A file can pass one and still wait for the other.
Use statuses that make the distinction clear enough for planning and production.
This prevents a technically ready file from being mistaken for a commercially approved file.
Make revisions visible to everyone already planning the job
Artwork often changes after material planning, tooling preparation or scheduling has started.
A version change therefore needs to notify or update the downstream process.
Possible effects include:
- plate or cylinder remake;
- die or tooling change;
- new barcode;
- different copy or language;
- different color requirement;
- obsolete printed stock;
- new proof requirement.
The artwork system should not behave as an isolated prepress island.
Control the release point to press
There should be one clear event that says the artwork is released for production.
That event should identify the approved revision.
Press operators should not need to interpret customer emails or compare folder dates.
If the job changes after release, the release status should be withdrawn or superseded visibly.
This protects the press from producing the wrong version efficiently.
Deal with local copies
Local workstation copies create risk when teams work under time pressure.
The control does not need to ban every local working file.
It needs to ensure that production output is generated from the approved controlled source.
Archiving or naming local work clearly can reduce confusion, but the final release should always point back to the controlled job record.
Include variable content and market versions
Packaging may have several language, market, promotional or regulatory versions that look almost identical.
That increases version risk.
The job definition should make the market/version relationship explicit.
A small visual difference can have large commercial consequences if the wrong pack reaches the wrong market.
Version identity should therefore be easy to verify before output.
Connect artwork revision to tooling
A revised file may or may not require new plates, cylinders, screens or cutting tools.
The change process should determine that explicitly.
Do not assume the tooling remains valid simply because the physical dimensions did not change.
Copy, graphics or barcode changes can still invalidate print tooling.
This connection is explored further in You Already Have the Die and Plates. Are They Still the Right Tools for This Revision?.
Use proofing as controlled evidence
A proof should identify the artwork version it represents.
If a customer approves a proof, the business should be able to link that approval to the production version.
A screenshot in a messaging app can be useful communication, but it should not become the only evidence if the job has significant version risk.
The stronger the consequence of an error, the stronger the approval evidence should be.
Measure artwork change behavior
Useful measures include:
- artwork revisions per job;
- revisions after customer approval;
- revisions after production release;
- plate remakes caused by artwork change;
- jobs held waiting for approval;
- production incidents caused by version ambiguity;
- obsolete stock created by artwork change;
- customer complaints where approval history was unclear.
These measures turn artwork change from anecdote into operational evidence.
ACC and Jupiter context
Jupiter supports the job-based printing and packaging process where artwork, specification, costing and production information need to remain connected to the same job. The objective is not to replace specialist design tools; it is to keep the operational status and approved production definition controlled. Explore Jupiter for printing and packaging.
Operational review point
Take one recent job with several artwork revisions.
Lay out the file history from the customer's first file through production.
Ask whether a new employee could identify the approved production version without asking the original account manager or prepress operator.
If not, identify which status, link or release step is missing.
Use visual identity as a secondary control
Where practical, production tools can help users recognize versions visually through thumbnails, controlled preview images or version markers. This should not replace status control, but it can reduce selection errors when files have similar technical names.
The visual reference should come from the controlled artwork record rather than a separate manually maintained image.
Review version risk before repeat production
Repeat jobs often move faster because teams assume the prior setup is still valid.
Before release, confirm that customer copy, barcode, market, material and tooling relationships have not changed since the previous run.
A short repeat-job check is usually cheaper than discovering after printing that the “same” job changed quietly.
Lock production output to release status
One practical control is to ensure that production output cannot be generated casually from any working file.
The plate, cylinder, digital press or other production output should reference the released artwork object.
The exact technical method will vary, but the operating rule should be consistent: working files are for preparation; released files are for production.
That distinction reduces the risk that a technically skilled user accidentally outputs a newer-but-unapproved or older-but-familiar version.
Manage external prepress suppliers explicitly
Some businesses outsource plate making, engraving or other prepress work.
External suppliers introduce another handoff where version ambiguity can occur.
The purchase order or instruction should identify the exact released artwork revision.
When replacement output is requested, record whether the cause is damage, supplier error or customer revision.
The supplier should not need to choose between several attachments in an email chain.
Use check digits or visual comparison for high-risk versions
Where several versions look almost identical, simple visual comparison may be unreliable.
The business can use controlled version IDs, proof references, barcode checks, dieline references or other verification methods appropriate to the product.
The point is not to add complexity to every job.
Use stronger verification where the cost of printing the wrong version is high.
Control translated and regulatory copy
Language and regulatory versions deserve particular attention because a one-line change can determine whether the pack is legally or commercially usable in a market.
Separate versions clearly by market and maintain approval history.
If one artwork contains several languages, confirm which markets the revision covers.
Do not rely on image similarity to infer equivalence.
Audit the release path with real jobs
Periodically take a sample of completed jobs and compare:
- customer-approved proof;
- released artwork;
- production output;
- final packed product.
This end-to-end check tests whether the version-control process is functioning in practice rather than only whether the files are stored correctly.
Frequently asked questions
Should old artwork versions be deleted?
Usually they should remain traceable for history, but clearly marked as superseded so they cannot compete with the current production version.
Is a customer email enough to approve artwork?
It may be acceptable for some businesses, but the approval should still identify the exact proof or revision covered by that decision.
What if the customer changes only one line of text?
A small content change can still require new output and can make existing printed stock obsolete. Assess the downstream impact before release.
Who should own the final production release?
The exact role varies, but the release should be controlled and understood across prepress and production rather than assumed from file location.