Download signNow app
4.7 / 5 rating on

Request During Form

Use a Request During template to make your document workflow more streamlined.

What Request During Form is

Request During Form is a generic document workflow used to ask another person for information, approval, or a signature; its exact legal purpose depends on the document’s issuer and contents. In signNow, upload the file, review automatically detected fillable fields, assign fields to the intended recipient, and send an invitation or signing link. The recipient reviews and signs electronically, while signNow records timestamps, actions, and document history in an audit trail. ESIGN and UETA can support electronic records when intent, consent, attribution, and reproducible retention requirements are met.

Who uses Request During Form

Financial services

A finance or accounts-payable team can send Request During Form for supplier information, approvals, or invoice-related records, assigning fields to the vendor and internal reviewer. The team should verify tax requirements separately because this generic form name does not identify an IRS form or filing deadline.

Healthcare teams

A healthcare organization can use Request During Form for administrative consent or intake records when the workflow protects health information. HIPAA-covered workflows require appropriate safeguards and a business associate agreement with signNow, while clinical and state requirements remain separate.

How Request During Form works

signNow turns the uploaded Request During Form into a controlled signing workflow from preparation through retention.

  • Upload document: Upload the Request During Form
  • Check fields: Review auto-detected fillable fields
  • Send for signature: Assign fields and send invitations
  • Complete and store: Store the signed record with audit evidence

Steps to complete Request During Form

Follow this sequence to prepare, send, complete, and preserve Request During Form in signNow.

  • Upload:

    Upload the correct file
  • Inspect:

    Review detected fields
  • Assign:

    Assign recipient responsibilities
  • Send:

    Send the signing invitation
  • Store:

    Download 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.

Signer authentication for Request During Form

Email authentication:

Email links identify the intended recipient

SMS authentication:

SMS OTP adds a second factor

Two-factor authentication:

Two-factor authentication strengthens signer access

PKI signatures:

PKI supports certificate-based digital signatures

X.509 certificates:

X.509 certificates support document integrity

Identity verification:

ID verification can strengthen identity proofing

Key features for Request During Form

signNow supports the Request During Form workflow from upload and field assignment through electronic signature, audit evidence, storage, and connected business processing.

Field detection

Upload Request During Form and review automatically detected fields before assigning each required value to the correct signer, reducing manual setup errors.

Digital delivery

Send the prepared Request During Form by email or signing link, allowing recipients to review and complete assigned fields without exchanging paper copies.

Audit evidence

Capture typed or drawn signatures, timestamps, signer actions, and document history in a record that supports later workflow review.

Reusable templates

Use templates for repeated Request During Form workflows so teams can preserve field placement, signer roles, and approval order across future sends.

Mobile signing

Let recipients complete Request During Form through signNow web and mobile experiences when work occurs away from an office or desktop.

Business integrations

Connect completed records with systems such as Salesforce, NetSuite, Google Drive, Box, or Microsoft 365 for controlled downstream processing.

Best practices for Request During Form

Accurate field assignment, documented consent, and controlled records make Request During Form workflows easier to review and defend.

Verify every field before sending

Upload the correct Request During Form version before placing fields. Review every auto-detected field, confirm required signer information, and test the completed document with a non-production recipient before sending it to customers or external parties.

Assign fields to the correct signer

Use signer roles that match the Request During Form workflow. Assign each required field to the correct person, check signing order, and prevent recipients from editing information that the sender must control.

Document electronic consent clearly

Capture consent before electronic signing when the recipient is a consumer. Provide the required ESIGN disclosure, confirm electronic-record access, and retain evidence showing the signer intended to sign the Request During Form.

Preserve the signed record and audit trail

Keep the completed Request During Form with its audit trail. Export the signed record and completion certificate, restrict access to authorized users, and apply the retention period required for the underlying business record.

Recommended Request During Form setup

Configure the Request During Form workflow around signer identity, field ownership, audit evidence, encryption, and the retention rule governing the underlying record.

SettingRecommendation
Authentication methodEmail links with SMS OTP
Signature typeTyped or drawn electronic signature
Audit trailRetain audit trail with signed PDF
Document retentionFollow the underlying record rule
EncryptionTLS 1.2/1.3 and AES-256

Integrations for Request During Form

Connect Request During Form with CRM, ERP, productivity, and storage systems to move signed records into the business workflow without rekeying information.

Salesforce
Procore
Zapier
Microsoft Teams
Hub spot
Box
Microsoft

Platform requirements for Request During Form

Request During Form can be prepared in supported versions of Chrome, Firefox, Safari, or Edge on Windows and macOS. signNow also provides mobile apps for iOS and Android, with TLS-protected access for browser and app sessions.

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

Organizations should manage browser updates, mobile app permissions, and device access before distributing Request During Form. Regulated teams should also confirm SSO, API, certificate, and long-term validation requirements for their environment, because those controls depend on the selected signNow plan and the organization’s compliance policy.

Audit trail actions for Request During Form

The audit trail records evidence around the Request During Form signing event, separate from the document’s initial setup and field placement.

01

Authenticate signer:

Records the authentication event
02

Timestamp action:

Captures signing date and time
03

Record activity:

Logs signer and document events
04

Hash document:

Preserves document history
05

Seal record:

Creates tamper-evident completion evidence
06

Export audit trail:

Allows audit-trail retrieval and export
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

Request During Form troubleshooting

Use these answers to resolve field, signer, consent, security, plan, and record-retention questions before sending Request During Form.

Upload the correct Request During Form file and inspect signNow’s auto-detected fields. If fields are missing, add them manually, assign each field to a signer, and run a test invitation before sending the production document.

The signNow Business plan includes templates, audit trails, mobile apps, and legally binding eSignatures at $8/user/month when billed annually. Business Premium adds bulk send at $15/user/month annually; choose it when sending the same form repeatedly.

For a consumer-facing Request During Form, provide the ESIGN disclosure, explain the right to receive paper records, confirm electronic access, and explain withdrawal procedures. These requirements come from 15 U.S.C. §7001(c), not from signNow.

signNow encrypts data in transit with TLS 1.2/1.3 and at rest with AES-256. HIPAA-covered Request During Form workflows require a business associate agreement, while the organization remains responsible for its own access and retention policies.

If a recipient cannot open the invitation, verify the email address, resend the signNow invitation, or provide a controlled signing link. If SMS authentication is enabled, confirm the phone number and delivery settings before changing identity controls.

A signed Request During Form should be retained with its audit trail and completion evidence. The correct period depends on the underlying record, contract, or industry rule; signNow does not determine the legally required retention period.

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.