Download signNow app
4.7 / 5 rating on

Request Background Check

Use a Request Background Check 2019 template to make your document workflow more streamlined.

What Request Background Check is

Request Background Check is an authorization document used to obtain an individual’s permission before a background screening process. It may identify the requester, the subject, the screening purpose, required disclosures, consent language, signature, and date. With signNow, upload the document, review automatically detected fields, assign consent and signature fields, send it to the signer, and retain the completed PDF with its audit trail. Electronic execution can satisfy ESIGN and applicable state electronic-transactions law when intent, consent, attribution, and record retention are established. Screening organizations must separately follow FCRA and state privacy requirements.

Documents and audiences for this request

Human resources

Human resources departments use signed background-check requests, authorization disclosures, and candidate consent records before screening. signNow can route these documents to applicants, preserve the completion record, and support controlled access. Employers must use legally appropriate disclosure and authorization language and follow applicable FCRA and state requirements.

Screening coordinators

Property managers and staffing organizations use applicant consent forms and screening authorizations before requesting reports. A signNow template standardizes signature placement and records the completed request, while authorized reviewers can retrieve the audit trail. The organization remains responsible for privacy notices, lawful purpose, and applicable state restrictions.

How the request workflow works

The signNow workflow turns a prepared Request Background Check into a traceable authorization record without changing the organization’s screening responsibilities.

  • Upload request: Upload the Request Background Check document to signNow.
  • Prepare fields: Review auto-detected fields and add missing consent fields.
  • Route signer: Route the request to the applicant or authorized signer.
  • Preserve evidence: Store the signed PDF and audit trail together.

Complete the request in signNow

Use this sequence to prepare, route, sign, and preserve a Request Background Check with clear completion evidence.

  • Upload form:

    Upload the Request Background Check PDF to signNow.
  • Review fields:

    Let signNow detect fillable fields, then review each placement.
  • Assign signer:

    Assign consent, signature, date, and disclosure fields to the signer.
  • Send request:

    Send the request by email or generate a secure signing link.
  • Store record:

    Confirm completion and retain the signed request 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.

What the audit trail records

The audit trail documents the signing event behind Request Background Check, helping reviewers connect the signer, actions, timestamps, and completed record.

01

Authenticate signer:

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

Capture timestamps:

Captures signing time, access activity, and document actions.
03

Link document:

Associates the completed Request Background Check with its audit history.
04

Seal record:

Preserves evidence of field completion and signer intent.
05

Retrieve certificate:

Maintains the signed PDF and completion certificate for retrieval.
06

Export audit trail:

Allows authorized users to export the audit trail for review.

Recommended workflow configuration

Configure Request Background Check for identifiable signers, traceable completion, protected records, and controlled access to screening information.

SettingRecommendation
Authentication methodEmail link with SMS verification
Signature typeTyped or drawn electronic signature
Audit trailEnabled for every completed request
Document retentionSix years for PHI records under HIPAA 45 CFR 164.530(j)
EncryptionTLS 1.2/1.3 and AES-256 protection

Find and fill out the correct request background check

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
2013 OH Request for Copy of Background Check [2013-12-04] 20194.8 Satisfied (5601 Votes)
2013 OH Request for Copy of Background Check [2013-12-04] 20134.8 Satisfied (176 Votes)

Connect the request to business systems

Connect Request Background Check workflows with CRM, ERP, cloud storage, HR, and project systems to route signed records without rekeying information.

Salesforce
Procore
Zapier
Microsoft Teams
Hub spot
Box
Microsoft

Security for sensitive request records

Transport encryption:

TLS 1.2/1.3 in transit

Storage encryption:

AES-256 at rest

Security assurance:

SOC 2 Type II certified

Information security:

ISO 27001 certified

Health information:

HIPAA compliant with BAA

Electronic signatures:

ESIGN and UETA compliant

Privacy and disclosure pitfalls

  • Including a full Social Security number when the approved screening process requires fewer identifiers increases exposure if the completed request is misdirected.
  • Omitting the required disclosure or authorization language can leave the screening request incomplete even when the signer successfully signs it.
  • Sending a completed request to an unintended recipient can disclose employment or tenant information; verify signer email addresses before delivery.
  • Keeping the signed request without its audit trail weakens the record needed to show signer attribution, intent, and completion history.

Best practices for the request

Accurate authorization language, limited disclosure, documented retention, and plan-aware routing make Request Background Check workflows easier to review.

Use approved authorization language

Use the organization’s approved disclosure and authorization language rather than adding unsupported statements to the template. Assign every consent, signature, and date field to the correct signer, then test the completed PDF before sending. FCRA duties and state requirements remain with the requesting organization.

Limit sensitive information exposure

Collect only information necessary for the screening request and restrict access to authorized personnel. In signNow, use role-based routing and preserve the completed document with its audit trail. Do not treat a signature platform as a substitute for lawful notice, consent, or permissible-purpose analysis.

Apply the correct retention rule

Export or retain the completed Request Background Check and audit trail under your organization’s approved records policy. If the record contains PHI, HIPAA requires six years from creation or the last effective date under 45 CFR §164.530(j). Other background-check records may follow state or contractual rules.

Match the plan to volume

Use signNow’s Business plan for templates and audit trails, or select Enterprise when advanced signer authentication is required. Confirm the plan’s included 100 signature invites per user per year before high-volume sending, and review overage terms before launching a batch.

Request Background Check troubleshooting questions

Resolve field, signature, plan, authentication, and privacy questions before sending a Request Background Check through signNow.

Upload the Request Background Check PDF to signNow and use field detection before placing signer fields manually. The Business plan includes templates and audit trails; Business Premium adds bulk send. For sensitive information, configure access controls and confirm HIPAA requirements, including a BAA when PHI is involved.

A typed or drawn signature can satisfy ESIGN and UETA when intent, consent, attribution, and record retention are established. signNow Business provides legally binding eSignatures and an audit trail. If the request contains consumer records, provide the electronic-record disclosure required by 15 U.S.C. §7001(c).

A signer can open the email invitation or signing link without creating a signNow account in many workflows. If stronger identity assurance is needed, use available authentication controls, such as SMS verification where configured. Keep the completed document and audit trail together for attribution evidence.

Business and Business Premium plans include 100 signature invites per user per year, with overage fees applying after the included amount. The Site License uses $1.50 per signature invite and is designed for usage-based volume. Review the current plan terms before sending large batches.

The Business plan includes audit trails, while Enterprise adds advanced signer authentication and other controls. signNow encrypts data in transit with TLS 1.2/1.3 and at rest with AES-256. HIPAA workflows require a BAA, and regulated teams should verify their configuration.

For a request containing background-check information, limit document access to authorized recipients and avoid unnecessary identifiers. signNow supports role-based workflows, audit trails, and secure storage features, but your organization remains responsible for lawful consent, FCRA procedures, privacy notices, and retention decisions.

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.