The intended purpose statement in your technical file is the single sentence every other section of the file depends on. MDR Annex II Section 1 requires it as the opening item of the device description, and MDR Article 2(12) defines exactly what it is. Write it as one stable paragraph that names the medical condition, the patient population, the intended user, the environment of use, the mode of action, and the contraindications. Then propagate that same paragraph, unchanged, to the label, the instructions for use, the promotional materials, and the clinical evaluation. If the four sources Article 2(12) recognises tell the same story, your classification and clinical evaluation hold. If they drift apart, your file does not survive a first audit.

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

TL;DR

  • The intended purpose belongs in Section 1 of Annex II of Regulation (EU) 2017/745 — the device description and specification. It is the first substantive content in the technical file and every downstream section refers back to it.
  • MDR Article 2(12) defines intended purpose as "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."
  • A well-written intended purpose paragraph is stable, narrow enough to match the clinical evidence you can actually produce, and specific enough that classification under Article 51 and Annex VIII is unambiguous.
  • The same paragraph must appear, verbatim or in clearly controlled variations, in all four Article 2(12) sources. A drift between them is a nonconformity waiting to be found.
  • Classification, the clinical evaluation scope under Article 61 and Annex XIV, the GSPR checklist, the risk file, the labelling, and the PMS plan all inherit their scope from this single paragraph. Get it right once and every later deliverable gets easier.

Why the intended purpose lives at the front of the technical file

Annex II of Regulation (EU) 2017/745 lays out the technical documentation contents in a deliberate order, and the first item is the device description and specification. Within that description, the intended purpose is the opening piece. This placement is not cosmetic. The structure of Annex II mirrors the logic of how a Notified Body reviews a file: first they read what the device is and what it is for, then they check whether everything that follows is consistent with that opening claim.

When the intended purpose is vague, contradictory, or missing a critical element, every reviewer who opens the file afterwards reads the rest of it through a haze. The classification rationale has to be second-guessed. The GSPR checklist cannot be judged for completeness because the obligations depend on what the device is for. The clinical evaluation cannot be scoped. The benefit-risk analysis has no denominator. A weak intended purpose statement silently weakens the entire file, and the weakness does not show up as a single finding — it shows up as a pattern of small findings scattered across every section, all of which trace back to the same root cause.

The discipline to write the intended purpose once, properly, at the front of the file, is the cheapest quality investment you will make in the whole project. It is also the one startups defer most often because it feels abstract compared to hardware tests and software verification. The deferral is the mistake.

What the intended purpose is, legally

The MDR does not leave the term open to interpretation. Article 2, point (12), defines it in one sentence:

"'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." — Regulation (EU) 2017/745, Article 2, point (12).

Three things follow from this definition that matter for the technical file.

First, the manufacturer is the sole source. Not the user, not the clinician, not the investor audience. The regulation regulates what you, the manufacturer, have written down. The technical file is where your written-down version becomes authoritative.

Second, the definition names four specific sources — the label, the instructions for use, promotional or sales materials or statements, and the clinical evaluation. This list is exhaustive for the legal definition. Article 2(12) does not recognise a fifth source. Whatever you put into those four places is what the regulation treats as your intended purpose, and anything inconsistent between them is a problem.

Third, the technical file has to make the intended purpose visible and traceable. You cannot store it only in the marketing team's slide deck and expect the file to survive an audit. The technical file must contain the authoritative text of the intended purpose as specified under Annex II Section 1, and every other source must align with that text.

The four Article 2(12) sources and how they relate to the file

The four sources named in Article 2(12) are not four copies of the same sentence. Each one has its own function. The technical file has to control all four.

The label. Printed on the device and on the packaging. Short by physical constraint. Every word carries weight because there is no room for nuance. The label is also where symbol-based statements (per EN ISO 15223-1) and the minimum information for identification live. In the technical file, the labels appear in full in Annex II Section 2 (information to be supplied by the manufacturer), but the intended purpose on the label has to match the paragraph in Section 1.

