Identity Fields
Full legal name, date of birth or DOB range if required, government ID type and number when strictly necessary for verification, and contact information in standardized format.
A concise PI template reduces collection errors, supports compliance with ESIGN and UETA for e-signed records, and helps organizations meet data-minimization and retention objectives. It standardizes consent language and field formats so records are easier to validate, audit, and reuse across business processes.
Organizations and individuals use a Miscellaneous PI Template where structured personal data capture is required for transactions, service access, or administrative records.
Use cases span small administrative tasks to enterprise intake; controls around storage, access, and consent vary by industry and jurisdiction.
Individual providing personal information and consenting to its use. The data subject must verify name, contact details, and sign or electronically assent in a manner that demonstrates intent and attribution under ESIGN/UETA.
Authorized staff member who configures the template, requests the signature, and retains records. This role is responsible for selecting authentication strength and ensuring legal disclosures are presented when collecting consumer-facing data.
Full legal name, date of birth or DOB range if required, government ID type and number when strictly necessary for verification, and contact information in standardized format.
Street address (not P.O. box when legal service is required), email in lowercase, and primary phone with country code. Use consistent formatting to avoid matching errors.
Clear, plain-language description of purpose, retention, data sharing, and how to withdraw consent when the form collects consumer-facing or health-related information.
Signatory name, role or relationship, date signed, and a signature field that supports electronic signatures with audit information for ESIGN/UETA compliance.
Checkboxes for accuracy declarations, attestations for identity verification steps, and optional witness or notary blocks where jurisdiction or policy requires them.
Automated capture of signer attribution data: timestamp, IP address, authentication method, and a machine-readable certificate or completion report retained with the record.
| Field | Configuration |
|---|---|
| Authentication Level | Email link, SMS code, or KBA depending on risk |
| Conditional Logic | Show or hide fields based on prior answers |
| Signer Order | Sequential or parallel routing for approvals |
| Retention Rule | Automatic archive and access controls on completion |
Choose channels that support secure delivery, signature capture, and the required authentication strength for your use case.
Many platforms integrate with common systems such as Salesforce, Microsoft 365, Google Workspace, and cloud storage to automate routing and archival.
Provide the template upon request; no universal statutory delivery deadline for miscellaneous PI forms
Common practice: allow 7–30 days for signers to complete
Allow 1–5 business days for identity verification steps
Record and archive within 1–3 business days after receipt
Retention clocks typically begin on effective date or filing date
| 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 | Varies | Varies | Varies |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies | Varies | Varies |