Plan Colour Development with Clear References
A colour direction needs a defined material and review basis. Keep inspiration, development and approved references distinct.
Illustrative colour review: a charcoal sample looks too blue to the designer, while purchasing only writes 'make it darker'. Identify the sample and reference together, record the viewing conditions, and separate hue feedback from lightness feedback. Ask for a revised candidate against that specific request; a new version still needs its own review.
Information needed for this decision
Identify the physical reference or the named colour system and edition, and say whether it is an inspiration target or an agreed reference. Link it to the candidate item, composition and finish. Ask which colour-development sample can actually be supplied, its purpose and conditions. Do not assume every programme offers the same lab-dip or woven-sample process.
Check the missing conditions
| Review problem | Information to record | Decision to request |
|---|---|---|
| Image only | Inspiration status; physical reference absent | Agree a physical review reference |
| Sample looks different | Sample/base IDs and viewing conditions | Review hue, lightness or texture separately |
| One colour approved | Approved version and colour allocation | Confirm each remaining colour |
| Base or finish changed | New material revision | Confirm whether colour review repeats |
Review the next action
A useful feedback record says which candidate was seen, what difference matters and what action is requested. Retain the actual physical reference and ask whether a proposed process changes the sample format. If visual agreement is insufficient for the project, agree the measurement method and acceptance criteria with the responsible parties before testing.
Copy and complete the worksheet
Give each colour its quantity and unit, including provisional splits. Ask separately about development conditions and minimum quantities per style and colour for the candidate programme. A published style minimum or a successful sample does not confirm that your proposed colour split can be ordered.
Colour reference ID and target status: ____________________ Candidate item, composition and finish: ____________________ Colour quantity and unit: ____________________ Development sample, cost and conditions: ____________________ Sample revision and viewing conditions: ____________________ Requested hue or lightness change: ____________________ Reviewer, date and approved scope: ____________________ Bulk-reference arrangement and open attributes: ____________________
Conditions before moving forward
Close a colour decision only against an identified sample, reviewer, date and scope. Ask how the physical reference will be retained for bulk discussion. Keep colour, finish and garment trials as separate approval tasks. A changed base or finishing route may need a fresh review; the previous version remains history rather than approval of the replacement.
Questions that make fabric colour approval usable
Can I approve a fabric colour from a phone photo?
A photo can communicate a direction or document a discussion, but screen and lighting conditions limit physical comparison. State that limitation and request the appropriate physical sample before describing the exact colour as approved.
Does a colour code guarantee a match on wool fabric?
No. Record the reference system and edition, the candidate base and finish, and the agreed comparison method. A code is a reference request; project acceptance depends on the actual candidate and the criteria the parties agree.
Should I approve colour and hand feel together?
Record them as separate decisions on the same identified sample. A colour approval does not automatically approve finish, handle or garment behaviour. Show open attributes and ask whether a later material change requires a new colour review.