Download signNow app
4.7 / 5 rating on

Assertion Of Right To Be Present Form

Use a ASSERTION OF RIGHT TO BE PRESENT template to make your document workflow more streamlined.

What this assertion form does

Assertion Of Right To Be Present Form is a document used to record a person’s statement that they have a right to be present in a specified situation. The supplied information does not identify an issuing agency, jurisdiction, required fields, filing deadline, or official form code, so those details must come from the requesting authority. In signNow, upload the source document, review its fields, route it to the designated signer, capture the electronic signature, and retain the completed PDF with its audit trail.

Who may use this form

  • A person asked to make the assertion should compare every factual statement with the underlying notice, proceeding, or event before signing. Because this form has no identified issuing agency in the supplied information, the signer should obtain the governing instructions from the requesting organization or state authority before completion.
  • A legal or compliance reviewer can check whether the assertion concerns an appearance, hearing, inspection, or other presence requirement, then confirm witness, notary, delivery, and retention expectations. signNow can route the record for review, capture signatures, and retain its audit history without determining the form’s legal sufficiency.

Complete the form in signNow

Use the original Assertion Of Right To Be Present Form, verify its required statements, and preserve the completed document with its signing evidence.

  • Upload the form:

    Upload the source PDF to signNow.
  • Check the fields:

    Review detected fields and add missing fields.
  • Add participants:

    Enter the required signer or recipient details.
  • Send for signature:

    Send the assertion for electronic signing.
  • Store the record:

    Download the completed PDF and audit trail.

How this form moves through signNow

The signNow workflow handles document preparation and signing evidence; the signer remains responsible for confirming that the assertion is accurate and authorized.

  • Prepare: Upload the form and inspect its detected fields.
  • Assign: Add the person who must make the assertion.
  • Authenticate: Route the document through the selected authentication method.
  • Complete: Capture the signature and preserve the completed record.
be ready to get more
Get legally-binding signatures now!
  • Best ROI. Our customers achieve an average 7x ROI within the first six months.
  • Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
  • Intuitive UI and API. Sign and send documents from your apps in minutes.

Recommended signing setup

Use a controlled workflow that verifies the signer, preserves the completed assertion, and follows the requesting authority’s retention instructions.

SettingRecommendation
Authentication methodEmail verification with SMS OTP
Signature typeTyped or drawn electronic signature
Audit trailRetain certificate of completion
Document retentionFollow the requesting authority’s policy
EncryptionTLS 1.2 or 1.3 and AES-256

What the signNow audit trail records

The audit trail supplements the signed assertion by preserving the events surrounding delivery, authentication, signing, completion, and later retrieval.

01

Authenticate signer:

SignNow records the authentication event associated with the signer.
02

Capture timestamps:

The audit history records when the document was opened and signed.
03

Record document history:

The completed document is preserved with its signing history.
04

Seal completion:

The signed file receives completion evidence for later review.
05

Retrieve evidence:

Authorized users can retrieve the audit trail with the document.
06

Export records:

Export the finished record according to internal retention procedures.

Signer authentication and evidence

PKI:

Public-key infrastructure

X.509 certificates:

X.509 certificate support

Two-factor authentication:

Two-step signer verification

SMS OTP:

One-time SMS passcode

ID verification:

Identity evidence review

Audit trail:

Signer action history

Platform requirements for signing

Use a current version of Chrome, Firefox, Safari, or Edge on Windows or macOS. signNow also provides mobile apps for iOS and Android, with an internet connection protected by TLS 1.2 or TLS 1.3.

  • Supported browsers Chrome, Firefox, Safari, Edge
  • Operating systems Windows, macOS, iOS, Android
  • Secure connection TLS 1.2 or 1.3 connection

Organizations should test managed Windows, macOS, iOS, and Android devices before distributing this form. Enterprise deployments may also require controlled access, SSO provisioning, API configuration, and retention policies that match the requesting authority’s records requirements.

Best practices for this assertion

Accurate source verification and complete evidence handling matter because the form’s issuing authority and jurisdiction are not identified in the supplied information.

Confirm the source and governing instructions

Confirm the requesting authority before entering information. The supplied form name does not identify an agency, jurisdiction, case number, or prescribed version, so obtain those details from the organization requiring the assertion.

Verify every factual statement before signing

Separate factual completion from electronic signing. Review dates, locations, names, and presence statements against contemporaneous records, then use signNow only after the assertion accurately reflects what the signer intends to certify.

Keep the signed record with evidence

Preserve the completed document and audit trail together. The signed PDF shows the final assertion, while signNow’s audit record can document timestamps, signer actions, and delivery history for later review.

Check state formalities and exclusions

Check state-specific formalities before sending. ESIGN and UETA generally recognize electronic signatures, but they do not eliminate exclusions or separate witness, notary, court, or agency requirements.

Issues to resolve before completion

  • The form name does not identify an issuing agency, so confirm the source before relying on its wording.
  • An assertion may require supporting facts, dates, or witness information that cannot be inferred from a blank template.
  • Electronic signing does not replace a state-required notary, witness, or in-person filing procedure.
  • Keeping only the signed PDF may omit the audit evidence needed to show signer identity, intent, and document history.

Legal standing of the completed record

A completed electronic assertion may be recognized under ESIGN, 15 U.S.C. chapter 96, and applicable state law when the signer shows intent, consents where required, can be identified, and the record can be retained and reproduced. These frameworks do not establish this form’s substantive right to be present or replace exclusions such as wills and certain court filings.

Why teams look for DocuSign alternatives

Questions about completing this form

These answers separate signNow’s document workflow from the issuing authority’s requirements, which are not identified in the supplied form information.

The supplied form name does not identify an official issuing agency or required version. Ask the requesting organization for the source document and governing instructions, then upload that exact PDF to signNow before adding fields or recipients.

ESIGN and UETA generally recognize electronic signatures when intent, attribution, consent where required, and record retention are established. They do not determine whether this assertion is substantively sufficient; verify any agency or state-specific rule separately.

Use signNow’s field detection as a starting point, then compare every field with the source form. Add missing signature, date, initials, or acknowledgment fields manually when the requesting authority requires them.

The Business plan is listed at $8 per user per month with annual billing and includes legally binding eSignatures and audit trails. Business Premium adds bulk send, while Enterprise adds advanced signer authentication.

Consumer-facing electronic records may require disclosure of the right to receive paper, proof that the consumer can access the electronic format, and procedures for withdrawing consent under ESIGN, 15 U.S.C. §7001(c).

A signed PDF should be retained with its signNow audit trail and completion evidence. Because no retention period is identified for this form, follow the requesting authority’s written policy rather than importing a period from another document type.

ROI at a Glance

Key performance indicators that demonstrate SignNow's proven track record.

28M+Documents signed
13+Years in business
4.6/5Average G2 rating

BE READY TO GET MORE

Get this form now!

If you believe that this page should be taken down, please follow our DMCA take-down process.