How a packaging maker gets artwork approved faster
An illustrative account of one approval sheet per job, with every artwork version and who approved it.
This story shows a practical response to one approval sheet per job, with every artwork version and who approved it.
The business
This composite concerns a printed flexible packaging business with about 40 people. Artwork approvals and colour consistency matter before a reel goes into print. A wrong revision can spoil the full run. The development engineer manages the daily development work. The quality manager is called when a commitment changes or a decision exceeds normal authority.
Records may be spread across latest approved drawing, trial notes, inspection record and customer approval. This story centres on this recurring task: one approval sheet per job, with every artwork version and who approved it.
What was going wrong
A written rule changes the choice: only the signed current revision is released to regular production. The difficulty is applying the rule to real exceptions. The team can usually explain the situation after several calls. That explanation is rarely attached to the document that the next shift or the customer sees. In this case, the important missing link is put artwork version and printed proof on one sheet. It is not enough to know that someone spoke about it.
The second problem is timing. When a sample is accepted but the floor makes the bulk quantity to an older specification, the check happens too late to change the next commitment.
What they changed
The team would start by giving one person responsibility for the sample and drawing approval file. Its first rule is simple: Only the signed current revision is released to regular production. Staff can still make calls and use WhatsApp, but the approved reference and the reply return to that record. One owner keeps the entry current, and another person handles decisions outside the routine limit.
For this particular problem, the operating instructions are concrete:
- First check: Put artwork version and printed proof on one sheet. Keep a reference to the source rather than a summary from memory.
- Next action: Confirm written customer approval. Add the responsible role and the time the next answer is needed.
- Decision point: Block print release if any differs. Do not quietly replace an old promise or technical record.
The team can copy this small register. Both entries below are illustrative examples, not records of a real business.
| Job / item | Quantity (example) | Check required | Status | Decision owner |
|---|---|---|---|---|
| S018-A | 33 | Put artwork version and printed proof on one sheet | Open | development engineer |
| S018-B | 36 | confirm written customer approval | Needs proof | quality manager |
At the end of the review, anything still uncertain stays open. The next person should be able to find the original source, understand which part is confirmed and see who is expected to act. If an approval involves price, safety or compliance, the authorised manager makes that decision.
What a normal morning looks like now
The development engineer opens the sample and drawing approval file alongside latest approved drawing, trial notes, inspection record and customer approval. They look first for work promised today and then for items missing an owner or proof. The quality manager does not need the complete history retold. Only the exceptions, their business effect and the requested decisions reach that desk.
A useful meeting ends with the reference, next action and date written down. The team checks the same list later rather than asking each department for a fresh verbal status. Trial conditions must be reproducible in normal shifts. A one-off sample made by a specialist is insufficient.
What did not work at first
A likely first attempt is adding more columns or asking everybody to update another report. People then spend time copying entries from their own registers. A second attempt is to mark cases closed after a reassuring phone call. Neither establishes whether the underlying goods, amount or instruction has been checked.
The simpler practice keeps the original reference and records only what has changed. A disputed entry remains disputed. If the team cannot find evidence, it names the person who can, and sets a time for the next check.
What is still not solved
A register cannot remove a material shortage, a customer's disagreement or a long outside lead time. It can expose the risk early enough for a person to decide. This story does not claim an achieved saving, improved margin or shorter delivery time. The useful outcome to measure would be fewer unowned exceptions and a clear record of decisions.
If you want to try this
- Open Sample submission approval and choose one live case matching this story. Identify the exact trigger and finish condition.
- Copy the fields from Sample tracker. Enter the source, one responsible person, the next check and its date. Use actual records, not the example figures here.
- At the next review, compare the register with the physical or financial evidence. If the same gap returns, revisit Specs in someones head and change the control at that point.
Read next
- Specs in someones head
- Sample submission approval
- Sample tracker
