Turn a scent idea into a useful fragrance brief, from sensory direction and references to the product base and intended use.
Give the scent somewhere to live
A fragrance brief describes the scent you want, the product it belongs in and the conditions it needs to work under. Start with the application. Fine fragrance, a wash-off product and a room product create different questions. “One scent for everything” is an ambition to discuss, not a technical specification.
Explain the role of scent in the experience. Is it the main reason someone chooses the product, a quiet supporting detail or a strong signal during use? Describe the audience and the context without turning them into a demographic cliché. A product for an early morning routine has a different job from a fragrance designed to make an entrance.
Translate the mood into something discussable
Words such as fresh, warm and premium are useful openings. Follow them with details. Does fresh mean cut citrus peel, airy linen or green leaves? Does warm mean soft woods, spice or a rounded sweet character? If you are unsure, show a range of references and explain the part that appeals.
Visual references can open a creative conversation too. A material, a place or a colour palette can communicate atmosphere. Then connect the mood to the product: restrained or assertive, dry or sweet, familiar or unexpected. The aim is a shared direction, with room to discover a better answer during development.
Share the awkward details early
Provide the product base, intended fragrance concentration, manufacturing process, packaging and planned markets. If a base has its own noticeable odour, flag it. If clarity or colour is central to the product, make that explicit. Give the technical team the actual formulation or agree how confidential information will be handled.
Ask which application tests are appropriate and who will perform them. Supplier guidance and your finished-product development programme need to join up. A fragrance can be evaluated creatively before every technical question is resolved, provided the team understands what that evaluation can and cannot approve. Write those boundaries into the project notes.
Keep the paperwork specific
Ask for the documents relevant to the selected fragrance, intended use and market. Where appropriate, an IFRA Certificate of Conformity addresses conformity with IFRA Standards for a specified use. The supplier issues it; IFRA does not certify the finished product. It does not replace a safety assessment.
Tell the team about any ingredient restrictions, declaration requirements and claims you intend to make. Avoid turning “natural” into a shortcut for suitability. State the precise requirement and ask what evidence supports it. Keep a record of the product code and document versions that belong to your approved sample.
Make feedback a direction, not a verdict
“Too much” is a feeling. “The opening is right, but the sweet note dominates the experience we want” gives development somewhere to go. Discuss which characteristics should stay, which should change and what the next version needs to answer. Specificity leaves more room for creativity because everyone can see the target.
Close the brief with the project budget, likely volumes, decision-makers and key dates. Agree the next step, then keep the brief live as the product evolves. Great creative direction is a conversation with a memory. Write down the parts worth remembering.
Sources & further reading
General guidance for project planning. Technical requirements depend on the actual formulation, intended use and market.
