Intended purpose — Zweckbestimmung in German — is the single sentence that determines your classification, your claims, your clinical evaluation scope, and the cost of your CE mark. Get it wrong early and you pay for years. The trap is not that founders forget to write one; it is that they write one that is too broad, too clinical, too vague, or silently contradicted by their own marketing.

By Tibor Zechmeister and Felix Lenhard.

TL;DR

  • Intended purpose under MDR Article 2(12) is the legal anchor for your entire device file.
  • Classification, promotional limits, and clinical evaluation scope all cascade from it.
  • The four most common founder mistakes are too broad, too clinical, too vague, and marketing-IFU drift.
  • Fixing a wrong intended purpose after technical documentation is built costs many multiples of getting it right at the start.
  • Lock it before the architecture, before the risk file, before the first test report.
  • The best intended purpose is the narrowest one that still describes a product worth buying.

Why this one sentence decides everything

If you ask a first-time MedTech founder what will kill their company, you will hear answers about funding, clinical data, or the notified body queue. You will almost never hear "my intended purpose statement". Yet that is the sentence most often responsible for the eighteen-month delays, the late classification jumps, the rewritten clinical evaluation reports, and the audit findings that turn into redesigns.

The intended purpose is not a marketing description. It is not a paragraph on your website. It is the legal statement of what your device is for, and the MDR reads it with extraordinary literalness. Every word in it activates machinery somewhere else in the regulation. Every adjective you add is a claim you will be asked to substantiate. Every clinical indication you write pulls in evidence obligations. Every patient population you name expands your risk file. Every use environment you list adds to your usability evaluation.

Founders who do not take this sentence seriously at the start are not being cavalier — they are almost always trying to be inclusive. They want to leave room to pivot. They want the sentence to describe everything the product might do one day. The trap closes the moment that inclusive sentence meets Annex VIII.

What MDR actually says

Article 2(12) of Regulation (EU) 2017/745 defines intended purpose as:

"intended purpose means the use for which a device is intended according to the data supplied by the manufacturer on the label, in the instructions for use or in promotional or sales materials or statements and as specified by the manufacturer in the clinical evaluation"

Read this sentence twice. There are four load-bearing phrases:

  1. "according to the data supplied by the manufacturer" — you define it, not the user. The user's off-label use is a different regulatory story.
  2. "on the label, in the instructions for use" — your formal documentation fixes it.
  3. "or in promotional or sales materials or statements" — and so does your marketing. There is no firewall between marketing and intended purpose. This is the drift trap.
  4. "and as specified by the manufacturer in the clinical evaluation" — your CER must match the intended purpose. If they diverge, one of them is wrong.

Three cascades follow from this definition:

  • Classification cascade (Annex VIII): the classification rules in Annex VIII read the intended purpose. Duration of use, invasiveness, body location, active vs non-active, diagnostic vs therapeutic, software decision support, patient population — all of these are fields the rules extract from your intended purpose. Change the intended purpose and the rules can land you in a different class.
  • Promotion cascade (Article 7): Article 7 prohibits the use of text, names, trade marks, pictures and figurative or other signs that may mislead the user or patient regarding the device's intended purpose, safety, or performance. If your marketing implies indications that are not in your intended purpose, you have an Article 7 problem. If your intended purpose implies indications your evidence cannot support, you have an Article 7 problem.
  • Clinical evaluation cascade (Annex XIV): the clinical evaluation under MDR Article 61 and Annex XIV Part A must demonstrate conformity with the general safety and performance requirements for the intended purpose. The scope of clinical data you need is defined by the intended purpose. Broaden the purpose and you broaden the CER. Narrow the purpose and you narrow the CER.

Every regulatory cost in your company is downstream of the sentence you write.

The four trap variants

Across hundreds of audits and startup reviews, the same four failure modes recur.

Trap 1 — Too broad. The founder writes "intended for monitoring of cardiovascular health in adults". This is a marketing sentence dressed as an intended purpose. It implicitly claims prevention, prediction, risk stratification, and lifestyle guidance. None of those are evidenced. The notified body reads it and asks for cardiovascular outcome data. The founder asks for a narrowing amendment. That amendment is technically a change to the device, and it propagates through the file.

Trap 2 — Too clinical. The opposite mistake: the founder, trying to sound serious, writes an intended purpose that promises direct clinical diagnosis or therapy guidance when the underlying product is a measurement or information tool. This pushes classification up — sometimes through Rule 11 of Annex VIII for software — and requires clinical data the startup cannot afford to generate. The device is then over-classified for the life of the first certification because rewriting the intended purpose mid-review is painful.

Trap 3 — Too vague. The founder writes "intended to support healthcare professionals". Support how? For what decision? For what condition? For what population? A vague intended purpose is worse than a broad one, because the auditor will pin it down for you, and you will not like where it lands. The rule of thumb: if the intended purpose does not unambiguously tell you which classification rule applies, it is too vague.

Trap 4 — Marketing-IFU drift. The intended purpose in the IFU says one thing. The landing page says another. The investor deck says a third. The clinical evaluation report quotes a fourth. Article 2(12) is explicit that promotional materials are part of the intended purpose. If your marketing has outrun your IFU, your intended purpose has moved without your knowledge — and that has consequences under Article 7 and across your entire file. Auditors look for this. They compare your website, your booth materials, your conference talks, and your IFU. Drift is a standard finding.

