Affiant Identification
Provide the affiant’s full legal name, date of birth if needed for identity proofing, and a clear mailing address to tie the affidavit to the correct person and to prevent misidentification during notarization.
A well-structured request reduces delays, avoids incomplete submissions, and preserves admissibility by specifying jurat, notarization, and exhibit requirements.
Legal Affidavits Requests are used across litigation, corporate, and public-sector contexts where sworn factual statements are required.
Requests should be tailored to the audience and include clear instructions on signing, notarization, and deadline to ensure timely and admissible affidavits.
Provide the affiant’s full legal name, date of birth if needed for identity proofing, and a clear mailing address to tie the affidavit to the correct person and to prevent misidentification during notarization.
Describe precisely what facts the affidavit should address, including relevant dates, locations, and events; limit open-ended prompts to avoid extraneous or hearsay content that may weaken admissibility in court.
List required supporting documents (photos, receipts, contracts) with exhibit labels and ordering instructions so the affiant can attach and reference exhibits consistently within the sworn statement.
Specify whether the document needs a jurat (sworn oath before a notary) or a notarized acknowledgement; include the exact jurat language if your jurisdiction or court prefers specific wording.
Note acceptable authentication methods (in-person notarization, RON if permitted, or specified ID checks); indicate any required witness count and whether electronic signatures are acceptable under ESIGN/UETA.
State a clear due date and preferred delivery method (courier, email to counsel, e-filing), and include consequences for late or incomplete affidavits such as exclusion from evidence or additional follow-up.
| Field | Configuration |
|---|---|
| Identity Proofing | Enable ID verification and optional KBA |
| Signature Type | Choose e-signature, digital PKI, or RON |
| Routing Order | Sequential signers and reviewer steps |
| Integrations | Connect to Salesforce, NetSuite, or Box |
Use standard file formats and account for authentication, notary, and integrations when accepting electronic affidavits.
Ensure your platform supports audit trails, AES-256/TLS encryption, and optional RON workflows to meet court and regulatory expectations.
Often 14–30 days per court or agreement
Schedule contemporaneous signing and jurat
Comply with the court’s filing deadline
Follow agency-specific deadlines where applicable
Date stamped on executed affidavit
Optica used online forms to collect sworn statements from remote investors and contractors
A healthcare provider collected patient-authorized affidavits during an audit response
| 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 | Trial available | Trial available | Trial available | Trial available |
| Bulk Send | Yes (Business Premium) | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes (BAA available) | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |