MRP/DCP variations: a pre-submission checklist

Fix the procedure context first

For a mutually recognised product, identify the Reference Member State, Concerned Member States, marketing authorisation numbers and the currently approved common and national product information. Confirm whether the proposed change affects one authorisation, several authorisations, or products that may qualify for grouping or worksharing.

The EU legal framework provides the classification basis, while CMDh publishes operational guidance for submission and processing in MRP/DCP. Both layers are needed for a defensible plan.

Products authorised through the decentralised procedure are handled as mutual recognition products once the initial procedure closes. Post-authorisation, the distinction that matters is not MRP versus DCP but whether the product sits in a Reference Member State-led procedure at all, or is a purely national authorisation that follows national rules.

Who does what in an MRP variation

The Reference Member State validates the application, leads the assessment and circulates its conclusions. Concerned Member States receive the same submission, can comment within the procedure and must reflect the agreed outcome in their national authorisations. The applicant deals with one assessing authority but with every national agency on fees, translations and administrative particulars.

The consequence for planning is that a submission is only as ready as its weakest national component. A scientifically complete package can still stall at validation in one Concerned Member State over a missing fee confirmation, a national form or a local administrative requirement nobody checked.

Where a Concerned Member State cannot recognise a Type II decision on grounds of a potential serious risk to public health, the matter is referred to CMDh (Article 13 of the Variations Regulation). This is uncommon, but it is the reason a Type II timetable in a multi-country procedure should carry contingency rather than end on the expected approval date.

What each variation type means in practice

Type IA changes are implemented first and notified afterwards. Standard entries are notified within twelve months of implementation — as an annual update, within a group, or in a super-grouping across several authorisations of the same holder. Entries the guideline marks as requiring immediate notification are notified immediately after implementation. If a notification is rejected, the holder must stop applying the change.

Type IB changes are notified before implementation. If the Reference Member State sends no unfavourable opinion within 30 days of acknowledging a valid notification, it is deemed accepted by all relevant authorities. An unfavourable opinion is not the end: the holder has 30 days to submit an amended notification addressing the grounds given.

Type II changes are assessed before implementation. The Reference Member State has 60 days from acknowledging a valid application to prepare its assessment report and decision; it can shorten that for urgent matters, or extend it to 90 days for changes to therapeutic indications and for groups that needed the authorities' agreement to be combined. Requests for supplementary information suspend the clock. The Concerned Member States then have 30 days to recognise the decision.

Approval is not the implementation date. An accepted Type II change in an MRP may be implemented 30 days after the Reference Member State informs the holder, provided the documents needed to amend the marketing authorisation have reached the Concerned Member States, and those Member States amend the national authorisations within two months of being informed.

• Record the implementation date for every Type IA change at the moment it happens.
• Do not implement a Type IB change before the review period ends without an unfavourable opinion.
• Build clock stops and response-preparation time into every Type II plan.
• Send the documents needed to amend national authorisations promptly — the 30-day implementation wait depends on it.

Build one controlled application inventory

Create a single inventory of variation codes, present-versus-proposed changes, conditions, documentation, affected strengths and pharmaceutical forms, and impacted countries. Reconcile that inventory with the electronic application form and cover letter.

The inventory is the document every downstream artefact is checked against. The application form, the cover letter, the eCTD sequence and each national administrative package restate parts of it, and discrepancies between them are the most common validation findings in multi-country procedures.

Include products that are not in scope and say why. A reviewer who sees three strengths listed and a fourth omitted will ask whether the omission was deliberate; the inventory should already answer.

• Confirm the current CMDh chapter for the selected variation type.
• Check variation numbering, grouping and worksharing rules.
• Identify common product-information changes and national translations.
• Confirm Member State administrative requirements and fees outside the common package.
• Plan validation responses, timetable ownership and dispatch evidence.

Grouping and worksharing across Member States

Grouping combines several changes to the same marketing authorisation in one submission. Combinations listed in Annex III of the Variations Regulation can be grouped as of right; other combinations need the agreement of the Reference Member State, in consultation with the Concerned Member States. Type IA changes can also be super-grouped: one notification covering several authorisations of the same holder, in the cases the classification guidelines list.

Worksharing lets one reference authority assess the same Type IB or Type II change, or group without an extension, across several authorisations of the same holder. When at least one of the authorisations is centrally authorised, EMA is the reference authority. Otherwise the holder states a preferred reference authority and CMDh chooses one.

Worksharing can be refused where the same change needs separate supporting data or a product-specific assessment for each product. Plan it for genuinely common changes — a shared site, a shared supplier, a class-wide safety update — rather than for changes that only look alike on the cover letter.

Unforeseen changes and Article 5 recommendations

Where a change is not covered by the classification guidelines, the holder can request a recommendation on its classification before submission. For MRP/DCP products the request goes to the Reference Member State, which consults CMDh and EMA if the answer would create a new classification. The recommendation is due within 60 days, and CMDh publishes agreed recommendations so that similar changes are classified consistently.

Search the published CMDh recommendations before requesting a new one. A matching recommendation is a citable classification source; a near-match is a reason to read its reasoning, not to copy its outcome.

Product information across languages

An MRP product has common product information agreed in English and national translations in each Concerned Member State, plus national particulars on the packaging. A change to the common SmPC, labelling or package leaflet is not complete until every national version reflects it.

CMDh sets expectations for when and how national translations are provided after a procedure ends; the timelines are short, so translations should be prepared in parallel with the procedure rather than started when the outcome arrives. National labelling particulars — the information Member States require in the 'blue box' on the outer packaging — sit outside the common text and need their own check.

Significant changes to the package leaflet may also require evidence that the leaflet remains readable for patients, either through new user consultation or a justified bridging argument. Decide this at planning stage; discovering it during assessment adds a clock stop.

• Track each national translation against the final agreed English text, not an interim draft.
• Check national packaging particulars separately from the common labelling text.
• Assess whether leaflet changes need user consultation or a bridging justification.
• Keep a record of which version each Member State has implemented.

Submission mechanics

MRP and DCP submissions are made in eCTD format and are typically delivered to the national agencies through the Common European Submission Platform (CESP). Confirm each involved authority's current delivery requirements; a small number of national specifics still apply.

The procedure number encodes the Reference Member State, the product, the strengths concerned, the variation type and a running number, with distinct forms for grouped and worksharing procedures. Use the numbering rules in the current CMDh guidance and apply the same number consistently across the application form, cover letter and eCTD envelope.

Keep dispatch evidence for every recipient authority. When a Concerned Member State reports that it never received a sequence, the delivery receipt is the fastest resolution.

Use the live CMDh hub as the entry point

CMDh best-practice guides are revised over time and different chapters can carry different revision dates. Link a working instruction to the current Variation Procedure hub, then record the exact document revision used for the submission.

The Variations Regulation was amended by Delegated Regulation (EU) 2024/1701, applicable from 1 January 2025, and the new Commission classification guidelines (C/2025/5045) apply from 15 January 2026. Procedures, templates and SOPs written against the earlier framework should be re-checked rather than assumed current.

This checklist is an orientation aid, not a substitute for the current CMDh documents, national requirements or qualified regulatory review.