---
title: Up-Classification Under MDR: How to Handle a Surprise Higher Class
description: When MDR up-classifies your device higher than expected, the workload jumps and the timeline shifts. Here is how to absorb the surprise without losing the project.
authors: Tibor Zechmeister, Felix Lenhard
category: Device Classification & Conformity
primary_keyword: up-classification MDR handling
canonical_url: https://zechmeister-solutions.com/en/blog/up-classification-mdr-handling
source: zechmeister-solutions.com
license: All rights reserved. Content may be cited with attribution and a link to the canonical URL.
---

# Up-Classification Under MDR: How to Handle a Surprise Higher Class

*By Tibor Zechmeister (EU MDR Expert, Notified Body Lead Auditor) and Felix Lenhard.*

> **When MDR up-classifies your device — whether through Annex VIII Rule 11 catching your software, Rule 21 catching your substance-based product, or a Notified Body reviewer reading Article 51 differently than you did — the first job is not to panic or push back reflexively. The first job is to confirm the new class against the actual text of Annex VIII of Regulation (EU) 2017/745, then replan the project on the new class. Up-classification changes the conformity assessment route under Article 52, the clinical evidence expectations under Article 61, the technical documentation depth, the Notified Body workload, the timeline, and the cost base. Absorbing the surprise means either accepting the new class cleanly, mounting a defensible dispute, or — for legacy devices — using the transitional provisions in Article 120 as amended by Regulation (EU) 2023/607 to buy time for an orderly transition.**

**By Tibor Zechmeister and Felix Lenhard. Last updated 10 April 2026.**

---

## TL;DR

- Up-classification under the MDR means your device has landed in a higher class than you planned for — often because Annex VIII of Regulation (EU) 2017/745 reads a rule more strictly than you did, or a Notified Body reviewer disagrees with your classification under Article 51.
- The first response is verification, not negotiation. Read the specific Annex VIII rule against your intended purpose and MDCG 2021-24 (October 2021) before deciding whether to absorb the higher class or dispute it.
- Options are finite: absorb the new class, dispute it through a written argument and if necessary Article 51(2) referral, or — for legacy MDD devices — use the transitional window extended by Regulation (EU) 2023/607 to stage the transition.
- Absorbing a higher class is not free. The conformity assessment route under Article 52 changes, clinical evidence obligations under Article 61 escalate, technical documentation depth increases, and Notified Body cost and time go up accordingly.
- The transitional provisions in Article 120 of the MDR, as amended by Regulation (EU) 2023/607, give legacy devices extended deadlines under strict conditions, but they do not freeze the class. When the transition completes, the device is certified at the current MDR class, not the historical class.
- A Subtract to Ship response to up-classification does not try to outrun the new class. It accepts the new regulatory scope, strips every activity that does not trace to a specific MDR obligation for that class, and rebuilds the plan without legacy assumptions.

---

## A founder who opened the wrong envelope

A seed-stage SaMD team had been building against a Class I assumption for fourteen months. The plan, the budget, the investor pitch, and the hiring roadmap all sat on top of that assumption. A regulatory consultant reviewed the intended purpose before the Notified Body quotation round and flagged Rule 11. The rule fit. The software provided information used to make therapeutic decisions. Class IIa, at minimum. Possibly Class IIb, depending on how one read the severity trigger.

The founder's first reaction was the reaction we see every time. Denial, then anger at the consultant, then a day of re-reading Rule 11 looking for an escape. By the end of the day the escape did not exist and the reality settled in. The device was Class IIa. The plan was Class I. The gap was eighteen months of regulatory work the team had not scoped, not staffed, and not funded.

The project did not die. It shifted. The team stopped building new features, rewrote the regulatory plan on the new class, raised a bridge round to cover the extended timeline, and entered the Notified Body queue. Eleven months later the device shipped under the correct class. The lesson was not that the founder should have read Rule 11 earlier — they should have, but every founder with this story will say the same. The lesson is that when up-classification lands, the response that actually works is structured, not emotional.

