A customer replies, “Yes, that is the one.” Sales marks the color approved. Production opens the job folder and finds an original sample, a revised sample, and a photograph attached to an older email.
Nobody has deliberately skipped a step. But the business still does not have an unambiguous instruction.
Custom color sample approval should connect a customer's decision to one identifiable sample and a clearly stated scope. Before custom paint batches enter production, the team needs to know what was accepted, what remains unresolved, and which formula notes belong to that decision.
This guide offers a practical communication handoff, not a color-testing method or legal interpretation of customer acceptance.
Why is a yes not always a production instruction?
Customers often discuss several decisions in one conversation: color, finish, price, quantity, delivery, and intended use. A reply approving one of those decisions can accidentally become permission for all of them.
“The darker option looks good” might mean the customer prefers a direction, not that the final sample is approved. “Proceed” might refer to preparing another sample rather than making the order.
Keep three questions separate: Which sample was selected? What did the customer accept about it? Has your business authorized the production job? A single email can answer all three, but do not assume it does.
Give each submitted sample a stable identity
Assign a sample reference before sending a panel, coated part, or other sample to the customer. Put that reference on the sample's accompanying information and in the message requesting approval. Use the same reference in your internal record.
A color name alone is weak identification. “Harbor Grey” may describe several revisions. A reference such as HG-SAMPLE-B can distinguish one submission without requiring the customer to understand your formula naming system.
Record the preparation date, linked formula version, customer or project, and what was actually sent. If you keep a counterpart or reference specimen, identify its location. Record the relevant preparation and evaluation context established for the job; the approval sheet should point to that method, not invent one.
Photographs can help someone locate a sample, but avoid treating an image filename as the entire identity record. Keep the reference attached to the physical sample and its history.
Use an approval-to-production handoff record
A shared form or a controlled document is enough to start. Keep these fields together:
- Customer and project: Who is requesting the work, and which order or development job does this concern?
- Submitted sample: Its unique reference, revision, preparation date, and linked formula record.
- Submission evidence: When it was sent, to whom, and where the covering message is saved.
- Decision evidence: The customer's actual reply, date, and named decision-maker.
- Accepted scope: What was accepted, described precisely rather than as a general “approved.”
- Open conditions: Any remaining questions about finish, quantity, price, application, timing, or other requirements.
- Internal disposition: Who may move the job forward, which production record applies, and what must happen first.
Preserve the customer's wording alongside your summary. If you paraphrase a qualified approval as an unconditional yes, the record can become more confident than the evidence.
Separate accepted appearance from permission to manufacture
Use clear operational states, such as awaiting customer response, clarification needed, sample accepted, and production authorized. These are suggested working labels, not universal industry requirements.
A sample can be accepted while the order remains blocked. Perhaps the customer has not confirmed the quantity, or your production team has not completed its required review. Show the blocker and its owner instead of leaving an unexplained hold.
Likewise, customer approval does not replace your established technical evaluation, product requirements, or internal release controls. Recordkeeping connects decisions; it does not prove a coating is suitable for every use.
When a sample is ready to move into manufacturing, use the separate guide to moving an approved custom-color sample into production. That is the next handoff, not a substitute for knowing what the customer accepted.
Resolve conflicting approvals before work starts
A purchasing contact may approve one sample while a designer later asks for another adjustment. Do not quietly choose the newest message or the person who sounds most certain.
For each project, establish who provides the customer's final direction. When instructions conflict, summarize the conflict in plain language and request clarification from that contact. Keep the job in a visible clarification state until the responsible people resolve it.
A useful message is: “Your earlier reply selected HG-SAMPLE-B. The later note requests a warmer version. Should we pause production and prepare a revised sample, or proceed with B unchanged?”
Save the answer with the sample record. Avoid hiding the decision in a private inbox that production cannot retrieve.
Walk through a revised sample handoff
Imagine a small coatings business submits sample A, then prepares sample B after a customer requests a change. The customer responds “approved” in the email thread originally used for A.
The coordinator does not guess. They ask the customer to confirm the sample reference and the accepted scope. The customer identifies B but says packaging quantity is still under review.
The coordinator records B as accepted for the agreed appearance decision, preserves the reply, and leaves production authorization pending the quantity decision and internal checks. The production worksheet points to B's formula record. A remains in the history as an earlier submission, not an alternative current instruction.
For repeat work, reconciling the final custom-color formula remains important. The approval record identifies the customer's selected result; formula reconciliation explains how the business produced it.
Frequently asked questions
Can approval by phone count?
A phone conversation may clarify the decision, but capture who spoke, when, the sample reference, and the exact scope. Send a written summary for confirmation under your business's agreed approval process. Do not turn silence into acceptance unless your applicable agreement and qualified advice support that interpretation.
What if the customer approves only a photograph?
Record that limitation explicitly. Clarify whether the reply selects a development direction or accepts an agreed deliverable. Do not silently describe photo-only feedback as approval of a physical sample or as proof that all appearance requirements have been met.
Does each repeat order need a new sample approval?
Follow the agreed requirements and your change-review process. Confirm which prior approval applies and whether the requested product, reference, or requirements changed. Reusing an identifiable approval is different from assuming a familiar color name settles the question.
Should an abandoned sample be deleted?
Keep its decision history under your document-retention policy, with a clear superseded or not-selected status. Remove it from the current production instruction path without making the earlier conversation impossible to reconstruct.
Test one approval before the next job starts
Choose one recently accepted color. Can someone outside the email conversation locate the exact sample, the customer's decision, its limits, and the authorized production reference?
If not, close that gap before the job moves forward. The goal is not more paperwork. It is one answer that the customer, sales team, and production team can all recognize as the same decision.
