REDCap eConsent: Versions, Signatures, and the Participant Copy

In clinical trials utilizing electronic informed consent (eIC), project teams often assume that selecting the “Auto-Archiver + eConsent framework” setting inside REDCap completes their regulatory compliance obligations. Enabling the framework within a project is a software configuration toggle. It does not certify that the displayed text is the current IRB-approved consent form, that the captured mark is attributable to the archived record, or that the research participant ever received a copy of the version they signed.

This operational analysis addresses exactly one reader decision: after a clinical operations or biostatistics team enables the REDCap eConsent Framework, how does it verify, prior to enrolling the first subject, that it can reconstruct three essential evidentiary pillars for every signer? Specifically, the team must be able to prove: (1) the exact Institutional Review Board (IRB) approved consent version that was presented to the participant, (2) an attributable, dated signature that is structurally bound to that archived record, and (3) contemporaneous documentation showing that the individual who signed received a verifiable copy of that same version.

To maintain strict analytical focus, this article establishes clear negative boundaries. It does not restate general audit trail rules from the 21 CFR Part 11 eCOA evidence guide, does not re-examine platform-level qualification versus protocol configuration from our computerized systems validation framework, does not address amendment release workflows from the eCOA protocol amendment change control guide, does not audit overarching trial quality frameworks from the ICH E6(R3) eClinical checklist, and does not cover site-less operational logistics from the decentralized endpoint collection guide. Crucially, it also fences off the distinct, subsequent workflow of reconsenting already-enrolled participants when a protocol amendment occurs. Our sole focus here is the release decision gate required before opening a survey instrument for initial participant enrollment.

Operationalizing electronic consent requires synthesizing requirements across federal statutes, agency guidance, and international good clinical practice standards. For clinical investigations regulated by the U.S. Food and Drug Administration (FDA), the foundational baseline is established by Title 21 of the Code of Federal Regulations.

Under 21 CFR 50.20, no investigator may involve a human being as a subject in research unless legally effective informed consent has been obtained in advance, under circumstances that provide sufficient opportunity to consider participation and minimize the possibility of coercion or undue influence. The documentation mechanism is governed by 21 CFR 50.27(a): consent must be documented through a written consent form approved by the IRB and signed and dated by the subject or the subject's legally authorized representative (LAR) at the time of consent. Furthermore, 21 CFR 50.27(a) explicitly mandates that “a copy shall be given to the person signing the form,” unless the IRB has formally granted a waiver of documentation under 21 CFR 56.109(c). Under 21 CFR 50.27(b), the documentation must take the form of either a comprehensive long-form consent embodying all required elements of 21 CFR 50.25, or a short-form document accompanied by an IRB-approved written summary of an oral presentation. In drug studies, 21 CFR 312.62(b) reinforces this mandate by requiring investigators to maintain case histories containing signed and dated consent forms demonstrating that consent was obtained prior to any study-related procedure.

For biomedical and behavioral research governed by the U.S. Department of Health and Human Services (HHS) under the 2018 Revised Common Rule, 45 CFR 46.117(a) establishes a parallel mandate: informed consent must be documented by a written consent form approved by the IRB and signed (explicitly “including in an electronic format”) by the subject or LAR, with a written copy provided to the signer, unless waived under 45 CFR 46.117(c).

The operational blueprint for deploying computerized systems in this domain is provided by the joint FDA/OHRP guidance, Use of Electronic Informed Consent: Questions and Answers (December 2016). While agency guidance documents reflect nonbinding current thinking under 21 CFR 10.115, this Q&A document outlines critical regulatory expectations that inspectors apply during data audits:

• Consent process and non-delegable investigator duty (Q1–Q3): Informed consent is a process that must present the required elements in understandable language and give sufficient opportunity for questions (Q1, Q3). Q2 states that the investigator cannot delegate the authority to obtain informed consent to the electronic system.

• Part 11 compliance in FDA trials (Q6): For FDA-regulated clinical investigations, electronic signatures used to document consent must comply with 21 CFR Part 11. The system must capture the calendar date when the signature was executed to substantiate that consent preceded investigational exposure.

• Identity verification (Q7): Under 21 CFR 11.100(b), organizations must verify the individual's identity before establishing, assigning, or sanctioning an electronic signature. The guidance notes that FDA does not mandate a specific verification technology, leaving methods (e.g., official photo identification, security challenge questions, multi-factor credentials, or video observation) to institutional SOPs.

• Copy delivery parameters (Q9): A copy of the written consent form must be provided to the signer unless documentation is waived. The copy may be paper or electronic (for example, an electronic storage device or email). FDA regulations do not require the subject's copy to include a signature, though FDA recommends providing a copy of the signed form that includes the date the eIC was signed.