## Why up-classification happens in the first place

Up-classification is rarely arbitrary. It usually traces back to one of four causes, and knowing which cause you are dealing with changes the response.

**The classification was wrong from the start.** The manufacturer applied the wrong rule, or applied the right rule loosely, and the correct reading of Annex VIII produces a higher class. Most Rule 11 up-classifications fit here. The team classified the software under an active-device default, or under Rule 9, or under nothing at all, and the Notified Body applied Rule 11 properly. This is not a dispute worth having. The Regulation says what it says.

**The intended purpose moved.** A product that started as a fitness monitor became a clinical decision-support tool as the team learned what the market wanted. The intended purpose under Article 2(12) drifted, but nobody re-ran the classification against Annex VIII. The up-classification is real because the device is genuinely different now.

**MDR vs MDD drift on a legacy device.** A device that was Class I under the MDD is Class IIa or higher under the MDR because Annex VIII rewrote the rules — Rule 11 for software, Rule 21 for substance-based devices, the Ir subcategory for reusable surgical instruments. See [Why Your Device Might Be Classified Higher Under MDR Than Under MDD](/blog/device-classified-higher-mdr-than-mdd) for the rule-by-rule comparison. The legacy class does not survive the transition.

**A Notified Body reviewer reads the rule differently.** The classification is genuinely debatable, the manufacturer's reading was defensible, and the reviewer's reading is also defensible. This is the case where a classification dispute is worth preparing. See [Classification Disputes: What to Do When You Disagree with Your Notified Body](/blog/classification-disputes-notified-body) for the route.

Identifying which of the four you are in is the first work. The response to cause one is acceptance. The response to cause two is a decision about whether the new intended purpose is worth the higher class. The response to cause three is the transition plan. The response to cause four is the dispute file.

## The immediate downstream effects

Classification is the input that sets everything downstream. When the class moves up, the downstream effects land in predictable places and in a predictable order.

The conformity assessment route under Article 52 changes. A Class I device outside the Is, Im, Ir subcategories can self-declare. Class IIa upward requires Notified Body involvement. The jump from self-declaration to Notified Body assessment is the largest single step in the MDR conformity landscape — not a modest escalation but a different universe of work. Class IIa, IIb, and III each have distinct annex routes, and moving up a class usually means selecting a different annex.

The clinical evidence requirements under Article 61 escalate. A Class IIa device needs a more rigorous clinical evaluation than a Class I device. A Class IIb device needs broader clinical data. A Class III device generally needs clinical investigations, with specific exemptions in Article 61(4) to (6). Up-classification from Class IIa to Class IIb can add months of clinical evaluation work. Up-classification to Class III can add years, or require an investigation the team has neither the protocol nor the budget for.

Technical documentation depth increases at every class boundary. The Annex II structure is the same, but the expected level of detail in risk management, verification and validation, and clinical evidence scales with the class. A Notified Body reviewing a Class IIb technical file applies more scrutiny than the same reviewer reading a Class IIa file on the same platform.

Post-market surveillance obligations scale. Vigilance obligations scale. The scope of the Person Responsible for Regulatory Compliance scales. The Notified Body surveillance audit frequency and depth scale. The quotation you had for the old class is not the quotation you will get for the new class — expect the Notified Body fee to rise, sometimes substantially.

Runway impact follows. A plan built on the old class has a cost curve and a timeline that do not match the new class. Reforecasting the plan on the correct class is not optional. The sooner it happens, the fewer surprises downstream.

## Options to push back

Pushing back is not the same as wishful thinking. A defensible push-back has three forms and each is available only under specific conditions.

**Re-read the rule.** The cheapest and most common response. Read the Annex VIII rule text in full, read MDCG 2021-24 on that rule, and compare against the actual intended purpose. If the re-read produces a lower class with a defensible citation, document the argument and keep it on file. Rule 11, in particular, has escalation triggers that do not always apply. Rule 21 has substance-category distinctions that a quick reading can miss. Sometimes the up-classification dissolves on a careful second read.

