Download signNow app
4.7 / 5 rating on

Information Requests

Use a Information Requests template to make your document workflow more streamlined.

What information requests do

Information Requests collect defined details, approvals, or signatures from a named recipient in a trackable document workflow. With signNow, a sender uploads the request, reviews or adds fillable fields, identifies the recipient, and sends it electronically. The recipient opens the document, enters the requested information, reviews the record, and signs when required. signNow records delivery, viewing, signing, timestamps, and other audit events with the completed file. ESIGN and UETA generally recognize qualifying electronic records and signatures, subject to applicable exceptions and transaction-specific requirements.

Documents and audiences for requests

Real estate

Real estate teams can use Information Requests to gather applicant details, lease-related responses, or approvals before routing the completed file for signature and storage.

Healthcare

Healthcare organizations can use Information Requests for administrative patient forms when HIPAA safeguards, consent requirements, and access controls are addressed.

Who benefits from information requests

Information Requests can support individual contributors, regulated practices, and larger operations teams when the document’s purpose and required responses are clearly defined.

  • Solo consultants can send Information Requests to clients for structured answers, approvals, and signatures without managing paper copies or separate email threads.
  • Healthcare practices can use Information Requests for patient-facing administrative forms when privacy controls, consent records, and HIPAA obligations are addressed.
  • Enterprise operations teams can standardize recurring Information Requests with shared templates, delegated sending, role-based access, and centralized audit evidence.

These tasks are executed by both individual contributors and centralized administrators depending on organizational policy and required controls.

Features for information requests

Information Requests workflows can combine field preparation, signer routing, electronic signatures, audit evidence, templates, and connected storage in one process.

Field detection

Upload an Information Requests file and let signNow identify fillable areas before you review names, dates, responses, and signature fields.

Signer routing

Route each request to the intended recipient by email or signing link, keeping the document workflow separate from ordinary email attachments.

Electronic signing

Collect typed, drawn, or uploaded signatures while recording the signer’s intent and completing the request electronically.

Audit trail

Keep the signed Information Requests document with timestamps, signer actions, and delivery details for later review.

Reusable templates

Use reusable templates when the same Information Requests document is sent repeatedly to customers, vendors, or internal teams.

System connections

Connect completed requests with Salesforce, Microsoft 365, Google Drive, or other named systems used for document operations.

Complete information requests online

Use signNow to prepare the document, route it to the right signer, and preserve the completed request with its signing history.

  • Upload document:

    Upload the Information Requests document to signNow.
  • Check fields:

    Review detected fields and add missing signer fields.
  • Send request:

    Enter signer details and send the request.
  • Sign online:

    Signer reviews the request and adds an e-signature.
  • Archive record:

    Store the completed document with its audit trail.
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 information request setup

Configure the workflow around signer identity, signature evidence, document protection, and the retention rule applicable to each Information Requests record.

SettingRecommendation
Authentication methodEmail link with SMS verification
Signature typeTyped or drawn electronic signature
Audit trailCapture timestamps and signer actions
Document retentionApply the governing record rule
EncryptionTLS 1.2/1.3 and AES-256

How the audit trail records requests

The audit trail documents who handled an Information Requests file, what happened during signing, and how the completed record can be reviewed or exported.

01

Authenticate signer:

Records the signer’s email or configured authentication event.
02

Capture timestamp:

Captures signing time and each recorded action.
03

Hash document:

Associates the completed request with document integrity data.
04

Seal record:

Preserves changes through a tamper-evident completion record.
05

Track activity:

Logs delivery, viewing, signing, and completion events.
06

Retrieve evidence:

Exports the audit trail with the signed document.

Platform requirements for information requests

Prepare and sign Information Requests through signNow on Windows or macOS using Chrome, Firefox, Safari, or Edge. The signNow mobile apps support iOS and Android, allowing recipients to review and sign from supported mobile devices.

  • Browsers Chrome, Firefox, Safari, Edge
  • Desktop systems Windows and macOS desktops
  • Mobile systems iOS and Android mobile apps

