A translation can read perfectly, pass a native speaker without a second glance, and still hand you a finding in the audit – and the reason tends to surprise the people.
The assumption going in is that translated documentation gets read for language, that the auditor or someone acting for them will weigh up whether the target text is any good. In practice it rarely works that way: in most audits nobody in the room reads the target language at all, and the quality of the prose is simply not what’s under examination.
What’s being tested is whether you can show where each translation came from, that it matches the source version you approved, and that someone with the authority to do so signed it off – traceability, version match and sign-off, with the language taken as read and the record put under the microscope.
The assumption: an audit of translations is a language check
It’s an understandable expectation, because you commissioned the translations and you’re responsible for their accuracy, so it feels as though accuracy is what gets tested. An auditor, though, isn’t a linguist and the audit isn’t a proofreading exercise: their job is to confirm that your quality system produced the translated documents in a controlled, repeatable way, not to form a view on your choice of subjunctive.
That distinction matters, because a manufacturer who prepares for the wrong test walks in with the wrong evidence. Hours go into confirming linguistic quality that will never be questioned, while the parts that will be questioned – the version history, the approval trail – sit undocumented.
What’s actually examined
Three things carry most audits of translated documentation.
Traceability. Can you show the path from an approved source file to the delivered translation? An auditor wants to follow a document backwards: this German IFU came from that source revision, translated on that date, by a process you can describe. A translation that exists with no visible origin is a gap, however well it reads – which is why an audit trail really begins with controlled source documentation, long before anything is handed over for translation.
Version match. Does the translation correspond to the current approved source, or to something earlier? This is where good translations come unstuck, because sources get revised, and if that revision never flows through to every language version you’re left holding an accurate translation of a superseded document – a mismatch an auditor will read as a finding however faultless the language.
Sign-off. Who approved the translated document, and on what basis? This is the awkward one, because for a language nobody internal reads, the honest answer is often that the file shipped because it looked finished rather than because a qualified person verified it and recorded that they had. The auditor isn’t really asking whether the translation is right so much as who is accountable for saying it is, and where that accountability is written down.
Why a perfect translation of the wrong version fails
Picture a device manufacturer updating a warning in the English IFU – a genuine safety change that gets approved, reissued and signed off before the product moves on. The translated versions, commissioned months earlier against the previous revision, are linguistically flawless in every sentence, and not one of them carries the updated warning. Nothing about the target files looks wrong, and a native reviewer would pass them without hesitation, because as translations they are faultless – yet they translate the wrong source. In the audit that reads as a version-control failure rather than a language problem, exactly the kind of thing traceability exists to catch, and the quality of the translation offers no defence, because it was never the question.
Translation as a quality-system artefact, not a language task
The reframe that helps here is to stop treating a translation as a piece of language and start treating it as a controlled document like any other. A translated IFU sits inside your quality system in the same way an approved drawing or a validated procedure does. It has a source, a revision, an approver and a place in the record. When an auditor examines it, they examine it as an artefact of that system – asking the same questions they’d ask of any controlled output.
Seen that way, the language is almost the easy part. Linguistic quality is what a competent translation partner delivers as a matter of course. The part that trips manufacturers up is the surrounding record: the evidence that this specific file, in this specific language, was produced from the right source, checked by the right person, and kept in step when the source moved. That record is what an audit is for, and it’s the part most likely to be thin.
What a defensible translation record looks like
A translation record that survives scrutiny tends to share the same features whatever the market: each translated file traces back to a named source revision; any change to that source triggers a review of every language version, not just the one that prompted it; sign-off is a recorded step with an accountable owner, including – especially – for the languages no one in the building reads; and the evidence is retained and retrievable, so the path from source to delivered translation can be reconstructed on request rather than reassembled under pressure. None of that is linguistic work – it’s document control applied to translation, and it’s what separates a translation that reads well from one you can stand behind when an auditor asks how it got there.
We’ve put the practical version of this into a short Translation Audit-Readiness Checklist – the questions an auditor is likely to ask of your translated documentation, and the records that answer them. Free to download and use.
If your translated documentation needs to hold up to that kind of scrutiny, our IVDR and MDR translation services are built around traceability and controlled sign-off, not just language. To talk through a specific project, request a medical translation quote.
Frequently Asked Questions: What an Auditor Checks in Translations
What do auditors look for in translated documentation?
Primarily traceability, version match and sign-off – not linguistic quality. An auditor wants to confirm each translation came from an approved source revision, corresponds to the current version of that source, and was formally approved by an accountable person. The prose itself is rarely assessed directly.
Does an auditor read the translated language?
Usually not. Most auditors aren’t linguists and don’t read every target language, so they examine the controls around the translation rather than the text. The assumption is that a competent translation partner delivers linguistic quality; the audit tests whether the process producing and approving that translation is controlled.
How do I keep translations in sync with the source version?
Tie every translated file to a named source revision, and treat any change to the source as a trigger to review all language versions – not only the one that prompted the change. A controlled approach to translation memory and terminology management, with disciplined version numbering, makes it possible to see exactly what changed and update each language accordingly.
Who should sign off a translated document?
Someone with defined authority to do so, and the sign-off should be a recorded step rather than an assumption. For languages no one internal reads, this is where records tend to be weakest, so the accountability – whether it sits with an in-country reviewer, a validated partner, or a defined internal role – needs to be explicit and written down.
Can a translation be accurate and still fail an audit?
Yes, and it’s common. An accurate translation of a superseded source, or an accurate translation with no traceable origin or recorded sign-off, will generate a finding despite being linguistically correct. In an audit, quality of language and control of the document are separate tests.
What is translation traceability?
It’s the ability to follow a translated document backwards to its origin: which source revision it came from, when and how it was translated, and who approved it. Traceability is what lets you demonstrate, on request, that a given file in a given language was produced through a controlled process.
Does a translation need re-approving when the source changes?
If the change affects the translated content, yes. A revised source that doesn’t flow through to every language version leaves you holding translations of an out-of-date document. A controlled process reviews each affected language version when the source is revised, and records the outcome.
How long should translation records be retained?
Retention should match the requirement that applies to the underlying documentation – translated files and their approval records are part of the same technical documentation, not a separate category. The practical test is whether you could reconstruct the path from source to delivered translation for any file, at any point in its required retention period.
What's the difference between checking a translation and auditing it?
Checking a translation is a linguistic review – is the language accurate and appropriate. Auditing it is a systems review – can you prove it was produced and approved under control. A translation can pass one and fail the other, which is why linguistic quality alone is not audit evidence.
How can I prepare my translated documentation for an audit?
Focus on the record rather than the language: confirm each translation traces to an approved source revision, that version changes have flowed through to every language, and that sign-off is documented with an accountable owner. Our Translation Audit-Readiness Checklist sets out the questions to test against.