Many budget overruns and quality problems in medical device translation are traceable to the source document rather than the translation itself. Translator queries, revision cycles, terminology inconsistencies across language versions, and compliance gaps in translated documentation frequently originate upstream – in decisions made during authoring, not during translation.
These are the most common source documentation mistakes, what each one costs you, and how to avoid it.
Mistake 1: Sending an Unfinished Document to Translation
The single most disruptive thing a technical author can do to a translation project is release a source document before it is genuinely finalised. It seems an obvious point, but in practice the pressure to hit translation deadlines regularly results in documents entering the process while internal review comments are still being resolved.
When the source changes mid-project – and it will – the translation team faces a choice between patching affected segments in isolation or restarting entirely. Patching is fast but risky: a change to one section can affect safety statements, cross-references, and terminology elsewhere in the document. Restarting is reliable but expensive, and it resets the project timeline in ways that can directly affect product launch schedules.
The fix is a locked source document date agreed with your medical translation team before the project begins, with a documented process for any changes that cannot wait. A specialist translation team working with current translation memory technology can then identify exactly which segments have changed, translate only those, and run consistency checks across the full document – rather than leaving your project manager to patch manually and hope for the best.
Mistake 2: Inconsistent Terminology Across the Document
If a technical author uses three different terms for the same component or process, the translator has to decide whether the variation is intentional or accidental. In most cases it is accidental – but the translator cannot know that, and standardising on one target-language term without flagging the inconsistency risks introducing a technical inaccuracy. Reflecting the variation produces a translated document that looks inconsistent to a regulator.
For IFU translation and other patient-facing documentation, this is a compliance risk as well as a quality one. Notified bodies reviewing translated technical files are well-practised at identifying terminology inconsistencies that trace back to poorly controlled source documentation.
The solution is a product-specific glossary agreed before drafting begins – developed jointly with the translation team and used consistently throughout the authoring process. This is not a significant additional workload, but its effect on translation quality and cost is disproportionate.
There is also a direct commercial benefit. Translation Memory systems, which a specialist healthcare translation provider will build and maintain for your account, work most efficiently when source terminology is consistent. The higher the consistency, the greater the leverage rate on future projects, and the lower the per-project cost. Terminology discipline in the source document is one of the most reliable ways to reduce translation spend over time.
Mistake 3: Ignoring UK MDR and EU MDR Terminology Differences
For manufacturers working across both UK and EU markets, this is a specific and frequently overlooked problem. The two frameworks use different device nomenclature systems – GMDN for the UK, EMDN for the EU – and a glossary or translation memory built around one will not serve the other correctly.
A source document that does not distinguish between the two, or that uses terminology anchored in one framework without flagging this to the translation team, will produce translated documentation with inconsistencies that may be difficult for an internal reviewer to catch but straightforward for a regulator to flag.
The practical implication for technical authors is that dual-market documentation requires two distinct, validated terminology sets – one anchored in GMDN, one in EMDN – managed separately and clearly identified in the source document and translation brief.
Mistake 4: Not Providing a Proper Translation Brief
The handover document that accompanies a source file to the translation team is one of the most consistently underused quality tools available to technical authors, project managers and translation teams alike. Most briefs contain the source file and a deadline. A brief that actually protects translation quality contains considerably more.
The translation team needs to know the intended audience – not just the target language, but the reader’s clinical role and the context in which the document will be used. A field service engineer, a clinical specialist, and a patient receiving an implant card each require a different register, even where the source text is identical. Without this context, the translator makes reasonable assumptions – but assumptions in medical document translation carry clinical and regulatory risk.
The brief should also include approved product and brand names, any terms that must not be translated, confirmed language variants for each target market, and reference to any previous translations of related documents for terminology consistency. For most projects this takes under an hour to compile and can prevent a significant number of avoidable queries and revision cycles.
Mistake 5: Treating Your Translation Team as a Last Step
The translation projects that run most smoothly – on time, on budget, with the fewest revision cycles – are those where the translation team is involved before the source document is finalised, not at the point of handover.
At the authoring stage, structural issues, ambiguous passages, and terminology gaps are straightforward to address. After translation has begun, the same issues carry a cost in time and budget that is consistently larger. A brief review of the source document structure and terminology approach before authoring is complete costs very little. Catching a terminology problem at that stage rather than mid-project can save days of rework across multiple language versions.
For complex medical device translation projects – multi-market IFU packages, regulatory submissions across several EU member states, or documentation for devices with multiple indications – early involvement consistently reduces overall cost and timeline. The source document is not the end of the documentation process. For any product going to market in more than one language, it is the beginning of the translation one.
Frequently Asked Questions
Does source document quality affect medical translation accuracy?
Yes, directly. Ambiguous structures, inconsistent terminology, and undocumented assumptions in the source all create decision points for the translator that carry compliance risk in a regulated context.
Why do medical translation projects go over budget?
The most common causes are translator queries driven by ambiguous source content, mid-project source changes, and revision cycles caused by terminology inconsistencies. Each is largely preventable through source document discipline before translation begins.
What should a translation brief for medical documentation include?
The intended audience and their clinical role, approved product names, terms that must not be translated, confirmed language variants per market, and the approved source document version.
How does translation memory reduce costs for medical device manufacturers?
Translation Memory stores previously translated segments and applies them automatically when the same or similar content appears in future documents. Consistent source terminology maximises the leverage rate, reducing the billable word count on every subsequent project.
What happens if the source document changes during a medical translation project?
A specialist team using current translation memory technology can identify changed segments, re-translate only those, and run consistency checks across the full document – producing a documented change record for regulatory audit purposes.
Omnilingua has provided specialist medical device translation and healthcare translation services for over 25 years.