A worked example: three words that moved a class

A wearable device startup drafted an intended purpose that included the phrase "for the detection of early-stage arrhythmia". The underlying product was a pulse sensor with a simple algorithm.

Three words did the damage: "detection", "early-stage", and "arrhythmia".

  • "Detection" implied a diagnostic function, not just measurement or display.
  • "Early-stage" implied a predictive or risk-stratification claim.
  • "Arrhythmia" named a specific clinical condition, which pulled in clinical evaluation requirements around that condition.

The resulting classification assessment placed the device significantly higher than the founders had planned, with clinical evaluation scope covering sensitivity, specificity, and positive predictive value for early arrhythmia detection in the intended population. Neither the clinical data nor the budget existed to support that.

The fix was to rewrite the intended purpose to reflect what the device actually did: measure and display pulse-related information, with no diagnostic claim, no prediction claim, and no named condition. The classification dropped. The clinical evaluation scope shrank. The CE mark became feasible. The "early-stage arrhythmia" positioning moved to a phase two roadmap item with its own clinical study plan.

The three words would have cost the company the company.

The Subtract to Ship playbook for intended purpose

Step 1 — Write it before the architecture. The intended purpose belongs on page one of the project, not in a documentation sprint before the notified body submission. Every architectural decision downstream should be traceable to it.

Step 2 — Use the narrowest description that still describes a saleable product. If you can take a word out and still have a product, take the word out. Remove adjectives that cannot be substantiated. Remove claims that are aspirational. Remove patient populations you are not ready to evidence.

Step 3 — Run a classification dry-run against Annex VIII. Walk the rules with the drafted intended purpose. Write down which rule applies, which class results, which conformity assessment route you need. If the answer changes when you rephrase the purpose, the phrasing matters.

Step 4 — Lock the language across every artefact. The IFU, the label, the landing page, the pitch deck, the CER, the technical documentation, and any promotional material must all say the same thing. Not "similar" — the same. Differences are findings.

Step 5 — Assign an owner for intended purpose drift. Someone on the team — often the PRRC or the regulatory lead — owns the sentence. When marketing drafts a new campaign, it goes through that person. When the team considers a new use case, it goes through that person. When the CER is updated, it goes through that person.

Step 6 — Re-review quarterly. Intended purpose drift is a slow-motion problem. A quarterly audit against all live materials — web, collateral, investor decks, conference talks, demo scripts — catches drift before it becomes a finding.

Step 7 — Change it deliberately, never accidentally. If you genuinely need to change the intended purpose, do it as a controlled change with a full impact assessment: classification, clinical evaluation, risk file, labelling, promotional material. The change itself is normal. The accidental change is fatal.

Reality Check

  1. Can you recite your intended purpose from memory in under twenty seconds?
  2. Does every word in it survive the question "what evidence supports this word"?
  3. Does your landing page use the same words as your IFU?
  4. Does your CER scope match your intended purpose exactly, or is one broader than the other?
  5. When did you last audit your promotional materials against Article 7 and your intended purpose?
  6. If an auditor read only your intended purpose, would they reach the same classification you did?
  7. Is there a named owner for the intended purpose statement in your team?
  8. If you had to narrow your intended purpose today, which three words would you remove?

Frequently Asked Questions

Is intended purpose the same as intended use? In MDR usage, intended purpose is the defined legal term under Article 2(12). Intended use is often used interchangeably in US and engineering practice but in an MDR file the term intended purpose is the one that matters.

Where does intended purpose need to appear? On the label, in the instructions for use, in the technical documentation, in the clinical evaluation report, and it must be consistent with all promotional and sales materials under Article 2(12) and Article 7.

Can I write a broad intended purpose now and narrow it later? That is the trap. Narrowing later means you built your file — and possibly your classification and evidence base — against a wider scope than you actually needed, and you will pay for that.

Can I write a narrow intended purpose now and widen it later? Yes, and this is usually the right approach. Widening is a controlled change with a defined impact assessment. You certify the narrow device, generate real post-market data, and widen from a position of evidence and revenue.

Who should write the intended purpose? A collaboration between regulatory, clinical, and product. Marketing should review it. A founder should never write it alone, and it should never be copied from a competitor without understanding the classification implications.

What happens if the notified body disagrees with my intended purpose? They may request a rewording, a narrowing, or additional evidence. This is survivable if caught early. If caught late, it can trigger a full re-review of the technical documentation.

Does this apply to Class I self-certified devices? Yes. Intended purpose drives classification, and classification drives whether you are truly Class I. A vague or overbroad intended purpose can mean a device is not eligible for self-certification at all.

Sources

  1. Regulation (EU) 2017/745 on medical devices, consolidated text. Articles 2(12), 7, 61; Annex VIII, Annex XIV Part A.
  2. MDCG 2021-24 (October 2021) — Guidance on classification of medical devices.
  3. MDCG 2019-11 Rev.1 (October 2019, Rev.1 June 2025) — Guidance on qualification and classification of software.
  4. EN ISO 14971:2019+A11:2021 — Medical devices — Application of risk management to medical devices.