Make every sample review answer a question.
A sample should help your team make a decision. Before asking whether you like it, define what the review is meant to establish: the texture direction, fragrance preference, dispensing experience or a specific change from the previous version.
1. Write the sample brief before the sample request.
Start with the product format, intended user, routine and market. Explain how the product should feel when dispensed, spread and left on the skin or rinsed away. A reference product can make the conversation more precise, but identify the feature you want to discuss rather than asking for an exact copy.
Distinguish requirements from preferences. “Must dispense through the selected pump” is a functional requirement; “a slightly silkier finish would be preferable” is a sensory direction. Ask which aspects the development sample represents and which will be checked later using the proposed commercial component.
- Identify the format and intended use.
- Name the reference and the specific feature it illustrates.
- Record fragrance preferences and ingredient constraints for review.
- Identify the proposed component and any open packaging decisions.
2. Compare under consistent conditions.
Give each sample a version reference and keep its accompanying information. When comparing sensory characteristics, use a consistent amount, application area and sequence. Record your observations before discussing them with the rest of the team so one strong opinion does not replace everyone else’s assessment.
| Review point | Specific observation to record |
|---|---|
| Dispensing | How readily the sample leaves the container; whether the output feels controllable. |
| Application | Initial flow, spread and resistance during application. |
| Finish | Perceived residue, tackiness, shine and comfort after application. |
| Rinse-off use | Lather character and rinse feel, where relevant to the format. |
| Fragrance | The perceived character and intensity, using the agreed reference. |
These observations describe experience. They do not establish clinical performance, microbiological quality, long-term stability or suitability for every user. A pleasant sample still needs the product-specific review and evidence required for its intended use.
3. Make feedback actionable.
Replace “make it better” with a change the development team can discuss. For example: “Sample B spreads as intended, but feels tackier than the reference after application. Retain the initial flow and review the finish.” This preserves what works while identifying the variable to change.
Consolidate feedback into one agreed response. Rank requested changes and name the person who approves the next version. If fragrance, viscosity and packaging are all changing, record them separately and agree which comparison remains meaningful. Confirm the cost, scope and timing of any further revision with the project team.
4. Close the review with a clear handoff.
Record the accepted sample reference, the features approved and the questions still open. Formula approval, artwork approval and component approval are connected decisions, but a single “looks good” message should not stand in for all three.
The Cosmetics Europe / CTFA stability guidance includes physical, chemical and microbiological considerations and the contents–container relationship. This is why a sensory sample review and a stability or packaging assessment serve different purposes. Agree the applicable checks and documentation for the actual product before production preparation.
- Approved sample reference and review date.
- Requested changes, if any, with a named decision owner.
- The intended component and artwork status.
- Further testing or review required for the agreed specification.
Sources & further reading
Practical examples and checklists are editorial guidance. The references below support the technical background and company information.
- Cosmetics Europe / CTFA — Guidelines on Stability Testing of Cosmetics (2004)
Background on stability studies and the formula–container combination.
- Yuanze — Product Development
Yuanze’s published cross-functional development workflow.