• Version control and inspection retrieval (Q12–Q16): IRBs must review and approve all electronic materials that subjects will view. SOPs must ensure that all historical, IRB-approved versions remain retrievable, and that executed, subject-specific electronic consent records are immediately available during regulatory audits.

At the international level, the International Council for Harmonisation (ICH) consolidated guideline, ICH E6(R3) Good Clinical Practice (16 June 2026), uses “should” language that applies in accordance with applicable regulatory requirements. Section 2.8.7 states that, prior to trial participation, the informed consent form should be signed and dated by the participant or legally acceptable representative and, where appropriate, by an impartial witness and by the investigator or delegated site staff who conducted the informed consent discussion. The process may involve a physical or electronic signature and date. The glossary defines a signature as a unique mark, symbol, or entry executed, adopted, or authorised to show expression of will and allow authentication of the signatory.

A pivotal distinction emerges when comparing FDA regulations to ICH GCP regarding the participant's copy. While FDA 21 CFR 50.27(a) and FDA's August 2023 guidance require a copy of the consent form and merely recommend that it be signed, ICH E6(R3) Section 2.8.11 states that prior to participation, the participant or legally acceptable representative should receive a copy (paper or electronic) of the signed and dated informed consent form and any other informed consent materials provided, in accordance with applicable regulatory requirements, and should receive copies of consent-form updates during the trial. For an investigational new drug (IND) study that also follows ICH E6(R3), a File Repository snapshot the participant never received, or a brochure link to an unsigned current PDF, can meet a narrow reading of FDA’s copy-of-the-form rule and still miss ICH 2.8.11’s signed-and-dated copy expectation. Those two sentences should not be collapsed.

REDCap (Research Electronic Data Capture) is a secure, web-based software platform developed at Vanderbilt University and maintained by the global REDCap Consortium. The eConsent architecture was initially detailed by Lawrence et al. (2020) in the Journal of Clinical and Translational Science (PMC7681162). The module was designed to bridge electronic data collection with institutional IRB and regulatory requirements by introducing formal version controls, wet-signature simulation, reviewer modes, and document archival.

When a project designer activates the “Auto-Archiver + eConsent framework” within REDCap, the underlying software engine modifies survey behavior through three specific functional mechanisms:

1. The In-Line Certification Page: Upon progressing through the survey questions, the system intercepts final submission and presents a dedicated certification screen. This screen displays an in-line, dynamically generated PDF rendering of the consent document and the participant's responses. The framework withholds the final submit button until the respondent actively checks an attestation confirming that they have reviewed the document and verify its accuracy.

2. File Repository Snapshot Archival: When the participant certifies and submits the survey, REDCap automatically compiles a static, consent-specific PDF and stores it in the project's File Repository. Lawrence et al. (2020) describe that archive as a consent-specific snapshot; later consortium builds rename the service PDF Snapshot of Records. Instance-level filename templates and folder labels vary and are not restated here as a global specification.

3. The Wet-Signature Field: The framework uses a signature field that captures a mouse, stylus, or finger mark as a timestamped PNG and renders that image in the signed PDF, as described by Lawrence et al. (2020). FDA’s October 2024 electronic-systems Q&A (Q25) classifies a finger or stylus mark on an electronic system as a handwritten signature executed to an electronic record, which still must remain linked to that record under 21 CFR 11.70.

However, understanding what the framework does not do is essential for regulatory compliance. As emphasized on the official project-redcap.org software and FAQ portals, no software product is intrinsically 21 CFR Part 11 compliant on its own. Compliance is an attribute of the total operating environment—including server infrastructure, access control, change management, and standard operating procedures. The 2016 eIC Q&A (Q6) allows IRBs, investigators, and sponsors to rely on a vendor statement that an electronic-signature system meets relevant Part 11 requirements; that sentence does not override the REDCap FAQ or Lawrence 2020 limit that software alone is not compliant and that each environment still needs procedural controls. While Vanderbilt University Medical Center (VUMC) validated its own eConsent framework module with JAF Consulting and shared methods with consortium partners, that validation is not a certificate for another institution’s instance.

Furthermore, operational mechanics evolved significantly with the release of REDCap 14.5, commonly referred to across consortium institutions as eConsent 2.0. As documented in VUMC Human Research Protections Program (HRPP) operational tipsheets (March 2025) and consortium implementation reports (e.g., Yale University, October 2024), eConsent 2.0 introduced critical architectural shifts:

• Relocation of Controls: Configuration settings were migrated from global Survey Settings into the Online Designer, associating framework parameters directly with individual instruments.

• Snapshot Terminology: The legacy “Auto-Archiver” designation was formalized as the “PDF Snapshot of Records” service.

• Field-Level Document Uploads: Rather than requiring teams to construct cumbersome, multi-instrument projects (where every consent amendment necessitated building an entirely new REDCap form), eConsent 2.0 introduced field-level upload of the IRB-approved PDF document.

