A clear identity.
Record the product name, internal reference, category and a short description. Use a stable record for the product, with revisions for changing details. A record name should distinguish similar products and variants.
A file being present does not mean it has been reviewed.
Synthetic example: “Willow face oil / 30 ml / revision 2” is easier to distinguish than three documents named “final oil”.
Market scope with visible unknowns.
Record where the product is sold or intended to be sold. Keep Ireland/EU, Great Britain and Northern Ireland as separate selections in the workspace. This is information for later scoping, not confirmation of regulatory coverage.
Use “not confirmed” when you do not know. An empty field should not silently become an assumption about the market.
Evidence with a useful description.
Link supporting files to the relevant product. Record when they were added, what they are intended to support and any open questions. Keep documents private to the people authorised to work with them.
An ingredient list, artwork file or supplier document can each serve a different purpose. The filename alone rarely explains the scope.
Actions and review history.
A workspace should show unfinished tasks alongside the underlying record. Keep decisions connected to the version reviewed. Record changes and their author so a later reviewer can understand what happened.
The workspace organises the work. A competent specialist still determines what the product needs and whether the evidence answers the question.
An organisational workflow guide. This article does not define regulatory obligations or certify a product. Specialist regulatory guidance has a separate review gate.
Download a blank organiser →