Informed Consent Form Template: Build an Inspection-Ready ICF from the Required-Elements Checklist (ICH E6(R3) / 21 CFR 50)

At a glance

• An informed consent form (ICF) is not a document you download and fill in. It is the audit-defensible output of a required-elements checklist plus a versioned, documented consent process.
• The authoritative US element list lives in 21 CFR 50.25: eight basic elements that always apply, plus six additional elements that apply when appropriate. ICH E6(R3) §2.8.10 carries a parallel disclosure list for ICH-region trials.
• The form proves almost nothing on its own. Inspectors look for the process behind it: who consented, that they were delegated to do so, that the participant had adequate time, that the original was signed and dated, and that the version signed matches the IRB-approved version.
• Re-consent is a version-control discipline, not a courtesy. When new information emerges, ICH E6(R3) §2.8.2 says revised consent materials need IRB approval before use.
• Retention rules differ by framework, and the difference matters: 21 CFR 312.62(c) sets a concrete US floor, while ICH E6(R3) defers to “applicable regulatory requirements.” Keep the longer.
• A downloaded WHO or university IRB template is a starting skeleton, not a finished ICF. Adapt it against the element list and your IRB-approved protocol, then build the documentation trail around it.

If you searched for an “informed consent form template,” you were probably hoping for a blank .doc you could drop your protocol title into and print. Every top result obliges: WHO’s ethics committee template, the NIH/NCI sample forms, university IRB libraries, vendor tip sheets. None of them tells you which elements are legally mandatory, why each one is there, or how to prove the consent actually happened. That gap is the difference between a form and a finding. This guide teaches you to build and defend an ICF for a regulated clinical trial, not to paste a generic one. (If you arrived here looking for a chiropractic, massage, psychology, or social-work consent form, this is not that: those are named here only to set scope, and they are not GCP-grade.)

Why a downloaded ICF template fails inspection (form vs. process)

The single most common conceptual error among site staff is treating the ICF as a document rather than as the artifact of a process. A regulator does not certify your form. They reconstruct your consent process from the records it left behind.

21 CFR 50.20 frames this directly: no investigator may involve a human subject in covered research unless the investigator has obtained the subject’s legally effective informed consent, sought only under circumstances that give the prospective subject sufficient opportunity to consider participation and that minimize coercion or undue influence, in language understandable to the subject. Notice what that requires: an opportunity to consider, understandable language, and absence of coercion. A blank template cannot deliver any of those. They are properties of the conversation, the timing, and the documentation, not of the PDF.

ICH E6(R3) §2.8.1 makes the same point from the process side: in obtaining and documenting informed consent the investigator should comply with applicable regulatory requirements and adhere to GCP and the ethical principles of the Declaration of Helsinki, and the process must begin with the IRB/IEC’s documented approval of the consent materials and process before any participant is consented or enrolled. So before the form is ever printed, two things must already exist: an approved version and an approved process. A downloaded template has neither.

Software and standard operating procedures can enable a compliant consent process, but they do not make you compliant. The investigator and sponsor remain responsible. A tool that version-stamps your ICF or logs delegations reduces the chance of error; it does not discharge the obligation.

The required-elements checklist: what every ICF must carry

This is the deliverable the download pages omit. 21 CFR 50.25(a) sets out the basic elements that must be provided to each subject. Print this, tick it against your draft, and keep it.

Basic elements (21 CFR 50.25(a), all required):

• A statement that the study involves research, the purposes, the expected duration of participation, a description of procedures, and identification of any experimental procedures.
• A description of any reasonably foreseeable risks or discomforts.
• A description of any benefits reasonably expected, to the subject or to others.
• A disclosure of appropriate alternative procedures or courses of treatment, if any.
• A statement of the extent to which confidentiality of records will be maintained, noting that the FDA may inspect the records.
• For research involving more than minimal risk, an explanation of whether compensation and medical treatments are available if injury occurs.
• Whom to contact for questions about the research and subjects’ rights, and whom to contact in the event of research-related injury.
• A statement that participation is voluntary, that refusal carries no penalty or loss of benefits, and that the subject may discontinue at any time without penalty.

Additional elements (21 CFR 50.25(b), required “when appropriate”): currently unforeseeable risks; circumstances under which the investigator may terminate participation; additional costs to the subject; consequences of withdrawal and orderly-termination procedures; a statement that significant new findings will be provided; and the approximate number of subjects. For applicable clinical trials, 21 CFR 50.25(c) also requires a specific ClinicalTrials.gov registry statement in the consent documents and process.

ICH E6(R3) §2.8.10 supplies a parallel disclosure list for the consent discussion and materials in ICH-region trials, covering the purpose of the trial, that it involves research, the investigational product and randomization probability, the procedures to be followed including invasive ones, and what is expected of the participant. The two lists overlap heavily but are not identical in structure. For an FDA-regulated US trial, 50.25 is the inspectable element source; for an ICH-region trial, map your draft against §2.8.10 as well. Where both apply, satisfy both; do not assume one subsumes the other.

Element-mapping table

