Cosmetics compliance action register template

Write an action that can be checked

An action needs a specific task, an owner and a way to recognise its completion. Obtain the current supplier declaration for formula 3 is more useful than sort compliance. Add the relevant product revision, market and evidence question so the next person understands what the task concerns.

The blank register is an administrative organiser for follow-through. It does not determine legal duties, promise complete coverage or convert a task status into a product compliance decision. The HPRA cosmetics guidance directory and GB product guidance provide separate authority starting points where a specialist needs to establish the underlying requirement.

Make the date mean something

Record the operational target date and its basis. If a legal deadline is relevant, keep its exact provision, applicability decision and reviewed date basis separate. Do not turn a convenient internal Friday deadline into a claimed regulatory transition date.

If the date is unknown, record who will resolve it and what information is missing. A blank date is a visible planning gap. An invented date hides that gap and can mislead the person prioritising the work.

Synthetic formula 3: one request, a separate review

The sample register contains three fictional tasks. The first asks a sample owner to obtain a supplier declaration. It is marked Done because the hypothetical file-request task is described as completed. Its specialist finding remains unresolved: receiving a file has not established its suitability.

The second task asks the specialist to review that declaration for the exact formulation and market. It remains In progress. The third asks the owner to obtain the evidence needed for a legal-date question and remains Open. No real reviewer, source finding or legal deadline is supplied.

The target dates demonstrate scheduling fields only. They are invented operational targets, not recommendations for a real product. The sample's closure descriptions refer to hypothetical records and should not be copied into customer evidence.

Keep evidence and closure separate

Record the file or finding used to close the task, who checked it and when. Where the action depends on a specialist decision, identify that decision explicitly. Do not close review the artwork merely because a designer uploaded a new PDF.

Use separate fields for task status, evidence completeness and specialist finding. A task can be finished while the product still has other open questions. A product change can also make an earlier action's scope worth checking without erasing the fact that the original task was completed.

Revisit ownership and dependencies

If an owner changes, record the handover and the remaining task. Do not leave an action assigned to an inaccessible account. Where one task depends on another, name the dependency and keep both outcomes visible. Waiting for a supplier and reviewing the returned evidence are different activities, even if the same person coordinates them.

Maintain Ireland/EU, GB and NI scope decisions separately. A shared administrative format can be reused, but the legal question and source basis must remain market-specific. No generic UK finding is supplied by the template.

Use a fresh blank organiser for real work, keep the synthetic file separate and agree how often the owner reviews outstanding tasks. The workspace action list can then filter by product, owner and due date while the review records retain the actual findings. Related released action and change-workflow guides provide the next task when available.

Sources and legal dates