CE·8 min read·By Angel Translation Corp.·Updated Oct 2026

EU MDR and IVDR Translation: Language-Scope Checklist

Scope EU medical-device language work by country, intended user and document type: labels, IFUs, declarations, technical documentation and revision control.

View references (3) ↓
Key points
  • Language is set per member state
  • Define the document scope before counting languages
  • When the language set gets fixed decides how hard the rest will be
  • Revisions are the real test
Who this is forRegulatory and market access teams planning EU launches across multiple member states.

Language is set per member state

For information accompanying a device, MDR Article 10(11) and IVDR Article 10(10) refer to official Union languages determined by the relevant Member State. The required set depends on the market, document and intended user, including professional-use provisions where applicable.

Use the Commission’s country tables as a starting point, then verify the current national position. Notified-body documentation languages and customer-facing labels or IFUs are separate questions; not every device requires a notified-body assessment.

Define the document scope before counting languages

Record the requirement and approval owner for each category. Technical-documentation language is not automatically the same as the IFU language set.

Language scopeConfirm the rule for each document and market; translation is not CE marking or conformity assessment.
DocumentWhat to verify
Labels and IFUMember State provisions, intended user and applicable exceptions.
Declaration of conformityLanguages required where the device is made available.
Technical documentationAuthority or assessment-route requirements and, where applicable, languages accepted by the notified body.
GUI and revision noticesApplicable national rules and consistency with the controlled document set.

When the language set gets fixed decides how hard the rest will be

Teams frequently finalise the English source, then discover the required language count late and compress translation into the last weeks before launch. That is where quality and consistency problems concentrate — not because the translators are weak, but because the same terminology question is being decided independently, in a dozen languages, at the same time.

So if you want to know whether a manufacturer has its language work under control, you learn more from when the market list was fixed than from a translation sample. The later that list lands, the more every downstream revision costs — and those costs rarely appear in the translation budget.

Revisions are the real test

Devices change, and labelling changes with them. The common failure is not a mistranslation — it is updating some language versions and not others, leaving markets holding different revisions of the same document with no one able to say what differs.

Version-control gaps can emerge at initial review or later revisions; check them throughout the document lifecycle. The test of whether a language asset is genuinely maintainable is simple: when one source passage changes, can you say which languages and which paragraphs it affects? If not, every revision is being done from scratch.

The maintainability testVersion-control gaps can emerge at initial review or later revisions; check them throughout the document lifecycle.
AskIf you can answer itIf you cannot
When one source passage changes, which languages does it affect?The change is scoped, and only the affected versions are reopened.Every revision is being done from scratch.
Which paragraphs in those languages does it affect?Reviewers check a delta instead of re-reading a document.Some language versions get updated and others do not.
Which revision is each market currently holding?You can state, per market, what is in force.Markets hold different revisions of the same document and no one can say what differs.

The common failure here is not a mistranslation. Under MDR 2017/745 and IVDR 2017/746 the language set is fixed per member state, so the later that market list lands, the more every downstream revision costs — and those costs rarely appear in the translation budget. Confirm the current requirement per market with your notified body.

Questions

How many languages will we actually need?
Build a document-by-country matrix from your actual market plan. Verify current national provisions and intended-user conditions; there is no universal EU language count for every device.
Does the technical file need translating too?
Check the applicable authority and conformity-assessment route separately from labels and IFUs. Where a notified body is involved, confirm accepted languages with it. Do not assume every technical file needs every sales-market language.
Can you handle all required languages?
Send the markets, languages, intended users and document set. We confirm qualified resources, review scope and schedule for the actual project rather than treating general language coverage as a guarantee of every regulatory need.

Sources

Related reading

FDAFDA 510(k) Translation: English Documents and eSTAR ChecksIFUIFU Instructions for Use: Why Mistranslation Creates Product Liability ExposureOperationsSimultaneous Multi-Language Release: How to Ship 20 Languages at Once

Have a project that touches this?

Tell us what you are shipping and where. We will tell you which service level it needs — including when it does not need our most expensive one.