Translated Informed Consent Materials

Non-English-speaking participants are entitled to the same disclosure, comprehension, and voluntariness protections as any other research participant — 45 CFR 46.116 requires that information be presented “in language understandable to the subject,” and that requirement doesn’t relax because a participant’s first language isn’t English. What changes is the mechanism: IRBs recognize two distinct, separately regulated pathways for meeting that requirement in another language, and researchers routinely conflate them. This entry distinguishes the two pathways and covers translation-quality practice (certified translation, back-translation) that neither pathway resolves by itself.

Pathway 1: a fully translated long-form document

The consent document itself — not just an oral summary of it — is translated into the participant’s language and submitted to the IRB for review and approval as its own version, carrying its own approval stamp, version number, and expiration date alongside the English original. This is the preferred pathway whenever a study anticipates enrolling a meaningful number of speakers of a given language, since it gives the participant a complete written document to read, retain, and consult, not just an oral presentation backed by a short summary. See CASRAI’s ICF (Informed Consent Form) entry for how version control and IRB approval-stamping work for any ICF, translated or not.

Pathway 2: the short-form process (45 CFR 46.117(b)(2))

Where a translated long-form document isn’t available — typically because an eligible participant speaking an unanticipated language shows up before a translation exists — 45 CFR 46.117(b)(2) (and the parallel 21 CFR 50.27(b)(2) for FDA-regulated research) permits a short-form written document instead. The short form, in the participant’s language, states that the required elements of consent were presented orally; the English-language document serves as the written summary of what was presented. A witness fluent in both languages must be present for the oral presentation (the witness may also serve as the interpreter, provided they are not otherwise affiliated with the study as an investigator). The participant signs the short form; the person obtaining consent signs the English summary; the witness signs both. This is a formal, IRB-approved regulatory pathway, not an informal workaround for a rushed enrollment — the IRB must have approved the short-form process and, in most institutional practice, the specific short-form template in advance. Institutions commonly keep a library of IRB-pre-approved short forms in the languages most frequently encountered in their participant population. Once a short form has been used, IRB and institutional guidance generally expect the study team to obtain and use a fully translated long-form document for any further participants who speak that language, rather than relying on the short form indefinitely.

Certified translation and back-translation practice

Neither 45 CFR 46 nor 21 CFR 50 specifies a numeric translation-quality standard or mandates a particular vendor or certification scheme — the regulatory text only requires that the result be understandable to the participant. In practice, IRBs commonly calibrate the rigor of translation review to study risk: for minimal-risk research, some IRBs will accept a translation performed and attested to by a qualified bilingual staff member without requiring a professional translation service, provided competency is documented. For greater-than-minimal-risk and biomedical research, IRBs more commonly require either certification from a professional translation service or a back-translation — an independent translator renders the translated document back into English without seeing the original, and the study team or IRB compares the back-translation against the source document to catch drift in meaning, omitted risk language, or altered emphasis. A machine translation alone (with no qualified human translator involved) is not treated as meeting the “understandable language” standard by IRB guidance reviewed for this entry, given the risk of mistranslating risk, consequence, or voluntariness language in a consent context specifically. Institutional practice on exactly where the minimal-risk/greater-than-minimal-risk line falls for translation rigor varies by institution — researchers should confirm their own IRB’s specific translation and certification requirements rather than assuming a single universal threshold.

Communication beyond the consent moment

Translating the consent document (or using the short-form process) addresses the enrollment moment, but IRB guidance commonly expects a broader communication plan for non-English-speaking participants covering the full duration of participation — study visits, adverse-event reporting, answering follow-up questions, and any amended-consent or re-consent events (see CASRAI’s guide on informed consent timing and re-consent). A translated enrollment document without an ongoing interpretation plan for the rest of the study is a common IRB or monitoring finding.

How this differs from the checklist item

CASRAI’s Informed Consent Checklist for Researchers flags language and translation as one item to confirm before IRB submission; this entry is the fuller regulatory and practical treatment of that single item — the two consent pathways, the witness/signature mechanics of the short form, and translation-quality practice.

Related terms and further reading

• ICF (Informed Consent Form) — the document artifact itself, including version control, IRB approval-stamping, and readability.
• Informed consent — the underlying disclosure-comprehension-voluntariness process under 45 CFR 46.116.
• Informed Consent in Research: What It Requires and How It Works — the full regulatory guide, including waivers and special populations.
• Informed Consent Checklist for Researchers — the working checklist this entry expands on for the language/translation item.
• When Should Informed Consent Be Obtained? — timing, re-consent, and the emergency exception.