EU variations in 2026: what changed and what regulatory affairs teams need to check

First: four dates that should not be mixed up

The framework changed in two steps, through two different instruments, and people often run them together. 'The new variations regulation started in 2026' is not quite right: the Regulation changed in 2025, and the Guidelines that most classification work cites changed in 2026.

When an SOP or classification note says 'the new framework', check which of these it means. A document updated in early 2025 may reflect the amended Regulation and still cite the 2013 Guidelines.

What changed on 15 January 2026?

C/2025/5045 is one document with two jobs. It gives procedural guidance for Type IA, Type IB and Type II variations, extensions, urgent safety restrictions and worksharing, and its annex classifies individual changes and lists the conditions and documentation for each. The changes RA teams run into in practice are these:

• The annex was restructured into chapters E (administrative), Q (quality), C (safety, efficacy and pharmacovigilance) and M (Plasma and Vaccine Antigen Master Files), so familiar codes changed.
• Type IA changes that do not need immediate notification are collected into an annual update, a grouping or a super-grouping. Individual submissions are the exception.
• Super-grouping of identical Type IA changes across several authorisations of the same holder is set out case by case.
• Where the same Type IB or Type II change affects several authorisations of the same holder, it must be submitted as one worksharing application.
• An unclassified change needs a detailed justification for submission as Type IB, or as Type II if the holder asks for that.
• If a variation revises the product information, that revision is part of the same variation, with translations for Type IA and IB at submission.
• Quality chapter entries cover post-approval change management protocols (PACMPs) and product lifecycle management (PLCM) documents.
• Submissions use the updated eAF, and supporting EMA guidance was revised on the same date.

The practical point: a variation cannot be planned from an old internal classification table. The current classification entry, its conditions and documentation, and the route-specific EMA or CMDh procedure have to be checked together.

What if the variation started before 15 January 2026?

EMA and CMDh use the same transition rules, with one difference that catches people out: Type IB and Type II go by submission date, Type IA by implementation date.

The new categories and eAF could not be used early. EMA stated that variations submitted before 15 January 2026 using the updated eAF or a new category would not be validated and would have to be revised. The reverse now applies: a 2026 submission that quotes a 2013 code is internally inconsistent, and it is cheaper to catch that before dispatch than after.

Type IA: the annual-update cycle now drives the plan

Type IA changes still need no prior approval, and Type IA IN changes are still notified immediately after implementation. What changed is the rhythm for everything else. EMA and CMDh both state that the first Type IA variation implemented as of 15 January 2026 starts a new annual-update cycle, unless an exemption applies to that change.

For centrally authorised products, EMA's Type IA Q&A (revised July 2026) sets the window: the annual update is submitted no earlier than 9 months and no later than 12 months after the implementation date of the first Type IA change it includes. For MRP, DCP and national products, check the current CMDh guidance for the same point rather than assuming it is identical.

EMA's Q&A lists the routes outside the annual update: as part of an acceptable grouping with Type IA IN, IB or II changes; as part of a super-grouping; resubmission of a single Type IA refused within an annual update; and, exceptionally and with justification, an individual submission straight after implementation. The justified cases include shortage mitigation where regulatory flexibilities were agreed, an EMA-identified public health need, updating the dossier before a routine site inspection or a transfer of the marketing authorisation, a third-country request for proof of EU acceptance of a shortage-related change, and Type IA changes implemented before 15 January 2026 that were not included in an annual update.

The consequence is operational. A Type IA tracker now needs the implementation date of each change, the date that opened the current cycle, and the resulting 9–12 month window per product or per super-grouping.

The classification is not the only thing that changed

Implementation dates reach well beyond the guidance document. They change submission tooling, internal templates, SOPs and controlled classification tables — and those are exactly the places nobody reopens once they look finished.

• Internal variation classification tables
• SOP and work-instruction references
• Submission checklists
• eAF instructions and templates
• Annual Type IA tracking
• Grouping, super-grouping and worksharing procedures
• Training material
• Source and version references in all of the above

IA, IA IN, IB, II or extension: start with the change, not the procedure you want

The classification logic itself is familiar. Extensions are listed exhaustively in Annex I of the Variations Regulation. Type IA conditions are cumulative. When one is not met, the change may go as Type IB under the same code, unless the annex or an Article 5 recommendation makes it Type II, or the holder considers it may significantly affect quality, safety or efficacy. Type IB remains the default category.