ICF element	Anchor	Why it is there
Research statement, purpose, duration, procedures	21 CFR 50.25(a)(1)	The subject must know this is research, not treatment.
Foreseeable risks and discomforts	21 CFR 50.25(a)(2)	Risk disclosure is the core of an informed decision.
Reasonably expected benefits	21 CFR 50.25(a)(3)	Honest benefit framing guards against therapeutic misconception.
Alternatives to participation	21 CFR 50.25(a)(4)	The subject must know they can decline and still be treated.
Confidentiality and FDA inspection notice	21 CFR 50.25(a)(5)	Subjects must know records may be inspected.
Injury compensation / treatment (>minimal risk)	21 CFR 50.25(a)(6)	Subjects must know what happens if they are harmed.
Contacts for questions, rights, and injury	21 CFR 50.25(a)(7)	A subject needs a named human to call.
Voluntariness and right to withdraw	21 CFR 50.25(a)(8)	Consent is meaningless if withdrawal is penalized.
No exculpatory language	21 CFR 50.20; ICH E6(R3) §2.8.4	The ICF may not waive the subject’s legal rights or release anyone from liability for negligence.
Process disclosure list (ICH-region)	ICH E6(R3) §2.8.10	Parallel disclosure obligations for the consent discussion.

A note inspectors care about: 21 CFR 50.20 prohibits any exculpatory language through which the subject appears to waive legal rights or release the investigator, sponsor, or institution from liability for negligence. ICH E6(R3) §2.8.4 states the same prohibition. If a downloaded template carries a “you agree not to hold us responsible” clause, strike it before it reaches a participant.

How to adapt a source template without breaking compliance

Source templates from WHO, NIH/NCI, or a university IRB are useful skeletons. The danger is adopting their structure and inheriting gaps, or worse, inheriting language that contradicts your protocol. Adapt, do not transplant:

1. Strip everything study-specific from the source and rebuild it from your IRB-approved protocol.
2. Run the draft against the 50.25(a) checklist above, then against the 50.25(b) “when appropriate” elements, deciding and documenting which additional elements apply.
3. For ICH-region trials, cross-check against ICH E6(R3) §2.8.10.
4. Remove any exculpatory language (50.20 / §2.8.4).
5. Submit it to the IRB/IEC. Per ICH E6(R3) §1.2.2 the IRB/IEC reviews the informed consent materials, including the description of how consent is to be obtained, and per §2.4.2 the investigator must hold the IRB/IEC’s documented, dated approval of the consent materials before initiating the trial. No participant may be consented on an unapproved draft.

The consent process: who consents, delegation, time, witness, dated original

This is where most inspection findings actually originate. The form was fine; the process around it was not.

Who may obtain consent. ICH E6(R3) §2.8.5 states the consent process should be conducted by the investigator or by investigator site staff delegated by the investigator, in accordance with applicable regulatory requirements. “Delegated” is load-bearing. A coordinator who obtains consent without being on the delegation log for that task has produced an inspection finding, even if the participant fully understood and the form is otherwise perfect. Under 21 CFR 312.60, the investigator is responsible for obtaining the informed consent of each subject in accordance with Part 50, and the investigator retains that responsibility even when the conversation is delegated.

Adequate time. ICH E6(R3) §2.8.6 requires that, before consent is obtained, the participant be given ample time and opportunity to ask about trial details and decide whether to participate, with questions answered to their satisfaction. A consent signed the same minute it was first handed over invites the question of whether the subject had a genuine opportunity to consider it.

The signed, dated original. ICH E6(R3) §2.8.7 requires the ICF to be signed and dated by the participant (or legally acceptable representative) and, where the discussion was conducted by site staff, by the investigator or delegated staff who conducted it. By signing, that person attests the consent was freely given and the information accurately explained. 21 CFR 50.27(a) requires that consent be documented by a written consent form approved by the IRB and signed and dated by the subject at the time of consent, with a copy given to the person signing. A missing date is not a clerical nit: the date is the evidence that consent preceded the first study procedure.

Witness and short-form consent. When a participant cannot read, ICH E6(R3) §2.8.9 requires an impartial witness present during the entire consent discussion, who then signs and dates the form attesting the information was accurately explained and consent freely given. 21 CFR 50.27(b)(2) describes the parallel US “short form” pathway: a short written document stating the required elements were presented orally, with a witness to the oral presentation, an IRB-approved written summary, and a specific signing choreography (the witness signs both the short form and the summary; the person obtaining consent signs the summary).

The participant’s copy. ICH E6(R3) §2.8.11 requires that the participant receive a copy of the signed and dated ICF and any other consent materials before participation, and copies of any updates during the trial.

Consent-process documentation table

Event	Who	Record that proves it
Consent conducted by an authorized person	Investigator or delegated staff (ICH E6(R3) §2.8.5)	Delegation log entry covering the consent task, dated before the consent.
Participant given adequate time	Participant (ICH E6(R3) §2.8.6)	Source note showing the gap between information and signature.
Form signed and dated	Participant + delegated staff (ICH E6(R3) §2.8.7; 21 CFR 50.27(a))	Signed, dated original ICF.
Witness present (illiterate participant)	Impartial witness (ICH E6(R3) §2.8.9; 21 CFR 50.27(b)(2))	Witness signature and date on the form / short-form summary.
Copy provided to participant	Participant (ICH E6(R3) §2.8.11)	Source note that the copy was given.
Consent obtained before participation	Investigator (21 CFR 312.62(b))	Case history documenting consent prior to participation.

