Since IVDR came into effect, IVD manufacturers have had to respond to changes across clinical evidence, quality management, vigilance and labeling. Among these, labels and IFUs stand out as significantly affected. Updates that were once occasional now occur more frequently. They are now driven by a broader range of regulatory and quality triggers than under the previous directive.
This article is about how those changes get managed once a product is already on the market.
How IVDR Has Shaped Label Change Management
Label change management covers the process a manufacturer follows whenever a label needs to be revised. That includes who initiates the change, how it gets assessed and approved, how it’s verified against the original specification and how the record is kept for inspection.
It differs from labeling requirements in a simple way. Requirements tell you what has to be on the label. Change management tells you how you get from an approved label to a revised, equally approved label without losing traceability along the way. This article deals only with the second part. So for a breakdown of what IVDR actually requires on a label, see our companion article on IVDR labeling requirements.
Why Label Change Management Has Become a Distinct Discipline Under IVDR
Under IVDR, label revisions are no longer occasional. Vigilance findings, CAPA actions, specification corrections and IFU updates all generate new label versions on an ongoing basis, and each one needs its own documented justification. The increasing frequency of label changes creates three operational pressures that require more than standard document control.
- Frequency: Label changes now happen continuously rather than during scheduled transition windows.
- Scale: A portfolio of several hundred articles can easily generate thousands of individual change events over a few years.
- Zero tolerance for inconsistency: Auditors expect an exact match between an approved specification and the data actually used to produce a label. At scale, manual cross-checking cannot reliably catch every gap.
The strain shows up in a predictable place. Manufacturers still manage label changes by spreadsheet and email approval. Missed reconciliations, duplicate revisions, unclear ownership and incomplete audit trails become common. And not because anyone is careless but because the process was never designed for this volume.
Since labels and IFUs are one of the areas IVDR has affected most, manufacturers need a defined way to manage that ongoing volume of change.
A Structured Methodology for Label Revision Management
IVDR does not specify a specific method for managing label changes. Instead, it sets expectations around traceability, documentation, control and consistency. Manufacturers are expected to establish a process that meets these requirements.
The most workable response is to stop thinking of a label as a single static document and start treating it as a chronological record of controlled versions, where every version exists because a specific event required it.
Here’s what that lifecycle looks like:
Trigger Event → Impact Assessment → Change Control → Label Revision → QA Verification → Approval → Release → Distribution → Archived Version
Each stage produces a record and each record links back to the one before it. The justification for a change is preserved in official records, making the process auditable and repeatable.
This also means every label carries its own controlled version history rather than existing as several disconnected copies maintained by different teams. When a new revision is approved, the previous version isn’t discarded. It stays archived and retrievable.
Common Trigger Events for Label Changes under IVDR
Not every trigger carries the same weight, so it helps to group them by source when prioritizing and resourcing a change.
Regulatory and safety events
- Reassignment of UDI-DI following a significant device change
- Field Safety Corrective Action (FSCA)
- Vigilance findings
- Notified Body observations
- Regulatory authority requests
Quality and product events
- CAPA implementation
- Risk management updates
- Performance evaluation outcomes
- Design changes
- Manufacturing changes affecting labeling
Content and administrative events
- Specification corrections
- IFU updates
- Translation corrections
- Editorial corrections requiring a controlled revision
- New language release
- Packaging configuration changes
- Software version changes affecting the IFU
- IVDR transition milestones
FSCA-driven and vigilance-driven changes typically carry the tightest timelines and the highest scrutiny. Editorial and translation corrections matter just as much for traceability, even though the urgency is usually lower.
Stage-by-Stage: How the Lifecycle Works
Here’s what happens at each point, from the moment a trigger is identified to the point the label gets archived. Each stage builds on the last.
Trigger event and initial logging: The change is logged as soon as it is identified. The source is recorded against it. This may be a CAPA, vigilance activity, FSCA or an internal review.
Impact assessment: The team determines which articles, languages, and documents are affected. The team also determines how urgently the changes need to be implemented.
Change control: The change is routed through cross-functional review and formally authorized before any label work begins.
Label revision: The specification and the underlying label data are updated together. This keeps both aligned throughout the change process.
QA verification and reconciliation: The revised label data is checked against the approved specification, field by field.
Approval and release: The revision receives formal sign-off and is released into production.
Distribution: The updated label reaches manufacturing and packaging operations through a coordinated implementation.
Archiving: The superseded version is retained and linked to the version that replaced it.
Most inconsistencies originate where one of these stages gets skipped or compressed, usually under deadline pressure from an FSCA or an urgent CAPA.
Label Master Data Sheets: The Operational Backbone
A specification defines the label requirements. A master data sheet records what was actually implemented, including the fields, symbols, language content and UDI information used in production.
That distinction matters because specification alone does not always ensure consistent results during reprints or system imports.A master data sheet provides greater clarity and ensures the same data is used every time. Downstream systems and printers can use this record directly, without requiring manual data entry or translation.
It also supports UDI consistency and translation consistency across every language variant of a label, since all versions trace back to the same governed source rather than being maintained independently.
In practice, the manufacturers with the fewest reconciliation problems are almost always the ones who built master data sheets early, before their portfolio grew past the point where a spreadsheet could keep up.
Change Logs and Version History
At a minimum, a change log should record the trigger, date, reason for the change, approver, affected articles, version number and effective date. Previous versions should be retained in the record instead of being overwritten.
This log becomes the primary evidence base during an inspection. When an auditor asks how a label reached its current state, the change log answers the question.
Overlapping changes require careful management. Two trigger events can affect the same article at the same time. Without a clear sequencing rule, two revisions can be approved independently and conflict at release. A well-run change log resolves this by requiring impact assessment to check for open changes on the same article before a new one is authorized.
QA Review and Reconciliation
Reconciliation should take place throughout change control, rather than being treated as a last-minute proofreading task. It should confirm that:
- Every field in the master data sheet matches the approved specification exactly
- Artwork reflects the approved revision
- UDI data is consistent across the label, the technical file and any relevant database
- Translations match the approved source language content
- Any discrepancy is documented and resolved before release
A mismatch found during this phase is easy to fix. The same mismatch found after printing or system import can lead to costly rework.
Cross-Functional Governance
No single department owns a label change from start to finish. Successful label change management depends on clearly defined responsibilities across multiple functions.
| Role | Responsibility |
| Regulatory Affairs |
Assesses regulatory impact and authorizes the change.
|
| Quality Assurance (QA) |
Performs verification and reconciliation.
|
| Labeling & Artwork |
Executes the label revision.
|
| Manufacturing & Supply Chain |
Coordinates release and distribution timing.
|
| Clinical / Performance Teams |
Evaluate changes related to clinical or performance evidence.
|
| Vigilance |
Manages changes triggered by safety signals.
|
| IT / PLM Teams |
Maintain the systems that support the label change process.
|
The transfer of responsibility between these groups is where delays and errors often occur. A change that is clearly assessed by Regulatory but poorly communicated to Manufacturing can still result in an inconsistent release. This can happen even when every individual step is completed correctly.
Best Practices for Managing Label Changes at Scale
A few practices consistently separate manufacturers who manage this well from those still catching problems late:
- Run change management as an event-driven workflow and not as a periodic batch review
- Centralize master data before scaling to a large portfolio
- Use digital, electronic approvals with a clear audit trail
- Prioritize changes by risk and urgency rather than by when they were logged
- Build reconciliation into the workflow itself
- Review inspection readiness periodically
- Track KPIs that reveal where the process is slowing down
- Integrate the change log with PLM, QMS and labeling systems so the record updates automatically rather than through manual re-entry
Business and Compliance Benefits
Manufacturers who make the shift to a structured label change methodology usually see faster turnaround on regulatory changes, cleaner audit evidence, fewer labeling errors making it to production and better coordination across teams. Because every version is traceable to a specific, documented cause, inspection preparation becomes a matter of pulling the record rather than reconstructing it.
IVDR-Specific Considerations Beyond the Core Methodology
A few areas deserve particular attention for IVD manufacturers specifically:
- UDI lifecycle management: A UDI-DI reassignment following a significant device change is one of the most common label change triggers and needs its own defined sub-process.
- Digital traceability expectations: Inspectors increasingly expect electronic, time-stamped records rather than paper trails.
- Linkage to post-market surveillance and vigilance: Label changes arising from vigilance findings need a documented link back to the originating case.
- FSCA-driven emergency updates: These require a compressed but still fully documented version of the standard lifecycle.
- CAPA-to-labeling linkage: A CAPA that results in a label change should reference the resulting version explicitly and not just note that “labeling was updated.”
- Managing concurrent changes across multiple products: Particularly relevant where a single component or supplier change affects several articles at once.
- KPI tracking: Cycle time from trigger to release and reconciliation findings per cycle are useful indicators of whether the process is holding up under volume.
Conclusion
Under IVDR, label changes happen too often and across too many articles to manage through document updates alone. A structured label change methodology ties every version to a specific trigger. Each version is verified against master data and archived instead of being overwritten. This gives manufacturers a process that scales with their portfolio and holds up under inspection. It also creates the structured foundation needed for further label lifecycle work, including the implementation of a digital label management system.
If you need support with label change management under IVDR, labeling governance, regulatory documentation or digital label lifecycle implementation, reach out to the experts at info@artixio.com for practical guidance tailored to your regulatory and quality objectives.
