Download signNow app
4.7 / 5 rating on

720 Request Form

Use a 720 Request Form 2019 template to make your document workflow more streamlined.

What the 720 Request Form is

The 720 Request Form is a document users can prepare, complete, and sign through a controlled electronic workflow when the underlying transaction permits electronic signatures. In signNow, the sender uploads the form, reviews automatically detected fillable fields, adds any missing text or signature fields, and routes it to designated recipients. Signers review the document, provide the requested information, and sign electronically. The completed form can be downloaded with its audit trail, which records signing events and supports later review. Legal suitability depends on the transaction, signer consent, and applicable U.S. law.

Who uses 720 Request Form

Business operations

Business teams can use the 720 Request Form for internal approvals, customer records, or other transactions where the form’s parties and fields are known. Review the underlying instructions before routing it electronically.

Regulated workflows

Legal, financial-services, healthcare, and administrative teams can adapt the workflow to their specific records, but industry rules may require additional disclosures, authentication, retention, or a HIPAA business associate agreement.

Who benefits from 720 Request Form workflows

720 Request Form workflows fit individuals and teams that need consistent completion, signature collection, and record handling across U.S. business operations.

  • A solo financial-services practitioner can prepare a 720 Request Form, collect a client signature remotely, and preserve the completed record without coordinating an in-person appointment.
  • A healthcare office can route a 720 Request Form through a controlled workflow when the document contains protected health information, subject to a signed HIPAA business associate agreement.
  • An enterprise operations team can use reusable templates, delegated sending, and audit trails to process 720 Request Form records consistently across departments and locations.

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

How 720 Request Form works online

The signNow workflow moves the 720 Request Form from an uploaded file to a signed, reviewable record.

  • Upload: Upload the form and inspect detected fields.
  • Assign: Assign fields to each intended signer.
  • Send: Send invitations through the selected workflow.
  • Archive: Store the completed record 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.

Complete 720 Request Form in signNow

Use this sequence to prepare the form, collect required signatures, and preserve evidence of completion.

  • Upload form:

    Upload the 720 Request Form PDF to signNow.
  • Check fields:

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

    Add recipients and send the form.
  • Store records:

    Download the signed form and audit trail.

Find and fill out the correct 720 request form

airSlate SignNow helps you fill in and sign documents in minutes, error-free. Choose the correct version of the editable PDF form from the list and get started filling it out.

VersionsForm popularityFillable & printable
2016 CA GV-720 [2016-01-01] 20194.8 Satisfied (1645 Votes)
2016 CA GV-720 [2016-01-01] 20164.6 Satisfied (987 Votes)

How the 720 Request Form audit trail works

The audit trail connects signer identity, document integrity, and event history so the completed 720 Request Form can be reviewed later.

01

Signer authentication:

Authentication evidence records the signer’s access method and verification event.
02

Timestamp capture:

Timestamp capture records when each signer opened and completed the form.
03

Document hashing:

Document hashing links the completed file to its recorded document state.
04

Tamper-evident seal:

Tamper-evident sealing shows whether the signed file changed afterward.
05

Action logging:

Action logging records views, invitations, signatures, and completed-form events.
06

Audit-trail export:

Export retrieves the audit trail with the completed 720 Request Form.

Signer authentication options for 720 Request Form

PKI signatures:

PKI supports certificate-based digital signatures

X.509 certificates:

X.509 certificates identify signing credentials

Two-factor authentication:

Two-factor authentication adds a second verification step

SMS OTP verification:

SMS OTP verifies a signer’s phone

ID verification:

ID verification strengthens signer identity evidence

Signing event records:

Audit trails preserve authentication and signing events

Privacy and disclosure risks to address

  • Sending the 720 Request Form to the wrong recipient can expose personal or business information before access controls are reviewed.
  • Missing consent language can weaken evidence that a signer agreed to conduct the transaction electronically under ESIGN requirements.
  • Overly broad folder permissions can let unauthorized users view, download, or forward completed 720 Request Form records.
  • Failing to export the audit trail can make it harder to demonstrate signer identity, timing, and document integrity during a dispute.

Best practices for completing the form

Careful field review, recipient control, evidence preservation, and record-specific retention reduce avoidable errors when processing 720 Request Form documents.

Review every detected field

Upload the final 720 Request Form version first, then inspect every detected field. Add required signatures, dates, initials, and text fields manually when the source PDF does not expose them reliably.

Confirm recipient routing

Name recipients in signing order and verify each email address before sending. Use role-based routing when different people must complete defined sections of the 720 Request Form.

Preserve completion evidence

Export the completed document and audit trail together after all required signatures appear. Store both records in a restricted location with access limited to the personnel handling this form.

Set a documented retention rule

Apply the retention period required for the underlying record, not a blanket platform setting. For tax records, consult IRC §6501(a) and the applicable federal or state requirements before deletion.

Troubleshooting 720 Request Form workflows

Resolve field-detection, signer-access, consent, plan-limit, and compliance questions before treating a 720 Request Form as complete.

If the uploaded 720 Request Form has no detected fields, review the PDF structure and add signature, date, and text fields manually before sending. signNow supports reusable templates for recurring versions, while the Business plan includes templates and audit trails for completed documents.

If a signer cannot open the invitation, confirm the email address, resend the request, or create a signing link when appropriate. For sensitive 720 Request Form records, use stronger authentication such as SMS verification rather than distributing an unrestricted link.

If a required signature is missing, reopen the document status and identify the incomplete recipient or field. Do not treat an unsigned 720 Request Form as complete; send a reminder or correct the routing order before archival.

For consumer-facing records, ESIGN requires disclosure of the right to receive paper, electronic-access capability, and withdrawal procedures under 15 U.S.C. §7001(c). Add the required disclosure before requesting a 720 Request Form signature when that rule applies.

The Business plan is listed at $8 per user per month with annual billing and includes audit trails. Its subscription plans include 100 signature invites per user per year; review invite usage before scaling 720 Request Form volume.

If a completed 720 Request Form contains protected health information, signNow identifies HIPAA compliance as requiring a business associate agreement. Confirm the BAA and organizational safeguards before using the workflow for PHI.

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.