How to prioritize IVD compliance work before the IVDR deadline

Time : Oct 02, 2026
Views:
IVDR deadline planning made practical: prioritize IVD portfolios, protect transitional market access, close evidence gaps, and build a realistic certification roadmap.

The IVDR deadline is not a single date that can be managed through a single documentation project. For many IVD portfolios, the immediate task is to determine which devices can still use the transitional pathway, which require a full IVDR conformity assessment sooner, and which products should not consume further compliance resources at all.

The most important management decision is therefore not “Which files should be updated first?” It is “Which product-market combinations create the greatest risk of losing lawful access to the EU market if work is delayed?” A legacy assay sold in several Member States, dependent on a single reagent supply chain and requiring notified body involvement, may deserve priority over a technically more complex product that has limited commercial value or no viable IVDR route.

Under Regulation (EU) 2017/746, as amended, certain legacy devices may remain on the market under specified conditions until 31 December 2027, 31 December 2028, or 31 December 2029, depending on their IVDR classification. The transition is conditional, not automatic. New devices and devices that do not meet the transition conditions must comply with IVDR requirements before being placed on the EU market. This distinction should drive the entire project plan.

Start with a defensible portfolio eligibility decision

Before assigning teams to clinical evidence, technical documentation, or label revisions, establish whether each device is actually eligible for the extended transition. This is a regulatory gate, not an administrative detail.

A transition assessment should be performed at the level of the specific device family, configuration, intended purpose, and EU market status. It should capture the former regulatory basis, current IVDR classification, certificate status where applicable, declaration of conformity history, and whether the device has been continuously placed on the market under the relevant conditions.

For legacy devices, the extended transitional periods are generally linked to IVDR class:

  • Class D devices: until 31 December 2027;
  • Class C devices: until 31 December 2028;
  • Class B devices and Class A devices placed on the market sterile: until 31 December 2029.

Eligibility also depends on meeting the applicable transition conditions. These include continued compliance with the earlier applicable legal framework, no significant changes in design or intended purpose, no unacceptable risk to patients, users, or other persons, and compliance with the required quality-management-system and notified body milestones. The amended IVDR transition framework includes key dates for having an IVDR-compliant quality management system in place, submitting a formal application to a notified body, and concluding a written agreement with that notified body.

A useful project output is an eligibility register with a clear status for every product-market combination:

Portfolio status Meaning Immediate action
Full IVDR required now No valid transition route, new device, or transition conditions cannot be met Launch or accelerate complete IVDR conformity assessment
Transition eligible but fragile Eligibility depends on unresolved QMS, notified body, change-control, or evidence issues Resolve the specific condition that could end market access
Transition eligible and controlled Conditions are documented and monitoring is active Plan IVDR certification according to the applicable end date and business value
Exit or deprioritize Low-value product, obsolete platform, weak evidence base, or disproportionate remediation burden Set an orderly discontinuation and customer communication plan

This exercise often reveals that the apparent product count is misleading. One analyzer platform may support numerous assays, but the regulatory and technical workload may differ sharply between them. A single software update may affect multiple devices. A reagent change can alter performance claims, stability evidence, risk controls, labeling, and the relationship between an instrument and its test menu.

How to prioritize IVD compliance work before the IVDR deadline

Prioritize by market-access exposure, not by document maturity

Teams frequently begin with the products whose technical files are easiest to improve. That can create visible progress while leaving the largest commercial and regulatory exposures untouched. The better approach is to rank work according to the consequences of delay.

High-priority products tend to have several of the following characteristics:

  • They support a material share of EU revenue or are necessary to retain a strategic distributor or hospital account.
  • They are classified as Class C or Class D, where evidence and notified body review can be more demanding.
  • They are dependent on a narrow group of suppliers, critical raw materials, reference materials, or manufacturing sites.
  • They carry claims associated with screening, diagnosis, disease staging, therapy selection, infectious disease detection, or other uses where clinical performance evidence requires careful scrutiny.
  • They have unresolved classification questions, incomplete performance evaluation records, or legacy evidence that does not map cleanly to IVDR General Safety and Performance Requirements.
  • They require significant updates to the quality system, post-market surveillance process, vigilance workflow, economic operator arrangements, or EUDAMED-related data management.

