Sponsors, CROs, research sites and academic teams choosing eConsent software for clinical trials and research studies.
Scope Electronic informed consent (eConsent) software that presents, explains, signs and version-controls participant consent for clinical trials and research studies, remote or on site, as sponsors, CROs, sites and academic research teams would shortlist it.
These notes describe the products in the eConsent guide.
Florence eConsent
Best for
Sites and site networks already on Florence eBinders that want consent in the same system
What to consider
Florence eConsent runs inside its eBinders eISF, with remote identity verification and re-consent tracking, and it is the only vendor here with a public price (on AWS Marketplace). Its product pages do not document multimedia or comprehension checks, and one customer institution lists English and Spanish only.
Clinical trials and research studies that need informed consent connected to ongoing participant engagement, questionnaires and follow-up
What to consider
WeGuide connects informed consent with ongoing participant engagement throughout clinical trials and research studies. Teams can combine screening, consent, questionnaires, reminders and follow-up in one study program, rather than treating signing as the end of the workflow. Publicly described consent features include multimedia forms, comprehension checks, version control, reconsent, remote signing and multiple signatories. Confirm protocol-specific signature, validation and implementation requirements.
Less suitable for
Teams that only need a basic consent-document workflow, or require a country-by-country signature service or native enterprise EDC from the same provider; confirm the required scope.
Single and double checks describe documented support for an individual feature. Double checks use the extended definition for that feature. Unknown means the available evidence does not establish support.
Expand a feature definition or support note for context and its original source.
Florence eConsent vs WeGuide (eConsent): category feature evidence and sources. Products are not ranked.
Category feature
Florence eConsent
WeGuide
Consent experience and comprehensionFeature definitions
Supported
A digital consent presentation or completion workflow is documented.
Extended support
Digital consent includes both multimedia content and participant comprehension checks.
Florence eConsent
Supported
Remote and on-site consent on any device, remote identity verification, re-consent distribution and tracking; multimedia and comprehension checks not documented.
Consent and identity verification are documented; multimedia and comprehension checks are not.
WeGuide
Extended support
The no-code consent builder supports video, audio and comprehension quizzes, electronic signatures, multiple signatories and representatives. Versions, reconsent and consent status are tracked in the study workflow.
Both multimedia consent content and participant comprehension checks are explicitly documented.
Compliance and regulatory track recordFeature definitions
Supported
Relevant trial or security controls are stated.
Extended support
Relevant trial controls plus a public ISO/SOC certificate or audit report are documented; a certification claim or logo alone is insufficient.
Florence eConsent
Supported
Compliant with technical requirements of Part 11, Annex 11 and ICH GCP; annual SOC 2 Type II; 88K sites in 90+ countries use Florence (platform-level).
Trial controls and annual SOC audits are stated; this note does not establish a public audit report.
WeGuide
Supported
WeGuide states ISO certification and support for HIPAA, GDPR and 21 CFR Part 11 requirements. Its public statements do not supply a current ISO certificate or SOC audit report.
English and Spanish are reported at a customer site; country compliance reviews do not establish multicountry use.
WeGuide
Extended support
WeGuide describes multilingual consent, including the INHERIT study, and participant research across five countries in BRACE. These are vendor-published study examples, not a country-by-country e-signature acceptance list.
Consent tasks link to screening and questionnaires in the same WeGuide program. The product page also documents connections to REDCap and other EDC or eClinical systems, with integration requirements scoped by the team.
No build process, self-service builder or turnaround is published.
Unknown does not mean unavailable. The public evidence does not establish support under this category’s definition.
WeGuide
Extended support
The no-code consent builder lets teams configure approved consent content. WeGuide states most eConsent studies can go live within days with team support. This is an eConsent setup claim; full app publishing and integration timelines require separate scoping.
The marketplace listing publishes an annual starter price and a monthly active study-site price.
WeGuide
Supported
WeGuide publishes a per-study quote basis. Contact the team for the study-specific scope and price; no numerical price or free production tier is published.