Organizations using Information Requests should manage access on approved devices, configure user provisioning, and confirm browser security policies before sending. Teams needing connected workflows can use API access or named integrations, while regulated deployments should configure authentication, retention, and certificate requirements according to the applicable record policy.

Connect information requests to business systems

Send completed Information Requests into Salesforce, Microsoft Dynamics 365, NetSuite, Google Drive, Box, or other connected systems while preserving the document workflow for review.

Salesforce
Procore
Zapier
Microsoft Teams
Hub spot
Box
Microsoft

Record-keeping practices for requests

Retention and record-keeping depend on what an Information Requests document records, who uses it, and which rule governs the underlying transaction.

Classify each completed request

Decide whether an Information Requests file is a tax, employment, healthcare, contract, or general business record before setting its retention period. Apply the controlling rule and any longer state or organizational requirement, rather than assigning one universal period to every completed request.

Preserve the audit evidence

Export the signed Information Requests document together with its audit trail, completion certificate, and relevant delivery history. Keep the files linked by a stable internal identifier so reviewers can understand the transaction without reconstructing events from separate email messages.

Protect sensitive request records

Restrict access to Information Requests containing personal, financial, or health information through role-based permissions and approved storage locations. Review sharing permissions periodically, remove unnecessary access, and document any transfer required by the organization’s records policy.

Review templates before reuse

Use signNow templates only after confirming that field labels, signer order, required responses, and retention instructions match the current Information Requests workflow. Review templates when the underlying business process or governing legal requirement changes.

Security for information requests

Encryption controls:

TLS 1.2/1.3 and AES-256

Security certification:

SOC 2 Type II certified

Information security:

ISO 27001 certified

Health data protection:

HIPAA compliant with BAA

Electronic signature law:

ESIGN and UETA compliant

Privacy frameworks:

GDPR and CCPA compliant

Challenges when managing requests

  • Unclear request ownership can send Information Requests to the wrong recipient or leave required responses without an accountable reviewer.
  • Missing signer, date, or response fields can make a completed Information Requests document difficult to interpret or validate.
  • Email-only routing may provide insufficient assurance when the request contains sensitive personal, financial, or health information.
  • Failure to preserve the signed file and audit trail can weaken the record’s usefulness during an internal review or dispute.

Limits and state-specific formalities

Notary required

State notarization

Excluded documents

Wills and codicils

Court exclusion

Family law decrees

Deed formalities

Real-estate deeds

Notice exclusion

Primary residence notices

Legal standing of information requests

For U.S. business transactions, an Information Requests record may be enforceable when the signer intends to sign, consents to electronic records, can be identified, and the record remains reproducible. ESIGN, 15 U.S.C. ch. 96, and UETA generally support that framework. Wills, codicils, family law decrees, and certain court filings remain excluded.

Why teams look for DocuSign alternatives

Troubleshooting information requests

Resolve field, plan, privacy, and legal-signature questions by checking the document setup, selected signNow plan, and applicable U.S. requirements.

Upload the Information Requests file again, then review whether required fields were detected. signNow Business includes templates and audit trails; manually add any missing response, date, or signature fields before sending.

The signNow Business plan is listed at $8/user/month with annual billing, while month-to-month pricing is $20/user/month. Confirm the selected billing term and plan before assigning users or preparing recurring request workflows.

Bulk sending is included with Business Premium, listed at $15/user/month with annual billing. If a recurring Information Requests workflow requires bulk send, verify the plan rather than assuming Business includes that feature.

HIPAA compliance requires a business associate agreement with signNow. Confirm that the Information Requests workflow handles protected health information, execute the BAA where required, and apply appropriate access and retention controls.

ESIGN and UETA generally support electronic signatures when intent, consent, attribution, and record reproduction requirements are met. Consumer-facing records may also require the disclosure and access steps in 15 U.S.C. §7001(c).

The signNow Site License is listed at $1.50 per signature invite and is designed for usage-based volume with unlimited users. Subscription plans include 100 signature invites per user per year, with overage fees.

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.