What an eConsent System Does and Does Not Prove

Part of Decentralized Trials (DCT) Training: Remote and Electronic Consent.

About 2 minutes. Free, in your language, no account needed.

It proves who clicked, and when

A well-configured system records the identity of the signer, the version signed, the timestamp and the audit trail of changes.

That is genuinely valuable and it is a narrow claim.

It does not prove who was in the room

A signature applied from a participant's account shows the account was used. It does not show who used it, or that anybody else was absent.

This is why identity verification and the consent discussion still matter, and why the discussion is documented separately.

Know which version they signed

Consent forms get amended. A system can serve the current version, or the one assigned when the participant enrolled, or the one cached on their device.

Confirm the version in the record matches the version approved and in force on that date. Participants consented to a superseded version are a common and awkward finding.

The audit trail is part of the record

Timestamps, IP or device information, and any field changes. It is the evidence that the signature is what it appears to be.

Know how to retrieve it. A system you can use but cannot export from will not help during an inspection.

Regulatory acceptance varies

Electronic signatures are accepted in most jurisdictions and not all, and the requirements differ. Some regions require a wet signature or an additional step for certain populations.

This is decided at study level, not by you. What you must know is which rule applies to your participants, because it changes per country.

When the system fails

Have a documented paper fallback. A participant ready to consent and a platform that is down should not mean the visit is lost.

Whatever route is used, the record must show which one and why.

Do not pre-fill anything

A form completed on the participant's behalf, however helpfully, is no longer their account of their own decision.