Type IA Variations: Why "Simple" Variations Are Never as Simple as They Look
- Jun 23
- 14 min read
Ask any experienced regulatory affairs professional about Type IA variations and most will tell you the same thing: they look easy, they are not. Known in the industry as "do and tell" procedures, Type IA variations represent the process by which pharmaceutical companies make minor changes to their marketing authorisation (MA) dossiers — implementing the change first, then notifying the relevant regulatory authority. No prior approval needed. In theory, this is the most straightforward variation procedure in the EU regulatory toolkit.
In practice, Type IA variations are riddled with procedural nuance, classification grey areas, and — increasingly — a raft of new regulatory requirements that have materially raised the stakes for getting them right. With rejection rates of up to 20% reported by European regulatory authorities in recent years, and a mandatory new annual reporting model introduced in January 2025 alongside revised classification guidelines landing in 2026, there has never been a more important time for regulatory affairs professionals and marketing authorisation holders (MAHs) to fully understand what "do and tell" actually demands.
This guide breaks down everything you need to know — from the fundamentals of what a Type IA variation is, through to the common pitfalls, the new regulatory requirements, and what this all means for those building or developing careers in regulatory affairs.
Launch Your Regulatory Affairs Career Faster Than You Think At Entry to Regulatory, we provide intensive, practical training courses for anyone looking to break into Regulatory Affairs — even with zero prior experience. Our programme covers EU, US, and UK regulations over 50+ CPD hours, pairs you with real-world work assignments, and gives you dedicated CV support, mock interviews, and job placement mentoring. Graduates are landing roles within weeks to months of completing the course. it. Speak to us and see how we can help you.
What Is a Type IA Variation? The Basics Explained
A Type IA variation is a minor amendment to a marketing authorisation that has minimal or no impact on the quality, safety, or efficacy of a medicinal product. It sits at the lowest level of the EU variation classification hierarchy and is governed by the European Commission's Variation Classification Guideline, which defines precisely which changes are eligible for the Type IA category.
The EU Variation Classification Framework at a Glance
Variation Type | Procedure | Timeline | Examples |
Type IA | Do and tell — implement, then notify | Notify within 12 months (annual report) | Minor manufacturing changes, admin updates, QC method adjustments |
Type IA (IAIN) | Immediate notification — implement, notify same day | Immediate | Certain safety updates, changes to batch size within approved range |
Type IB | Notify and wait — submit, then wait 30 days | 30-day review | Moderate changes to specifications, stability data updates |
Type II | Prior approval — cannot implement until approved | 60–90 day review | New indications, significant safety changes, new manufacturing sites |
Extension | Prior approval + full assessment | Varies | New strength, new dosage form, new route of administration |
The core distinction of Type IA is the "do first, tell later" principle. The company is trusted to implement the change responsibly, with the regulatory authority reviewing the notification after the fact. This trust is what makes classification accuracy so critical — because if the change was not actually eligible for Type IA, the company has already implemented something the regulator has not approved.
Common Examples of Type IA Variations
- Minor changes to a manufacturing process that don't affect product quality
- Updates to administrative information, such as the name or address of a manufacturer
- Minor adjustments to quality control test methods that don't change specifications
- Changes to the immediate packaging that don't affect product delivery or patient safety
- Updates to artwork/labelling that are purely editorial (e.g., correcting a typographical error)
- Addition or deletion of an alternative manufacturing site for a starting material
The "Do and Tell" Reality: Why Things Go Wrong
The perception that Type IA variations are "entry-level" submissions — suitable for newly qualified regulatory professionals with minimal oversight — has contributed to a worrying rate of non-acceptance across European regulatory authorities. The reality is that Type IA variations require just as much rigour as any other variation type, and the consequences of getting them wrong are compounded by the fact that the change has already been implemented.
Top Reasons Type IA Variations Are Rejected
1. Misclassification
This is the most serious error. Submitting a change as a Type IA when it should be a Type IB or Type II means the company has implemented an unapproved change. Regulatory authorities can require immediate reversion, and in serious cases, this can trigger quality investigations, CAPAs, and regulatory action.
2. Unmet Conditions
Each variation code in the classification guideline comes with specific conditions that must be met for the Type IA classification to apply. Failing to satisfy all stated conditions — even if the change itself appears minor — is grounds for non-acceptance.
3. Timing Errors
Late submission (beyond the 12-month window from implementation), incorrect implementation dates, or submitting before the 9-month threshold under the new annual reporting rules — all create procedural grounds for rejection.
4. Documentation Deficiencies
Insufficient supporting data, incorrectly completed cover letters, missing eCTD technical requirements, or incomplete condition verification documents are consistently cited in rejection notices.
5. Incorrect Grouping
When multiple Type IA variations are grouped into a single notification, all changes must be completely identical across all affected products. Where this condition is not met, the grouping is invalid — a common mistake in larger portfolios with variations spanning multiple marketing authorisations.
6. Specification Parameter Deletions
Deleting a test specification parameter that is considered 'non-significant' is a particular grey area. The definition of non-significant is not always clear-cut, and regulatory authorities interpret this differently. A parameter the MAH considers redundant may be viewed by the authority as safety-relevant.
What Happens When a Type IA Variation Is Not Accepted?
Non-acceptance is not a minor administrative inconvenience. It can have serious operational and commercial consequences, and the response obligations are immediate.
The Consequences of Non-Acceptance
When a regulatory authority issues a non-acceptance decision on a Type IA variation, the following obligations apply:
- ✋ Immediately cease applying the rejected change — this means reverting to the previous registered version of the dossier
- 📋 Submit a consolidating sequence within 15 calendar days to revert the dossier to its last approved state
- 🔄 You may resubmit a corrected application for the same change, provided you are still within the original 12-month implementation window
- 🚫 There is no option to resubmit a corrected application without first ceasing the implementation — you cannot simply patch the error on top of the non-accepted submission
Operational impact in practice: If the rejected variation touched EU Product Information (i.e., the SmPC, labelling, or Patient Leaflet), the reversion has direct implications for packaging. Any printed or approved packaging materials using the rejected Product Information must be withdrawn from the next packaging run. Version control across artwork systems, regulatory dossiers, and QMS becomes an immediate and complex challenge.
In extreme cases — where a genuinely significant change was misclassified as a Type IA — the consequences can escalate to patient safety concerns, product recalls, and regulatory authority enforcement action.
> Business context: This is why experienced regulatory affairs oversight of Type IA submissions is not optional. The financial and reputational cost of a mismanaged non-acceptance far exceeds the cost of investing in proper regulatory expertise at the submission preparation stage.
The Do's and Don'ts of Type IA Variations
THE DO'S
DO verify classification rigorously against the full condition list
Every Type IA variation code in the classification guideline includes specific conditions. Check every condition is met — not just the headline description of the change. If even one condition is not satisfied, the Type IA classification does not apply.
DO distinguish between IAIN and standard annual Type IA
Immediate notification (IAIN) variations must be submitted on the day of implementation. Standard Type IA variations (now under annual reporting) are batched and submitted later. Mixing these up is a procedural error. Know which category applies before you implement.
DO maintain a robust variation tracking system
Under the mandatory annual reporting model introduced in January 2025, you are collecting variations over time and submitting them as a consolidated package. Without a reliable tracking system, variations can be missed, submitted out of window, or duplicated. A live register of all implemented changes, their dates, and their assigned variation codes is essential.
DO plan your annual report strategically
The submission window for the annual Type IA update opens no earlier than 9 months after the first implemented variation and must close within 12 months. This means you have a narrow submission window — sometimes as tight as 3 months if your first variation was implemented early in the year. Front-load your planning accordingly.
DO build contingency into your variation planning
Always have a documented contingency plan for the possibility of non-acceptance. Know in advance: who in your organisation is responsible for triggering a reversion, how quickly artwork and QMS can be updated, and who signs off the consolidating sequence submission within the 15-day window.
DO consult the updated classification guideline (January 2026)
The revised variation classification guideline introduced on 15 January 2026 redefines a number of variation classifications. Some biological CMC updates previously defaulted to Type IB can now be classified as Type IA — expanding the scope of "do and tell" for biological products. Monitor EMA Q&As and technical guidance as they are released on a rolling basis.
DO use the watershed date strategically
Changes implemented before 15 January 2026 follow the old classification guideline; those implemented after follow the new one. MAHs can plan the timing of implementation to benefit from revised classifications — but only with careful regulatory review to ensure the new classification genuinely applies.
DO coordinate with manufacturing and supply chain
Type IA variations often affect manufacturing processes, batch records, or product information that is embedded in operational systems. Regulatory affairs teams must work with manufacturing, QA, and supply chain counterparts to ensure the change is properly implemented and can be swiftly reversed if required.
THE DON'TS
DON'T assume "minor" means "no risk"
The single most dangerous assumption in Type IA management. A change can be genuinely minor in its clinical impact yet still be misclassified, submitted incorrectly, or implemented without meeting all conditions. Every "minor" change must be treated with the same due diligence as any other regulatory submission.
DON'T submit Type IA variations individually after 1 January 2025
Under Regulation (EU) 2024/1701, individual submission of Type IA variations (for those not requiring immediate notification) is no longer permitted. All standard Type IA variations must now be collected and submitted as a consolidated annual report. Submitting individually — unless falling within the defined exceptions — is non-compliant.
DON'T miss the 9-month opening of the submission window
You cannot submit the annual Type IA report earlier than 9 months after implementing the first variation in the package. Submitting early is a procedural error. Mark this threshold date in your variation tracker and build your submission timeline backwards from it.
DON'T group variations across MAs unless they are identical
Super grouping — consolidating Type IA variations across multiple marketing authorisations — is only valid when the changes are completely identical across all included products. Even minor differences in how a change applies to different products mean they cannot be grouped. When in doubt, submit separately.
DON'T delete specification parameters without a full impact assessment
The deletion of any test parameter — even one that appears redundant — requires careful justification. Assess whether the parameter has any relationship to product safety or efficacy, check the classification guideline's guidance on 'significant' parameters, and document your justification fully. This is one of the most commonly cited causes of non-acceptance.
DON'T overlook the EU Product Information implications
If a Type IA variation results in any change to the SmPC, labelling, or Patient Leaflet, the implementation date is determined by the date the company internally approves the revised Product Information — not by when it is submitted to the authority. This date must be accurately reflected in all submission documentation.
DON'T ignore the 15-day reversion deadline on rejection
If a Type IA variation is not accepted, the clock starts immediately. The consolidating sequence to revert the dossier must be submitted within 15 calendar days. Treating this as a soft deadline or allowing it to slip while investigating the rejection is a compliance failure on top of a compliance failure.
DON'T confuse the new fee model with a cost reduction
While Regulation (EU) 2024/568 (effective January 2025) absorbs Type IA and IB fees into the annual EMA maintenance fee for centrally authorised products, this only applies to the centralised procedure. National procedure products may still carry separate fee obligations. Do not assume cost changes apply universally without checking the relevant national authority's fee structure.
New in 2025: Mandatory Annual Reporting — What Has Changed
Regulation (EU) 2024/1701 entered into force on 7 July 2024 and became operational on 1 January 2025. It represents the most significant procedural change to Type IA variation management in decades.
### What the New Annual Reporting Model Requires
- All standard Type IA variations implemented from 1 January 2025 onwards must be batched into a single annual consolidated report
- The annual report must be submitted no earlier than 9 months after the first change in the package was implemented
- The submission must be within 12 months of that first implementation — creating a 3-month window for submission
- The cover letter must clearly identify the submission as a 'Type IA Annual Update'
- EMA will conduct a 30-day review of the consolidated annual report
Exceptions to Annual Reporting
Annual reporting is NOT required in the following situations:
Exception | Description |
IAIN | Immediate notification variations must still be submitted on the day of implementation |
Grouping with other variation types | Where a Type IA is related to a higher variation type, it can be grouped with that variation |
Super grouping | Identical Type IA variations across multiple MAs can still be super grouped |
Shortage mitigation | With regulatory authority agreement, a Type IA can be submitted outside annual reporting to address a medicine shortage |
Resubmission after rejection | A corrected resubmission following non-acceptance remains within the 12-month window and is submitted directly, not as part of an annual report |
New in 2026: Updated Variation Classification Guidelines
Alongside the procedural changes from 2025, the revised EU Variation Classification Guideline, published by the European Commission on 15 January 2026, introduces updated definitions of which changes fall into which category.
Key Change: Biological Products
The most notable update is the potential reclassification of certain biological Chemistry, Manufacturing, and Controls (CMC) updates from Type IB to Type IA. Previously, changes to biological manufacturing processes defaulted to a higher classification due to their inherent complexity. Under the new guideline, specific, well-characterised CMC changes for biologics may now qualify for the "do and tell" pathway — reducing regulatory burden for manufacturers but also expanding the scope of what must be managed under the annual reporting model.
What This Means in Practice
- MAHs with biological products should systematically review their upcoming planned changes against the new classification guideline to identify where reclassification may be possible or required
- The watershed date of 15 January 2026 means changes implemented before this date follow the old guideline; those after follow the new — creating a transition management challenge for ongoing projects
- EMA is releasing rolling Q&As and technical guidance to support the new classifications, particularly for complex areas such as drug-device combinations and decentralised manufacturing
Type IA Variations and Regulatory Affairs Careers: The Skills Gap
Understanding Type IA variations — truly understanding them, not just at surface level — is a core competency for any regulatory affairs professional working in post-authorisation or lifecycle management. Yet the nuance of the "do and tell" procedure is consistently underestimated in hiring, training, and day-to-day RA operations.
Why Type IA Expertise Is More Valuable Than Ever
With the introduction of mandatory annual reporting, the updated classification guidelines, and rejection rates hovering around 20% across many European competent authorities, demand for RA professionals who can manage Type IA submissions with precision is growing across the industry.
Specifically, employers are seeking professionals who can:
- Classify changes accurately using the current (and transition-aware) classification guideline
- Build and manage annual variation tracking systems across complex product portfolios
- Prepare consolidated annual reports with correct eCTD structure, cover letter content, and supporting documentation
- Identify grouping and super-grouping eligibility across multiple MAs
- Manage non-acceptance scenarios including contingency planning and rapid reversion procedures
- Coordinate cross-functionally with manufacturing, QA, and supply chain on implementation and reversion timelines
These are not theoretical skills — they are applied, daily responsibilities in regulatory operations, CMC regulatory affairs, and lifecycle management roles across branded and generic pharmaceutical companies, CROs, and regulatory consultancies.
Key Takeaways: Type IA Variations Do and Tell Checklist
✅ Verify every condition in the classification guideline before implementing any Type IA change
✅ Distinguish IAIN from standard Type IA — the notification timelines are fundamentally different
✅ Annual reporting is mandatory from January 2025 — individual submissions are no longer permitted for standard Type IA variations
✅ The annual report submission window is between 9 and 12 months after the first implementation in the package
✅ Non-acceptance triggers a 15-day reversion deadline — plan your contingency before you need it
✅ Super grouping requires identical changes across all included marketing authorisations — no exceptions
✅ The 2026 classification guideline update may reclassify some biological CMC changes to Type IA — review your pipeline against the new guideline
✅ The 15 January 2026 watershed date determines which guideline applies to a given variation — plan implementation timing accordingly
✅ Type IA fees are now included in EMA annual maintenance fees for centrally authorised products under the 2025 fee regulation
Frequently Asked Questions (FAQs)
Q: What is the difference between a Type IA and a Type IA IAIN variation?
A standard Type IA variation can be batched and submitted as an annual report within 12 months of implementation. A Type IA IAIN (Immediate Action — Immediate Notification) must be submitted on the very day it is implemented. IAINs are reserved for specific changes — such as certain safety-related labelling updates — that require the regulator to be informed without any delay.
Q: Can I still submit Type IA variations individually after January 2025?
In most cases, no. Regulation (EU) 2024/1701 mandates consolidated annual reporting for standard Type IA variations implemented from 1 January 2025. However, exceptions exist — including IAIN variations, changes grouped with higher variation types, super-groupings, and shortage-related submissions with authority agreement.
Q: What happens if I misclassify a change as Type IA when it should be a Type II?
This is a serious regulatory compliance failure. The company has implemented an unapproved change. The authority can require immediate reversion, and depending on the nature of the change and its impact on the product, escalation to quality investigations, product recalls, and formal regulatory action is possible.
Q: Do the new 2026 classification guidelines apply to variations I have already implemented?
No. The watershed date of 15 January 2026 determines which guideline applies. Variations implemented before this date follow the previous guideline, regardless of when they are submitted in the annual report.
Q: How does the new annual reporting model affect grouping across multiple marketing authorisations?
Super grouping across multiple MAs is still permitted under the annual reporting model, provided that all changes being grouped are completely identical across all affected products. The annual report for a super grouping must meet the same timing rules (no earlier than 9 months after first implementation, within 12 months).
Ready to Master Regulatory Affairs from the Ground Up?
Type IA variations are a perfect example of why regulatory affairs is a profession that rewards genuine expertise over surface-level knowledge. The gap between "I know what a Type IA is" and "I can manage a full annual variation programme, classify correctly under transitional guidelines, and handle a non-acceptance with confidence" is exactly the gap that employers are trying to fill right now.
At Entry to Regulatory, we train people to work at that level.
Our regulatory affairs training courses are built around real-world assignments — the actual types of tasks you'll encounter in a live regulatory role. We don't teach theory in a vacuum; we teach you how to apply regulatory knowledge to real submissions, real products, and real scenarios. That includes post-authorisation work, lifecycle management, and variations — the bread and butter of regulatory operations roles across the EU and beyond.
What sets Entry to Regulatory apart:
- ✅ Real-life work assignments — not just case studies, but hands-on regulatory tasks mirroring actual employer expectations
- ✅ Job support included — CV development, application guidance, and interview coaching tailored to the regulatory affairs market
- ✅ Up-to-date, evolving curriculum — including the 2025 and 2026 regulatory changes covered in this very article
- ✅ Designed for career changers and graduates — no prior regulatory experience required to start
Whether you are a life sciences graduate stepping into RA for the first time, or a professional moving across from a clinical, quality, or manufacturing background — we can help you build the skills and confidence to compete for and win regulatory affairs roles.
Next cohort starts: 12 July 2026. Limited spaces available.
About the Author: Rabiea is an Honorary Associate Professor at UCL, former MHRA Health Authority reviewer, and CEO of Entry to Regulatory and Advanced Regulatory Consulting. After transitioning from retail pharmacy to regulatory affairs, she has dedicated her career to helping others make the same successful career change. Connect with her on LinkedIn for the latest regulatory affairs insights and career advice.
Comments