**Narrow the intended purpose.** If the intended purpose as drafted triggers a higher class, and the team can live with a narrower purpose that triggers a lower class, the narrower purpose is a legitimate response — provided the narrower version is honestly the product the team is shipping, consistent with the label, the IFU, the website, and the clinical evaluation. A narrowed purpose that contradicts the marketing materials will not survive a Notified Body review. It will also not survive the first post-market question from a regulator.

**Mount a formal dispute.** Where the classification is genuinely debatable and the stakes justify it, prepare the written classification argument and work through the escalation ladder — reviewer, second reviewer or certification committee, and finally Article 51(2) referral to the competent authority. The full process is in [Classification Disputes: What to Do When You Disagree with Your Notified Body](/blog/classification-disputes-notified-body). A dispute is a real tool, not a bluff, and it is not a first resort.

None of these three options is about avoiding work the MDR actually requires. They are about ensuring the class is correct, not aspirational.

## Options to absorb

When push-back is not available or not appropriate, absorption is the response. Done well, absorption is structured and fast. Done badly, it becomes an open-ended panic that drains runway.

The first step in absorption is a complete, brutal reforecast. Rebuild the regulatory plan on the new class from scratch. Do not patch the old plan. Identify the new conformity assessment route under Article 52. Identify the new clinical evidence expectations under Article 61. Identify the new technical documentation gaps. Identify the new Notified Body scope and request a revised quotation. Produce a realistic new timeline.

The second step is cutting. Every activity in the old plan that was designed around the old class comes under review. Some of it is still valid at the new class. Some of it is not. Some of it is not enough. The discipline is to strip everything that does not trace to the new class's obligations and then add back only what the new class genuinely requires — not what the team fears the new class might require.

The third step is communicating the reforecast. To investors, to the board, to the Notified Body, to the team. The temptation is to minimise the impact. The better move is to report the new plan honestly, with the specific Annex VIII rule citation, the specific cost and timeline delta, and the specific mitigations. A board that hears the unvarnished plan once rebuilds confidence faster than a board that hears an optimistic plan that then drifts.

The fourth step is execution on the new plan without relitigating the class. Founders who keep looking for an escape after absorption has started burn time on the wrong problem. Once the decision to absorb is made, the energy goes into the new plan.

## Transitional provisions for legacy devices

For a legacy device carrying a valid MDD certificate, up-classification on the MDR side does not immediately stop sales. Article 120 of the MDR, as amended by Regulation (EU) 2023/607 of 15 March 2023, provides extended transitional deadlines under specific conditions for devices with a valid MDD certificate on 26 May 2021. The extended deadlines run until 31 December 2027 for Class III devices and certain Class IIb implantables, and until 31 December 2028 for other Class IIb devices, Class IIa devices, and specified Class I categories, subject to the conditions in the amended Article 120.

The conditions are strict. The manufacturer must have a QMS compliant with the MDR in place by 26 May 2024. The manufacturer must have lodged a formal MDR application with a Notified Body and signed a written agreement by 26 September 2024. The device must continue to comply with the MDD. There must be no significant changes in design or intended purpose. MDR post-market surveillance, market surveillance, vigilance, and registration obligations apply during the extended period.

The critical point for an up-classified legacy device is the one [post 087](/blog/device-classified-higher-mdr-than-mdd) already makes: Regulation (EU) 2023/607 extends the time to transition but does not freeze the class. The device transitions to the current MDR class under Annex VIII, not the historical MDD class. A Class I MDD software product that is Class IIa under MDR Rule 11 is Class IIa from the moment the MDR applies. The transitional window buys runway to complete the transition to that class. Used properly, the window is a gift. Misread as a class freeze, it is a trap that closes on the day the certificate expires.

## Planning for up-classification before it lands

The best response to up-classification is to price it into the plan before it arrives. Three practices make that cheap.

