Keep notification, assessment and accountability distinct
A notification reference records a notification event. It should not be presented as an authority's approval of the product's safety or of its marketing claims. A maker reviewing a handover needs to see what was actually done, by whom and for which product revision.
The Commission's CPNP overview describes an information system used by Responsible Persons and, in certain circumstances, distributors, with information available to authorities and poison centres. It does not describe the reference as a product-approval certificate. HPRA's claims guidance expressly identifies approval-implying claims among its legal-compliance examples.
Read four different records
The working diagram separates product identity and evidence, the specialist assessment record, the notification event and continuing Responsible Person activities. The lines show evidence relationships, not an approval conveyor belt. Each record retains its own owner, date, scope and version.
Begin with the product identity. Which formulation, use, market and artwork does the evidence describe? Then inspect the actual assessment and its scope. Next inspect the notification record and the information supplied. Finally identify the person responsible for keeping the relevant product and market records current. One missing answer is not repaired by repeating another record's reference number.
Synthetic handover: replace an approval badge with a factual question
A fictional maker proposes the badge EU approved because someone remembers completing a portal task. No receipt, submission date or product revision has been supplied. The example keeps both the notification evidence and the wording decision unresolved. It does not invent an approved registration number.
Ask the owner to obtain the actual record and connect it to the product. Ask the claim reviewer to consider the proposed wording in context. The working wording file suggests a factual internal record format, such as recording the notification reference and date after verification. It does not approve that text for a public product claim or authorise use of a badge.
If the only file is a portal draft screenshot, retain that distinction. The official Article 13 manual distinguishes the save-draft and notify operations. Establish which event occurred before describing the handover as complete.
Follow a later change
Suppose formula 3 becomes formula 4 after a supplier change. Keep the earlier evidence and notification references. Record what changed and assign the question of which records require updating or renewed specialist review. An older reference does not by itself answer whether the current formulation has been reviewed or its information kept current.
In CosmeBeacon, a file upload, an organisational completeness check and a specialist finding are separate states. A new product revision also remains separate from a decision on an older revision. Use that distinction to ask a precise question rather than attaching a universal approved label to the workspace.
Keep the market branch visible
For GB, use the separate official product guidance and its notification route. Northern Ireland needs a distinct scope check. The diagram is an organisational aid and does not establish a common UK-wide legal route.
The final handover should state the evidence inspected, unresolved questions, responsible owners and next actions. The notification hub supplies the relevant released task guides as they become available. No diagram, portal reference or software status replaces the underlying product-specific work.
Sources and legal dates
European Commission / DG GROW: Article 13 notification overview, recipient authorities and poison centres, and official manual links. No claim of authority-issued product approval.
EU notification system; Northern Ireland scope must be separately verified · Version: Live official overview retrieved 16 October 2026; Article 13 manual listing dated 18 March 2026 · Retrieved: 2026-10-16 · Legal effective date: See the legal-date basis below
Source type: Official guidance
Manual listing dates and retrieval dates do not establish legal application dates or product readiness.
The nanomaterial module and distributor circumstances need their own current applicability review. No actual portal submission was performed.
European Commission / DG GROW Digital Solutions: Guide to Using CPNP for Responsible Persons and Distributors: pages 15-18, 28 and 36, including draft/notify distinction, identity, formulation context and field-specific Not available meaning.
CPNP Article 13 interface guidance; territorial applicability is a separate review · Version: 80-page PDF, last published 18 March 2026 as shown on page 1; downloaded and text-inspected 16 October 2026 · Retrieved: 2026-10-16 · Legal effective date: See the legal-date basis below
Source type: Official guidance
The manual publication date is not the commencement of Article 13. Check the current official manual at the time of the task.
Interface guidance is not a product-specific determination of required notification contents, formulation method or special-substance duties.
HPRA: Claims requirements: marketing channels, evidential support, honesty and approval-implying claims; linked Regulation 655/2013 needs full legal-text review.
Ireland / EU · Version: Live official guidance retrieved 16 October 2026 · Retrieved: 2026-10-16 · Legal effective date: See the legal-date basis below
Source type: Official guidance
Retrieval date is not the application date of Regulation 655/2013. The underlying legal text was not fully retrieved in this batch.
No finding on any real claim, medical boundary or GB/NI wording. Exact current legal requirements and product context require specialist review.
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
Product evidence, assessment and notification records
Diagram · Page revision 1 · 3 KB
Download accountability.svg ↓How to use these unpublished working files
Instructions · Page revision 1 · 1 KB
Download instructions.txt ↓Synthetic notification wording review
Synthetic example · Page revision 1 · 1 KB
Download notification-wording-synthetic.csv ↓