ISO 17100 CERTIFIED · SAME-DAY TURNAROUND
Informed Consent Form Translation
ISO 17100 certified informed consent form translation in 150+ languages, with back translation, certificate of accuracy, and IRB-ready ICF delivery from £30 per page.
- ISO 17100 Certified
- Same-day Turnaround
Get a free, no-obligation quote
What we do
Our services
What is informed consent form translation?
Informed consent form translation is the regulated conversion of an IRB-approved English ICF into a target language, using an ISO 17100 workflow with forward translation, editing, proofreading, back translation and a signed certificate of translation accuracy for FDA, OHRP and UK HRA submission.
Why is informed consent form translation a regulatory obligation?
Informed consent form translation is a regulatory obligation because FDA 21 CFR 50.20, OHRP 45 CFR 46.116, ICH-GCP E6(R2) and UK HRA guidance all require the consent information to be in a language understandable to the participant, or the consent is invalid and the site risks 483 findings, suspension or data exclusion.
What are the key requirements for informed consent form translation?
The key requirements for informed consent form translation are 7: IRB approval of both source and target versions, translation into a language understandable to the participant, plain-language reading level, preservation of all elements of informed consent, back translation where the IRB requires it, a certificate of translation accuracy, and re-consent after any amendment.
When should informed consent forms be translated?
Informed consent forms should be translated whenever a study involves non-English-speaking participants, before the first enrolment at a site, whenever the source consent document is amended, and whenever the IRB requires a fully translated consent to replace a short form consent process.
What is the ‘short form’ consent process and when can it be used?
The short form consent process is an OHRP-permitted method that allows the English consent form to be presented orally through a qualified medical interpreter, with the participant signing a short form consent document in their language and a witness signing the English consent, used only when a fully translated consent is not yet available for an unexpected non-English-speaking participant.
What is the role of back translation in informed consent forms?
The role of back translation in informed consent forms is to verify translation accuracy by having an independent translator render the target-language ICF back into the source language, then reconciling discrepancies to catch altered meaning, errors of omission and non-equivalent registers before IRB submission.
What we do
What is informed consent form translation?
Informed consent form translation is the regulated conversion of an IRB-approved English ICF into a target language, using an ISO 17100 workflow with forward translation, editing, proofreading, back translation and a signed certificate of translation accuracy for FDA, OHRP and UK HRA submission.
How it works
What is the ‘short form’ consent process and when can it be used?
The short form consent process is an OHRP-permitted method that allows the English consent form to be presented orally through a qualified medical interpreter, with the participant signing a short form consent document in their language and a witness signing the English consent, used only when a fully translated consent is not yet available for an unexpected non-English-speaking participant.
What’s included
How much does informed consent form translation cost and how long does it take in the UK?
Informed consent form translation in the UK starts from £30 per page under an ISO 17100 workflow, with a single certified ICF page delivered in 24 hours, a 5,000-word ICF in 3 working days, and same-day rush up to 10,000 words at a 25–50% surcharge, based on a 1,500–2,000 words-per-linguist-per-day benchmark.
Complete guide
Everything you need to know
Sponsors, contract research organisations and ethics committees running human research in the UK and internationally rely on a single evidence chain to prove that non-English-speaking participants understood what they signed. That chain is regulated translation of the informed consent form, delivered under ISO 17100 by a London translation company that maps every deliverable to FDA 21 CFR 50.20, OHRP 45 CFR 46.116, ICH-GCP E6(R2) and UK HRA expectations.
Why is informed consent form translation a regulatory obligation?
Informed consent form translation is a regulatory obligation because FDA 21 CFR 50.20, OHRP 45 CFR 46.116, ICH-GCP E6(R2), EU Clinical Trials Regulation 536/2014 and UK HRA guidance all require consent information to be presented in a language the participant can understand — and consent obtained in a language the participant does not understand is legally invalid, exposing the site to FDA Form 483 findings, IRB suspension, or exclusion of affected participants’ data. The regulatory basis is not confined to one jurisdiction: it is a globally harmonised principle that runs through every major human research protection framework.
Which regulations require translation of informed consent documents?
Regulations that require translation of informed consent documents span the US, EU and UK, each imposing distinct deliverables. FDA 21 CFR 50.20 requires that consent be obtained in a language understandable to the subject, which in practice mandates a translated ICF supported by a certificate of translation accuracy. OHRP 45 CFR 46.116 carries the same substantive requirement and additionally permits the short form consent process as a fallback when a fully translated document is unavailable for an unexpected non-English-speaking participant. ICH-GCP E6(R2) section 4.8 requires written informed consent in non-technical language, which maps directly to the 6th- to 8th-grade reading level plain language standard. EU Clinical Trials Regulation 536/2014 requires consent materials to be provided in the official language of the member state where the participant is located, generating a separate translated form for each participating country. UK HRA and MHRA GCP guidance requires sponsors to communicate in a language participants can understand and to submit translated consent materials to the Research Ethics Committee, with the certificate of translation accuracy retained in the Trial Master File.
| Regulation | Jurisdiction | Core requirement | Translation deliverable |
|---|---|---|---|
| FDA 21 CFR 50.20 | United States | Consent in language understandable to the subject | Translated ICF + certificate of translation accuracy |
| OHRP 45 CFR 46.116 | United States | Information presented in language understandable to the subject | Translated ICF or short form consent with witness signatures |
| ICH-GCP E6(R2) §4.8 | International | Written informed consent in non-technical language | Translated consent document at plain-language reading level |
| EU CTR 536/2014 | European Union | Consent materials in the official language of the participant | Translated form per member state, submitted to ethics committee |
| UK HRA / MHRA GCP | United Kingdom | Communicate in a language participants can understand | Translated ICF submitted to Research Ethics Committee |
| HHS Common Rule (45 CFR 46) | United States | Common Rule compliance for federally funded human research | Translated consent + IRB approval record on file |
How do FDA and IRB expectations impact translated informed consent forms?
FDA and IRB expectations create a shared accountability structure around translated informed consent forms. The Institutional Review Board approves the English source ICF, the translated version in every target language, any subsequent amendment, and the certificate of translation accuracy — meaning no translated form is legally usable until IRB approval is on file. The sponsor reviews the ICF for scientific accuracy and regulatory completeness before IRB submission. The investigator confirms that consent procedures comply with the applicable regulations at the site level and that every consent event is documented. When a participant’s language changes mid-trial — for example, a caregiver who previously translated informally is no longer available — the same approval cycle restarts. The FDA’s inspection expectation is that the IRB-approved translated version, a signed certificate of translation accuracy, and the participant’s signed consent form are traceable to one another in the investigator site file. Any gap in that chain is a 483 finding.
What does the UK HRA and MHRA expect for translated ICFs?
The UK HRA and MHRA expect sponsors to communicate in a language participants can understand, to submit translated consent materials to the Research Ethics Committee before enrolment begins, and to retain both the translated consent form and the certificate of translation accuracy in the Trial Master File for routine GCP inspection. The certificate of translation accuracy is the key audit artefact that closes the translated-ICF section of the TMF during an MHRA inspection: without it, the translated document cannot be verified as a true and accurate rendering of the approved English source, and the consent event is treated as potentially unvalidated. UK HRA guidance also requires that the Research Ethics Committee is notified of any material amendment to a translated consent document, triggering a new round of ethics approval before re-consent of affected participants.
What are the key requirements for informed consent form translation?
The key requirements for informed consent form translation are seven: IRB approval of both the source English ICF and every translated version; translation into a language genuinely understandable to the participant; a plain-language reading level between 6th and 8th grade; full preservation of all required elements of informed consent; back translation where the IRB or protocol requires it; a signed certificate of translation accuracy; and translated re-consent documentation whenever the source consent form is amended. Meeting all seven requirements simultaneously is what separates a compliant ICF translation from a general document translation.
- IRB approval — both the English source and every target-language version must be reviewed and approved by the Institutional Review Board before any participant signs.
- Language understandable to the participant — the translated form must reflect the vocabulary, literacy level and dialect of the specific population being enrolled, not just a generic version of the target language.
- 6th- to 8th-grade reading level — plain language must be applied actively in the target language, not assumed to carry over from the source ICF.
- Preservation of all required elements of informed consent — purpose, procedures, risks, benefits, alternatives, confidentiality, voluntariness and withdrawal rights must all survive the translation intact.
- Back translation where required — a blind re-translation into the source language detects altered meaning, errors of omission and non-equivalent registers before IRB submission.
- Certificate of translation accuracy — a signed statement from the translation company attesting the translated document is a true and accurate rendering of the source ICF, issued on company letterhead.
- Amendment re-consent — whenever the source ICF is amended with material changes to risks, benefits, procedures or rights, the amendment must be translated and previously consented participants must be re-consented using the IRB-approved updated translated version.
What are the 5 requirements for informed consent that must survive translation?
The five requirements for informed consent that must survive translation are disclosure of study purpose and procedures, disclosure of foreseeable risks and discomforts, disclosure of reasonably expected benefits, disclosure of available alternatives, and affirmation of voluntary participation with the unconditional right to withdraw without penalty. Every translated form is checked against these five anchors during the back-translation reconciliation stage to confirm that no element has shifted in meaning, been softened by register drift, or omitted through condensation. Where a legally authorized representative signs the translated consent form on behalf of a participant who cannot consent directly — such as a cognitively impaired adult or a minor — all five elements must remain intact in the translated version the representative receives, because their signature carries the same legal weight as the participant’s own.
What reading level must a translated consent document meet?
A translated consent document must meet a 6th- to 8th-grade reading level in the target language, not merely in the English source. That distinction matters because translation does not automatically carry a reading level across languages: a source sentence written at a 7th-grade English level may translate into a target-language construction that scores at university level if the translator defaults to formal or clinical register. Plain-language rewriting in the target language — using short sentences, active voice, everyday vocabulary and defined medical terms — is the mechanism that keeps the translated consent document within the required range. Register drift toward professional or technical vocabulary is the most frequent quality failure identified during ICF translation review, and it is the failure mode that makes the consent document legally suspect even when every medical fact is translated correctly.
Who is qualified to translate an informed consent form?
Qualified ICF translators are native speakers of the target language with verified medical or life-sciences specialisation, operating within a documented ISO 17100 TEP workflow, and engaged by a translation company that can issue a certificate of translation accuracy on company-headed paper. The translator’s curriculum vitae, academic credentials and subject-matter specialisation are retained in the ISO 17100 supplier qualification file and are available to the sponsor’s quality assurance function or an IRB reviewer on request. A single bilingual speaker — however fluent — cannot fulfil these requirements, because the ISO 17100 standard mandates a minimum of two independent linguists and a documented revision stage before output is released.
When should informed consent forms be translated?
Informed consent forms should be translated whenever a study involves participants with limited English proficiency, before the first enrolment at any affected site, whenever the source consent document is materially amended, and whenever the IRB requires a fully translated long form to replace an accumulation of short form consent events. Proactive translation planning — ideally at the protocol design stage — eliminates the audit risk that arises when short form consents accumulate at a multilingual site because no translated ICF was commissioned in advance.
What triggers the obligation to translate an informed consent form?
The trigger for translation is a participant’s limited English proficiency — that is, any situation where the participant cannot fluently understand the English consent form as presented. That trigger activates the site’s obligation under FDA 21 CFR 50.20 and OHRP 45 CFR 46.116 to provide consent information in a language the participant can understand. In practice, sponsors should identify expected participant languages during site feasibility, commission translations for all anticipated languages before site initiation, and build translation timelines into the trial master schedule so that IRB-approved translated forms are available before the first participant is screened at each site.
Do you need to translate the form into many languages for multilingual clinical trial sites?
Yes — sponsors must translate the informed consent form into every language spoken by the expected participant population at each site, because a single English consent document cannot satisfy the regulatory requirement to obtain consent in a language the participant understands. In a multinational phase III trial, that requirement routinely generates 10 to 15 or more target-language versions of the same protocol, each requiring IRB or ethics committee approval in its jurisdiction. Each translated version must independently meet the plain-language reading level standard, preserve all required elements of informed consent, and be supported by a certificate of translation accuracy. For sponsors coordinating parallel language streams at scale, a single project manager overseeing all language pairs from one translation management platform prevents version-control errors and ensures that every site is working from the same approved source version.
Do you need translation for clinical research outside dedicated trials?
Yes — the translation obligation applies to any human research that requires informed consent under applicable regulations, including observational studies, registries, biobanks, survey research and any federally funded activity subject to the Common Rule under 45 CFR 46. The consent form may be simpler in a low-risk observational study than in a phase III interventional trial, but the requirement that it be understandable to the participant — and therefore translated when the participant has limited English proficiency — is identical. Wherever a participant’s signature on a consent document is required, the document they sign must be in a language they can understand.
When must a consent amendment be translated and participants re-consented?
A consent amendment must be translated and previously consented participants re-consented whenever the amendment introduces changes to risks, benefits, procedures, confidentiality provisions or participant rights that could affect a participant’s willingness to continue. The re-consent process must use the IRB-approved translated version of the updated consent document — not a verbal summary, not the English amendment alone. Failure to translate amendments and document re-consent in the participant’s language is one of the most frequently cited ICF findings during FDA inspections, because the audit trail must show that every consented participant received material changes in a form they could understand, not merely that the English master file was updated.
How it works
What is the role of back translation in informed consent forms?
The role of back translation in informed consent forms is to verify translation accuracy by having an independent translator who has not seen the original English ICF render the target-language consent document back into the source language, then systematically reconciling every discrepancy to identify altered meaning, errors of omission and non-equivalent registers before the translated form is submitted for IRB approval. Back translation is a quality-assurance mechanism, not a second translation product: its output is a reconciliation report that documents every identified discrepancy and the corrective revision applied to the target-language form. The process is blind — the back-translator works only from the target-language document, without access to the English source — so any shift in meaning introduced during forward translation surfaces as a visible gap between the back translation and the original.
Three categories of error are consistently identified during ICF back translation review: non-equivalent registers, where the target language uses a more formal or clinical term than the plain-language source; errors of omission, where a phrase, disclosure or rights statement present in the English ICF is absent from the target-language version; and other meaning-affecting mistranslations, where the target-language sentence carries a different factual meaning from the source. All three categories have direct regulatory consequences — an omitted disclosure violates the informed consent elements, and a shifted meaning may affect a participant’s risk comprehension or decision to participate.
When do IRBs require translation with back translation?
IRBs require back translation when the trial involves more than minimal risk, the target language uses a non-Latin script where meaning shifts are harder to detect through surface review alone, the protocol involves vulnerable populations such as paediatric participants, pregnant women or cognitively impaired adults, or the sponsor’s standard operating procedures mandate it for all ICF translations. Some institutional review boards formally require back translation for all greater-than-minimal-risk studies as a condition of approving any non-English ICF. Even where an IRB does not formally mandate it, sponsors frequently commission back translation proactively because the reconciliation report provides documentary evidence of translation quality that auditors and regulators can examine during a GCP inspection.
How is a back translation reconciled with the source language ICF?
A back translation is reconciled by comparing the back-translated text segment by segment against the original English source ICF, logging every discrepancy in a structured reconciliation report, determining whether each discrepancy represents a true meaning shift or an acceptable linguistic variance, revising the target-language consent where a true shift is identified, and reissuing the certificate of translation accuracy against the revised target-language version before IRB submission. The reconciliation report is retained in the ISO 17100 project file alongside the translator credentials, the forward translation, the back translation and all revision notes, forming a complete documentary record of the translation quality process. This record is made available to the sponsor’s quality assurance function, and to the IRB or regulatory inspector on request.
Is a certificate of accuracy required for informed consent form translations?
Yes — a certificate of translation accuracy is required for informed consent form translations in virtually all regulated research contexts. The Institutional Review Board uses it as documented evidence that the translated consent document is a true, complete and accurate rendering of the IRB-approved English source ICF. The FDA uses it to verify, during site inspection, that the translated form participants signed corresponds exactly to the approved English version in the investigator site file. The UK HRA and MHRA use it to close out the translated-ICF section of the Trial Master File during routine GCP inspection. Even where an IRB stops short of formally mandating the certificate as a named submission requirement, sponsor quality assurance standards and auditor expectations treat it as the default deliverable — and its absence creates an audit gap that must be explained and remedied.
The certificate is a signed statement from the translation company attesting that the translated consent document is a true and accurate rendering of the source language ICF. It identifies the language pair, the document and version translated, the translator credentials, the translation company as the accountable legal entity, and the date of issue — all of which allow the certificate to be cross-referenced against the IRB approval record and the participant’s signed consent form.
What must a certificate of translation accuracy contain?
| Element | Purpose |
|---|---|
| Source and target languages | Identifies the exact language pair the certificate covers |
| Document title and version number | Ties the certificate to a specific, version-controlled ICF |
| Translator name and qualifications | Evidences ISO 17100 translator competence for inspection |
| Translation company name and address | Identifies the legally accountable entity |
| Attestation of accuracy and completeness | The core legal statement required for regulatory acceptance |
| Signature of authorised company representative | Establishes personal accountability under GCP |
| Date of issue | Allows cross-referencing against the IRB approval date |
| Company-headed paper | Meets IRB and regulatory documentary presentation standards |
Each element serves a distinct regulatory function. The document title and version number ensure the certificate cannot be reused across ICF versions — a single certificate covering multiple amendments is not acceptable, because each approved version of the translated ICF must be independently attested. The date of issue must align with or precede the IRB approval date for that version of the consent document, demonstrating that the translation was complete and attested before the form was put in front of participants.
Do ICF translations always require a certificate of accuracy?
ICF translations almost always require a certificate of accuracy in practice, even when the reviewing IRB’s written submission checklist does not list it by name. FDA and sponsor audit teams routinely request the certificate during GCP inspection to close out the translated-ICF section of the Trial Master File, and an inspector who finds a translated consent form in the site file without a corresponding certificate of translation accuracy will raise it as a finding. Issuing the certificate as a standard deliverable on every ICF translation — regardless of whether the specific IRB has explicitly demanded it — removes an unnecessary audit variable and demonstrates the quality management posture that regulators expect from clinical research sponsors and their translation partners.
What are the best practices for translating informed consent forms?
Best practices for translating informed consent forms combine a documented ISO 17100 Translation-Editing-Proofreading workflow, native in-country reviewers with medical specialisation, a shared translation memory aligned with the trial protocol, active plain-language rewriting to a 6th- to 8th-grade reading level in the target language, back translation for high-risk or vulnerable-population studies, and a certificate of translation accuracy issued on company-headed paper before IRB submission. Applying all of these practices in combination is what produces a translated consent document that is simultaneously linguistically accurate, regulatorily compliant and genuinely comprehensible to the participant — the three requirements that IRBs, FDA inspectors and UK HRA reviewers each assess independently.
What does the ISO 17100 TEP workflow look like for an ICF?
The ISO 17100 TEP workflow for an ICF runs through four mandatory stages, each performed by a credentialled professional and documented in the project file:
- Translation — a native speaker of the target language with verified medical or life-sciences specialisation produces the forward translation, working from the IRB-approved English source ICF and any applicable translation memory from prior trial documents.
- Editing — a second independent linguist revises the translation against the English source, checking for accuracy, completeness, plain-language compliance and register consistency. Any discrepancy between the translator’s output and the source is logged and resolved at this stage.
- Proofreading — a proofreader reviews the final formatted document for typographic errors, numbering consistency, layout fidelity and any formatting element — such as a signature block or version number — that must match the approved English original.
- Validation — where back translation is required by the IRB or protocol, an independent back-translator renders the target-language document into English without access to the source ICF, and the reconciliation report is completed before the certificate of translation accuracy is issued. Where back translation is not mandated, an in-country reviewer may perform a final meaning and comprehension check as a lighter-weight validation step.
All four stages are documented, and the credentials of every linguist involved — translator, editor, proofreader and back-translator — are retained in the project file for sponsor and IRB review.
How is translation memory used across the ICF, protocol and patient diary?
Translation memory stores segment-level source-to-target pairs in a reusable database, so that clinical terminology, safety language, regulatory disclosures and rights statements that appear in both the protocol and the ICF are rendered identically across every translated document in the trial. A participant’s risk disclosure in the ICF must use the same terminology as the corresponding section of the clinical study report; a procedure description in the patient diary must match the procedure description in the consent form. Terminological inconsistency across trial documents is the first thing quality assurance auditors check when reviewing a translation package, because inconsistency raises questions about whether the participant’s understanding was coherent across the materials they received. Translation memory eliminates that risk by enforcing consistency mechanically rather than relying on individual translators to remember prior choices.
How do you match the translation to the participant’s level of understanding?
Matching the translation to the participant’s level of understanding requires rewriting medical terms into plain target-language equivalents, targeting the 6th- to 8th-grade reading level actively in the translated text rather than assuming it carries over from the source, using culturally familiar analogies where technical concepts have no plain-language equivalent in the target language, and validating comprehension through an in-country reviewer or, for high-risk studies, a pilot readback with members of the target population. A register audit on the finished translated form — systematically checking every clinical term against its plain-language alternative — is the operational tool that catches drift toward technical vocabulary before the form reaches the IRB. The goal is not simplification that loses meaning; it is clarity that preserves meaning in a form the participant can genuinely understand, discuss with the investigator, and use as the basis for a voluntary, informed decision to participate.
How should amendment translations be managed throughout the trial lifecycle?
Amendment translations should be managed through a version-controlled workflow that mirrors the amendment management process for the English source ICF. Every time the English consent form is updated with a material change — new risk data, a modified procedure, a change to participant rights or compensation — the amendment must be translated into every target language in use at affected sites, approved by the IRB in translated form, and used for re-consent of all previously consented participants before any protocol activity related to the amendment begins. The certificate of translation accuracy must be reissued for each amended version, and the superseded translated version must be retired from site use and flagged as obsolete in the Trial Master File. Treating amendment translation as a routine part of the change management process — rather than an afterthought triggered by an audit finding — is the practice that keeps the trial’s consent documentation continuously compliant throughout the study lifecycle.
What are the common challenges in informed consent form translation?
The common challenges in informed consent form translation are 6: non-equivalent registers, errors of omission on lengthy risk sections, altered meaning of technical terms, culturally sensitive concepts, tight IRB timelines, and version control across ICF amendments in multi-site trials.
What are non-equivalent registers and altered meaning errors?
Non-equivalent registers are shifts in formality between the source and translated consent, and altered meaning errors are translations that change the clinical or legal sense of the source ICF. A peer-reviewed study of four professional Spanish ICF translations catalogued both patterns and confirmed they slip past single-pass review, which is why back translation and independent reconciliation are the recommended controls.
What are the top 8 FDA 483 audit risks in ICF translation?
| # | Audit finding | Preventive control |
|---|---|---|
| 1 | Missing certificate of translation accuracy | Issue by default with every language delivery |
| 2 | Unapproved translated version in use | Route every translated form through IRB approval |
| 3 | Un-reconsented consent amendment | Log re-consent for every previously consented participant |
| 4 | Mismatched translator credentials | Retain ISO 17100 supplier CV file |
| 5 | Unlogged short form consents | Track per site, escalate to full translation after 2 |
| 6 | Incomplete elements of informed consent | Reconciliation checklist against 45 CFR 46.116 |
| 7 | Register mismatch to reading level | Fry-grade check by in-country reviewer |
| 8 | Inconsistent terminology across trial documents | Shared translation memory across ICF, protocol and diary |
Pricing
How do you commission an ISO 17100 certified informed consent form translation?
You commission an ISO 17100 certified informed consent form translation in 4 steps:
- Send the IRB-approved English consent form and protocol synopsis under NDA.
- Confirm target languages, back-translation scope and IRB submission deadlines.
- Receive a fixed quote with turnaround, price per language and certificate scope.
- Receive the translated informed consent documents with a certificate of translation accuracy for IRB submission.
Start the project by sending files to Request a Translation Quote.
What files should the sponsor supply for ICF translation?
- The IRB-approved English consent form in editable format.
- Any pending consent amendment and version history.
- The protocol synopsis for context.
- The sponsor’s approved terminology glossary, if one exists.
- The target-language list mapped to each site country.
- The site-country regulatory contact for the translation process.
How is participant confidentiality protected during the translation process?
Participant confidentiality is protected by signed confidentiality agreements with every linguist, ISO 27001-aligned information security controls, encrypted file transfer, and named-project access limited to the assigned TEP team. HIPAA authorisation, where the study is US-regulated and involves protected health information, sits alongside informed consent as a separate legal requirement handled in the same translated package.