Most founders building a medical device spend their first regulatory conversation asking the wrong question. They ask: what do we need to do to get certified? The better question is: what does our product claim to do? That single answer determines every regulatory decision that follows.

Your intended purpose is not a marketing choice. It is a legal one. Write it too broadly and you claim clinical capabilities you did not mean to assert. Write it too narrowly to avoid regulation and you create a gap between what your device does and what your documentation says. Each adjustment seems reasonable at the time. Together, they become a problem that cannot be solved with money or momentum.

A quick explanation of what we are talking about

Under Article 2(1) of MDR 2017/745, your product is classified based on what you say it does, not what it technically does. A wearable that tracks heart rate for fitness is not a medical device. The same wearable marketed to detect arrhythmia probably is. This statement, your intended purpose, sets your regulatory class, determines whether you need a Notified Body, and defines the clinical evidence you must produce. Get it wrong and every document downstream is built on the same mistake.

The 3 risks that will not wait

Wrong class. Your intended purpose feeds directly into the classification rules in Annex VIII. A vague or ambitious statement can push your device into a higher risk class than your product requires. Higher class means a Notified Body is mandatory, timelines stretch, and the clinical evidence bar rises. Founders who discover this late often face a full restart.

Clinical evidence mismatch. Your Clinical Evaluation Report must support the claims in your intended purpose exactly. Change the intended purpose mid-development and your existing clinical data may no longer apply. The worst outcome is arriving at a Notified Body audit with a CER that does not match the device you are presenting.

QMS scope creep. Your Quality Management System must cover what your device claims to do. If your intended purpose expands as the product develops, your QMS must expand with it. Most do not. The result is a technical file where documents contradict each other, which is the most common reason Notified Body audits stall.

What starting early actually means

1. Write your intended purpose statement before your product roadmap, not after it. It is the document everything else points back to, and changing it mid-development triggers a cascade of rework.
2. Run that statement against the Annex VIII classification rules before you engage a Notified Body. Know your class before they tell you. It changes how you prepare.
3. Treat every change to your intended purpose as a regulatory change. Flag it, document it, and update your QMS scope. A product pivot that looks minor can shift your conformity route entirely.

Before the words set in concrete

The gap is rarely resources or expertise. It is one honest conversation about what your product claims to do before the development commitments are locked.

HealthTech Pathways offers a free 20-minute MDR assessment that walks you through the qualification questions based directly on Article 2(1), so you know where you stand before committing to a regulatory pathway. Start at healthtechpathways.org.

Take the free MDR assessment at https://healthtechpathways.org/ before your intended purpose statement becomes your most expensive assumption.