Electronic consent version tracking answers a narrow operational question: which approved form did a participant sign, and does that match the version currently in effect? The FDA guidance does not prescribe a technical method, but it states that the eIC process should ensure all versions of the IRB-approved eIC can be retrieved easily [1]. That requirement pushes the design burden onto the platform and the site. Vendor documentation shows at least three distinct approaches. CRIO embeds version checks into the eSource visit workflow [3]. Signant Health describes version control within PDF-based and interactive consent options [4]. REDCap-based guidance at Vanderbilt and Utah treats version control as a configuration discipline within a research data platform [2][5]. Each approach changes who owns the version record, what triggers a re-consent, and what evidence an auditor can retrieve.

What the Regulatory Text Actually Requires

The December 2016 FDA and OHRP guidance on electronic informed consent establishes a retrieval expectation rather than a versioning algorithm. It states that the eIC process should incorporate procedures to ensure that electronic documents can be archived appropriately and that all versions of the IRB-approved eIC can be retrieved easily [1]. The guidance also addresses amendments: if the eIC is updated or amended, the subject should have sufficient opportunity to ask questions, and the subject or legally authorized representative must sign the amended eIC before the subject continues in the study [1]. This creates a temporal boundary. A signature is valid for the version in effect at the time of signing, and continued participation after an amendment depends on executing the newer version.

The October 2024 FDA guidance on electronic systems adds a validation dimension without naming consent platforms. It states that validation should be applied to system functionality, configurations specific to the clinical trial protocol, customizations, data transfers, and interfaces between systems [6]. For version tracking, this means the logic that compares a participant's executed version against the current approved version is itself a configurable behavior that should be assessed for the specific protocol. The guidance also notes that when systems are decommissioned or hosted contracts end, sponsors should ensure metadata are obtained, retained, and linked to each corresponding data element [6]. A version identifier is only useful if it remains linked to the signed record after the platform changes.

Three Documented Implementation Models

CRIO describes version control as embedded in its eSource workflow. The vendor states that at the outset of each patient visit, the system automatically checks whether the patient has executed the most recent ICF, and if not, notifies the clinical research coordinator and provides a link to open the associated eConsent or initiate a remote consent procedure [3]. The vendor also claims the system can automatically track which patients have executed which versions [3]. In this model, the version check is a gate within the visit workflow, and the executed consent flows into the vendor's Reviewer EDC for remote monitoring [3]. The documentation attributes these capabilities to CRIO and does not establish independent verification.

Signant Health separates version control across two consent formats. The vendor states that its PDF-based eConsent process imports and presents existing PDF versions of the informed consent form and contains elements such as ICF version control and re-consent process management [4]. The interactive option is described as a multimedia consent experience, but the source does not detail whether its version control mechanics differ from the PDF-based option [4]. Signant also states that its eConsent solution offers integration with other SmartSignals products and other eClinical systems [4]. The documentation frames version control as a property of the consent solution rather than a visit-level gate, which suggests a different trigger point than CRIO's embedded check.

A Suggested Validation Scenario for Version Tracking

A site could validate version tracking by creating two IRB-approved versions of a consent form in a test project, then executing a scripted sequence. First, a test participant signs version 1 and the system archives a timestamped PDF. Second, the site activates version 2 and records whether the platform flags the participant as not having executed the current version. Third, the participant signs version 2 and the site confirms that both version 1 and version 2 remain retrievable as separate records with distinct identifiers. Fourth, the site attempts to delete or inactivate version 1 and verifies that the signed record remains accessible, following the Utah warning about data loss [5]. This scenario is a suggestion for internal testing, not a claim that any vendor has passed such a test.

Version Control as a Configuration Discipline in REDCap

The Vanderbilt IRB tipsheet describes REDCap eConsent version control as a managed process rather than an automatic workflow. It states that all consent form versions will be managed using the REDCap version control system, and that any changes to the consent form will be resubmitted to the IRB for approval prior to implementation [2]. The tipsheet also states that the system will ensure all signed forms are archived as PDF snapshots for compliance and future reference [2]. This places the version boundary at IRB approval, with the platform preserving signed snapshots. The source does not claim that REDCap automatically blocks a visit when a participant has not signed the current version.

The University of Utah guidance adds an operational warning that reveals a failure mode. It instructs users to avoid deleting expired eConsent instruments because deleting the instrument will result in the loss of all data collected within that specific instrument, and instead to follow versioning guidance or inactivate the survey [5]. This is a consequential distinction. In a platform where versioning is a configuration choice, a user action can destroy the version history that the FDA guidance expects to be retrievable. Utah also directs users to maintain a systematic approach to version control and to follow specific modify e-consent guidance [5]. The institutional documentation therefore treats version tracking as a shared responsibility between the platform and the study team.

What a Version Record Must Contain

The ACRP peer-reviewed article on eConsent interoperability identifies consent version as a required discrete data element, with the stated purpose of audit-ready version tracking and facilitating re-consent workflows [8]. The same table lists participant ID, date of consent, investigator signature date, consent method, consent status, and participant copy provided as separate required fields [8]. This separation matters for system design. A version identifier alone does not establish that the participant received a copy or that the investigator signed on the correct date. The table implies that version tracking is one field within a larger consent record, not a standalone log.

The FDA guidance on archiving reinforces this point. It states that FDA regulations do not specify a preferred method for archiving documents, but the eIC process should incorporate procedures to ensure appropriate archiving and easy retrieval of all IRB-approved versions [1]. The guidance also notes that if a copy provided to the subject includes hyperlinks, the hyperlinks should be maintained and information should be accessible until study completion [1]. A version tracking system that stores only the signed PDF may not preserve linked content that was part of the consent experience. The documentation leaves open whether platforms capture the full rendered consent or only the signature page.

Where the Documentation Leaves Questions Open

None of the sources specify how version identifiers are generated or whether they use a consistent scheme across platforms. The ACRP article calls for consent version as a discrete data element for interoperability, but it does not define a standard identifier format [8]. Medidata states that its Consent product replaces parallel paper workflows with automated version control and ensures the right forms are always used [7]. The vendor also states that the platform supports eIDAS-compliant signatures and a hybrid paper-to-digital upload feature for regions where wet-ink signatures are still required [7]. The documentation does not explain how a paper-signed version is reconciled with the digital version record in the hybrid scenario.

A second open question concerns re-consent triggers. CRIO describes a visit-level check [3]. Signant describes re-consent process management without specifying the trigger [4]. Medidata states that automated notifications alert teams when re-consent is required [7]. The FDA guidance requires signing the amended eIC before the subject continues in the study, but it does not define what constitutes continuation [1]. A platform that triggers re-consent at the next visit may treat a telephone contact or remote data entry differently. The sources do not resolve this boundary, and sites should document their own interpretation.