Make the proposed role change traceable

Start with the exact product set, recorded market, current role evidence and proposed new arrangement. Identify what is changing: the entity, its address, an administrative contact, access to records or the supply activity. These are different facts and should not be compressed into a new contact name in a spreadsheet.

The HPRA role guidance is the Ireland/EU starting point. Article 4 of the current EU consolidation describes particular role and designation circumstances, including written mandate and acceptance provisions. The reviewer must establish which circumstance applies; this organiser is not an appointment contract or a determination that a proposed entity qualifies.

Record the actual scope

List the product identifiers and revisions, relevant destinations, business activities and the proposed effective arrangement. Keep a target handover date separate from the specialist's legal-date finding. Do not infer the applicable establishment requirement from a country abbreviation in a mailing address.

The GB guidance and NI scope require separate review. A service agreement covering one destination should not silently become the evidence for all markets.

Build the handover index

The blank organiser records the existing and proposed role references, the legal basis to verify, acceptance evidence where applicable, product-file access, assessment and artwork references, notification questions, unresolved actions and owners. Use actual document versions and retain the earlier arrangement.

For each topic, distinguish evidence located, completeness checked and specialist finding. A new party receiving a folder does not by itself establish a valid appointment or resolve the duties attached to the role.

Synthetic cream: a proposal with missing acceptance evidence

Fictional SAMPLE-CREAM, revision 3, has a proposed change from Example Entity A to Example Entity B for an Ireland/EU scope. No actual entity, address, signed mandate, acceptance or role decision is supplied. The example records those absences explicitly.

One sample owner must obtain the proposed scope and role evidence. Another task concerns the product-file access arrangements. The notification and artwork implications remain questions for the appropriate reviewer. No real appointment is made and no portal update is performed by completing the example.

Check the records that depend on the decision

Once a real scoped decision is recorded, identify which associated records require action. Do not rewrite old artwork or notification history to make it appear that the new arrangement always applied. Retain the earlier product and role references and the date basis used for the actual change.

Verify that the agreed recipient can access the controlled product information and unresolved actions. Record who checked access and what remained unavailable. Coordinate confidentiality and retention arrangements with the responsible owner instead of using a public folder link as a substitute for a handover.

The roles hub provides the released next tasks. Finish with a documented question or decision, its product and market scope, evidence versions and accountable owners. The administrative organiser supports that review; it does not replace the legal role analysis or either party's actual acceptance.

Sources and legal dates

HPRA: Responsible Person guidance: role, activity examples, appointments and pre-market documentation

Ireland / EU · Version: Live web guidance retrieved 16 October 2026 · Retrieved: 2026-10-16 · Legal effective date: See the legal-date basis below

Source type: Official guidance

Guidance retrieval is dated. Applicable legal provisions and their dates remain a separate specialist check.

An individual role decision needs the actual manufacturing, branding, import and appointment facts.

EUR-Lex / European Union: Regulation 1223/2009, Article 2 cosmetic definition and Article 4 role/designation circumstances, including written mandate and acceptance provisions. No case-specific appointment or product classification.

EU; territorial applicability for NI needs separate confirmation · Version: 18 May 2026 consolidation shown as current on retrieval, checked 16 October 2026 · Retrieved: 2026-10-16 · Legal effective date: 2013-07-11

Source type: Regulation

Article 40(2) gives 11 July 2013 as the general application date, with express exceptions. This records the base date for Articles 2, 4 and 11; it does not establish later amendment dates, a case-specific result or NI applicability. Annex V entry 29 is used only as an identity reference. Date metadata checked by Codex against the cited EUR-Lex text on 16 October 2026.

Identify the actual business activities, entity establishment, market and product presentation. Authentic acts, relevant amendments and application dates require specialist verification.

GOV.UK / OPSS: GB guidance: scope, Responsible Person, PIF, safety information and assessor responsibilities

Great Britain · Version: Current official web guidance retrieved 16 October 2026 · Retrieved: 2026-10-16 · Legal effective date: See the legal-date basis below

Source type: Official guidance

The guidance publication date and retrieval date are not substituted for the legal effective dates of the relevant GB provisions.

GB is separate from NI. Current amended law and case-specific exceptions are not inferred from this summary.

Related next steps

Reviewed downloads

How to use the role-change working files

Instructions · Page revision 1 · 1 KB

Download instructions.txt ↓

Blank proposed role-change handover

Blank · Page revision 1 · 1 KB

Download role-handover-blank.csv ↓

Synthetic unconfirmed role-change proposal

Synthetic example · Page revision 1 · 2 KB

Download role-handover-synthetic.csv ↓