Magic Field Detection
Automatically recognizes common field labels such as Name, Date, and SSN, reducing manual placement time and preventing data mismatches on imported PDFs.
Using a reliable PDF import workflow speeds signatures, reduces printing and scanning, and maintains an evidentiary record required under ESIGN and UETA for enforceability.
Teams who import PDFs include administrators preparing agreements, operations staff issuing standard forms, and external signers who receive completed files for signature.
These roles prioritize fidelity to the original document, accurate field placement, and retention that meets applicable regulatory requirements.
Usually an operations or legal administrator who uploads the PDF, maps fields, manages authentication, and ensures the final signed record meets internal controls and regulatory retention policies.
A customer, vendor, employee, or third party who receives the prepared PDF for signature; their identity and consent are captured in the platform audit trail to satisfy intent and attribution requirements.
| Field | Configuration |
|---|---|
| Auto Field Detection | Enable to map common fields automatically during import. |
| Signer Authentication | Set default: email, SMS code, or knowledge-based auth where required. |
| Template Save | Save prepared PDFs as templates for reuse in recurring workflows. |
| Storage Path | Choose default cloud folder or local archive location for signed copies. |
Preserves original fonts, images, and form spacing so the signed output matches the source PDF exactly, avoiding formatting disputes.
Detects or allows manual placement of text, checkbox, date, and signature fields so data is captured in structured form for downstream processing.
Records signer identity, timestamps, IP addresses, and stepwise actions to support intent, attribution, and legal admissibility under ESIGN/UETA.
Supports delivery to document repositories and business systems (Salesforce, NetSuite, Google Workspace) for automated recordkeeping and reporting.
Automatically recognizes common field labels such as Name, Date, and SSN, reducing manual placement time and preventing data mismatches on imported PDFs.
Shows or hides sections based on inputs so a single PDF can serve multiple scenarios without separate templates or manual editing.
Enables sending the same imported PDF to many recipients with individualized fields, improving throughput for high-volume processes.
Offers SMS, knowledge-based, or identity-provider authentication when stronger signer verification is legally or operationally required.
Supports signing on a shared device or kiosk when signers are physically present, while still preserving audit metadata.
Automates import, field placement, and routing through integrations or developer APIs to embed import workflows into existing applications.
| Criteria | Electronic Signature | Digital Signature |
|---|---|---|
| Legal Status | broadly accepted | subset with cryptographic proof |
| Authentication | email/sms/account | pki certificate |
| Non-repudiation | audit evidence | strong cryptographic proof |
| Common Uses | contracts, consent forms | fda records, high-assurance filings |
Upload the PDF and run automatic field detection to identify editable areas.
Add missing fields, set required flags, and preview for all parties and devices.
Dispatch signing invitations and monitor signer authentication and completion.
Store the signed PDF with audit trail and retention metadata for compliance.
15–60 minutes for a single uploaded PDF depending on field complexity.
24–72 hours is typical for recipient completion in business transactions.
Large bulk sends may require prevalidation and staged delivery over 24–48 hours.
RON audio-video recordings are typically retained 5–10 years per state rules.
Signed PDF and audit trail should be accessible immediately after final completion.