The instructions for use. The long form. This is where the intended purpose is expressed with its full clinical context — the medical condition addressed, the patient population, the intended user, the environment, the principle of operation, the contraindications, the warnings, and the training or qualification required of the user. The IFU version of the intended purpose is usually the most complete natural-language statement in the entire file. In Annex II terms, the IFU also lives in Section 2, and its intended purpose paragraph must be the canonical one.

Promotional or sales materials or statements. The website, the brochures, the investor deck, the pitch video, the LinkedIn posts, the conference booth, the email campaigns, the app store description. Article 2(12) gives this source the same legal weight as the IFU and the label. A medical claim on your homepage is part of your intended purpose even if the IFU is silent. The technical file has to include or reference the controlled marketing claims list, and that list has to be checked against the Annex II Section 1 paragraph on a fixed cadence.

The clinical evaluation. Under Article 61 and Annex XIV, the clinical evaluation must demonstrate conformity of the device with the applicable GSPRs under the conditions of its intended purpose. That means the clinical evaluation report states the intended purpose at the top and evaluates the device against that statement. If the clinical evaluation assesses a broader or different use than the one in Section 1 of the technical file, the two deliverables contradict each other and the auditor will see it within minutes.

The practical rule is simple. Pick the Annex II Section 1 paragraph as your canonical source. Then mirror it — with format adjustments appropriate to the medium, but not with meaning changes — into the other three sources. When the device changes, you change the paragraph in one place and propagate the change through your document control system to the other three.

How to write a stable intended purpose paragraph

A stable intended purpose paragraph is one that does not need rewriting every time a new marketing slide is produced or a new clinical study enters the evaluation. It is narrow enough to be honest, specific enough to be auditable, and structured enough to force the classification question to have a clear answer.

Write it as a single paragraph of three to six sentences. Longer than that and the team will paraphrase it rather than quote it, which defeats the purpose. Shorter and you will be missing an element the regulation expects.

The paragraph should contain the following elements, in roughly this order:

What the device is. One clause naming the device and its general category ("a software application," "a single-use sterile surgical instrument," "a wearable monitoring device"). This grounds the reader.

The medical condition, disease, injury, or physiological state being addressed. Use the specific clinical condition, not a vague area. "Chronic heart failure NYHA class II to III" is auditable. "Cardiac problems" is not. If the device addresses no specific condition — for example, a general-purpose monitoring device — state that the device supports monitoring of a named physiological parameter in a named context.

The intended medical function. One of the verbs from Article 2(1) — diagnosis, prevention, monitoring, prediction, prognosis, treatment, or alleviation — applied to the named condition. Or, if the device is non-medical, deliberate absence of these verbs. This is the sentence that decides whether you have a medical device at all.

The intended patient population. Age range, clinical status, inclusion and exclusion criteria at the level at which the clinical evaluation will be scoped. "Adults 18 years and older undergoing elective orthopaedic surgery" is a scope. "Patients" is not.

The intended user. Healthcare professional, trained lay user, patient as self-user. Each of these has usability engineering and labelling consequences under EN 62366-1, and the technical file has to match.

The intended environment of use. Hospital operating theatre, clinician's office, home use, mobile use. Environment drives electrical safety categories, ingress protection requirements, and usability assumptions.

The principle of operation — briefly. How the device achieves its effect. One sentence. The full mode of action lives in Section 3 of Annex II (design and manufacturing), but the high-level principle belongs in the intended purpose because classification rules sometimes key off it.

Key contraindications and exclusions. What the device is explicitly not for. This is where the scope is defended at the edges. A contraindication in the intended purpose paragraph removes a population from your clinical evidence burden and from your risk analysis.

Write the paragraph. Read it out loud. Ask: if a Notified Body reviewer read only this paragraph and then had to pick the applicable classification rule from Annex VIII, would they pick the rule you expect? If yes, you have a stable intended purpose. If no, the paragraph is either missing information or hiding ambiguity, and you keep working.

How the intended purpose paragraph anchors classification and clinical evaluation

Classification and clinical evaluation are the two largest regulatory deliverables that inherit their entire scope from this paragraph.

