delegation log.

Consent Process Documentation in Source Notes:

The source documentation should reflect the consent process clearly. The note should include:

• Date and time of consent discussion

<liConfirmation that the ICF was reviewed with the participant

• That the participant was given sufficient time to decide
• Confirmation of questions asked and answered
• Verification of the signed, dated, and witnessed ICF
• Documentation of language and translator/witness (if applicable)

Example entry: “On [date], participant reviewed ICF v3.0 (dated [X]) with Dr. Y. All questions were answered. Subject signed and dated the ICF; copy provided. Consent obtained in Hindi with witness present.”

Maintaining Consent Documents in the Investigator Site File (ISF):

Signed consent forms must be stored securely in the ISF. Best practices include:

• Filing the original signed ICF in chronological order
• Keeping a master log of all ICF versions and approval dates
• Cross-referencing with participant ID and screening logs
• Protecting confidentiality and access control

These practices align with clinical trial documentation expectations and GCP inspections.

Version Control and Audit Trail:

Consent version control is vital. Investigators must ensure:

• The correct ICF version is used for each participant
• Old versions are not used once superseded
• All amended ICFs are Ethics Committee (EC) approved
• Signed revised consent is documented for re-consented participants

Maintain an Informed Consent Version Log and update the validation master plan accordingly.

Handling Special Consent Situations:

1. Illiterate Participants:

• ICF should be read aloud in the participant’s language
• An impartial witness must be present throughout the discussion
• Consent must be documented with participant’s thumb impression and witness signature

2. Verbal Consent:

• Allowed only in exceptional EC-approved cases
• Must be accompanied by detailed notes and witness signatures
• Written documentation must follow as soon as possible

3. Electronic Consent (eConsent):

If using eConsent tools, ensure:

• Electronic signature validity is confirmed
• System has audit trails and secure access
• Participant receives a downloadable or printed copy

Ensure the platform follows GMP guidelines and is validated under 21 CFR Part 11.

Staff Training and Delegation:

Only trained and delegated personnel may obtain and document consent. Keep training records that confirm staff understand:

• Consent documentation requirements
• Version control and approval processes
• How to handle special populations and translations
• Documentation in source and regulatory files

Training logs should be kept updated and audited during monitoring visits.

Common Audit Findings and How to Avoid Them:

• Missing participant or investigator signatures
• Incorrect ICF version used
• No record of re-consent for protocol amendments
• Improperly documented consent for illiterate participants
• Unsigned witness section when required

Use consent checklists to avoid omissions and ensure consistent site practices per pharma regulatory requirements.

Checklist for Consent Documentation per GCP:

1. Obtain latest EC-approved ICF version
2. Document full consent process in source notes
3. Verify and file signed ICF in the ISF
4. Record witness or translator involvement if needed
5. Update consent logs and screening logs
6. Ensure consistency across monitoring visits and audits

Conclusion:

Documenting the informed consent process is not just about obtaining a signature—it is about capturing the entire communication, understanding, and agreement process in a verifiable, compliant manner. By adhering to ICH-GCP, national regulations, and sponsor SOPs, investigators can ensure that participant rights are respected and trial data remains valid. Meticulous documentation reinforces trial integrity, safeguards against regulatory findings, and upholds ethical standards in every clinical study.