Change #8 of 10 — RA Operations

Minor changes no longer need a variation. They need a database update.

Article 92 overhauls the variation framework: fully electronic submission, database record updates for truly minor changes, enhanced grouped variations, and formalised PACMPs for connected change programmes. Your variation operating model is changing — not just the forms.

The operational impact

Faster for some changes. Completely different for others.

Database updates eliminate procedures that previously required Type IA filings. PACMPs transform connected change programmes. Electronic-only affects every procedure simultaneously.

100%

Of variation procedures become electronic-only from mid-2028 — CAPs and NAPs

SourceArt. 92, EU Pharmaceutical Directive 2026

0days

Assessment time for changes eligible for database record update vs 30-day Type IA

SourceArt. 92, EU Pharmaceutical Directive 2026

~40%

Of typical RA variation workload is Type IA and administrative — most directly simplified

SourceEMA variation workload analysis, 2023
What's actually changing

From paper procedure to electronic operating model

Five parallel shifts happening simultaneously — each affects a different part of your variation operations.

Workbench
+ New Task
Quick Tasks/Variations — current vs new directive

We submit around 300 Type IA variations a year. Most look like they're address changes or minor document updates. Do we still need to file them?

RegIntel
RegIntel12:39
126.00s256 sources95% confidence2 warnings
2 warnings

Here's the obligation delta for Variations. The new EU Pharmaceutical Directive replaces Directive 2001/83/EC[1][2] — below is what changes, row by row.

Current vs. new directive4 rows
Current — 2001/83/EC
New directive — from ~mid-2028
Submission format
Current

Mix of electronic and paper. Type IA often via email with PDF attachments. Paper persists in many national procedures.

New directive

All procedures fully electronic via PLMS, IRIS or NCA systems. Paper eliminated. Structured data fields replace free-text notifications.[3][4]

Minor administrative changes
Current

Administrative changes require formal Type IA notification — company name, address, contact details. Each change is a separate procedure with filing fee.

New directive

Purely administrative changes handled as database record updates — no assessment clock, no dossier, no filing fee. Immediate registry amendment.[5]

Grouped variations
Current

Grouping rules complex. Type II changes slow down all IA/IB components in the same group.

New directive

Enhanced grouping with clearer rules. Annual Type IA notification batches multiple changes in a rolling 12-month period.[6]

Change management protocols
Current

PACMP available voluntarily for CAPs under EMA guidance. Not available for nationally authorised products.

New directive

PACMP given formal legal basis for all authorisation types. Pre-approved protocol; implementing changes are simplified notifications.[7][8]

Dates reflect the political agreement text; final deadlines depend on entry into force and the transition period for each obligation.

Synthesised from 24 citations across 256 regulatory sources.

Book a 15-minute live walkthrough of the Workbench

Book a demo
Where teams get stuck

The missing layer

Benefits only materialise if your team knows which procedure applies and can use the new pathways from day one.

CU

Current variation SOPs

The existing playbook

EL

Electronic submission tools

The submission portals

Regunaut

The variation operating system

Every change routed to the right procedure — built for Art. 92.

How Regunaut solves it

Five steps. Your variation operations on the new framework.

Each step maps variation management under Art. 92 — from classifying changes through PACMP-based programmes.

Questionnaire-based classification engine routes changes to DB update, IA, IB, II, or PACMP based on EMA taxonomy, authorisation route, and active PACMPs in your portfolio.

  • Art. 92 aligned classification: DB update / IA / IB / II / PACMP
  • CAP vs NAP aware classification logic
  • PACMP overlap check on active protocols
  • Classification rationale documentation for audits
Operational evidence

Variation volume is growing. The new framework needs to handle it efficiently.

EMA's electronic-only mandate and new pathway options reduce overhead — but only for teams equipped to use them correctly.

18k+

Variation procedures assessed by EMA annually for CAPs alone — national procedures add multiples

EMA Annual Report, 2023

30%

Reduction in Type IA processing time in EMA's electronic-only pilot for CAP variations

EMA e-submission pilot evaluation, 2023

12mo

Typical time for a complex manufacturing change programme across 10+ MAs — the scenario PACMPs compress

EFPIA variation operations survey, 2024

Variations are the daily engine of regulatory operations. Teams that rebuild around Art. 92 will move faster. Teams that adapt incrementally will carry the overhead of a framework that no longer exists.

TOPRA Regulatory Operations Working Group, Directive Impact Review, 2025
Common questions

What RA teams are asking about the variation reform

Rebuild your variation operating model before mid-2028

Your SOPs, tracking tools and submission workflows are built for a framework being replaced.

Audit your variation operations

Map your portfolio against Art. 92 classification — which procedures change type, which become database updates.

Streamline my variations

Design a PACMP for your portfolio

30-minute session to identify change programmes best suited for PACMP treatment.

Book a PACMP scoping session
8 / 10