• Immediate Go-Live Behavior: Under the revised architecture, saving an edited eConsent configuration causes the new document to go live for all subsequent participant survey sessions immediately upon saving. Historical records retain their original version-tagged snapshots, but new respondents instantly receive the newly uploaded document.

flowchart TD
    A["IRB Review and Approval"] -->|"Approved form available"| B["REDCap Configuration"]
    B -->|"Upload after IRB approval; deactivate superseded version"| C["Survey Deployment"]
    C -->|"Participant reviews displayed version"| D["Required Signature and Date"]
    D --> E["In-Line Certification Screen"]
    E -->|"Certified submission"| F["Static PDF Snapshot"]
    F -->|"Site record only"| G["Project File Repository"]
    F -->|"Separate named delivery step"| H{"Copy of that version delivered?"}
    H -->|"Yes: download, print, email, or mail"| I["Signer has reconstructable copy"]
    H -->|"No: snapshot only"| J["Does not meet 21 CFR 50.27(a) or ICH E6(R3) 2.8.11"]

The first major compliance failure occurs when the document presented to the participant does not match the active, approved version authorized by the IRB. Under 21 CFR 50.27(a) and 21 CFR 56.109, an investigator may only present a consent form that has received prior prospective approval. Presenting an unapproved draft or continuing to present a superseded version violates federal regulations and compromises the validity of the subject's enrollment.

In REDCap operations, versioning failures typically manifest through three distinct operational traps:

• The Go-Live-on-Save Trap: Because REDCap 14.5 eConsent 2.0 pushes revisions live immediately upon saving in the Online Designer, study coordinators often upload a revised Word document or draft PDF while awaiting the final IRB approval letter. If a participant accesses the survey during this window, they execute an unapproved version, creating an immediate non-compliance event under 21 CFR 50.27(a) and 21 CFR 56.109.

• The Lingering Superseded Version Trap: In studies retaining legacy multi-form versioning, or in multinational trials managing distinct linguistic instruments across different Data Access Groups (DAGs), coordinators frequently activate the newly approved instrument but neglect to deactivate the survey settings on the prior instrument. Prospective participants continuing through existing invitation links sign the obsolete version after the IRB's mandatory transition date.

• The In-Text Descriptive Field Mismatch: Some institutions construct eConsents using REDCap descriptive text fields rather than uploading a static PDF. When an amendment occurs, coordinators may update paragraphs of text in the designer but overlook the separate survey-instruction metadata or version-date field. VUMC’s public electronic-consent page tells in-text users to list the version date in survey instructions exactly as it appears on the approved consent. If that date is left stale, the compiled File Repository snapshot can show updated body text next to an outdated version date, so the archived footer and the IRB stamp disagree.

The second critical failure involves capturing a mark that cannot be legally or forensically attributed to the participant and bound to the specific consent record. In FDA-regulated clinical investigations, electronic signatures are evaluated against the strict technical criteria of 21 CFR Part 11.

To satisfy 21 CFR 11.50 (signature manifestations), signed electronic records must contain three explicit data items displayed in both human-readable screen views and printed outputs: (1) the printed name of the signer, (2) the date and time when the signature was executed, and (3) the associated meaning of the signature (such as authorship, review, approval, or informed consent). Under 21 CFR 11.70 (signature linking), the electronic signature must be linked to its respective electronic record so that the signature cannot be excised, copied, or transferred to falsify another record by ordinary means.

FDA's October 2024 guidance, Electronic Systems, Electronic Records, and Electronic Signatures in Clinical Investigations: Questions and Answers, reinforces that signed electronic records must contain printed name, date and time of signing, and meaning (21 CFR 11.50), and that the signature must remain linked to its record (21 CFR 11.70). Q25 classifies a finger or stylus mark as a handwritten signature executed to an electronic record, which still requires that 11.70 link. Q26 restates that 21 CFR 11.100(b) identity verification is required before an organization sanctions an electronic signature, without specifying one method; examples include official government identification, security questions, or strong login credentials with multi-factor authentication or video observation. The method used for an FDA-regulated investigation should be named in the protocol or IRB file.

In standard REDCap configurations, several structural vulnerabilities can compromise signature attribution:

• Non-Required Signature Fields: If the signature field is not marked required, a participant can reach the certification page, confirm the preview, and submit without a mark. The File Repository then archives a blank signature block, which does not document informed consent under 21 CFR 50.27(a).

• Unverified Typed Text: Allowing a remote participant only to type a name into a generic text box, without identity verification and without printed name, date/time, and meaning on the same archived snapshot, does not by itself satisfy 21 CFR 11.50, 11.70, and 11.100. A typed string sitting apart from the signed record is not, on its own, a manifested, linked signature.

