Home/Capabilities/Regulatory excellence/Lifecycle management
Regulatory excellence
Lifecycle management
Where portfolio size stops being an asset and starts being a liability — unless the classification decision is made early and the framework is used properly.
Why it matters
One change, forty markets, forty different answers
Lifecycle management is where portfolio size stops being an asset and starts being a liability. A single manufacturing change can generate dozens of submissions, each classified differently, each on its own clock.
The work itself is rarely difficult. What makes it hard is volume, divergence and memory: knowing what is approved in each market, which changes are in flight, which are blocked behind another, and what the consequence is if one slips.
Organisations that do this well are not working harder. They have made the classification decision early, grouped what the framework allows them to group, and built a portfolio view that answers questions without a manual exercise.
European Union
The revised variations framework
This is the most consequential change to EU lifecycle management in over a decade, and it rewards portfolios that are organised enough to exploit it.
Regulation (EC) No 1234/2008 was amended by Commission Delegated Regulation (EU) 2024/1701, which entered into force on 7 July 2024 and became applicable on 1 January 2025. The accompanying revised Variations Guidelines apply from 15 January 2026 — so both the regulation and its guidelines are now in force, and submissions must follow the current classification and forms.
What changed, and why it matters commercially
Super-grouping of Type IA variations
The same Type IA change affecting several products of the same marketing authorisation holder can be consolidated into a single application, provided the change is genuinely identical across them. For a portfolio holder making an administrative change across many authorisations, this is the single largest reduction in submission volume in the reform.
Annual reporting of Type IA
Type IA variations move to a periodic reporting model, with the submission date within the holder's control provided the twelve-month cycle is respected. The flexibility is real, but it depends entirely on internal tracking — a change that is not recorded when it is made will not be reported when it is due.
Wider use of worksharing
Where the same Type IB or Type II change affects several marketing authorisations, it is handled through a worksharing procedure so the change is assessed once rather than repeatedly. This pushes portfolios towards harmonised dossiers, because divergence between authorisations is what makes a change ineligible.
Vaccine and emergency flexibilities
Expedited mechanisms developed during the pandemic have been extended to a broader set of human vaccines, with pathways for public health emergencies.
Grouping, super-grouping and worksharing compared
| Route | Applies when | Consolidates | Condition |
|---|---|---|---|
| Grouping | Several changes affect one marketing authorisation. | Changes | The changes are submitted together in a single application. |
| Super-grouping | The same Type IA change affects several products of one holder. | Products | The change must be identical across all included authorisations. |
| Worksharing | The same Type IB or II change affects several authorisations. | Assessment | One assessment covers all included authorisations. |
United States
Reporting category is the whole decision
US post-approval change turns on one question: what reporting category does this change fall into, and therefore may it be implemented before, shortly after, or only following approval?
The categories run from prior approval supplements, where the change cannot be implemented until FDA has approved it, through changes-being-effected supplements with and without a waiting period, to changes reportable only in the annual report. The difference between them is measured in months of manufacturing flexibility.
The recurring failure mode is a category assumed rather than assessed. A change implemented on the basis of an optimistic classification is a compliance problem, not a regulatory one, and it is discovered at inspection rather than at review.
We make the classification decision explicitly, document the reasoning, and align it with the equivalent decision in every other market where the product is registered — because the same physical change will not carry the same category everywhere.
Global
Running lifecycle management across a portfolio
Beyond the US and EU, the constraint is coordination. The same change will be a notification in one market, a prior approval in another, and unclassified in a third.
Order matters
Where markets rely on a reference approval, the reference filing has to come first, and its approval date becomes a dependency for everything downstream.
Same change, same evidence
Divergent supporting data across markets is what makes a portfolio unmanageable. The evidence package should be built once and used everywhere it fits.
Periodic obligations
Renewals, periodic safety reporting and local commitments run on their own clocks and have to be planned alongside change activity, not separately from it.
Ownership change
Marketing authorisation transfers, entity changes and divestitures each generate a wave of submissions with hard commercial deadlines attached.
The practical requirement underneath all of this is a portfolio view that is actually current: what is registered where, at what version, with what in flight. Where that exists, lifecycle management is planning work. Where it does not, it is archaeology.
What we do
How we work on lifecycle management
Establish the baseline
What is approved in each market, at what version, with what commitments outstanding. Usually the hardest step, and always the first.
Classify before committing
Determine the category in every affected market before manufacturing fixes an implementation date.
Design the submission strategy
Group, super-group or workshare where the framework allows it, and identify where harmonisation would unlock a route currently unavailable.
Sequence against dependencies
Order filings so reference approvals land before the markets that rely on them, with the consequences of a slip made visible.
Execute and track to approval
File, respond to questions, and track each market to national approval as a fact in a system rather than an email thread.
Close out with evidence
Confirm implementation, update the baseline, and retain the record — so the next change starts from a known position.
Bring us the challenge
Where are you in this, right now?
The most useful conversations start with the specific decision or deadline in front of you, not with a service category.