First, classify early and classify written. The classification argument, two to five pages, citing the specific Annex VIII rule and the intended purpose under Article 2(12), should exist before the first Notified Body conversation. If the argument is weak, the weakness shows up before the project has sunk months of work into the wrong class. The hub [MDR Device Classification Explained](/blog/mdr-device-classification-explained) walks through the classification discipline.

Second, run a Rule 11 and Rule 21 pre-check on every software or substance-based product. These are the two rules that produce most up-classification surprises. Thirty minutes with the rule text, the intended purpose, and MDCG 2021-24 is cheaper than thirty days of replanning.

Third, build the financial model with a class-sensitivity line. What does the project cost at the current class? What does it cost one class higher? What does it cost two classes higher? Founders who know those three numbers at the start are never fully blindsided when the class moves.

## The Subtract to Ship angle on up-classification

The [Subtract to Ship framework for MDR compliance](/blog/subtract-to-ship-framework-mdr) treats classification as the second of four passes, and up-classification is the scenario the pass is designed to handle. The discipline of the classification pass is to find the lowest defensible class, not the lowest wishful class. When the defensible answer turns out to be higher than the wishful answer, Subtract to Ship absorbs the new reality and strips the plan accordingly.

Subtracting under up-classification means cutting every activity, document, and feature that was scoped for the old class and no longer traces to a specific MDR obligation. It also means not adding fake rigour to compensate for the shock. The instinct after up-classification is to over-document, over-engineer, and over-test to prove diligence to the new Notified Body. Subtract to Ship says the opposite. Do only what the new class's specific articles and annexes require. Skip everything else. The Notified Body is assessing compliance, not anxiety.

The framework also says when not to dispute. A classification dispute costs time and credibility. If the up-classification is grounded in a correct reading of Annex VIII, the Subtract to Ship response is acceptance and replanning, not a fight. The fights are reserved for disputes where the argument is genuinely defensible and the stakes are genuine. See [post 089](/blog/classification-disputes-notified-body) for the decision framework.

## Reality Check — Are you handling up-classification well?

1. Have you verified the up-classification against the specific Annex VIII rule text and MDCG 2021-24, rather than relying on a reviewer's summary or a consultant's informal read?
2. Do you know which of the four causes — wrong initial classification, intended purpose drift, MDR vs MDD drift, or a defensible reviewer disagreement — applies to your situation?
3. Have you completed a full reforecast of the regulatory plan on the new class, including Article 52 route, Article 61 clinical evidence, technical documentation depth, and Notified Body cost and timeline?
4. If you are considering a push-back, is the written classification argument complete, cited, and defensible against MDCG 2021-24?
5. If you are absorbing the new class, have you cut every activity that was scoped for the old class and no longer traces to a specific MDR obligation?
6. For a legacy device, have you confirmed that your MDD certificate meets the conditions of Article 120 as amended by Regulation (EU) 2023/607, including the QMS and Notified Body application deadlines?
7. Have you communicated the new plan honestly to investors, the board, and the team — with the specific rule citation, cost delta, and timeline delta?
8. Have you stopped looking for an escape route once the decision to absorb is made, and committed the team's energy to the new plan?

## Frequently Asked Questions

**What does up-classification mean under the MDR?**
Up-classification means your device has landed in a higher class under Annex VIII of Regulation (EU) 2017/745 than you originally planned for. It can happen because the initial classification was wrong, because the intended purpose drifted, because the MDR Annex VIII rules produce a higher class than the equivalent MDD rules did, or because a Notified Body reviewer reads a rule differently than the manufacturer did. The higher class changes the conformity assessment route under Article 52 and the clinical evidence expectations under Article 61.

**What should I do first when my device is up-classified?**
Verify the new class against the actual text of the relevant Annex VIII rule and MDCG 2021-24 (October 2021). Do not negotiate, dispute, or replan before the verification is complete. Most up-classification responses fail because the team acts on a summary of the new class rather than on the rule text itself.

