In short
A mod is a modified version of a fragrance in development, and tracking one means being able to say exactly which formula any sample holds, who has it, and what they said about it. The guide covers the system. This exercise sets one up, because projects usually go wrong in the third week, not the first.
What you will learn
- Design a code that links a sample to its formula
- Keep client feedback attached to the right version
Before this lesson: Stability as a Commercial Gate
What to look for as you read
- How internal codes differ from what a client sees.
- Where feedback should be stored so that it stays attached to its version.
- What to retain, and for how long.
Practical exercise: Track one project's mods
- Write a coding scheme with project, round and mod, plus a separate neutral code for samples sent out.
- Build a log with these columns: internal code, formula version, batch date, sample code, recipient, date sent, feedback and decision.
- Fill it in for an actual sequence of three versions of one of your formulas, and make a retained sample of each.
- Run a test. Pick a sample code at random, then find its exact formula and feedback. Time yourself.
You have done this well if you can go from a code to a formula in under a minute, and feedback is recorded in the person's own words.
Knowledge check
Written and reviewed by the RUŌOD Lab team. This is general education, not legal, regulatory, medical or safety advice. Example dilutions and exercises are for learning, are not validated products, and have not been safety-assessed. Completing a lesson confers no qualification. How we check these lessons.