Version control and re-consent: tying each signature to an IRB-approved version

A signature is only as good as the version it sits on. The discipline is simple to state and easy to fail: every signed ICF must correspond to an ICF version the IRB approved and that was current at the time of signing.

ICH E6(R3) §2.8.2 governs re-consent: participants must be informed in a timely manner of new information relevant to their willingness to continue, and the communication and confirmation must be documented. When re-consent is needed (for example, emerging safety concerns), the new information must be clearly identified in revised consent materials, and those revised materials must receive IRB/IEC approval before use. So the sequence is fixed: new information, revised ICF, IRB approval, then re-consent. Re-consenting a participant on a draft the IRB has not yet approved inverts that order and is a finding.

Version-control decision callout. When the protocol or ICF changes: (1) Does the change affect a participant’s willingness to continue? If yes, re-consent is likely required (§2.8.2). (2) Has the IRB approved the revised ICF? If no, stop; you cannot consent on it yet. (3) Does the new version apply to already-enrolled participants, to new participants only, or both? Decide and document. (4) Does each signed form in the binder cite the correct version number and date for the version current when it was signed? Reconcile the consent log against the IRB approval dates.

Documenting consent so it survives a BIMO inspection

For US trials under an IND, the documentation obligation is explicit. 21 CFR 312.62(b) requires the investigator to maintain adequate and accurate case histories, and states that case histories include supporting data such as signed and dated consent forms; critically, the case history for each individual must document that informed consent was obtained prior to participation. That last clause is what a BIMO inspector verifies first: not merely that a signed form exists, but that the record shows consent came before the first study activity.

ICH E6(R3) reinforces this on the essential-records side. The Essential Records Table in Appendix C lists completed, signed, and dated informed consent forms among the records that must be retained, and §2.8.7’s attestation requirement means the signature itself carries evidentiary weight.

Where teams get it wrong

Four findings recur often enough to plan against:

• Consent obtained by an undelegated coordinator. The form is perfect, the participant understood everything, but the coordinator was not on the delegation log for consent at that date. ICH E6(R3) §2.8.5 ties the authority to delegation; an off-log signature is a finding regardless of quality.
• The mismatched-version signature. A participant signed version 3.0 the week after the IRB approved version 4.0, because the site was still printing old stock. §2.8.2 and the version-control discipline above exist precisely to catch this. Reconcile the consent log against IRB approval dates.
• The missing date. The participant signed; nobody dated it, or only one party dated it. 21 CFR 50.27(a) and ICH E6(R3) §2.8.7 both require a signed and dated form, and the date is the proof that consent preceded participation (21 CFR 312.62(b)).
• No source note for the consent conversation. There is a signed form but nothing showing the participant had adequate time (§2.8.6) or received their copy (§2.8.11). Build a brief consent source note into your process so the conversation, not just the signature, leaves a record.

For the surrounding records, see the related topics this site covers separately: protocol deviations (how an out-of-window consent gets documented and reported), essential documents and the TMF (where the signed original lives and how it is retained), and investigator delegation of duties (the log that authorizes who may consent).

Retention: how long the signed original is an essential document

Retention is the clearest place where two in-scope frameworks make different demands, and you should not smooth that over.

21 CFR 312.62(c) sets a concrete US floor for IND trials: the investigator must retain records required under Part 312, which include the signed consent forms within the case history, for 2 years following the date a marketing application is approved for the indication being investigated; or, if no application is filed or the application is not approved for that indication, until 2 years after the investigation is discontinued and FDA is notified.

ICH E6(R3) does not name a number. §2.12.12 requires the investigator/institution to retain the essential records for the required retention period in accordance with applicable regulatory requirements, or until the sponsor informs them the records are no longer needed, whichever is longest; §9.5 echoes that essential records be retained “for the required period in accordance with applicable regulatory requirements.”

These two are not in agreement on the period, and the gap is the practical point: ICH E6(R3) deliberately defers to local law, while 21 CFR 312.62(c) supplies the local number for FDA-regulated trials. The operational rule that satisfies both is the one ICH E6(R3) §2.12.12 already states, keep records for the longest applicable period: the FDA’s 2-years-post-approval (or post-discontinuation) floor or any longer sponsor or local requirement, whichever runs longest. Do not retire a signed ICF on the FDA minimum if your sponsor contract or local law demands more.

Sources

• ICH E6(R3) Good Clinical Practice, version r3 (ICH, 2025) — https://www.ich.org/page/efficacy-guidelines
• 21 CFR Part 50 Protection of Human Subjects, version 2024 (FDA) — https://www.govinfo.gov/content/pkg/CFR-2024-title21-vol1/pdf/CFR-2024-title21-vol1-part50.pdf
• 21 CFR Part 312 Investigational New Drug Application, version 2026-04 (FDA)