Classification under Article 51 and Annex VIII. Article 51 requires every device to be classified according to the rules in Annex VIII, and those rules read the intended purpose literally. The classification rationale in Section 1 of your Annex II file identifies the applicable rule and shows, in plain language, why that rule applies to the intended purpose as you have written it. If the rationale has to paraphrase the intended purpose to make the classification argument work, the intended purpose was not specific enough. Rewrite the paragraph, not the rationale. The rationale should read as a direct mechanical application of the rule to the paragraph.

A narrow intended purpose often lands the device in a lower class. A broad one inflates the class. Both can be the right answer — the test is whether the paragraph honestly reflects what you want to claim and sell. The Subtract to Ship Purpose Pass (see post 065) is the discipline for finding the narrowest honest paragraph before classification work begins.

Clinical evaluation under Article 61 and Annex XIV. Article 61 requires manufacturers to plan, conduct, and document a clinical evaluation for their device, and Annex XIV Part A sets out the methodology. The clinical evaluation report must demonstrate that the device performs as intended and that the clinical benefits outweigh the risks, for the intended purpose, in the intended patient population, used by the intended user, in the intended environment.

Every one of those elements comes from the intended purpose paragraph. Broaden the patient population in the paragraph and you broaden the clinical evidence burden. Add a new medical function verb and you add a new evidence stream. Extend the environment of use from clinic to home and you add usability data in the new environment. The clinical evaluation cost is a direct function of the intended purpose text.

Everything else downstream. The GSPR checklist checks applicability based on intended purpose. The risk management file (under EN ISO 14971) scopes foreseeable misuse around the intended user and environment. The PMS plan under Annex III specifies data collection for the intended purpose in the field. The labelling in Section 2 repeats the intended purpose. The benefit-risk analysis weighs benefits and residual risks against the intended purpose, not against some abstract general-case device. A single paragraph, written once, determines the shape of everything that follows.

What to avoid when documenting intended purpose

Across startup technical files, the same mistakes keep showing up in the intended purpose paragraph.

  • Marketing adjectives masquerading as clinical content. "Innovative," "next-generation," "best-in-class," "revolutionary" — none of these say anything auditable. Strip them out. The paragraph is a regulatory artefact, not a pitch.
  • Undefined populations. "Patients with cardiovascular disease" is a nation. "Adults diagnosed with atrial fibrillation and a CHA2DS2-VASc score of 2 or greater" is a population the clinical evaluation can actually address.
  • Implicit expansion via marketing. The paragraph says one thing, the website says another. Article 2(12) reads both. Lock the marketing claims list to the paragraph.
  • Mixed verbs. Using "diagnose" and "monitor" and "assist in the management of" all in the same paragraph without specifying which applies when. Each verb changes the classification rule and the evidence burden. Pick the ones you can defend and remove the rest.
  • Copy-paste from competitor IFUs. A competitor has a different clinical evaluation, a different risk file, and possibly a different class. Their intended purpose is not a template for yours.
  • Hidden off-label framing. Writing a narrow IFU and then selling the device broadly through sales reps. Sales statements are one of the four Article 2(12) sources. The off-label framing is visible in the file the moment an auditor looks at the marketing materials.
  • Version drift. The paragraph is updated in the IFU but not in the clinical evaluation report, or vice versa. Document control must treat the intended purpose as a high-importance controlled item propagated across all four sources simultaneously.
  • Absence of contraindications. A paragraph that lists only what the device is for, with no statement of what it is not for, leaves the outer boundary of the scope undefined. Auditors and users will both fill the gap, usually in directions the manufacturer did not intend.

The Subtract to Ship angle

Subtract to Ship for the intended purpose paragraph is a single discipline: narrow honestly, then freeze. Narrow, because every extra word in the paragraph costs you downstream work across classification, clinical evaluation, labelling, and PMS. Honestly, because Article 7 of Regulation (EU) 2017/745 prohibits misleading claims and because the narrowing only holds up under audit if it reflects what you actually want to sell. Freeze, because a paragraph that keeps moving is a paragraph that has not been decided, and every section of the file that inherits from it will inherit the indecision.

