I Certify That On Sent Copies Of This Request To Form

Use a I Certify That On Sent Copies Of This Request To template to make your document workflow more streamlined.

What this request form does

I Certify That On Sent Copies Of This Request To Form is a certification document used to state that copies sent with a request accurately represent the relevant records or materials. The signer reviews the request, confirms the certification language, supplies any required identifying information, and signs the completed copy. With signNow, the sender uploads the form, checks detected fields, adds the signer, and sends it for completion. The signed document and audit trail preserve evidence of the transaction, while the underlying request determines any separate legal or retention requirements.

Individuals

Individuals certify that sent copies accurately represent a request, supporting email, or business record before returning the completed document.

Business teams

Operations, legal, and administrative teams route the certified copy for review, signature, storage, or later production.

How to complete this request form

Use signNow to prepare the request, confirm its fields, collect the required signature, and preserve evidence of completion.

Upload document:
Upload the request form to signNow.
Check fields:
Review detected fields and add missing certification or signature fields.
Send request:
Enter the intended signer and send the completed request.
Store record:
Review the signed copy and audit trail before storing it.

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.

Field preparation

Upload the request and inspect detected fields before placing certification, date, and signature controls on the correct pages.

Signer delivery

Send the prepared request to the designated signer by email, or provide a controlled signing link when appropriate.

Audit trail

Capture the signer’s actions, timestamps, and delivery events in an audit trail associated with the completed request.

Record integrity

Keep the signed request and completion evidence together for later review, comparison, or production to an authorized recipient.

Signer verification

Use SMS OTP or configured identity checks when the request’s contents require stronger attribution than email access alone.

Mobile access

Review and sign from a supported desktop or mobile browser without recreating the request manually.

Setting	Recommendation
Authentication method	Email verification with SMS OTP
Signature type	Typed or drawn electronic signature
Audit trail	Capture timestamps, IP address, and actions
Document retention	Retain signed copies under organizational policy
Encryption	Use TLS 1.2/1.3 and AES-256 protection

Platform requirements for this request form

Complete I Certify That On Sent Copies Of This Request To Form in a current browser using TLS-protected access. Chrome, Firefox, Safari, and Edge support the web workflow on Windows and macOS; signNow mobile apps extend document review and signing to iOS and Android.

Desktop browsers Chrome and Firefox on Windows 10 or later
Apple browsers Safari on macOS 12 or later
Microsoft browser Edge on Windows 10 or later

Organizations should test managed Windows and macOS devices before deployment, especially when this request contains confidential correspondence. Confirm that browser updates, identity controls, network filtering, and signNow permissions allow the signer to open, complete, and return the document without altering its required certification language.

Signer authentication and certificates

PKI certificates:

PKI-based certificate option

X.509 certificates:

X.509 certificate support

Two-factor authentication:

Two-factor signer verification

SMS OTP:

SMS one-time passcode

ID verification:

Identity checks when configured

Audit evidence:

Signer activity and timestamps

Record-keeping practices for this form

Keep the request, certification, signed copy, and audit evidence together, with retention determined by the record’s underlying business or legal purpose.

Preserve the request and signed copy

Preserve the original request and the signed copy together so reviewers can compare the certified statements, attachments, and signature event. Apply the organization’s records schedule to both files, and document any later correction as a new version rather than replacing the signed record.

Export the audit trail

Export the completed audit trail with the signed document. The record should show signer identity, timestamps, delivery actions, and completion events, allowing an administrator to explain how this specific certification request moved through the workflow.

Limit access to confidential copies

Restrict access to staff who handle the request or its underlying record. Use role-based permissions, protect downloaded files, and review sharing settings before sending a copy containing personal information or confidential business correspondence.

Document electronic consent

For consumer-facing electronic records, provide the ESIGN Act disclosure and confirm electronic access before signing. The disclosure must explain paper-record rights and withdrawal procedures under 15 U.S.C. §7001(c).

Authenticate signer:

Confirm the signer through email access or configured authentication.

Capture timestamp:

Record the signing time and related document actions.

Hash document:

Associate the completed request with integrity evidence.

Seal record:

Seal the signed copy against unauthorized changes.

Log activity:

Preserve the signer’s actions and delivery history.

Retrieve evidence:

Export the audit trail with the completed request.

Troubleshooting this request form

Resolve field, signer, consent, and record-retention questions before relying on a completed certification request.

Upload the original file again and verify that its pages are readable. signNow can detect fillable fields, but a scanned request may require manual placement of certification, date, and signature fields before sending.

The Business plan includes templates and audit trails, while Business Premium adds bulk send and kiosk mode. For one request, add the signer directly; use bulk send only when separate copies require distribution.

Use signNow’s SMS OTP or another configured authentication control, then retain the audit trail with the completed request. ESIGN and UETA focus on intent, attribution, consent, and record reproducibility.

A typed or drawn signature can evidence intent when properly associated with the record. If the request requires notarization or another state-specific formality, signNow’s signature workflow does not replace that legal requirement.

For consumer-facing records, provide the ESIGN disclosure, confirm access to the electronic format, and explain paper-record and withdrawal rights under 15 U.S.C. §7001(c) before signing.

Export the signed PDF and audit trail after completion, then apply the retention schedule for the underlying request. Federal law does not create one universal period for every business 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.