How to brief a flavour project: the product, the sensory target, the constraints and the decisions that move development forward.
Start with what you are making
A flavour brief is a working description of the product you want to create and what its flavour needs to do. It gives everyone a shared target before samples start travelling. It can be short. It cannot be vague. “Something fruity” leaves rather a lot of fruit on the table.
Begin with the finished product, the intended user and where it will be sold. Say whether you are developing a new launch, changing an existing product or looking for another supply option. These are different projects, even when the flavour name on the request is identical.
Give the flavour a job
Describe the experience in ordinary words. For a citrus direction, that might mean fresh peel at the start, juicy character through the middle and a dry finish. Explain the balance you want, the notes you want to avoid and how strong the flavour should feel in the finished product.
Bring a reference when it helps, then say exactly what it demonstrates. You might like its opening but dislike its aftertaste. You may want its intensity with a completely different character. A reference plus a clear explanation is more useful than a reference treated as a mind-reading test.
Bring the base into the conversation
Share the base recipe and relevant processing information with the technical team through an agreed confidential route. Include known ingredients, intended preparation, processing stages, packaging and storage. Flag any parts of the formulation that are still changing. The developer needs to know which version of the product they are solving for.
If the base is unavailable, say so. Ask how early screening should be handled and what it can establish. A promising sample in a demonstration base is a development step. Approval should be tied to the product you intend to make. Food and drink flavourings also have use conditions; the application and sales market belong in the brief from the start.
Make the commercial constraints useful
Give an indicative cost target for the finished product alongside expected volumes and likely launch quantities. If you have a concentrate price target, explain the basis. A price per kilogram means little without understanding how the material will be used. State whether the target is firm, estimated or still being worked out.
List required declarations and restrictions in precise terms. Share the wording your technical team needs to support, rather than adding a broad “clean” or “natural” label and hoping everyone means the same thing. Include your target launch window, approval owner and purchasing process. Dates are easier to discuss when dependencies are visible.
Decide how you will decide
Before development begins, agree who evaluates samples, which base they use and what counts as progress. Separate sensory comments from technical acceptance and commercial approval. Put the sample code, preparation details and evaluation date beside every set of notes so feedback points to the right version.
A useful first brief can fit into six statements: what we are making; who it is for; how it should taste; what the base and process require; what the commercial limits are; and how we will approve it. Start there. Bring the ambition. Leave the guessing out.
Sources & further reading
General guidance for project planning. Technical requirements depend on the actual formulation, intended use and market.
