Download signNow app
4.7 / 5 rating on

To Be The Person Who Is Described In And Who Executed The Within And Form

Use a To Be The Person Who Is Described In And Who Executed The Within And template to make your document workflow more streamlined.

What this form language means

This form language identifies the person described in a document and the person who executed it. In plain terms, it connects the named individual to the act of signing or completing the record. It may appear in business, legal, or administrative documents where attribution matters. A preparer can upload the document to signNow, place the required fields, send it to the intended signer, and retain the completed copy with its audit trail. ESIGN and applicable UETA law generally recognize qualifying electronic signatures, subject to statutory exclusions and transaction-specific requirements.

Who uses this form language

Business records

Teams can use this form language alongside contracts, NDAs, HR records, invoices, and consent documents when the record must identify the person described and the person who executed it.

Administrative workflows

Legal, finance, human resources, and operations teams can route the document for review, signature, and secure storage without changing the underlying wording.

Teams handling signed business records

  • Finance coordinators at U.S. businesses use this acknowledgment language to document who is identified in, signed, or otherwise executed within a business record, preserving attribution when approvals move between departments or counterparties.
  • Legal operations teams use signNow to route documents containing this clause, capture signer identity and timestamps, and retain the completed record with an audit trail for later review.

Features that support this form

The workflow connects document preparation, signer attribution, electronic execution, and evidence preservation for this specific form language.

Field placement

Upload the document and place signature, date, and identity fields without recreating the underlying form language.

Signer routing

Route the document to the person identified in the record and capture the signing event in sequence.

Audit trail

Record timestamps, signer actions, and completion evidence in an audit trail connected to the signed document.

Electronic signing

Support typed or drawn signatures when the transaction permits electronic execution under ESIGN and applicable state law.

Record export

Review and export the completed document and certificate of completion for controlled business storage.

Access control

Use role-based access to limit who can prepare, send, review, and retain the document.

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.

How to complete this form

Use this signNow workflow to prepare the document, identify the signer, capture execution, and preserve the resulting record.

  • Upload document:

    Upload the completed document to signNow.
  • Detect fields:

    Let signNow detect existing fillable fields.
  • Place fields:

    Add signature, date, and identity fields.
  • Send for signature:

    Send the document to the intended signer.
  • Review completion:

    Review the signed copy and certificate.
  • Store evidence:

    Store the record with its audit trail.

Choose a signing method for this form

  1. Use the signNow web app when a preparer needs to upload this document, place fields, and send it from a desktop workflow.
  2. Use the signNow mobile app when an authorized user must review or sign this document from an iOS or Android device.
  3. Use kiosk mode when people sign the document on a controlled shared device, with the organization managing the signing session.
  4. Use a shareable signing link when approved recipients need access without a separate email invitation for each signing event.

Recommended workflow setup

Configure the document so signer identity, execution intent, evidence, and access controls remain connected to the completed record.

SettingRecommendation
Authentication methodEmail verification with SMS OTP
Signature typeTyped or drawn electronic signature
Audit trailEnable certificate of completion
Document retentionRetain under the applicable record rule
Encryption and provisioningAES-256 storage with role-based access

Best practices for completing this form

Accuracy depends on identifying the correct person, preserving the surrounding document, and retaining evidence of the signing event.

Confirm the described person before sending

Confirm the named person before sending

Use the exact document context

Review the form wording and surrounding document so the signer understands exactly which record and execution event the statement describes. Avoid adding identity details that are not required for the transaction.

Capture informed electronic consent

Require the intended signer to review the complete document before applying a signature. For consumer-facing records, provide the electronic-record disclosure and access information required by 15 U.S.C. §7001(c).

Preserve the signed record

Export the completed document and audit trail together when the transaction closes. Store them under the organization’s retention policy, with access limited to authorized personnel.

Privacy and disclosure pitfalls

  • Including unnecessary personal details can expose identity information to recipients who only need the signed business record.
  • Failing to capture electronic-record consent may weaken the evidence that a consumer agreed to conduct the transaction electronically.
  • Unrestricted template or completed-document access can expose the signer’s identity and execution details beyond the authorized transaction team.
  • Separating the signed document from its audit trail can make later review of attribution, timestamps, and signer actions more difficult.

Risks from incomplete execution

Signer identity disputed

Weak attribution

Electronic consent challenged

Missing consent

Audit evidence unavailable

Incomplete record

Clause applied incorrectly

Wrong document scope
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

Questions about completing this form

These answers address execution, electronic-signature evidence, signNow workflow choices, and document retention for this form language.

Upload the document to signNow, review detected fields, and manually add any missing signature, date, or identity fields. Confirm that the document’s wording identifies the correct person before sending it.

The Business plan includes legally binding eSignatures, audit trails, templates, mobile apps, ISO 27001, SOC 2, and GDPR support. Select a plan based on required controls, signer volume, and organizational policy.

signNow records the signing event through its audit trail and certificate of completion. Review signer identity, timestamps, and document history before exporting the completed record for business retention.

ESIGN and UETA support qualifying electronic signatures when intent, consent, attribution, and record reproducibility are established. They do not remove exclusions for wills, court orders, or specified family-law records.

For consumer-facing electronic records, provide the disclosure and access information required by 15 U.S.C. §7001(c). Confirm that the signer can access the electronic record and understand the consent process.

Use role-based access and signNow’s audit trail to preserve the completed document and execution evidence together. Retention duration depends on the underlying transaction and applicable federal or state recordkeeping rule.

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.