Which Clinical Trial Records Auditors Check for Translation Evidence
- 1 day ago
- 5 min read
An inspector opening a clinical trial file looks for five translation records, and a gap in any one of them turns a clean translation into an audit finding.
Since ICH E6(R3) took effect in the EU on 23 July 2025, the trial master file (TMF, the complete set of records a sponsor keeps to reconstruct how a trial was run) is where a Good Clinical Practice inspector goes first. E6(R3) renamed the old "essential documents" to "essential records" and put accountability for the translation process on the sponsor. A translated consent form is no longer enough on its own. The proof that it was translated correctly, reviewed, and matched to the version used at site has to be there and retrievable.
Under CTIS, the single EU portal for clinical trials since 31 January 2025, inspectors expect documentary proof, not assertions. Here are the five records auditors check for translation evidence, what each one is, and what a gap signals under ICH E6(R3).
1. ICF version history
The informed consent form (ICF) is the document a participant reads and signs before joining a trial. Its version history is the dated log of every approved revision, in the source and in each language.
An inspector checks that each translated ICF carries a version number and date tied to the approved source, and that the version a participant signed on a given day was the one current then. A translated consent form with no traceable version, or a language version lagging two revisions behind the source, tells the inspector that people may have consented on outdated information. That is a participant-safety and data-integrity finding, because consent is the legal basis for enrolling anyone.
2. Back-translation and reconciliation reports
Back-translation is an independent rendering of the target text back into the source language. The reconciliation report lists every discrepancy the comparison found and records how each was resolved.
The report has to be signed off, not assumed. It should show a formal comparison of the original and the back-translation, a documented resolution of each discrepancy, and review by a clinical or subject-matter expert. A back-translation sitting in the file with no reconciliation report is half an audit trail. It shows the check was run, not that anyone acted on it. We cover this evidence chain in detail in our guide on whether ICH E6(R3) raises the bar for ICF back-translation.
3. Linguistic-validation certificates
Linguistic validation is the structured process, following ISPOR good practice, that confirms a patient-reported outcome (PRO) instrument means the same thing to patients in every language. The certificate is the signed record that the process ran and which version it covers.
For each translated PRO or clinical-outcome instrument, an inspector wants a certificate naming the stages completed: two forward translations, reconciliation, back-translation, and cognitive debriefing with 5 to 8 patients per language. A questionnaire that collects a trial’s primary endpoint, with no validation certificate, puts the endpoint data itself in question. Cognitive debriefing is the stage teams cut under time pressure, and its absence is the gap an inspector notices first. Our walkthrough of how to validate a PRO instrument for EU trial sites sets out each stage.
4. Translator qualification records
These are the CVs, credentials, and competence records for the linguists who produced and revised each translation.
The file should show that named translators had the subject-matter and language competence for the work, held to a standard such as ISO 17100, which requires a second qualified linguist to revise every translation. If the file cannot say who translated a document or whether they were qualified, the sponsor cannot defend the accuracy of anything produced. E6(R3) makes the competence of everyone involved a documented expectation, not an assumption you can make after the fact.
5. Change-control logs
A change-control log connects a protocol or ICF amendment to the retranslated versions it triggered across every language.
Each substantial modification submitted through CTIS under CTR 536/2014 should have a traceable line to the updated translations, with dates showing the languages moved together. A protocol amendment approved centrally but reflected in only some language versions is a divergence an inspector spots by comparing dates. It signals that sites may have been running on different instructions. The same discipline applies to the certified translation of ICF and protocol documents that sit behind each submission.
How AD VERBUM builds the audit trail
Every record above is a by-product of how the translation was run, not something you can reconstruct afterward. At AD VERBUM we generate the evidence as we work. Our ISO 17100 process puts a second qualified linguist on every translation, and that revision step produces the reconciliation record an inspector expects. We hold ISO 13485, the medical-device quality standard, which ties each validated translation to its source version and change-control history, so an ICF amendment and its retranslations share one traceable line. Our ISO 27001 certified, EU-hosted infrastructure keeps participant data, which is special-category data under GDPR Article 9, inside the EEA with a documented access record. Translator credentials, version logs, and sign-offs sit in the project file from the start, so when a sponsor is asked for translation evidence during a CTIS-era inspection, the answer is a folder, not a scramble.
Our clinical trial 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 ICH E6(R3) Good Clinical Practice evidence and GDPR Article 9 handling of participant data 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 a trial master file under ICH E6(R3)?
The TMF is the set of essential records that lets a sponsor and an inspector reconstruct how a trial was conducted. ICH E6(R3), effective in the EU on 23 July 2025, renamed "essential documents" to "essential records" and expects translation evidence to be retrievable and matched to the version used at site.
Does ICH E6(R3) require back-translation?
E6(R3) does not name back-translation, but it raised the standard of proof for the translation process. Back-translation with a signed reconciliation report is the evidence inspectors accept that a translated consent form or instrument was checked and corrected.
Who is accountable if a translation record is missing?
The sponsor. ICH E6(R3) places accountability for the translation process on the sponsor, so an undocumented translation is an inspection finding against the sponsor even when a vendor did the work.
How long must translation records be archived?
Under CTR 536/2014 Article 58, the sponsor and investigator archive the trial master file for at least 25 years after the trial ends, unless other Union law requires longer. Translation evidence is part of that record.
What standard covers translator qualifications?
ISO 17100 sets competence requirements for translators and requires an independent second linguist to revise each translation. A qualification record held to ISO 17100 answers the auditor’s question about who did the work and whether they were competent.
Where does CTIS fit in?
CTIS has been the single EU portal for clinical trial applications since 31 January 2025. Substantial modifications, including protocol and ICF amendments, are submitted through CTIS under CTR 536/2014, and inspectors expect the translation change-control log to match those submissions.