Commercial importance alone should not determine priority. A low-volume device can be operationally critical if it completes a laboratory workflow, supports a bundled analyzer placement, or prevents a distributor from replacing an entire product line with a competitor’s portfolio. Conversely, a high-revenue legacy assay may not justify remediation if its underlying evidence cannot support the intended purpose without a disproportionate new study programme.

For project control, each device should receive a combined score covering market impact, regulatory urgency, remediation uncertainty, notified body dependency, and technical interdependence. The point is not to create a mathematically perfect score. It is to make prioritization explicit, traceable, and reviewable when commercial teams, regulatory affairs, quality, R&D, and finance compete for the same resources.

Separate “transition protection” from “full certification readiness”

These are related workstreams, but they should not be treated as identical.

Transition protection focuses on maintaining lawful market access while the full IVDR programme is in progress. Its main questions are whether the device remains eligible, whether the QMS and notified body conditions have been met, whether change control is sufficiently disciplined, and whether post-market obligations are functioning.

Full certification readiness concerns the complete IVDR conformity assessment package. It includes classification rationale, technical documentation, risk management, performance evaluation, scientific validity, analytical performance, clinical performance, usability where relevant, labeling, instructions for use, stability evidence, software lifecycle evidence, cybersecurity considerations where applicable, and post-market performance follow-up planning.

Combining these streams into one broad “IVDR project” can obscure critical risks. A device may have a credible multi-year plan for full certification but still lose transitional eligibility because a significant design change is introduced without a robust regulatory assessment. Equally, a company may successfully preserve transitional status while accumulating a future certification bottleneck because performance evidence has not been addressed early enough.

Project governance should therefore maintain two separate views: a short-horizon market-access control board and a longer-horizon certification roadmap. The first asks, “Can we continue placing this device on the market lawfully?” The second asks, “What evidence, remediation, and review capacity are needed to obtain the IVDR certificate?”

Identify evidence gaps before technical writing begins

Technical documentation work often slows down because teams discover too late that the real problem is not document formatting but missing evidence. For IVDs, the performance evaluation is commonly the point where legacy files prove insufficient.

The IVDR performance evaluation framework requires manufacturers to demonstrate scientific validity, analytical performance, and clinical performance. The available evidence must support the intended purpose and claims made for the device. A well-organized legacy study library may still be inadequate if it does not reflect the current assay formulation, specimen types, target population, cut-off values, comparator method, intended user, or clinical setting.

Evidence triage should focus on questions with direct schedule consequences:

  • Does the scientific validity evidence support the analyte-disease or analyte-condition relationship claimed in the intended purpose?
  • Are analytical performance studies complete for the current design, including relevant precision, analytical sensitivity, analytical specificity, measuring range, interference, cross-reactivity, specimen stability, and traceability elements?
  • Does clinical performance evidence represent the intended users, target population, sample types, and use environment?
  • Are performance claims in marketing material, instructions for use, labels, distributor training material, and technical documents consistent?
  • Has the device changed since the supporting studies were generated, even if the change was considered minor under the previous framework?

Do not allow document authors to compensate for missing evidence through increasingly complex narratives. A gap that requires new samples, a new comparator study, access to clinical specimens, or external laboratory support is a project-critical dependency. It needs a budget, owner, protocol timeline, decision points, and contingency plan.

Use notified body capacity as a scheduling constraint

For devices requiring notified body involvement, the notified body is not an external checkpoint at the end of the programme. It is a capacity-limited project dependency that affects timing, evidence strategy, and the level of documentation readiness required at each stage.

Notified body engagement should begin with a portfolio-specific submission plan rather than a generic request for certification. The plan should define intended certificate scope, device groupings, classification rationale, anticipated application timing, technical documentation availability, significant evidence gaps, and internal readiness dates. It should also identify whether one certificate scope depends on shared software, common reagent production, common performance studies, or a shared quality-system process.

