Cosmetic safety assessor handover checklist

Give the assessor a traceable handover

A handover should let the next person identify the product, open the evidence and see the unanswered questions. Start with a stable product reference, formulation revision, intended use, packaging and intended sales destination. Agree the recipient and scope before sharing confidential composition or supplier records.

The GB official product guidance distinguishes safety information from the qualified assessor's assessment. For Ireland/EU, the HPRA CPSR guidance provides the corresponding authority starting point. The organiser below helps prepare a discussion; it is not the complete legal contents of a safety report or a certificate that a product is ready.

Use the blank organiser for the real product

Download the blank file and create a separate copy for each product revision and market scope. Enter the sender, intended reviewer and handover date when known. Keep any proposed deadline distinct from a statutory date. Agree which files the recipient needs and how access will be provided.

For each topic, record the precise evidence reference and version, its location, presence, completeness and the unresolved question. Avoid a single received checkbox that could be mistaken for reviewed. A file can be available but relate to an older formulation or leave an important question unanswered.

Synthetic cream: complete the administrative record honestly

The fictional SAMPLE-CREAM handover concerns formula 3 and an Ireland/EU scope. Its rows identify proposed packaging, supplier information, safety evidence and intended use. They deliberately record missing composition and testing information rather than inventing values. No real formulation, assessor, safety report or test result is included.

The sample has an owner for obtaining each missing item. That is a completed administrative example of an incomplete evidence bundle. It does not show a completed assessment. Keep it separate from the blank file and do not replace its fictional product name with a real product while leaving the invented references in place.

Ask the reviewer to define the remaining evidence

Use the handover conversation to resolve identity, scope and evidence questions. A maker may know which supplier record exists; the assessor determines what information and reasoning are needed for the actual safety assessment. The organiser does not prescribe a universal testing package or infer that every test is either mandatory or unnecessary.

When the recipient asks for more information, retain the request, product revision, owner and response reference. Do not overwrite the original question with a file name and lose the reason it was requested. Link a returned file to the question it is intended to answer.

Verify the bundle from the recipient's view

Check that the named recipient can open the agreed files and identify the current version. Retain the evidence index used for the handover. Record any access failures separately from substantive gaps. Public sharing links are not needed simply because the task is urgent.

Use separate copies and authority routes for GB and NI questions. This Ireland/EU example does not establish those markets' evidence requirements or assessor arrangements. Record the recipient's actual agreed scope rather than labelling the bundle internationally compliant.

After the review, retain the actual finding, its scope and the evidence versions considered. New formulation or evidence revisions may create another review question. Use the workspace to keep those versions and owned actions connected. The assessor-preparation guide and resource hub become linked next tasks when their reviewed versions are released.

Sources and legal dates