**Can I dispute an up-classification by my Notified Body?**
Yes, where the classification is genuinely debatable. The route runs through a written classification argument, escalation within the Notified Body if needed, and finally a referral to the competent authority under Article 51(2) of Regulation (EU) 2017/745. A dispute is a real option, not a bluff, and it is not a first resort when the up-classification is grounded in a correct reading of Annex VIII.

**Does Regulation (EU) 2023/607 protect my legacy device from up-classification?**
No. Regulation (EU) 2023/607 extended the transitional deadlines in Article 120 of the MDR under specific conditions, giving legacy devices more time to complete the transition. It did not freeze the class. When the MDD certificate expires and the device transitions, the class is determined by Annex VIII of the MDR, not by the historical MDD class. The extension is runway, not a class freeze.

**How do I rebuild the project plan after an up-classification?**
Rebuild from scratch on the new class. Identify the new conformity assessment route under Article 52, the new clinical evidence expectations under Article 61, the new technical documentation gaps, the new Notified Body scope, and the new timeline. Cut every activity from the old plan that was scoped for the old class and no longer traces to a specific MDR obligation. Add back only what the new class genuinely requires. Communicate the new plan to investors, the board, and the team with specific citations and specific deltas.

## Related reading

- [Why Your Device Might Be Classified Higher Under MDR Than Under MDD](/blog/device-classified-higher-mdr-than-mdd) — the rule-by-rule reasons legacy devices move up.
- [Classification Disputes: What to Do When You Disagree with Your Notified Body](/blog/classification-disputes-notified-body) — the full dispute route including Article 51(2).
- [MDR Device Classification Explained](/blog/mdr-device-classification-explained) — the hub post on classification under the MDR.
- [MDR Annex VIII Classification Rules: Complete Guide](/blog/mdr-annex-viii-classification-rules-complete-guide) — the rule-by-rule walk underpinning every classification question.
- [MDR Classification Rule 11: Software](/blog/mdr-classification-rule-11-software) — the rule that drives the majority of software up-classification cases.
- [Reclassification After Certification: Changing Device Class](/blog/reclassification-after-certification) — the post-market route when the class needs to change later.
- [The Subtract to Ship Framework for MDR Compliance](/blog/subtract-to-ship-framework-mdr) — the methodology that runs classification as a dedicated pass.
- [MDR Article 120: Transitional Provisions Explained](/blog/mdr-article-120-transitional-provisions) — the legal mechanics of the extension under Regulation (EU) 2023/607.

## Sources

1. Regulation (EU) 2017/745 of the European Parliament and of the Council of 5 April 2017 on medical devices, Article 51 (classification), Article 52 (conformity assessment procedures), Article 61 (clinical evaluation), Article 120 (transitional provisions, as amended), Annex VIII (classification rules). Official Journal L 117, 5.5.2017.
2. Regulation (EU) 2023/607 of the European Parliament and of the Council of 15 March 2023 amending Regulations (EU) 2017/745 and (EU) 2017/746 as regards the transitional provisions for certain medical devices and in vitro diagnostic medical devices. Official Journal L 80, 20.3.2023.
3. MDCG 2021-24 — Guidance on classification of medical devices, October 2021.

---

*This post is part of the Device Classification & Conformity Assessment series in the Subtract to Ship: MDR blog. Authored by Felix Lenhard and Tibor Zechmeister. Up-classification is one of the moments where the difference between a panicked replan and a disciplined replan decides whether the project survives — and where a sparring partner who has seen the same surprise across dozens of certifications can compress weeks of rethinking into a single focused session.*

---

*This post is part of the [Device Classification & Conformity](https://zechmeister-solutions.com/en/blog/category/classification) cluster in the [Subtract to Ship: MDR Blog](https://zechmeister-solutions.com/en/blog). For EU MDR certification consulting, see [zechmeister-solutions.com](https://zechmeister-solutions.com).*