The aim is not to submit incomplete files simply to create activity. It is to meet applicable transition milestones and secure a workable assessment path while avoiding preventable rounds of questions. Weak scope definition is particularly damaging: a portfolio may be grouped too broadly, creating unnecessary evidence burden, or too narrowly, multiplying submissions and audits without improving regulatory control.

Notified body interaction should be reflected in the critical path. Allow time for application review, contract finalization, QMS assessment, technical documentation sampling or review, questions, corrective action responses, and final certification decisions. None of these tasks should be represented as a single “approval” line in a project schedule.

Freeze changes that threaten legacy status, but do not freeze necessary quality work

One of the most difficult IVDR management issues is the handling of product changes during transition. Commercial teams may seek new claims, expanded specimen types, revised packs, improved software features, alternative suppliers, or updated instruments. Operations may need to replace an unavailable component. R&D may be correcting a known usability or stability weakness.

A blanket ban on changes can create supply disruption, quality problems, and product obsolescence. An uncontrolled change process can jeopardize transitional status or generate a documentation mismatch that becomes difficult to defend during assessment.

The practical answer is a dedicated IVDR transition change-control gate. Each proposed change should be assessed against intended purpose, design, performance, risk profile, labeling, manufacturing process, software behavior, and evidence applicability. The assessment should distinguish between changes required to maintain safety and supply continuity and changes intended to expand commercial positioning.

Changes with uncertain significance should be escalated early, not after implementation. The relevant question is not whether the change appears small from an engineering perspective. It is whether it could be considered significant under the transitional provisions or invalidate the evidence used to support the current device configuration.

Build a programme around dependencies, not departmental task lists

An IVDR programme fails when every department completes its own list while the dependencies between those lists remain unmanaged. Regulatory affairs may finalize classification, but R&D may not have released the design history records needed to support it. Quality may update procedures, but post-market data may still be scattered across distributor complaints, service records, and separate vigilance databases. Clinical teams may identify a study need, but procurement may not have secured sample access or laboratory contracts.

The most useful project plan links each deliverable to its prerequisites, reviewer, approval criteria, and effect on market access. Instead of tracking “technical documentation complete,” track the components that can actually block submission or certification: performance evaluation conclusion approved, risk-benefit conclusion aligned with claims, stability protocol completed, supplier change assessed, PMS data reconciled, labeling released, and notified body questions answered.

Clear escalation thresholds are equally important. A product should be escalated when a key evidence gap has no feasible closure route, when a notified body timeline moves beyond the product’s transition deadline, when a planned change could affect eligibility, or when a shared platform issue threatens several certificates at once. Waiting for routine monthly reporting can turn a manageable delay into a market-withdrawal decision.

Make discontinuation a controlled compliance option

Not every legacy device should proceed to IVDR certification. Continuing all products by default can consume scarce regulatory and technical resources while delaying strategically important devices. A controlled discontinuation decision may be preferable where the device has weak market value, declining demand, an unsustainable evidence burden, obsolete components, or an intended purpose that no longer fits the manufacturer’s long-term portfolio.

Discontinuation still requires management. Inventory, distributor commitments, service support, reagent continuity, customer notification, complaint handling, vigilance obligations, and retention of technical documentation must remain controlled. For instrument-reagent systems, withdrawal of one component can affect the usability of another component already installed in laboratories.

The strongest IVDR deadline plan is not the one with the largest number of projects. It is the one that preserves justified market access, protects high-value device families, prevents avoidable transition failures, and gives each remaining certification programme a realistic evidence and notified body path. That requires early portfolio choices, disciplined change control, and a schedule built around regulatory dependencies rather than the appearance of documentation progress.

Have questions about the global trade trends discussed here, or planning your expansion and supply chain strategy? Leave a message below and let the trade experts at MTHH guide you.

Dispatch Transmission

We respect your privacy. Your information is strictly confidential.

Related News