If EU MDR feels like a mountain, there’s a surprisingly simple place to start: your intended purpose.
Not your QMS. Not your technical file. Not your Notified Body.
A clear, review-ready intended purpose is the sentence that drives classification, clinical strategy, labeling, and your entire technical documentation.
If you haven’t read the broader roadmap yet, start here first: EU MDR for startups: where do I start?
What “intended purpose” really means
Under EU MDR, the intended purpose (sometimes called intended use) is your official statement of:
- Who the device is for
- Who uses it
- Where it’s used
- What it does (and does not do)
- The medical context it supports
In practice, it becomes the anchor for:
- Classification (and whether you need a Notified Body)
- Clinical evaluation (what evidence you must generate or justify)
- Risk management (which hazards are relevant)
- IFU/labeling (what you can claim publicly)
- Tech Doc structure (what you must document and trace)
Why startups get this wrong (and pay for it later)
Most early teams make one of these mistakes:
- Marketing language instead of regulatory language
- Over-claiming (“diagnoses”, “prevents”, “treats”) before evidence exists
- Too broad (“for all patients”, “for all indications”)
- No boundaries (what the product is explicitly not intended for)
The result is predictable: rework, scope creep, and a heavier conformity assessment than you planned.
The 6 building blocks of a strong intended purpose
You don’t need 10 pages. Start with these six elements:
- Target population / patient group
- Intended user (HCP vs lay user)
- Use environment (home, clinic, OR, etc.)
- Medical context / condition / workflow
- Core function (what the device does)
- Output + decision influence (does it only inform, or does it drive clinical decisions?)
For software and AI: be explicit about whether the output is informational or action-driving. That single detail often changes classification and evidence needs.
Copy-paste template (starter version)
“[Product name] is a [device type, e.g., software/instrument] intended for [target population] and intended to be used by [intended user] in [use environment] to [core function] in the context of [medical condition/workflow].”
Add a boundary line early:
“[Product name] is not intended for [key exclusions / out-of-scope use].”
A quick “review-ready” self-check
If you can answer these three questions clearly, you’re on the right track:
- What is the medical statement in one sentence?
- Which claims can you support now, and which are future claims?
- What is explicitly out of scope?
Want to pressure-test your intended purpose in 60 minutes?
If you want a founder-friendly sanity check before you lock your claims and build too far, book a free 60-minute MDR Strategy Call.
We’ll typically:
- Sharpen your intended purpose and boundaries
- Pressure-test likely classification direction
- Identify the first documents that will unblock your MDR work
Book here: https://calendly.com/niko-mangold-consultants/30min