Purpose
Plain-language explanation of why the procedure or request is proposed and what it seeks to accomplish for the participant.
A clear, complete consent document protects individual rights, documents informed decision-making, and reduces legal risk by demonstrating disclosure and voluntary agreement. It supports regulatory compliance where required, clarifies responsibilities, and creates a reproducible record that can be audited or produced in proceedings when needed.
Common users include clinicians, researchers, legal teams, institutional administrators, and guardians who must document consent or authorization reliably.
The document’s audience determines required language, additional disclosures (for example HIPAA or FERPA), and whether witness or notarization elements are necessary.
Plain-language explanation of why the procedure or request is proposed and what it seeks to accomplish for the participant.
Clear, specific description of foreseeable risks and possible side effects, including likelihood and severity where available.
Concise explanation of anticipated benefits to the individual or to general knowledge, avoiding guarantees of outcomes.
Statement of reasonable alternatives including the option to decline, with any differences in risks or outcomes.
How collected data will be used, retained, shared, and protected; include HIPAA or research-specific authorizations when required.
Spaces for printed name, role (if representative), signature, date, and witness or notary sections if applicable.
| Field | Configuration |
|---|---|
| Signature Field | Required for each signer; include date and initials fields |
| Authentication | Email link plus SMS code or stronger KBA for sensitive consents |
| Conditional Fields | Show representative fields only when 'Signing for another' is checked |
| Retention Policy | Automate secure storage and retention per institutional schedule |
Choose a platform that supports secure delivery, detailed audit trails, and the authentication strength your jurisdiction or policy requires.
Ensure the platform can produce tamper-evident signed documents, export audit trails, and meet any regulatory BAA or 21 CFR Part 11 needs.
Consent takes effect on the effective date signed unless otherwise specified.
Signer may revoke consent per form instructions; confirmation procedures vary by policy.
Adverse events or reportable incidents must follow regulatory deadlines.
Research consent may require annual IRB review and re-consent.
Respond to records requests per HIPAA and institutional timelines.
| Criteria | Electronic signature | Digital (PKI) signature |
|---|---|---|
| Legal status | valid under esign/ueta | valid under esign/ueta |
| Technology | audit trail, image overlay | cryptographic certificate |
| Non-repudiation | based on metadata | stronger via ca chain |
| Typical use cases | general consents | high-assurance regulated filings |
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |