Opens in a new tab
blog

What happens when a translation goes wrong? (and how to make sure it doesn’t)

10th March 2026
Author: Team Atlas

In most industries, a mistake gets caught, corrected, and filed away as a lesson learned. In highly regulated industries (e.g., pharmaceutical, clinical trials, or healthcare), the stakes can be quite different. It’s not only embarrassing when there’s a poorly rendered term on a patient leaflet or an application inconsistency flagged by a regulatory authority. These are the types of mistakes that can be costly, time-consuming, and in some cases, potentially harmful.

We’re going to walk through three hypothetical yet entirely plausible scenarios where translation goes wrong. Then we’ll identify the specific safeguards that would have prevented each from happening.

The mislabelled dosage

A manufacturer has a new paediatric formulation translated into three European languages ahead of launch. The translator, working without a client-approved glossary, uses the term “daily dose” for the instruction. In one of the target languages, that phrase is more commonly understood as “per administration.” The packaging clears internal review and goes to print.

The error isn’t discovered until a pharmacist raises a query.

Two things were missing here:

  1. A project-specific glossary – a document that captures approved terminology so the same translation decisions are made consistently, regardless of who’s doing the work or when.
  2. A back-translation step – having the completed translation rendered back into the source language by an independent linguist. This is done specifically to catch ambiguities that look fine on the surface but carry a different meaning in context.

For any information on a physical product (especially anything dosage-related), these steps are an expected baseline.

The rejected regulatory submission

A contract research organisation (CRO) submits translated patient-facing documents to a national authority referencing a Phase III trial application. The authority flags inconsistencies in the rendering of adverse event terminology across the informed consent form and the patient diary. The submission is returned for revision, pushing the trial start date back by six weeks.

In this instance, two different translators worked on the documents, using different reference materials, with no shared translation memory.

Translation memory tools solve this problem directly. Once a term or phrase has been approved, it’s stored and applied consistently across every document in the project. It’s also stored for every future project for that client. The result is a body of work that reads as though it came from a single, well-briefed source, because in effect, it did.

This is one of the reasons that partnering with an ISO 17100 certified translation agency matters in practice, rather than just on paper. The standard requires these processes to be in place and audited, and not just a “to-do” item on a whiteboard.

The localisation blunder

Next, we see a pharmaceutical company launching a patient support campaign across four global markets. The central message reassures patients that the treatment “works quietly in the background.” In one target language, that phrase carried a connotation of secretive or undisclosed, almost the opposite of the intended reassurance. The local marketing team flags it after launch.

The translation was linguistically accurate. The problem was that it was only linguistically accurate.

Localisation goes further than translation. For patient communications and marketing materials, in-country review by a native-speaking translator with genuine cultural fluency is priceless. It’s what fills the gap between what something technically means and what it actually communicates to a reader in that market.

Language proficiency and cultural insight are related, but they’re not the same thing. It’s this kind of scenario that shows exactly where that distinction shows up.

A common thread

The three scenarios above look different on the surface, but they share a common underlying thread: no standardised reference materials, quality checkpoints, or localisation. Every project was either winging it, starting from scratch, or poorly considered, with no shared materials or managed processes in place.

The good news is that none of this requires a complicated overhaul of how you work.

Agencies certified to ISO 17100 and ISO 9001 standards have these safeguards built into every project. Glossary management, translation memory, qualified review processes, and documented quality checks are the norm at each stage of a translation project. When you work with a certified partner like Atlas Translations, you don’t have to hope that those systems exist, because they’ve been in place for years.

If you’d like to talk through how your current translation workflows measure up, or you’re bringing on a new project and want to get the setup right from the start, we’re keen as biscuits to have that conversation with you.

Want to work with a translation agency who makes sure things go right?

Get in touch and we'll start the process.

Call us on 01727 812 725

Tell us some details and get a quote

Use the chatbox to start a conversation. It’s a real-life human, no bots here! (During UK business hours – we do need to sleep.)

See more options on our contact page.

Further reading

3rd March 2026

What the ISO 17100 and ISO 9001 certifications actually mean for your translation projects

Read post
4th November 2025

Why sector-specific experience makes all the difference in the translation industry

Read post
30th September 2025

Why machine translation post-editing can make or break your pharmaceutical document quality

Read post
All blog posts