Identify the colour reference
Name the starting reference: a physical garment, a yarn card, a specified colour standard or an inspiration image. Say whether it represents an exact target for review or a general direction.
If using a numbered colour system, include the system and reference format, not just a number. Keep any physical reference identifiable when it is sent between teams.
Compare under an agreed viewing condition
Screens, photographs and viewing environments can make comparisons difficult. Agree how physical references will be reviewed and use the same method when possible.
Do not approve a material solely because it appears close in a messaging-app photograph. Use those images for discussion and clearly state when a physical review remains outstanding.
Review the actual knitted surface
Review the proposed colour in the knitted surface intended for the garment. A loose yarn wrap and a finished knitted swatch are different references, so name what each approval covers.
For a coordinated set, compare the relevant pieces together. If yarn, stitch or finishing differs between pieces, do not assume a shared colour name guarantees the same visual effect.
Keep the approved reference identifiable
Record the selected yarn reference, colour reference, sample version and approval date. Keep an identifiable physical reference where practical.
If a revised proposal is needed, name it separately and mark the earlier option as superseded. This makes later questions easier to resolve without relying on a long sequence of chat photographs.
Before you send the brief
- Target reference and approval intent
- Agreed physical viewing method
- Colour reviewed in the proposed knitted surface
- Approved reference and version retained
Bring the details. Let’s review the next step.
Share your garment reference and highlight the decisions you want to discuss.
Discuss Your Project ↗WhatsApp ↗Images are illustrative. AI-generated photographs, edited process scenes and explanatory visuals are not verified records of a particular factory, customer order, approved specification or test result. Confirm product details with the development team.