
Packaging artwork is approved in conversation and disputed in documents. A proof is circulated, a reply says it looks right, a printer asks for a file, and somewhere between those three messages the revision number stops being certain. By the time cartons are printed, the question is no longer what the artwork says but which artwork was agreed.
This guide is for private-label flooring teams coordinating carton artwork with a printer and a customer. It describes a single approval log per packaging item, and the few fields that make it work. It is editorial approval-recordkeeping guidance only: not a print specification, not a colour standard, not a proofing requirement, not a packaging drawing, not a regulatory labelling statement and not a substitute for the current customer specification and printer documents.
Approvals fail on identity, not on judgement

Most artwork disputes are not disagreements about design. They are disagreements about which file was being discussed. Two proofs with the same visual layout and different revision letters behave identically in a conversation and completely differently in a print run. The log exists to remove that ambiguity before it costs a pallet.
The failure is structural rather than personal. Email threads are ordered by time, decisions are ordered by item, and the two orders diverge as soon as a second packaging item joins the conversation. A log re-sorts the same information by item, which is the order the questions arrive in.
One log per packaging item, not per project
A project-level log grows into a wall of rows where a carton and a pallet label compete for attention. Item-level logs stay short, and short logs get maintained. Each packaging item — the retail carton, the outer shipper, the pallet label, the insert — carries its own sheet with its own revision sequence.
Item-level separation also matches how printing is actually scheduled. A carton can be approved and printed while the insert is still in revision, and a single combined log makes that ordinary situation look like an inconsistency.
The row
Seven fields are enough. The table is the specification for the log; anything beyond it tends to be commentary that belongs in the note column.
| Field | What to enter | What it prevents |
|---|---|---|
| Packaging item | The item name and its part reference | Mixing revisions between items |
| Revision | The identifier printed on the proof itself | Approving a file that cannot be named later |
| Issued date | The day the proof was sent | Losing the sequence when replies arrive out of order |
| Decision | Approved, approved with notes, or rejected | A verbal yes that nobody can point to |
| Decision date | The day the decision was made | Reconstructing timing from memory |
| Approver | The person with authority, by name | An approval by whoever replied first |
| Change note | One line on what moved in this revision | Re-arguing a settled point |
Name the file after the row
An approval log that cannot be tied to a file is a diary. The file name that was approved belongs in the row, and the row reference belongs in the file name, so the two can be found from either direction. A convention as plain as item, revision and date survives staff changes; a convention built on folder names usually does not.
Keep one copy of every approved proof in a location that is not a personal mailbox. The log says which file; the archive holds it. Neither is sufficient alone, and together they answer the only question that matters when a print run is questioned.
Say what the approval covered
An approval is only as broad as its wording. "Approved" against a proof of the carton front says nothing about the back panel, the barcode placement or the language variant. Write the scope into the note: which panels were seen, which were still open, and what the approver was told was not yet final.
This matters most on private-label work, where the customer approves design and the printer needs production data. Two approvals can be valid and still cover different things, and only a note that names the scope keeps them from being read as one. When the artwork carries a surface reference, the reference itself is part of the approval: the swatches published on the Benchwick innovation page are the material references a proof is being compared against, not a colour standard for the print run.
Close the row when the run ships
Add the print date and the run reference to the approved row once production is confirmed. This converts the log from a design record into a production record, and it is what lets a later carton be matched back to the artwork it was printed from.
It also closes the loop honestly. An open row with no print reference says an approval exists and nothing was made from it, which is a useful fact when a shipment is expected and the cartons are not there.
None of this improves a design. It keeps a design decision attached to a file, a date and a person, in a form that a printer and a customer can both read without asking, which is the part that tends to go missing first on a fast private-label programme.
Frequently asked questions
Why not rely on the email thread that carried the proof?
+
Because a thread is ordered by time and a decision is ordered by item. Six revisions across three recipients produce a thread where the approved file is somewhere in the middle, quoted in a reply, with an attachment name that no longer matches. A log has one row per revision per item, so the question "which proof was approved" has an answer that does not depend on scrolling.
What is the minimum a row needs?
+
The packaging item, the revision identifier, the date the proof was issued, the date it was approved or rejected, who approved it, and the exact file name that was approved. Add one line saying what changed in that revision. Those seven fields answer almost every later question, and they fit in a single spreadsheet row.
How should a rejected revision be recorded?
+
As its own row, with the reason in plain words. Deleting rejected revisions destroys the most useful part of the log, because the reason a proof was turned down is usually the thing that gets re-litigated later. A row that says which element was wrong and who asked for the change converts an argument into a lookup.
Does the log replace the printer proof or the customer sign-off?
+
No. It records that a proof existed, which revision it was and who approved it. The print specification, the colour standard, the packaging drawing and the formal customer sign-off are separate documents with their own authority. The job of the log is to point at the right one of them without ambiguity.