The Purpose Pass in post 065 sits here. Before you write any other section of the technical file, you run the Purpose Pass on a draft intended purpose paragraph. You check it against Article 2(1) to confirm whether the device is a medical device at all. You check it against Annex VIII to confirm the expected classification. You check it against the clinical evidence you can realistically produce under Article 61. You check it against the marketing story the business actually needs to tell. When the four checks agree, you write the paragraph into Section 1 of the technical file and you treat it as the most controlled sentence in the whole project.

A startup that runs this discipline before the technical file exists writes a tighter file, commissions a smaller clinical evaluation, and carries a lighter PMS burden. A startup that skips it pays for the skip every month until certification.

Reality Check — Where do you stand?

  1. Is there a single authoritative intended purpose paragraph in Section 1 of your technical file today, and can you read it aloud in under thirty seconds?
  2. Does that paragraph contain all of: device category, medical condition, medical function verb (or deliberate absence), patient population, intended user, intended environment, principle of operation, and contraindications?
  3. Does the exact same paragraph (or a document-controlled variant of it) appear in the IFU, on the label, in the website product page, and in the clinical evaluation report?
  4. If a Notified Body reviewer read only your intended purpose paragraph, would they identify the same Annex VIII classification rule you cite in your rationale?
  5. Is the clinical evidence plan scoped to the exact population, environment, and medical function named in the paragraph — no broader, no narrower?
  6. Is the paragraph under document control with a version number, an owner, and a cadence for reviewing consistency across the four Article 2(12) sources?
  7. Have you ever deliberately removed a clinical function verb from the paragraph because the clinical evidence to support it was not worth the work?

Frequently Asked Questions

Where in the technical file does the intended purpose statement belong? In Section 1 of Annex II of Regulation (EU) 2017/745 — the device description and specification. Annex II lists the intended purpose as part of the opening description, which is why it appears at the very front of the technical file. Every section that follows refers back to it.

How long should the intended purpose paragraph be? Three to six sentences. Long enough to cover device category, medical condition, medical function, patient population, intended user, environment of use, principle of operation, and contraindications. Short enough that the team can quote it from memory and that it can be mirrored verbatim into the IFU, label, and clinical evaluation.

Does the intended purpose in the clinical evaluation have to match the one in the technical file? Yes. Article 2(12) explicitly names the clinical evaluation as one of the four sources of intended purpose, and Article 61 requires the clinical evaluation to demonstrate conformity under the conditions of the intended purpose. Any drift between the two will produce a finding at audit.

Can marketing materials override what the IFU says about intended purpose? Neither overrides the other — they are both primary sources. Article 2(12) names the label, the IFU, promotional and sales materials or statements, and the clinical evaluation as the four sources, and treats them with equal legal weight. A claim on the website that the IFU does not support is still part of your intended purpose and still creates regulatory obligations.

What happens if we later want to expand the intended purpose? A substantive change to the intended purpose is a significant change that typically triggers a change notification to the Notified Body, an update to the classification rationale, an update to the clinical evaluation, and updates to labelling and PMS. This is why the initial paragraph is worth writing carefully — expansion is expensive, narrowing is cheap.

Does every variant of the device need its own intended purpose paragraph? If the variants differ in the medical function, patient population, intended user, or environment, yes. If they differ only in cosmetic or non-clinical features, one paragraph with a note on the covered variants is usually enough. Annex II Section 1 asks for the variants and accessories covered by the file, so the variant scope is part of the same section as the intended purpose.

Sources

  1. Regulation (EU) 2017/745 of the European Parliament and of the Council of 5 April 2017 on medical devices, Article 2(1) (definition of medical device), Article 2(12) (definition of intended purpose), Article 51 (classification), Article 61 (clinical evaluation), Annex II (technical documentation — Section 1: Device description and specification), Annex XIV (clinical evaluation and post-market clinical follow-up). Official Journal L 117, 5.5.2017.

This post is part of the Technical Documentation & Labeling series in the Subtract to Ship: MDR blog. Authored by Felix Lenhard and Tibor Zechmeister. The intended purpose paragraph is the single sentence that decides the shape of your entire regulatory project. Spend the afternoon it deserves before you write anything else in the file.