To Me Known To Be The Person Or Persons Form

Use a , To Me Known To Be The Person or Persons template to make your document workflow more streamlined.

What this form is and how it works

The To Me Known To Be The Person Or Persons Form is a document used to record information about the person or persons identified in its title and obtain their acknowledgment or signature. Because no issuing agency, statutory form code, field list, or filing deadline is supplied for this title, its legal purpose depends on the transaction and applicable state law. In signNow, upload the document, review detected fields, add signer roles, send it securely, capture consent and signatures, and retain the completed PDF with its audit trail.

Business transactions

Use the form for contracts, acknowledgments, consent records, or other documents when the transaction owner identifies this exact document and its required signers. Confirm any agency-specific instructions before relying on an electronic copy.

Multi-party workflows

Use role-based routing when several people must review or sign. Separate preparer, signer, witness, and approver responsibilities so the audit trail clearly shows who performed each action.

Who benefits from this workflow

The right workflow depends on whether one person or a controlled team prepares, sends, reviews, and stores the form.

A solo practitioner can use a reusable signNow template to collect the identified person’s information and signature, then download the completed record without coordinating paper copies or in-person appointments.
A regulated healthcare office can route the form through designated staff, apply stronger signer authentication when needed, and retain the signed record with an audit trail under its privacy and records policies.
An enterprise compliance team can control templates, assign roles, and connect signNow with business systems so repeated requests use consistent fields, routing, access permissions, and retention procedures.

How to complete this form in signNow

Use this workflow to prepare the document, collect signatures, and preserve evidence of completion.

Upload document:
Upload the source document to signNow.
Check fields:
Review detected fields and correct placements.
Add signers:
Assign signer roles and routing order.
Send form:
Send the form for secure completion.
Store evidence:
Download the signed PDF and audit trail.

be ready to get more

Get legally-binding signatures now!

Start free trial

Request a call

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.

Setting	Recommendation
Authentication method	Email verification; add SMS for sensitive records
Signature type	Typed or drawn signature with clear intent
Audit trail	Retain the completion certificate with signed PDF
Document retention	Follow the transaction’s governing record rule
Encryption	Use TLS 1.2/1.3 and AES-256 protection

Best practices for completing this form

Accuracy depends on confirming the document’s purpose, assigning the right signer roles, and preserving evidence of the completed transaction.

Confirm the form’s legal purpose

Confirm what the form is intended to establish, identify every required signer, and verify whether a state agency, court, employer, or contracting party requires a particular version before sending it through signNow.

Review every detected field

Upload the source document, inspect signNow’s detected fields, and compare every required name, date, acknowledgment, and signature field against the authoritative instructions for this transaction.

Assign precise signer roles

Use signer roles and routing order when different people must complete separate portions. Send only the information each recipient needs, and avoid placing sensitive data in unnecessary fields or messages.

Preserve the signed record

Export the completed PDF and audit trail, then store both under the organization’s approved retention policy. Keep the authoritative source and signed version distinguishable for later review.

Security for signed records

Stored document protection:

AES-256 encryption at rest

Transport security:

TLS 1.2/1.3 encryption in transit

Independent assurance:

SOC 2 Type II certified

Information security:

ISO 27001 certified

Protected health information:

HIPAA compliant with BAA

Signer access control:

Two-factor authentication available

Connect this form to business systems

Connect signNow with CRM, ERP, cloud storage, and productivity tools to route this form, preserve records, and reduce rekeying.

Challenges to check before sending

The title alone does not identify the issuing authority, required fields, signer qualifications, or filing destination, so users may need transaction-specific instructions before completion.
Auto-detected fields can be misplaced when the source PDF has unusual formatting, creating missing signatures, dates, or acknowledgments unless the sender reviews every page.
A signed PDF without its audit trail may provide less evidence about identity, consent, timing, and document history during a later dispute.
Sending personal information to the wrong recipient can expose sensitive data and make the completed form unsuitable for the intended transaction.

Risks from incomplete execution

Confirm governing source

Unknown authority

Electronic record challenged

Missing consent

Attribution becomes uncertain

Wrong signer

Audit proof unavailable

Unretained evidence

Authenticate signer:

Records the signer’s authentication event and access method.

Capture timestamps:

Captures when the signer opens and completes.

Track document history:

Associates document activity with the signed record.

Seal evidence:

Preserves a tamper-evident completion record.

Record actions:

Logs signer actions and routing events.

Export audit trail:

Allows authorized users to retrieve and export evidence.

Questions about completing this form

These answers address the title’s missing authority, the signNow workflow, electronic-signature evidence, and record retention.

The title does not identify a federal agency or official code, so confirm the source, required fields, and filing instructions with the transaction owner before uploading it. signNow can route and document signatures, but it does not determine which version is legally required.

Upload the source PDF, then inspect every field signNow detects. Add or reposition text, date, initials, and signature fields before sending. Compare the prepared document with the authoritative instructions because automated field detection cannot establish whether a field is legally required.

A signer can complete a signNow request through the secure signing experience without preparing a separate account in many workflows. The sender should verify the recipient’s email address and select SMS or stronger authentication when the transaction requires additional identity evidence.

Electronic enforceability depends on intent, consent, attribution, and the ability to retain and reproduce the record. ESIGN, 15 U.S.C. ch. 96, and applicable UETA rules provide the framework, but state-specific requirements and statutory exclusions still need review.

Use signNow’s Business plan for templates, legally binding eSignatures, and audit trails at $8 per user per month when billed annually. The verified plan information includes 100 signature invites per user per year, with overage fees.

Export the completed PDF together with its audit trail and store both under the rule governing the underlying transaction. Do not assume a universal period for this unnamed form; state law, industry rules, and the document’s purpose control retention.

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.