• Disconnected Investigator Countersignatures: Under ICH E6(R3) Section 2.8.7, the investigator or delegated staff member who conducted the consent discussion should also sign and date the form. In many REDCap setups, site staff execute that countersignature on a separate instrument that is never compiled into the primary eConsent PDF snapshot. The File Repository file then is not the signed record 21 CFR 11.70 requires to stay linked. This article does not claim that every REDCap build auto-merges investigator signatures into the participant snapshot; the local configuration has to be tested.

Importantly, a jurisdictional boundary must be maintained: as clarified by OHRP, research regulated exclusively under the HHS Common Rule (45 CFR Part 46) that does not involve FDA-regulated test articles is not generally subject to 21 CFR Part 11. For HHS-only research, OHRP permits electronic signatures if they are legally valid in the jurisdiction where the research is conducted (eIC Q6). Institutional IRBs may accept typed names, PINs, or written marks for non-FDA studies. Those options do not automatically satisfy Part 11 when the investigation is FDA-regulated.

The third operational failure is easy to miss: completing the electronic survey and archiving a snapshot in the investigator's database while failing to deliver a copy to the participant. Investigators routinely mistake the File Repository record for proof that the signer received a copy.

This assumption violates the explicit text of 21 CFR 50.27(a) (“a copy shall be given to the person signing the form”), 45 CFR 46.117(a), and ICH E6(R3) Section 2.8.11. The File Repository file is an investigator trial master record maintained under 21 CFR 312.62(b). It demonstrates what the site retained; it does not demonstrate what the participant received.

To evaluate participant copy mechanisms objectively, clinical operations teams must examine five common delivery channels across regulatory, technical, and operational dimensions:

A particularly hazardous workflow occurs during on-site consent using shared clinic tablets. If a participant completes the REDCap survey on a tablet where personal downloads are disabled, and confirmation email is turned off, the participant can leave with no copy. Even if the File Repository contains a signed PDF, the site has not given a copy as 21 CFR 50.27(a) requires.

To demonstrate the practical application of this release decision gate, consider a hypothetical clinical trial scenario: a U.S. IND Phase 2 randomized, double-blind study evaluating an investigational oral small molecule for migraine prevention. The study operates under FDA IND oversight, documentation of consent is not waived, and the protocol explicitly commits to ICH E6(R3) standards.

The sponsor issues Protocol Amendment 3, requiring ICF Version 3.0. The amendment introduces mandatory monthly urine pregnancy testing and a new 24-hour medical emergency contact number. The IRB approves the amendment and issues the official approval letter and stamped ICF Version 3.0 PDF on 1 August 2026. The clinical site utilizes an institutional REDCap 14.5 instance configured with eConsent 2.0. Before enrolling the first participant under Version 3.0, the clinical research coordinator (CRC) and regulatory lead execute the three-part verification gate:

1. Step 1: Version Lock and Deployment Verification. The regulatory lead confirms receipt of the IRB approval letter dated 1 August 2026. The coordinator opens Online Designer, uploads the stamped ICF Version 3.0 PDF into the eConsent 2.0 document field after that approval, and records the version identifier the protocol uses. Because saving makes the file live immediately, the coordinator performs a test submission in a non-production or practice record, if the local instance provides one, to confirm that the in-line preview shows the stamped approval text, that version metadata match the IRB stamp, and that the prior English version has been deactivated.

2. Step 2: Signature Attribution and Linking Verification. The coordinator audits the field attributes in Online Designer. The participant printed name, scribble signature, and date fields are confirmed as required. For remote signers, the protocol names an identity-verification method (FDA specifies none; 21 CFR 11.100(b) still requires verification before the organization sanctions an electronic signature). The team then checks that the investigator countersignature required by the protocol appears on the same File Repository snapshot as the participant mark, or documents how a separate instrument remains linked to that snapshot under 21 CFR 11.70. This example does not assert that every REDCap build auto-merges countersignatures.

3. Step 3: Participant Copy Delivery Verification. The study team names dual copy-delivery pathways based on enrollment modality and tests them before opening the survey. For remote enrollments, if the instance’s survey-completion email or file-send pathway is enabled, the completed PDF snapshot of that version is sent to the signer’s recorded address and the send is recorded if the instance logs it. For on-site enrollments on clinic tablets, the SOP requires printing the executed snapshot and handing it to the signer before study procedures begin, with delivery recorded in the site file. A brochure link to the current unsigned v3.0 PDF is not treated as a copy of the form that person signed.

By verifying version control, signature attribution, and copy delivery prior to opening enrollment, the study team can reconstruct the three facts 21 CFR 50.27, 21 CFR Part 11, and ICH E6(R3) 2.8.7/2.8.11 ask an inspector to retrieve. Enabling the framework is still not IRB or FDA approval, and the hypothetical example is not a real protocol, NCT number, or inspected site file.