From fragrance brief to approval sample.

The fastest way to lose time in fragrance development is to make every sample answer every question at once. A better workflow gives each round a job, records what was learned and keeps the finished product in view.

Write a brief that gives the idea a home.

Start with the product, not only the notes. A reference such as “fresh floral” or “warm amber” becomes more useful when the development team knows how the scent will be experienced.

• Product format: identify the fine fragrance, personal-care, home, air-care or fabric-care application.
• Audience and market: describe who will use it, where it will launch and the positioning it should support.
• Olfactive direction: share the mood, materials, references, dislikes and the memory you want the scent to create.
• Performance intention: explain whether the priority is opening, radiance, comfort, room diffusion, freshness or lasting character.
• Project context: include target timing, estimated volume and any documentation requirements already known.

For category-specific prompts, start with DOWRY’s pages for fine fragrance, personal care or home and air care.

Give the first sample one job.

Define what the first round needs to clarify. It might be the overall direction, the balance between freshness and warmth, the way a fragrance opens, or whether an idea belongs in the intended base.

Keep the evaluation language concrete. Instead of asking whether the sample is simply “good”, ask which part is working, where it moves away from the brief and what should change in the next round.

Evaluate the scent in context.

Blotter evaluation can help compare direction, but the finished product creates the real decision. Skin, a wash base, a cream, a candle, a diffuser, a spray or a fabric-care format can change how a fragrance opens and remains.

Review the sample in the intended use moment and record the basics: first impression, development, texture, diffusion, persistence and any interaction with the product base. The right review route depends on the formula and the market requirements for the project.

Define what “approved” means.

Approval is easier when the team agrees on the decision criteria before the final round. Confirm the chosen direction, intended format, target market, required documentation path and the internal owner of the decision.

Then keep a simple record of the approved reference and the next production conversation. Technical documents and safety requirements should be scoped against the actual formula and destination market, rather than assumed from a generic checklist.