(e.g., typos or contact details) may not require re-consent but should still be version-controlled.

Steps to Revise and Re-Implement Informed Consent:

1. Identify Changes That Require Re-Consent:

Collaborate with medical monitors, regulatory affairs, and safety teams to determine if an amendment warrants participant re-consent.

2. Draft Revised ICF:

• Use a clear, non-technical language to explain the changes
• Highlight modifications in risks, procedures, or rights
• Update version number and date prominently

Refer to your pharma SOP documentation on ICF development and version control.

3. Ethics Committee Approval:

Submit the revised ICF and protocol amendment to the Institutional Review Board (IRB) or Ethics Committee (EC). Provide:

• Tracked and clean versions of the revised ICF
• Rationale for the changes
• Communication plan for ongoing participants

No re-consenting can occur before EC approval.

4. Train Site Staff on New Procedures:

Ensure that investigators and site coordinators understand:

• The nature of the changes
• How to explain revisions to participants
• Documentation requirements and version use

Update site training logs and delegation logs accordingly to remain compliant with GMP compliance expectations.

5. Re-Consent Process with Participants:

Conduct one-on-one sessions with each enrolled subject. Ensure that:

• Revised consent is provided in the participant’s preferred language
• Time is given to review and ask questions
• A new signature is obtained on the revised ICF
• The reason for re-consent is documented in source notes

Witnesses are required for illiterate subjects or when required by protocol or EC.

Documentation and Version Control:

Accurate documentation of consent revisions is crucial for inspection readiness:

• Label revised ICFs clearly with version and date
• Maintain both signed old and new ICFs in the ISF
• Use validation master plan principles to track consent workflow
• Update the Informed Consent Log and screening checklist

Handling Participants Who Refuse Re-Consent:

If a participant chooses not to continue under the revised protocol:

• Document the reason and date of withdrawal
• Report to the sponsor and Ethics Committee
• Ensure any follow-up per protocol for early withdrawals is completed

This decision must be respected and must not affect the subject’s access to standard medical care.

Managing eConsent During Protocol Amendments:

If using an eConsent system:

• Update digital templates with new version and content
• Re-validate system outputs per clinical trial documentation standards
• Re-capture digital signatures and audit trails

Common Audit Observations Related to Re-Consent:

• Using outdated ICF versions for new enrollments
• Failure to re-consent enrolled participants after significant amendments
• Missing EC approval for revised ICF
• Poorly documented re-consent process in source notes

These issues can lead to findings in inspections by EMA, FDA, or national agencies.

Checklist for Re-Consenting Participants:

1. Confirm need for re-consent based on amendment
2. Prepare revised ICF (translated if needed)
3. Submit to and obtain EC approval
4. Train site staff on the update
5. Conduct re-consent sessions
6. Update logs and ISF with new documentation
7. Ensure no old version is used after cutoff date

Conclusion:

Re-consenting participants after protocol amendments is not just a regulatory requirement—it is a matter of ethical transparency and participant protection. A well-managed re-consent process upholds the integrity of the study and fosters trust between participants and researchers. By following structured SOPs, ensuring proper documentation, and engaging with ethics committees, clinical trial teams can seamlessly manage consent revisions across the study lifecycle.