Build a folder that another person can navigate

A digital product information file needs a reliable route from the product on the shelf to the evidence used for its review. Begin with a stable product identifier, a named record owner and the intended sales market. A folder called final-final does not establish which formulation, artwork or assessment it contains.

For Ireland/EU, Article 11 of Regulation 1223/2009 addresses the PIF, including accessibility in electronic or other format. The HPRA PIF overview describes its main components. The folder proposal below is an organisational example, not a prescribed legal format or a finding that those components are complete.

Start with the index, then the folders

Keep one index at the top level. For each item, record its document identifier, title, issuer, revision, issue date, file location, applicable product revision and review state. Add the specific unresolved question where an item is missing. The index should show what the reviewer can inspect today, rather than only the documents somebody intends to obtain.

Group working records by purpose: product identity and formulation; supplier evidence; safety information; manufacture; artwork and claims; and review decisions. Agree the legal contents with the specialist. Put a short explanation beside any empty section so an absent file is not mistaken for an irrelevant requirement.

Synthetic Product A: changing the formula

Product A is a fictional face cream with product identifier SAMPLE-A. Its formulation changes from revision 2 to revision 3 while artwork revision 4 is still being prepared. Retain the revision-2 index and its referenced files. Create a new working index for revision 3 and identify which records are reused, replaced or awaiting review.

Use a name such as SAMPLE-A_FORMULA_r03_2026-10-16.pdf. Keep the issuer's original name in the index where the local filename differs. Do not change a supplier's issue date to the date you downloaded its file. Link an artwork record such as SAMPLE-A_ARTWORK_r04 to formulation revision 3 explicitly; matching numbers are not required and should not be assumed.

The working folder-layout file shows this example. Its names and empty placeholders are synthetic. A folder called reviewed contains only a saved decision and the evidence references within its scope; moving a file there does not confer approval.

Give access for the task

Use named access where the chosen document system supports it. A maker maintaining the index may need edit permission; an external assessor may need access to a defined review bundle; a packaging designer may need only the artwork and correction record. Avoid sharing formulation files through a public link merely because the artwork review is urgent.

The access example records intended permissions and the check needed to confirm them. It does not demonstrate permissions in a real storage account. Test the recipient's actual view and revoke access when the agreed task ends. Keep the Responsible Person's access arrangements separately documented.

Verify the handover

Open the index from the recipient's view, follow several file links and confirm the product revision. Check that a withdrawn file remains distinguishable from its replacement. Agree backup, recovery, retention and authority-access arrangements with the record owner and specialist; a successful cloud upload answers none of those questions on its own.

Great Britain has a separate official PIF route. Keep GB and Northern Ireland scope decisions separate instead of renaming an Ireland/EU folder UK. Return to the PIF task index, D00, for the next evidence question, or use the product-evidence workflow to record the exact version being handed over. Links to unreleased guides remain unavailable until review and publication.

Sources and legal dates

HPRA: PIF guidance: product-specific file, components and retention; cross-check current Article 11 before publication

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

Do not infer a legal date from the web retrieval date. The legal basis and applicable dates require Frances's review.

Retention triggers, version scope and cross-market applicability need specialist confirmation.

EUR-Lex / European Union: Article 11, particularly paragraph 3 on access; Annex V entry 29 identity reference for Phenoxyethanol. No finished-product finding or concentration calculation.

EU; separate territorial applicability review required for Northern Ireland · Version: Consolidation 18 May 2026, shown as current by EUR-Lex on retrieval; authentic acts and subsequent amendments require publication review. · 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.

No product-specific application or transition date determined. The current consolidation date is not substituted for legal application dates.

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

Synthetic task-based permission review

Synthetic example · Page revision 1 · 1 KB

Download access-example.csv ↓

Synthetic product-revision folder layout

Synthetic example · Page revision 1 · 2 KB

Download folder-layout.txt ↓

How to use these draft working files

Instructions · Page revision 1 · 2 KB

Download instructions.txt ↓