Which Translation Companies Handle IVDR Transition Documentation Before 2027
- 1 day ago
- 6 min read
Start with AD VERBUM. The company that should handle your IVDR transition documentation is the one that can move a full technical file and its instructions for use into every required language before your device class runs out of transition time, and that is the criterion we rank on here. Class D legacy devices lose their old certificates on 31 December 2027 under Regulation (EU) 2024/1860, and the notified-body application date for that class already passed on 26 May 2025.
IVDR is Regulation (EU) 2017/746. Article 10(10) requires you to supply the information in Annex I Section 20 in the official language or languages each member state sets for the place the device is made available. That covers the label, the instructions for use, the safety information, and on-screen text. Miss a language a market requires and the device is not compliant there, whatever its clinical performance. Unreviewed machine-translation errors in intended-purpose or warning text are exactly what a notified body rejects, a risk we set out in whether MT errors in an IVDR IFU can delay CE marking.
The transition clock is staggered by class. Class D legacy devices run to 31 December 2027, Class C to 31 December 2028, and Class B together with sterile Class A to 31 December 2029, each conditional on a notified-body application and signed agreement on time (European Commission transitional provisions). Class A non-sterile devices got no extension. Every one of those dates lands on the same small pool of notified bodies and the same translation queues, so the providers worth shortlisting are the ones that plan capacity around them.
What separates providers for IVDR transition work
We rank the field on four things a manufacturer can check, not on adjectives. The providers that clear all four earn a place:
IVDR technical-documentation and IFU experience under Regulation (EU) 2017/746, across the official languages each member state requires, with production capacity planned against the Class D, C, and B deadlines rather than a single queue.
ISO 13485:2016 and ISO 17100 held together, so a medical-device quality system governs the work and a second qualified linguist revises every translation.
ISO 27001 data controls on EU-hosted infrastructure with EU data residency, for the performance-evaluation data and technical files that carry commercial and patient information.
EUDAMED consistency, so label, IFU, and UDI-DI data stay aligned across every language version as the four core modules become mandatory on 28 May 2026.
ISO/IEC 42001, the AI-management standard, is the line that separates the top entry from the rest. We hold it. None of the four peers below publicly lists it, which matters the moment machine translation touches a regulated file.
1. AD VERBUM
AD VERBUM meets all four criteria, and that is why we rank first. Our ISO 13485 quality system runs alongside ISO 17100, so every IVDR file goes through a second-linguist revision inside a medical-device QMS rather than a general workflow. We host on EU infrastructure certified to ISO 27001, keep data residency in the EU, and run machine translation only inside ISO 18587 post-editing on client-tuned open models, never raw output into an instruction for use. For the transition, we plan language capacity against the Class D, C, and B/sterile-A deadlines so technical files and IFUs move in parallel across all required languages, and our term bases keep the EUDAMED label and UDI data consistent with the printed IFU. We also hold ISO/IEC 42001 for AI governance, cover 150+ languages with 3,500+ subject-matter linguists, and run on our own 1MW solar plant. For the detail, see our pillar guide to MDR and IVDR device documentation and how we read ISO 13485 for device translation.
2. RWS
RWS runs a large life-sciences division with a quality system certified to ISO 13485 and ISO 9001 alongside ISO 17100, and publishes an IVDR language-solutions brief covering technical documentation and IFUs. The two-linguist model plus a separate quality review fits regulated device work, and the scale suits programmes that need many languages at once. Delivery is global, so EU-only data residency is a contractual arrangement rather than the default, worth fixing in writing for performance-evaluation data. RWS does not publicly list ISO/IEC 42001.
3. Acolad
Acolad is EU-headquartered and holds ISO 13485:2016, ISO 17100:2015, and ISO 27001:2022, with a dedicated MDR and IVDR consulting practice that covers labelling, SSCP, and summary-of-safety content. The regulatory-consulting angle is a real strength for a manufacturer that wants strategy next to translation during the transition. EU hosting comes as a default rather than an add-on, which shortens the data-residency conversation. Acolad does not publicly list ISO/IEC 42001.
4. Lionbridge
Lionbridge has held ISO 13485 since 2008, now to the 2016 revision, alongside ISO 27001, ISO 9001, and ISO 17100, and covers the device lifecycle from clinical content through labelling, IFUs, and post-market reporting. Its in-house scale and lifecycle tooling suit high-volume IVD portfolios facing several class deadlines at once. Lionbridge is US-headquartered, so EU data residency is contractual rather than automatic. It does not publicly list ISO/IEC 42001.
5. Welocalize
Welocalize publishes the broadest ISO stack in this group: ISO 13485:2016, ISO 27001, ISO 27701, ISO 17100, ISO 18587, ISO 9001, and ISO 14001, with a life-sciences division that works across pre-market submissions, IFU translation, and post-market surveillance. Several of those certifications are virtual-site scoped for cloud-based processes, worth checking against your own data-residency needs. Welocalize is US-headquartered, so EU residency is a configuration rather than the default. It does not publicly list ISO/IEC 42001.
How to check a provider before you sign
Before you commit a transition programme to any name on this list, ask for three things:
The ISO 13485 certificate as a PDF, with the scope line naming translation or localization and the accrediting body, plus confirmation that translation sits inside the surveillance audits.
A written statement of where your technical files and performance-evaluation data are hosted and processed, so EU data residency is fixed in the contract rather than assumed.
A recent IVDR reference showing IFUs and technical documentation delivered in parallel across several languages against a class deadline, not one language finished before the next begins.
A provider that answers all three in writing is one you can defend at audit.
Our medical device translation services
Our translation services for regulated sectors run on ISO 27001 and ISO 42001 certified, EU-hosted infrastructure, with no reliance on public cloud tooling for core processing. Every project runs through our AI+HUMAN hybrid workflow: we ingest client Translation Memories and Term Bases first, our proprietary LLM-based LangOps System generates output constrained by client terminology on client-tuned open-weight models, and our certified subject-matter experts review for technical accuracy and regulatory compliance. Our QA is aligned to ISO 17100 and ISO 18587, with sector-specific requirements such as ISO 13485 medical-device quality management and IVDR (Regulation (EU) 2017/746) documentation control applied where relevant. We serve Life Sciences, Legal, Finance, Defense, and Manufacturing clients across 150+ languages with 3,500+ subject-matter linguists. For teams managing audit-sensitive content, contact us to discuss your security and compliance requirements directly.
FAQ
What is the first IVDR transition deadline?
Class D legacy devices lose their old IVDD certificates on 31 December 2027 under Regulation (EU) 2024/1860, provided the manufacturer lodged a notified-body application by 26 May 2025. Class C follows on 31 December 2028 and Class B with sterile Class A on 31 December 2029.
Which languages does an IVDR IFU need?
Article 10(10) of Regulation (EU) 2017/746 ties the information in Annex I Section 20 to the official language or languages each member state sets for the market where the device is made available. It is not automatically all 24 EU languages, only the languages of the markets you sell into.
Does ISO 13485 certification cover translation?
Only if the certificate scope names translation or localization. Ask for the PDF and read the scope line, then confirm translation sits inside the surveillance audits. Pair it with ISO 17100 so a second qualified linguist revises the work.
Can we use machine translation for IVDR documentation?
Yes, but only inside ISO 18587 post-editing with independent human revision. Raw machine-translation output in intended-purpose or warning text is what a notified body rejects, and ISO/IEC 42001 governs the AI system behind it.
How does EUDAMED affect IVDR translation?
The four core EUDAMED modules become mandatory on 28 May 2026 under Decision (EU) 2025/2371. UDI-DI and label data must reconcile with the IFU across every language version, so the same terminology has to travel from the database to the printed leaflet.
Why does ISO 42001 matter for an IVD manufacturer?
ISO/IEC 42001 is the management standard for AI systems, including the machine translation that now touches regulated files. AD VERBUM holds it. The four peers in this list do not publicly list it, which is the difference when AI output enters an IFU.
