A manufacturing site changes; an analytical method is updated. A specification is revised. A new supplier is introduced.
Inside the company, it may be one change. Regulatorily, it can become twenty, forty or even more separate lifecycle actions. That is the central challenge of global post-approval change management. A change approved for a pharmaceutical product does not move through every market under one global regulatory pathway. Each marketing authorisation remains subject to the rules, classifications, evidence expectations, submission timelines and implementation conditions of the jurisdiction in which it is held. Even where countries are working from the same underlying CMC evidence, one authority may require prior approval, another may require notification before implementation, and another may allow the change to be implemented and reported later.
Global pharma companies therefore need to manage two things at once: one scientifically controlled global change and multiple market-specific regulatory pathways. Effective regulatory variation management starts by separating those two layers. The scientific change should remain globally controlled. The regulatory implementation should be mapped market by market.
Why One Global Change Becomes Multiple Regulatory Submissions
Pharmaceutical products are increasingly developed and manufactured through global networks.
The same drug product may be:
- Manufactured at one or several sites
- Tested through common analytical methods
- Supplied through shared API (Active Pharmaceutical Ingredient) or excipient sources
- Registered in dozens of jurisdictions
- Supported by one global stability strategy
- Maintained through a common pharmaceutical services
Operationally, changing one element of that network may be a single quality change.
Regulatorily, however, every affected marketing authorisation must be assessed against its own approved dossier and local requirements. Consider a change to a drug-product manufacturing site, the scientific justification may be global.
But each market may differ in:
- How the change is classified
- Whether authority approval is required before implementation
- Which supporting data must be submitted
- Whether GMP documentation or inspection status is relevant
- Whether stability data are required at filing
- Which application form or dossier sections must be updated
- How long the procedure may take
- When product manufactured after the change can enter that market
The EU and US illustrate why one internal change cannot be assigned one universal regulatory category.
The EU uses the variations framework, including Type IA, Type IB, Type II and extensions, with classification and procedural requirements governed by EU legislation and variation guidance. The revised EU Variations Regulation has applied since January 2025, and the new Variations Guidelines apply from 15 January 2026.
US-FDA uses a different post-approval reporting framework for approved NDAs and ANDAs. Depending on the nature and potential impact of a change, regulatory reporting can include prior-approval supplements, changes-being-effected supplements and annual reporting. The underlying change may be the same, the regulatory action is not. That is why global change management pharma teams should never begin with the assumption that a variation classification from one jurisdiction can simply be copied into another.
The Same Change Does Not Mean the Same Variation
Within the EU, variation has a defined regulatory meaning under the variation’s framework. For global governance, companies may use variation as an operational umbrella term, but the actual regulatory classification must always follow the loca framework. This is one global Chemistry, Manufacturing, and Controls CMC change. The EU classification is Type IB for the relevant authorisation, while other markets require separate classification under their applicable post-approval frameworks.
It may determine:
- Whether the change requires approval
- Whether notification is sufficient
- Whether implementation can occur immediately
- Whether a waiting period applies
- Which data are required
- Whether several changes can be grouped
- Whether one procedure can cover several authorisations
- When commercial supply using the changed condition can begin.
Effective global variation management therefore requires a market-specific regulatory determination for every affected authorisation.
Start With One Global Change, Not One Country at a Time
A common operational mistake is to let every local affiliate independently interpret a change from the beginning.
- That often produces fragmented regulatory work
- One country calls the change a site transfer
- Another describes it as a manufacturing-process change
- Another treats the same package as a specification update
Supporting documents are created in different versions, submission rationales diverge and teams begin answering the same scientific questions multiple times.
The better model starts globally.
Step 1: Create the global change record
Define exactly what is changing.
Capture:
- Current approved state
- Proposed future state
- Reason for the change
- Affected product(s)
- Dosage forms and strengths
- Manufacturing sites
- Processes
- Specifications
- Analytical procedures
- Materials or suppliers
- Supporting validation
- Stability impact
- Implementation target
Step 2: Establish the global scientific justification
Quality and CMC teams should determine the evidence supporting the change before regulatory teams begin creating individual submissions.
This becomes the controlled scientific core.
Step 3: Identify every affected marketing authorisation
Map the change against:
Product → Market → Authorisation → Approved condition
Not every market may be affected in the same way.
A manufacturing site, specification or process may be registered differently across jurisdictions.
Step 4: Perform local regulatory classification
Only after the global change is understood should regional and local teams determine:
- Reporting category
- Required documentation
- Authority procedure
- Submission timing
- Implementation restrictions
This is the difference between global change management and managing fifty independent local projects.
Build a Global Regulatory Variation Matrix
A strong global post-approval change management process needs one controlled matrix linking the global change to every affected market.
At minimum, the matrix should contain:
| Field | What to Track |
|---|---|
| Global change ID | One master reference for the change |
| Product | Product, strength and dosage form |
| Market | Country or region |
| Authorisation | MA/NDA/ANDA/BLA or applicable identifier |
| Current registered condition | What the authority currently has approved |
| Proposed condition | What will change |
| Local classification | Variation/supplement/notification category |
| Regulatory basis | Applicable regulation, guideline or local requirement |
| Submission requirement | Prior approval, notification, reporting or other route |
| Data package | Local supporting documentation required |
| Submission date | Date filed |
| Authority status | Submitted, under review, approved, accepted, etc. |
| Implementation eligibility | When the changed condition may legally be used |
| Approval/acceptance date | Where applicable |
| Supply impact | Existing stock, new stock and market transition considerations |
| Dependencies | GMP, labeling services, stability, review artwork, supply or other requirements |
| Owner | Regional/local regulatory owner |
The most important field is often not approval date.
It includes:
Implementation eligibility
That is because not every jurisdiction requires formal approval before every post-approval change can be implemented.
For example, EU Type IB variations generally follow a “Tell, Wait and Do” model: the MAH notifies the authority and normally waits 30 days before implementing the change if the notification is considered acceptable. Other categories may permit implementation before notification, while more significant changes may require approval first. FDA similarly differentiates reporting categories according to the potential effect of the change. Major changes generally require a prior approval supplement, whereas certain moderate changes may follow CBE mechanisms.
Where ICH Q12 and PACMPs Fit
ICH Q12 post-approval changes provide an important framework for more predictable pharmaceutical lifecycle management, particularly for CMC changes.
ICH Q12 introduces several tools and concepts relevant to CMC change management, including:
- Risk-based categorisation of post-approval CMC changes
- Established Conditions (ECs)
- Post-Approval Change Management Protocols (PACMPs)
- The Product Lifecycle Management document
- Pharmaceutical Quality System considerations
- Structured approaches for frequent post-approval CMC changes
ICH defines Established Conditions as legally binding information considered necessary to assure product quality; changes to ECs require regulatory communication. It also describes PACMPs as a mechanism that can create greater predictability around the evidence and regulatory pathway for a future CMC change when agreed in advance between the (Marketing Authorization Holder) MAH and the regulatory authority.
What does a PACMP do?
A PACMP prospectively describes a future CMC change and the studies, acceptance criteria and evidence that will be used to evaluate it. Instead of waiting until the company is ready to implement the change and then determining the regulatory evidence package from the beginning, the MAH and authority can agree prospectively on how the future change will be assessed.
What a PACMP does not do?
A PACMP does not create one automatic global regulatory pathway. ICH itself recognises that implementation of Q12 tools depends on regional regulatory frameworks. Some flexibilities may not be available in every jurisdiction or for every situation.
Therefore, a global company should map:
Global proposed change → PACMP applicability → authority acceptance → local reporting category → implementation conditions
The EU further updated its Q&A on PACMPs through Revision 1, legally effective from 15 January 2026, aligning PACMP use with the revised EU variations environment. For global teams, the strategic value of PACMPs is therefore predictability, not universalisation.
Coordinate Regulatory, Quality, CMC and Supply Chain
A variation may be filed by Regulatory Affairs Services, but it is rarely created by Regulatory Affairs alone. Successful regulatory variation management depends on several functions working from the same global change strategy.
Quality
Quality owns the pharmaceutical quality system and ensures that the underlying change is appropriately assessed, controlled and implemented.
CMC
CMC teams establish:
- Scientific justification
- Comparability
- Validation requirements
- Specifications
- Analytical impact
- Stability requirements
- Dossier content
Regulatory Affairs
Regulatory teams determine:
- Which registrations are affected
- Local classification
- Submission route
- Documentation requirements
- Authority interaction
- Implementation restrictions
Supply Chain
Supply Chain must understand when changed product can enter each market. This becomes particularly important when regulatory approval dates diverge. One market may be ready for the changed product while another still requires the old, registered configuration.
ICH Q12 explicitly recognises that supply chains involve multiple stakeholders— including MAHs, manufacturing sites, R&D organisations, contract manufacturers and suppliers—and that effective interaction between them is important for managing lifecycle changes.
A global change should therefore have one integrated governance structure rather than separate Quality, Regulatory and Supply Chain project plans that only meet near implementation.
Track Regulatory Approval Before Global Implementation
Some changes require prior authority approval. Others require notification and a defined waiting period; others may be implemented first and reported afterward. The correct control point is therefore not one worldwide approval date. It is a market-by-market implementation decision. This is where regulatory approval tracking becomes operationally critical. A dashboard that says “40 of 50 markets approved” is not enough. Poor coordination can create avoidable inventory complexity even when every individual submission is technically compliant.
2026 Regulatory Variation Trends
Several developments make post-approval regulatory trends particularly relevant in 2026.
- The revised EU variations framework is now operational
The revised EU Variations Regulation became applicable on 1 January 2025, while the updated Variations Guidelines became applicable on 15 January 2026.
The new framework updates variation classifications and procedural expectations, meaning MAHs need to ensure that internal classification matrices, SOPs, submission templates and regulatory systems reflect the current rules rather than legacy classifications.
- PACMPs have renewed practical relevance in the EU
EMA’s revised Q&A on post-approval change management protocols became legally effective on 15 January 2026.
This makes PACMP planning particularly relevant for companies considering predictable management of suitable future CMC changes in the EU.
- Grouping andwork sharing remain important efficiency tools
EU procedures allow certain related variations to be grouped, while work sharing can be available where qualifying variations affect more than one marketing authorisation.
EMA’s procedural guidance continues to be updated in 2026, including guidance on grouped variations and Type IB/II procedures.
For global companies, this reinforces the importance of identifying related changes before individual submissions are launched independently.
- ICH Q12 is pushing lifecycle management toward greater predictability
ICH Q12 has already established the conceptual framework.
The strategic shift is toward using product knowledge, Established Conditions, PACMPs and stronger pharmaceutical quality systems to manage appropriate CMC changes more predictably.
However, regional implementation still matters.
Global companies should therefore avoid assuming that a Q12 tool accepted in one market produces an identical regulatory outcome everywhere.
- Variation management is becoming a regulatory-data problem
This is an operational trend rather than a new regulatory requirement, this is why global variation management increasingly depends on connected product, registration and lifecycle data rather than isolated submission trackers.
DDReg’s VITALIC LC, for example, is designed to maintain product-by-market registration, variation and renewal status with ownership and tracking visibility across portfolios.
Global Variation Management Checklist
Before a multinational post-approval change moves into implementation, global teams should be able to answer yes to the following.
Global change definition
- Is there one controlled global change record?
- Is the current and proposed state clearly documented?
- Is the scientific rationale agreed?
- Are affected products, sites, processes and specifications identified?
Market impact
- Have all affected marketing authorisations been identified?
- Has the currently approved condition been verified for each market?
- Has each market independently classified the change?
Regulatory pathway
- Is the local reporting category documented?
- Is the regulatory basis recorded?
- Is the required evidence package known?
- Have grouping, work-sharing or PACMP opportunities been evaluated where applicable?
Submission
- Is there one controlled core CMC package?
- Are local adaptations traceable to that core?
- Are submission dates and authority questions being tracked?
Implementation
- Is implementation eligibility recorded separately for every market?
- Is prior approval required?
- Does a notification waiting period apply?
- Can the change be implemented before reporting?
- Is the legally permitted implementation date documented?
Supply
- Are Quality, Manufacturing and Supply Chain using the same regulatory status data?
- Can old- and new-condition inventory be separated where required?
- Is the market transition plan linked to regulatory approval or notification status?
Closure
- Have all affected markets completed the required regulatory action?
- Are authority decisions and acknowledgements retained?
- Has the registered condition been updated in the regulatory information system?
- Can the complete history of the global change be reconstructed?
If several of these answers are unclear, the company does not yet have global post-approval change management. It has a collection of local variation projects.
Conclusion
A global pharmaceutical change should begin once; its regulatory implementation may happen many times. That distinction is the foundation of effective global variation management. Companies need one globally controlled scientific change, one authoritative evidence package and one governance model—but they must also recognise that every affected market may classify, review and permit implementation differently.
ICH Q12 and PACMPs can improve predictability for suitable CMC change management, but they do not eliminate regional requirements. Likewise, regulatory harmonisation does not mean that one approval automatically unlocks global implementation. For multinational portfolios, the competitive advantage comes from visibility. Regulatory, Quality, CMC and Supply Chain teams should be able to see the same change, the same evidence and the exact regulatory status of every market.
DDReg’s Post-Approval Life Cycle Management services support pharmaceutical companies in managing variations and other lifecycle changes across jurisdictions, while VITALIC LC provides portfolio-level visibility of registrations, variations and renewals across markets. The goal is not to make every regulator treat the change the same. It is to ensure the company manages every regulatory difference through one controlled global regulatory strategy.
Frequently Asked Questions
No. Regulatory classifications, reporting categories and implementation requirements differ between jurisdictions. The same underlying CMC change may require prior approval in one market, notification in another and a different reporting mechanism elsewhere.
ICH Q12 provides a lifecycle-management framework for post-approval CMC changes. Its tools include risk-based categorisation, Established Conditions, PACMPs and the Product Lifecycle Management document. Actual implementation depends on regional regulatory frameworks.
Not necessarily. Different jurisdictions have different implementation rules. Some changes require prior approval, some involve notification or waiting periods, and others may permit implementation before subsequent reporting. Companies should therefore track implementation eligibility separately for each market.
It should connect the global change to every affected product, market and authorisation and record the local classification, regulatory basis, required evidence, submission status, authority status, implementation eligibility, supply impact, dependencies and accountable owner.
Regulatory lifecycle technology can connect global changes with product-market registrations, variation records, deadlines, ownership and implementation status. This enables Regulatory Affairs, Quality, CMC and Supply Chain teams to work from one current view of the portfolio rather than separate regional trackers.
