Cosmetic Product Safety Reports: a maker's guide

The report and the wider file have different scopes

The Cosmetic Product Safety Report is part of the PIF. HPRA describes Part A as safety information and Part B as the safety assessment, with Part B performed and signed by a suitably qualified assessor.

For a maker, the practical task is to provide an accurate, identifiable information pack and obtain a properly scoped assessment. This page does not teach a maker to sign Part B or turn an automated check into a safety conclusion.

Prepare information, not a prewritten conclusion

Agree the information required for the actual product with the assessor. Identify the specification, intended use, target users, packaging and the material supporting the review. Record what is known and which questions remain open. Keep assumptions distinguishable from confirmed facts.

The GB guidance's safety-report section also explains the Part A/Part B distinction and the assessor's role. It is a GB-scoped source, not a reason to treat GB and Ireland/EU requirements as one interchangeable checklist.

Make the pack easy to trace

Use a cover sheet naming the product and revision. Give attachments stable references and explain why each is included. Keep supplier information linked to the materials used in the current product specification. Mark an outdated or uncertain attachment for clarification rather than silently replacing it with a similar file.

Ask the assessor to confirm what testing or additional information is needed. Do not select a universal testing package from this article or assume that the absence of a test result means a particular test is automatically required or unnecessary.

A synthetic handover question

Sample Product A has a proposed specification and an ingredient bundle. The packaging reference changed after the bundle was assembled. No assessor has confirmed that the pack is sufficient for review.

Create a clear question about the changed packaging and the information the assessor needs. Keep the product record pending. The correct organisational response is to resolve the missing context, not to mark Part A complete because a certain number of files have been attached.

Keep the report connected to the product lifecycle

When a report is received, identify the assessed product, version, signatory, date and any instructions or limitations. Have the Responsible Person and relevant specialist check that the report addresses the intended case. Preserve the relationship between the report and the specification it concerns.

If the product or relevant information changes, ask what review or update is needed. Store the resulting decision and follow-up actions against the new record. Frances's QC review and the safety assessor's qualification are distinct matters; no assessor credential is inferred from the software or a QC role.

Read the source provisions, jurisdiction and review details alongside the example. No report or safety conclusion is issued by following this organisational workflow.

Sources and legal dates