A practical sample-evaluation guide for flavour and fragrance projects: prepare consistently, keep records and send feedback a developer can use.
Decide what this round is for
Useful sample evaluation starts with a question. Are you choosing a creative direction, comparing a revision with a reference or checking performance in the finished product? Write that question at the top of the evaluation sheet. Otherwise a single meeting can attempt three different jobs and produce one very confused answer.
Description, preference and acceptance are different things. A team can describe a sample as more intense without liking it more. The Society of Sensory Professionals distinguishes sensory test methods by the questions they answer. Informal internal feedback has its place, but it should not be presented as a representative consumer study.
Prepare it properly
Use the supplier’s preparation and handling instructions. Confirm that the material is intended for the planned evaluation and ask about any restrictions. Concentrates are development materials; do not improvise tasting, skin application or other exposure. A product that smells appealing still needs to be handled according to its instructions.
Keep the preparation record attached to the sample: code, base version, inclusion level, process, preparation date and evaluation conditions. For fragrance, record the application and observation points. For flavour, record the product preparation and serving conditions. If two people prepared different versions, treat them as different evaluations.
Give every sample an identity
Use clear codes so notes do not become separated from the material. When you are trying to compare sensory properties rather than brand stories, avoid giving one sample an irresistible name and the other a number. Blinded codes and considered presentation order can help reduce avoidable bias.
Keep the session manageable and allow the evaluator to work without a running commentary from the loudest person in the room. Ask for individual notes before a group discussion. The purpose is to hear what people noticed, not to discover how quickly a confident opinion can spread across a meeting table.
Describe the difference
Start with character, intensity and balance. Then describe the sequence of the experience and any unwanted notes. Link every comment to the project target. “More citrus” could mean brighter peel, juicier fruit or a sharper overall impression. Say which one. If you cannot name the note, describe where it appears and how it affects the product.
Keep observations and preferences separate on the page. “The woody note lasts longer” records an observation. “We want that note to recede sooner” gives a development direction. Both are useful. Together they explain what changed and what should happen next, without pretending that personal liking is an objective specification.
Close the loop
Consolidate the feedback before sending it. Include sample codes, preparation records, areas of agreement, unresolved differences and the decision required. If the team disagrees, preserve that fact. A tidy summary that erases disagreement can send development towards a target nobody actually approved.
Finish with a clear next step: keep this direction, revise these characteristics, compare against this reference, or pause while the base changes. State what has been approved and what remains open. A successful sample meeting leaves a decision trail as well as a stack of bottles. That trail is what makes the next round better.
Sources & further reading
General guidance for project planning. Technical requirements depend on the actual formulation, intended use and market.
