Combined Consent
Separate, numbered consent items within one document so each authorization can be identified and analyzed independently during review or audit.
A combined consent streamlines administrative steps, creates a single source of truth, and reduces signer burden while preserving separate, itemized permissions. It also centralizes retention and audit-trail requirements, which helps organizations meet regulatory obligations when properly drafted and signed.
Use this form only when each consent element is explained clearly; separate documents may still be preferable for highly regulated or high-risk authorizations.
The individual whose personal data or decisions are the subject of consent. Provide full legal name, contact information, and any required identifiers. The primary client must demonstrate intent and consent for each item; mismatches between IDs and the signed name can invalidate consent for regulated uses.
A legally authorized signer (guardian, power of attorney, parent) who signs on behalf of the client. Documentation proving authority should be attached or referenced, and the representative’s name, relationship, and authority scope must be captured on the form.
Separate, numbered consent items within one document so each authorization can be identified and analyzed independently during review or audit.
Plain-language description of what data or actions are authorized, why they are needed, and which third parties may receive the information.
Effective date and expiration or event-based termination for each consent item to limit open-ended authorizations.
How a signer can revoke consent, the expected processing time, and any consequences of revocation for services or data processing.
Record of how the signer was authenticated (email, SMS OTP, KBA, ID verification) and any witness or notary details if required.
Time-stamped signing events, IP addresses, and a certificate of completion to support enforceability under ESIGN and UETA.
| Field | Configuration |
|---|---|
| Authentication Method | Email link, SMS OTP, or KBA per risk level |
| Conditional Fields | Show specific consent items based on prior answers |
| Notification Settings | Email reminders, expiration notices, and escalation |
| Template & Versioning | Save as template and track document version |
Ensure the vendor supports HIPAA BAAs where required, offers exportable audit logs, and integrates with your records retention system to maintain compliance.
The date entered becomes the start of consent obligations
Specify if consent auto-renews or requires reauthorization
Set expected processing — e.g., immediate or within 30 days
Schedule archival or deletion according to retention policy
Provide timeframe to respond to requests for signed records
| 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, no credit card required | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No envelope cap | 100 envelopes/user/year | Varies by vendor | Varies by vendor | Varies by vendor |