necessary for significant protocol or risk changes.

Steps to Implement Re-Consent After a Protocol or Safety Change:

Step 1: Receive Official Amendment or Safety Notification

• Protocol amendment or Dear Investigator Letter (DIL) received from sponsor or CRO
• Safety update from DSMB or pharmacovigilance unit
• Updated Investigator’s Brochure (IB)

Step 2: Draft Revised Informed Consent Form (ICF)

• Clearly incorporate protocol/safety changes
• Update risk-benefit section, procedures, visit schedule, or product description
• Use version control (e.g., Version 6.0 dated 15-Apr-2025)
• Highlight new changes using tracked changes if required

Step 3: Submit for Ethics/IRB Review

Before re-consent can occur:

• Revised ICF must be reviewed and approved by the EC/IRB
• Any associated safety communication or amendment must be submitted
• Await approval letter before proceeding

Step 4: Train Site Personnel

Ensure all staff involved in consent obtainment:

• Understand changes in the protocol or safety profile
• Can explain new risks or procedures clearly to the participant
• Follow the site’s re-consent SOP and documentation flow

Step 5: Conduct Re-Consent with Participants

• Explain the new changes and why re-consent is needed
• Encourage questions; allow time to consider
• Have the participant sign and date the new ICF
• Complete AV recording for Indian sites per CDSCO if required

Best Practices for Ethical Re-Consent:

• Never pressure participants—ensure voluntariness
• Provide information in local language when necessary
• Maintain privacy during consent discussions
• Ensure the participant receives a signed copy of the updated ICF

Documentation Requirements:

Source Notes

• Record the reason for re-consent
• Note the version of the ICF used
• Document the staff member and date of consent

Consent Logs

• Maintain a consent tracker or log with all version histories
• Note status of re-consent for each subject

TMF/ISF Filing

• File updated signed ICF in participant binder
• Archive previous version with appropriate cross-referencing
• File EC/IRB approval letters for audit readiness

Common Triggers for Re-Consent After Amendments:

1. Change in investigational product dosing
2. New adverse event reported
3. Addition of genetic testing or imaging procedures
4. New exclusion criteria added
5. Trial extension or long-term follow-up inclusion

Tools and Templates to Support Re-Consent:

• Re-Consent SOP (from Pharma SOP templates)
• Version control log for ICFs
• Consent deviation reporting form
• Participant communication script
• Consent audit checklist

Consequences of Poor Re-Consent Compliance:

Issue	Impact	Resolution
Participants not re-consented after protocol change	Data invalidation and potential subject risk	Immediate re-consent and CAPA submission
Outdated ICF version used	IRB deviation and audit finding	Implement SOP for version control
No documentation in source	GCP non-compliance	Use re-consent templates and logs
AV recording skipped (India)	Violation of CDSCO regulations	Retraining and protocol deviation report

Real-World Example:

In a Phase III oncology trial, a new cardiotoxicity risk was discovered. The sponsor issued a protocol amendment and Dear Investigator Letter. Sites had to re-consent all ongoing participants using the revised ICF version 4.0 and complete AV recordings. Ethics Committees were notified within 7 days. This action preserved subject safety and ensured trial compliance with regulatory stability documentation expectations.

Conclusion:

Re-consent after protocol amendments or safety updates is more than a regulatory formality—it is a participant right and ethical necessity. By following structured SOPs, maintaining comprehensive documentation, and respecting participant autonomy, clinical trial teams ensure both compliance and trust in the research process.