For medicinal products registered under the Eurasian Economic Union framework, variation management is no longer a Russia-specific regulatory exercise. The governing system is the EAEU Rules for Marketing Authorization and Expert Examination of Medicinal Products for Human Use under EEC Council Decision No. 78, with the detailed variation framework contained in Appendix No. 19.
This distinction is important in 2026.
For medicinal products that still have a Russian national marketing authorization only because a transition-to-EAEU procedure was initiated before the end of 2025 and the national authorization remains temporarily valid while that procedure is completed, the extension of validity does not recreate a normal Russian national pathway for new post-approval variations. Under the transition provisions of Decision No. 78, changes to nationally formed medicinal-product dossiers under national law were available only through 31 December 2025.
The remaining routine Russia-specific variation pathway is principally relevant to pharmaceutical substances manufactured for sale and included as standalone entries in the Russian State Register of Medicines. Changes to those API documents continue under the Russian Federal Law No. 61-FZ, including Article 34 with reference to Articles 30 and 31. This is a separate national API procedure and should not be confused with EAEU variations to a medicinal-product dossier.
For medicinal products, the core question is therefore:
What exactly is changing in the approved EAEU dossier, how is that change classified under Appendix No. 19, when may it be implemented, which data are required, which member states are affected, and can related changes be grouped without creating a more complex regulatory pathway than necessary?
For an international regulatory team, the difficult part is rarely locating the word “variation”. The difficulty is converting a real manufacturing, analytical, safety or commercial change into the correct EAEU code, procedure and dossier package.
Appendix No. 19 is a decision system, not a short list of variation types
The EAEU framework uses familiar high-level categories:
- IA — minor variation;
- IA_NU — minor variation requiring prompt notification after implementation;
- IB — minor variation requiring assessment;
- II — major variation;
- extension of the marketing authorization — a change sufficiently substantial to require the extension procedure rather than an ordinary variation.
That top-level list is deceptively simple.
The current classification is highly granular. Supplement V to Appendix No. 19 classifies changes through a structured code system and, for individual variation codes, specifies:
- the regulatory scenario;
- the conditions that must be fulfilled;
- the documents and supporting data that must be submitted;
- the applicable procedure.
The classification covers much more than manufacturing-site changes. It includes administrative changes; active-substance manufacture and control; finished-product manufacture and quality control; specifications; analytical procedures; packaging; stability; post-approval change-management protocols; pharmacopoeial and CEP-related changes; devices or other products included in a medicinal-product pack; safety, efficacy and pharmacovigilance changes; and specialized master-file changes.
A change cannot therefore be classified reliably from its business description alone.
“Change of analytical method”, “new manufacturer”, “change of specification”, “new packaging component” or “change of manufacturing process” are not sufficiently precise regulatory descriptions. The classification can change depending on what exactly is being changed, the product type, the previously approved dossier, whether predefined conditions are fulfilled and what supporting data exist.
The classification table must be read horizontally
A common error is to find a variation title that looks similar to the planned change and stop reading.
That is not enough.
For many IA scenarios, the classification depends on a set of explicit conditions. If one or more required conditions are not fulfilled, the variation may no longer qualify as IA. Under the current Supplement V, an IA that fails its conditions may generally fall to IB by default, unless the rules or a regulatory recommendation classify it as Type II or the applicant itself concludes that the change can significantly affect quality, safety or efficacy.
The competent authority can also conclude during review that a change filed as default IB may have a significant impact on quality, safety or efficacy and require it to be treated as Type II.
This means classification should be documented as a regulatory argument:
change → applicable code → conditions → evidence that every condition is fulfilled → required documents → procedural category.
Pharegis uses this logic before the dossier is assembled. The objective is to prevent the classification from changing after filing, when the project timeline and implementation plan are already committed.
IA: “do and tell” does not mean “no regulatory control”
Type IA changes are minor changes that meet the relevant conditions in the classification.
For many IA changes that do not revise product information and do not affect data in the EAEU common register, the EAEU system allows the change to be implemented first and notified later. The current rules allow the applicant to submit such IA changes within 365 calendar days from implementation.
This is the classic “do and tell” model.
However, two qualifications are important.
First, some IA changes affect product information or information contained in the EAEU register. Under the current rules, these must be submitted before implementation, despite remaining classified as IA.
Second, an IA variation remains a controlled dossier change. The applicant must retain the implementation date, demonstrate that all classification conditions were met, update the affected dossier sections and maintain an auditable link between the operational change and the regulatory sequence.
A portfolio with many manufacturing sites can accumulate a large volume of IA changes. If the regulatory team merely stores them in a spreadsheet for an annual submission, it can lose control of which dossier versions, sites and products have actually implemented each change.
IA_NU: notification is faster because the regulator needs visibility
The EAEU framework also identifies a subset of minor changes as IA_NU—IA changes requiring prompt notification after implementation for continuous regulatory oversight.
Under the current rules, IA_NU notifications are submitted no later than 20 working days after implementation.
This category matters because international teams sometimes assume that all IA changes can be collected and submitted annually. They cannot.
The classification code must be checked to determine whether the change is ordinary IA or IA_NU.
Typical risk areas include certain changes implemented under an approved change-management protocol and selected changes to product information or regulatory commitments where prompt authority visibility is required.
A company therefore needs two clocks for minor variations:
ordinary IA → up to 365 calendar days after implementation, where the relevant conditions allow post-implementation notification;
IA_NU → notification within 20 working days after implementation.
IB: the default category is often where classification judgment matters most
Type IB is described as a minor variation, but it should not be treated as a “slightly bigger IA”.
Supplement V gives specific examples of IB changes, but it is intentionally not an exhaustive list. The current EAEU framework expressly uses IB as a default category for changes that do not qualify as IA, are not defined as Type II, and are not extensions.
This creates a large judgment zone.
A proposed analytical, manufacturing or packaging change may appear operationally minor but fail one IA condition. That can move it into IB. Conversely, a proposed change that appears to fit a familiar global IB concept may have product-specific features—especially for biologicals, sterile products, complex dosage forms or safety-relevant changes—that push it into Type II.
For EAEU products registered in more than one member state, the reference-state authority conducts the substantive procedure, while the recognition states participate in accordance with Appendix No. 19. The applicant must also manage recognition-state Module 1 documents and local fees where applicable.
The standard expert-review period for an IB dossier is up to 30 working days after the dossier is accepted for expertise. Depending on grouping and the applicable provisions, that period can extend to 60 working days. The administrative completeness stage and any applicant response periods sit outside or around that expert-review period according to the Rules.
For a query issued during the procedure, the applicant can be given up to 90 working days to provide missing or additional materials.
The practical lesson is that a Type IB dossier should be complete enough to answer the scientific question before it is filed. A weak “minor variation” can otherwise consume more calendar time than a well-prepared Type II.
Type II: the change is significant because its impact requires full assessment
A Type II variation is a significant change with potential material impact on quality, safety or efficacy.
For medicinal products registered in more than one EAEU state, a Type II dossier undergoes substantive expert assessment in the reference state and coordination with the recognition states. The standard expert-review period is up to 60 working days. Where different variation types are grouped into a single application containing at least one Type II change, the applicable period can reach 80 working days.
Type II can include major CMC changes, clinically important product-information changes, new indications or other changes whose impact cannot be handled through the minor-variation framework.
The classification should not be based on corporate terminology. A manufacturing organization may call a change “site optimization” while the regulatory dossier sees a major process change. A medical team may call an update “label alignment” while the change actually introduces new clinical data requiring assessment.
Pharegis therefore separates two questions:
How large is the change operationally?
and
How large is the change in the approved EAEU regulatory position?
They are not always the same.
Extension of registration: not every lifecycle change is a variation
Some changes are too fundamental to be handled as IA, IB or II. Supplement I to Appendix No. 19 defines changes that constitute an extension of the marketing authorization.
An extension can involve, for example, certain changes to strength, pharmaceutical form or route of administration depending on the specific scenario.
This category requires special attention because an extension is not simply “the heaviest Type II”. It is a separate regulatory concept.
The current Rules allow an extension to appear in a group only where all other changes in the group are related to that extension or are consequences of it. The procedural logic then follows the extension pathway.
A regulatory team should therefore perform an extension screen before classifying the remaining variations.
Grouping changes: the simple rule is “the heaviest change drives the pathway”—but only after grouping is justified
The operational principle is straightforward:
where a valid mixed group is permitted, the procedure follows the most complex change in the group.
If a package contains IB and Type II changes, the group is processed on the Type II logic. If it contains several IB changes, the IB procedure governs. The Rules specifically provide that, for mixed groups, the procedural period is calculated according to the most complex variation type and may extend up to 60 working days where the group contains no Type II, or 80 working days where the group contains Type II.
But grouping is not simply a way to put unrelated changes into one submission.
Appendix No. 19 provides specific grouping rules and examples. Supplement III includes, among others, cases where:
- a Type II change drives consequential changes;
- an IB change drives consequential changes;
- all changes concern administrative aspects of product information;
- all changes concern an API master file, vaccine antigen master file or plasma master file;
- the changes form part of a programme to improve the manufacturing process or product/API quality;
- the changes concern a pharmacovigilance system;
- the changes result from an urgent safety restriction;
- the changes arise from a periodic safety report, post-authorization study or regulatory obligation.
The regulatory relationship among the changes should therefore be explicit.
A practical grouping memo should answer:
- Why do these changes belong in one regulatory package?
- Which change is the lead or highest-classification change?
- Which changes are direct consequences?
- Are any IA/IA_NU changes subject to notification rules that make mixed grouping inappropriate?
- Does the package contain an extension?
- Will the same dossier sections be updated coherently in one sequence?
- What happens to implementation if the entire group is rejected?
That last point matters because the Rules provide that if one change included in a grouped application is rejected, all changes in that application are rejected.
Grouping therefore reduces administrative fragmentation but can increase portfolio risk if unrelated or weakly supported changes are tied together.
A grouped variation package needs one regulatory narrative
A group should not look like several individual changes stapled together.
The cover letter and variation dossier should explain the causal sequence.
For example:
new manufacturing process → revised in-process controls → revised analytical strategy → updated specification → revised stability commitment.
The regulatory reviewer should be able to understand why the changes belong together and which supporting data justify the whole package.
This is especially important where the lead variation is Type II. The more complex procedure can absorb related lower-category changes, but only if the technical story is coherent.
Identical changes across several products can sometimes be managed as a package
The 2024 reform of Appendix No. 19 expanded mechanisms for efficient handling of repeated minor changes.
In defined situations, identical multiple IA and/or IA_NU changes affecting dossiers held by the same marketing authorization holder can be submitted together as a package. Similar mechanisms apply to certain holder-related changes and grouping scenarios described in Supplement III.
This is particularly useful for corporate changes, pharmacovigilance changes, shared API master-file changes or portfolio-wide updates.
However, “same corporate project” does not automatically mean “same regulatory change”. Each product dossier must still contain the affected approved data and satisfy the conditions for the claimed code.
A global manufacturer changing the legal name of one production entity may have 40 EAEU dossiers, but the actual regulatory impact can differ among those dossiers if site roles, manufacturing steps or approved documents are not identical.
Portfolio grouping should therefore start from a dossier-impact matrix, not from the corporate change request.
The reference state remains the regulatory anchor
For a medicinal product registered in several EAEU member states, the reference state remains central to variation management.
The reference state performs the core assessment and updates the assessment report, while recognition states participate in the procedure and update their national implementation of the EAEU authorization.
For IB and Type II changes, the current Rules require the applicant to submit the relevant application and fees to the recognition states within 10 working days from filing in the reference state, together with recognition-state-specific Module 1 documentation where required.
This is easy to underestimate in a global lifecycle system.
A headquarters regulatory team may regard the variation as “filed” when the reference-state package is transmitted. In the EAEU, that is not enough. Recognition-state filing readiness, local documentation, translations, fees and dossier-sequence access must be synchronized.
Pharegis therefore treats an EAEU variation as a multi-state controlled rollout, not a single-country submission with later administrative copying.
“National procedure” in Appendix No. 19 does not mean the old Russian national rules
One of the most confusing terms in Appendix No. 19 is the heading for medicinal products registered in only one reference state: the Rules refer to this as a “national procedure”.
In this context, “national procedure” means an EAEU medicinal product that is registered in one EAEU reference state only.
It does not mean the pre-EAEU Russian national registration system.
The variation is still classified under Appendix No. 19, still uses IA / IA_NU / IB / II / extension logic, and still belongs to the EAEU dossier lifecycle.
This distinction is important for Russian products registered under Decision No. 78 only in Russia. They may look “Russia-only” commercially, but their variation system is EAEU, not the historic Russian Ministry of Health variation classification.
What remains genuinely national in Russia: standalone API changes
A separate Russia-specific pathway remains relevant for a pharmaceutical substance manufactured for sale and included as a standalone API entry in the Russian State Register of Medicines.
Article 34 of Federal Law No. 61-FZ expressly provides that changes to documents for such a pharmaceutical substance are made under the procedure established by Articles 30 and 31 of the same law.
This is not an EAEU medicinal-product variation under Appendix No. 19.
For that reason, Pharegis separates:
change to the standalone Russian API record
from
change to 3.2.S / ASMF-related data inside one or more EAEU medicinal-product dossiers.
The same technical change—such as a manufacturing-process change, specification change, new analytical method or site change—may therefore create two regulatory workstreams if the API is both independently registered for sale in Russia and used in EAEU medicinal-product dossiers.
The impact assessment should map both.
This article does not reproduce a separate Russian API variation-classification table. For API projects, the correct filing strategy is determined from the current Russian legal framework, the registered API documents and the corresponding medicinal-product dossier impact.
Extended national medicinal-product authorizations after 2025 are transitional, not a new variation pathway
The 2025 amendments to Decision No. 78 allowed certain national marketing authorizations to remain valid while previously initiated procedures for bringing dossiers into EAEU compliance or adding recognition states are completed.
Depending on the transition scenario, the validity can continue for the prescribed procedural period, subject to the limits established by the amended Rules.
This extension protects the legal continuity of products during transition.
It should not be interpreted as permission to start a new ordinary national medicinal-product variation procedure after 31 December 2025. The transition provisions themselves stated that changes to medicinal-product dossiers formed under member-state national legislation could be made under that national legislation only through 31 December 2025.
For lifecycle planning in 2026, the manufacturer therefore needs to ask:
What is the status of the transition procedure, what is the current EAEU reference dossier, and where must the next change be filed within the EAEU framework?
Not:
Can we continue using the old Russian variation pathway because the old authorization is still visible as valid?
Variations during an unfinished recognition-state procedure require sequencing strategy
Decision No. 78 was amended in 2025 to address a practical lifecycle problem: what happens if the reference-state dossier changes before the medicinal product has completed recognition in all intended recognition states?
Appendix No. 19 now contains a dedicated procedure for new variations initiated in the reference state before completion of the recognition procedure.
This is important for products being rolled out sequentially across the EAEU.
A manufacturer may need to implement a safety update, quality change or other variation while a recognition-state expansion is still pending. The regulatory team must decide whether to:
- complete the recognition procedure first;
- file the variation in the reference state and then propagate the approved sequence;
- use the specific mechanisms introduced for variations arising during recognition;
- delay a non-critical commercial change to avoid creating parallel dossier histories.
The correct answer depends on the variation class, implementation urgency and the status of the recognition procedure.
Version control becomes a regulatory issue, not merely a document-management issue.
Product type can change the classification
The same conceptual change can fall into a different procedural category depending on the medicinal product.
Biological products, sterile products, complex dosage forms, combination products, products with devices in the pack and medicinal products with special safety commitments may require different supporting evidence and may fail conditions that would allow a simpler procedure for a conventional small-molecule product.
Supplement V expressly contains product-specific conditions and, in some cases, different procedures for biological products.
A global classification taken from an EU variation assessment or an internal corporate change-control system should therefore be treated as an input—not as the final EAEU classification.
The EAEU code has to be revalidated against the actual approved EAEU dossier.
Pharmacopoeial updates can create hidden lifecycle work
The current classification rules contain an important practical provision for pharmacopoeial updates.
Where the approved dossier refers dynamically to the current edition of an applicable EAEU or member-state pharmacopoeial article, a separate variation notification may not always be required simply because that article is updated. However, the manufacturer still has to implement compliance with the updated pharmacopoeial article within the period specified by the Rules—currently 180 calendar days from publication for the relevant provision.
This creates a compliance task even where no standalone variation is filed.
For CMC teams, the correct question is therefore not only “Do we need a variation?” but also:
Does the revised pharmacopoeial requirement change our approved specification, analytical practice, reference standards, validation package or quality document in a way that triggers a separate variation?
That distinction should be built into pharmacopoeial surveillance.
Implementation date must be controlled separately from approval date
Every variation project needs at least three dates:
regulatory filing date
regulatory approval / notification acceptance date
operational implementation date
For IA and IA_NU, implementation can precede notification where the Rules permit it. For IB and Type II changes, implementation strategy should be tied to the applicable approval procedure and supply plan.
The operational implementation may also differ among batches, sites and recognition states.
A manufacturing change can be approved on one date but implemented at the site later after validation, stock depletion or supply-chain transition. Conversely, an IA change may already be implemented before the notification package is filed.
Without explicit implementation control, the regulatory dossier, manufacturing documentation, release specifications and commercial product can drift apart.
Supply continuity has to be designed into the variation strategy
The technically correct variation pathway can still create an avoidable supply interruption if implementation is not sequenced properly.
Before filing, Pharegis maps:
- existing inventory manufactured under the current dossier;
- first batch under the changed process;
- packaging and labeling transition;
- release testing under old and new specifications;
- stability commitments;
- recognition-state implementation;
- whether old configuration can continue circulating during the transition;
- whether the change affects GMP scope or inspection readiness;
- whether a related API or finished-product change must be approved first.
For manufacturing-site transfers and significant CMC changes, this implementation map can be as important as the classification itself.
The variation dossier should be built around the changed regulatory position
A strong variation dossier does not merely show “current” and “proposed” text.
It demonstrates why the proposed regulatory position remains acceptable.
Depending on the change, that can require:
- updated CTD sections;
- comparative current/proposed tables;
- manufacturing and process-validation data;
- analytical validation or transfer data;
- batch analyses;
- stability data;
- comparability data;
- revised quality overall summary;
- updated quality document;
- revised SmPC, patient leaflet or packaging;
- pharmacovigilance documents;
- GMP documentation;
- environmental or device-related information;
- impact assessment across strengths, forms, packs and member states.
The dossier should also make the classification logic visible. If the applicant claims IA, the conditions should be demonstrably satisfied. If it claims IB, the rationale should explain why the change is not Type II. If the package is grouped, the relationship among changes should be clear.
Where EAEU variation projects most often fail
The recurring problems are usually classification and sequencing problems rather than missing forms:
- importing an EU or global variation category without checking the EAEU code and conditions;
- identifying the correct variation title but failing one of the IA conditions;
- treating all IA changes as annual notifications and missing IA_NU or pre-implementation filing requirements;
- assuming that “Russia-only” EAEU registration still uses Russian national variation rules;
- attempting to file a new national medicinal-product variation because a transitional Russian authorization remains temporarily valid;
- failing to identify that a planned change is actually an extension;
- grouping changes for administrative convenience rather than regulatory relationship;
- forgetting that rejection of one change can reject the entire grouped package;
- filing in the reference state without recognition-state readiness;
- allowing parallel recognition and variation procedures to create inconsistent dossier sequences;
- changing API data without checking both the standalone Russian API record and the EAEU medicinal-product dossiers;
- treating a pharmacopoeial update as “no variation” without assessing the underlying CMC impact;
- implementing a manufacturing change without aligning approval, GMP scope, batch release and existing inventory.
These failures are predictable. They can be prevented by classifying the change before the implementation plan is locked.
What Pharegis manages in an EAEU variation programme
Pharegis can classify and file a single complex variation or manage a multi-product lifecycle portfolio. Typical deliverables include:
- variation classification memo with Appendix No. 19 code, conditions and rationale;
- assessment of IA vs IA_NU vs IB vs II vs extension;
- review of unclassified changes and proposed regulatory position;
- grouping strategy and identification of the lead/highest-classification variation;
- EAEU reference-state / recognition-state filing map;
- dossier-impact matrix across Modules 1–5;
- CMC impact assessment for API and finished-product changes;
- assessment of the standalone Russian API record where relevant;
- pharmacopoeial impact assessment;
- GMP-scope and manufacturing-site impact review;
- current/proposed dossier tables and updated CTD sections;
- quality-document and product-information updates;
- expert-question response strategy;
- implementation and supply-transition plan;
- variation portfolio tracker with regulatory and operational implementation dates;
- sequencing strategy where recognition-state expansion and variations overlap.
For an international regulatory team, the objective is not to outsource the mechanical filing step. It is to obtain a local regulatory interpretation of how a global change maps into the EAEU dossier and how that interpretation affects timing, implementation and the rest of the product portfolio.
Discuss an EAEU variation or lifecycle project
For an initial assessment, prepare:
- the current EAEU marketing-authorization status and reference state;
- list of recognition states;
- approved dossier baseline and latest sequence;
- precise description of the proposed change;
- implementation date proposed by manufacturing or global regulatory;
- current and proposed CTD sections;
- product type and dosage form;
- affected manufacturing and testing sites;
- GMP status;
- available validation, stability, comparability or clinical data;
- any ongoing recognition, renewal or other variation procedures;
- whether the API has a separate standalone registration in Russia.
Pharegis can then determine the correct EAEU classification, identify whether the change can be implemented before filing or requires prior assessment, define the grouping and member-state strategy, and place the variation on a lifecycle timeline that manufacturing, supply and regulatory teams can actually use.
The objective is not simply to obtain approval for a change. It is to preserve one coherent EAEU regulatory position while the product, manufacturing process and supply chain continue to evolve.
Regulatory basis
- EEC Council Decision No. 78 of 3 November 2016 — Rules for Marketing Authorization and Expert Examination of Medicinal Products for Human Use, consolidated version including amendments through Decision No. 93 of 26 November 2025.
- Appendix No. 19 to Decision No. 78 — Rules for variations to the marketing-authorization dossier, including Supplement I (extensions), Supplement III (grouping examples), Supplement IV (variation dossier documents) and Supplement V (detailed classification).
- EEC Council Decision No. 43 of 29 May 2024 — major revision of the variation framework, including expanded notification procedures and risk-based simplification.
- EEC Council Decision No. 34 of 22 May 2025 — amendments including procedures relevant to variation handling during recognition-state review.
- EEC Council Decision No. 77 of 12 September 2025 — transitional provisions for national authorizations and pending EAEU transition/recognition procedures.
- EEC Council Decision No. 93 of 26 November 2025 — current revision of the detailed variation classification in Supplement V.
- Federal Law of the Russian Federation No. 61-FZ of 12 April 2010, Article 34 — changes to documents for pharmaceutical substances manufactured for sale and included in the Russian State Register of Medicines.
Regulatory status reviewed: August 2026.