What is new is the address. The codes teams know by heart moved: the finished-product batch release entry B.II.b.2 is now Q.II.b.2, and chapter C was flattened, so the product-information change for new safety data is C.4. Do not convert codes by swapping the letter; subsections, conditions and documentation lists were rewritten too.

The full, evergreen classification workflow — reading conditions, unclassified changes, recording the reasoning — is in the guide EU variation classification: IA, IB, II or extension?, linked below. This article only covers what the 2026 change means for it.

Grouping and worksharing need an early check

A group is handled at the level of its highest variation type. Where the same Type IB or Type II change, or the same group, affects several authorisations of the same holder, worksharing is not optional: the application must cover all of them, and a submission that leaves some out has to be amended. Extensions are never workshared, and worksharing does not fit where each product needs its own data or assessment. EMA is the reference authority whenever a centrally authorised product is included.

The rules are short. Knowing which authorisations a change reaches is the hard part, so ask these questions before the classification note is finished, not after:

• Are several of the planned changes linked, so that one pulls others behind it?
• Do they affect one marketing authorisation or several?
• Are several products of the same holder involved, perhaps through a shared site, supplier or excipient?
• Could worksharing apply — and would it be mandatory?
• Which authority would act as reference authority?

The route-specific detail is in the MRP/DCP and centralised procedure guides linked below.

Don't update the classification table and forget the supporting guidance

The framework change came with a set of revised guidance, and a 2026 variation may need both. EMA's Guideline on stability testing for applications for variations to a marketing authorisation, Revision 3 (EMA/CHMP/QWP/441071/2011-Rev.3), was published on 12 December 2025 with a legal effective date of 15 January 2026. The Q&A on post-approval change management protocols, Revision 1, has the same effective date.

So the stability data proposed for a quality change is checked against Revision 3, not the guideline the SOP was written around. The same applies to any change that uses a PACMP. Regulatory change management is not 'download the new classification guideline, done'; it is a connected set of sources that move together and have to be re-checked together.

A practical 2026 RA readiness check

If you check only one thing from this article, check these eight points.

1. Are internal classification tables built on C/2025/5045, entry by entry?
2. Do procedures distinguish 1 January 2025 (Regulation) from 15 January 2026 (Guidelines)?
3. Is the current eAF version built into the submission workflow and templates?
4. Are Type IA annual-update cycles tracked from the correct first implementation date, with the 9–12 month window?
5. Have grouping, super-grouping and worksharing instructions been updated, including the mandatory worksharing rule?
6. Are EMA and CMDh procedural documents referenced by their current revision and date?
7. Have supporting scientific guidelines, such as stability testing for variations, been checked for 2026 revisions?
8. Can a reviewer trace every internal rule back to its current official source?

Example: adding a finished-product batch release site

Proposed change: add a new site responsible for batch release of the finished product. It looks like a one-line answer. It is a sequence.

1. Define exactly what the new site will do: batch release only, or batch release and batch control testing.
2. Open the current entry, Q.II.b.2 'Change to batch release arrangements and batch control testing of the finished product' — not the 2013 B.II.b.2.
3. Pick the sub-entry: (c)(1) release without testing, Type IA IN; (c)(2) release with physicochemical or microbiological testing, Type IA IN; (c)(3) release with biological, immunological or immunochemical testing of a biological product, Type IB.
4. Check every condition: for example, the release site is in the EU/EEA with a manufacturing authorisation for the operations, method transfer is complete where testing moves, and at least one testing site remains in the EU/EEA or an MRA country.
5. Check the documentation list: GMP evidence, the qualified person's declaration on active substance GMP, dossier amendments, transfer protocols, revised product information and, for centralised products, the EU contact for defects and recalls.
6. Confirm the product type and whether batch control testing is also changing.
7. Confirm the route and the EMA or CMDh procedural requirements, including linked changes and worksharing.
8. Prepare the notification on the current eAF and check the dossier and product-information impact.
9. A qualified RA professional confirms the final classification.

Answering 'that's an IA IN' without steps 1, 4 and 6 is unsafe. If the site also tests a biological product with a biological method, the change is Type IB. If a Type IA condition cannot be met, it may become Type IB by default. And a Type IA IN has to be notified immediately after implementation — outside the annual-update cycle — which is a planning fact, not a detail.

Where RafiHive fits

RafiHive's reviewed knowledge base includes the current EU variations framework alongside EMA, CMDh and other official EU/EEA sources. When you research a variation, the agent retrieves the applicable entries, distinguishes law from procedural guidance, shows the source behind each substantive claim, and reports missing facts — such as what the new site will actually test — instead of completing the classification from assumptions. The final classification stays with a qualified professional.