Is an electronic checklist legally binding?

Yes. Electronic signatures and records are generally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted; ensure intent, consent, attribution, and retention are documented to meet the four ESIGN elements.

Do I need notarization for screening documents?

Typically no. Most screening checklists do not require notary acknowledgement. Notarization is only necessary if a specific affidavit or legal attestation is required by contract or a state law.

Can I accept signatures via a document platform?

Yes. Use a platform that provides an audit trail with timestamp, signer identity, and IP details. For higher-assurance needs consider multi-factor or certificate-based authentication.

What if a candidate refuses background checks?

If consent is refused, you cannot lawfully perform the check. Document denial and apply your policy consistently; for regulated roles, refusal may prevent hiring or access.

How are remote notarizations treated?

Remote online notarization (RON) rules vary by state; some states allow permanent RON while others impose conditions. Verify with the applicable state notary authority before relying on RON.

How long must I keep completed checklists?

Retention depends on applicable laws and internal policy: IRS records three years (IRC §6501(a)), HIPAA six years (45 CFR §164.530(j)), and company policy may extend retention for litigation or audit reasons.

Electronic Signature
Templates
Miscellaneous
IT Screening Checklist

IT Screening Checklist

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

IT Screening Checklist

Client Name: Service Provider Name:

RECITALS

WHEREAS, Client Name: seeks to engage Service Provider Name: to conduct an information-technology screening and preliminary security assessment of Client systems and operational controls; and

WHEREAS, Service Provider represents that it has the professional expertise, technical capability, and personnel necessary to perform the screening, to identify technical and administrative gaps, and to provide remediation recommendations consistent with industry standards and Client requirements; and

WHEREAS, the parties desire to document the scope, schedule, payment terms, confidentiality obligations, and checklist-based deliverables for the screening engagement as set forth below.

SCOPE OF WORK

Detailed Scope

IT SCREENING CHECKLIST

Inspector Name: Company:

Date of Screening:

Please complete each item. Check box if verified; provide notes where indicated.

Inventory and Configuration

Hardware inventory completed

Software and Patch Review

Software versions reviewed and documented

Access and Identity Controls

Administrative and privileged accounts reviewed
Multi-factor authentication presence verified

Network and Vulnerability

Network ports and services scanned
Vulnerability scan completed

Endpoint and Backup

Antivirus/endpoint protection present and updated
Backup processes verified and tested

Data Handling and Compliance

Data classification and access policies reviewed
Applicable compliance controls checked (e.g., contractual, regulatory)

RESULTS SUMMARY & RECOMMENDATIONS

Overall Risk Rating (select highest applicable)

Low Medium High

Summary of Findings and Remediation Recommendations

PAYMENT TERMS

Total Fee Payment Schedule Late Payment

TERM AND TERMINATION

This agreement commences on Start Date: and terminates on End Date: , unless earlier terminated as provided herein.

Either party may terminate for convenience upon Notice Period: days' prior written notice. Termination for material breach is effective immediately if a breach is not cured within thirty (30) days after written notice.

CONFIDENTIALITY

Each party shall treat as Confidential Information any nonpublic information disclosed in connection with the screening, including system architecture, credentials, vulnerability data, and remediation plans. Confidential Information shall not be disclosed to third parties except to the extent required by law or as necessary to perform the Scope of Work, and only after the recipient ensures that such third parties are bound under confidentiality obligations at least as protective as those herein. Confidentiality obligations shall survive termination of this agreement for a period of three (3) years.

GOVERNING LAW

This agreement shall be governed by and construed in accordance with the laws of the jurisdiction specified below, excluding its choice-of-law rules.

Governing Jurisdiction

ENTIRE AGREEMENT

This document, including the Scope of Work and Screening Checklist, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, and communications, whether oral or written. Any amendment must be in writing and signed by authorized representatives of both parties.

LIMITATION OF LIABILITY (SUMMARY)

Except for liability arising from willful misconduct or gross negligence, each party's aggregate liability for claims arising out of or related to this agreement shall not exceed the total fees paid by Client to Service Provider under this agreement for the screening described herein.

Client Printed Name:

By:

Date:

Service Provider Printed Name:

By:

Date:

What an IT Screening Checklist Is and When to Use It

An IT Screening Checklist is a standardized form used to verify technical access, security clearances, and compliance prerequisites before granting network or system privileges to an individual or vendor. It consolidates identity details, device authorization, background-check consent, and role-based access needs into a single record. Organizations use it for new hires, contractors, temporary staff, or third-party vendors to document eligibility, capture approvals, and create an auditable trail that supports onboarding, access provisioning, and later audits.

Why a Formal Checklist Adds Value

A consistent IT Screening Checklist reduces security gaps, speeds onboarding decisions, and produces a defensible audit trail for compliance and access reviews.

Who Typically Completes or Reviews the Checklist

Collaboration among these roles ensures identity, technical access, and contractual safeguards are verified before privileges are issued.

Hiring manager — initiates the checklist, defines role access needs, and confirms job responsibilities.
IT security or IAM team — validates technical requirements, approves device and network access.
Vendor management or procurement — confirms contractual terms, insurance, and third-party risk assessments.

Essential Sections to Include in a Professional Checklist

A complete IT Screening Checklist groups identity, authorization, and compliance items to make review and audit straightforward.

Identity

Full legal name, government ID type and number, date of birth, and a copy of photo ID to support identity verification and auditability.

Contact Details

Work and personal phone numbers, corporate and personal email addresses, and physical address for credentialing and emergency contact.

Role & Access

Requested systems, minimum privilege levels, required administrative rights, and justification to align access with job duties.

Background Checks

Consent for background checks, scope (criminal, credit, education), vendor performing check, and expected turnaround times.

Device Authorization

Approved devices, MDM enrollment status, OS versions, and required security controls such as full-disk encryption and antivirus.

Approvals & Audit

Sign-off fields for hiring manager, security lead, and HR plus date stamps and an audit log to record decisions and changes.

Step-by-Step: Completing the IT Screening Checklist

Follow these sequential steps to collect required data, obtain approvals, and document the decision for provisioning.

01

Prepare Request: Hiring manager defines role and access scope.
02

Collect Identity: Requester uploads ID and contact details.
03

Authorize Checks: Obtain written consent for background screening.
04

Approve & Provision: Security signs off and IT grants access.

How to Configure an Online Screening Workflow

Set template fields, routing order, and authentication to match your security and HR policies before sending.

Template	Create a reusable checklist template in your document system.
Routing Order	Define signer sequence: requester → HR → security → IT.
Authentication	Use email plus SMS or SSO for higher-assurance signers.
Reminders	Configure automated reminders for outstanding actions.
Attachments	Allow uploads of ID, contracts, and proof of training.

Where Completed Checklists Should Be Sent

Route the finalized checklist to the teams that need it and store a copy in the secure records repository.

HR Records: Permanent personnel file storage for compliance.
Security Team: Access approvals and incident history reference.
IT Provisioning: Used to create accounts and set permissions.
Vendor Management: Third-party checks and contract compliance tracking.

Digital Submission and Integration Considerations

Integrations with HR systems, identity platforms, and cloud storage reduce duplication and hold a single source of truth for audits and provisioning.

File formats: PDF, DOCX, and scanned images
Integrations: SSO, HRIS, and IAM connectors
Security: TLS and AES-256 encryption

Typical Timelines and Processing Expectations

Set realistic deadlines for each screening step to align hiring needs with compliance checks.

Initial Submission Deadline:

Requester should submit checklist at offer acceptance.

Background Check Turnaround:

Expect 2–7 business days depending on scope.

ID Verification:

Complete within 24–48 hours of submission.

Final Approval:

Security and HR sign-off typically within 3 business days.

Onboarding Start:

Provision access only after all approvals are recorded.

Common Mistakes to Avoid

Submitting incomplete identity documents slows verification and may require resubmission or manual follow-up with the candidate.
Requesting excessive privileges without justification increases risk and often triggers escalation or denial by security teams.
Using inconsistent field formats (dates, names) causes data mismatches and failure in automated checks or background vendor integrations.
Failing to capture explicit consent for background checks can legally prevent screening and create compliance gaps.

Primary Risks and Compliance Consequences

Unauthorized Access: Data breach exposure and operational impact.

Regulatory Fines: Penalties for HIPAA or sector violations.

Employment Claims: Wrongful access decisions can trigger litigation.

Vendor Liability: Contract breaches and indemnity obligations.

Failed Audits: Audit findings increase remediation costs.

Reputational Harm: Customer trust erosion after incidents.

Required Data Elements for Screening Records

Full Name: Exact legal name

Date of Birth: MM/DD/YYYY

Government ID: ID type and number

Contact Info: Email and phone

Access Scope: Systems and privilege levels

Consent Record: Signed background consent

Realistic Use Scenarios for an IT Screening Checklist

These examples show how checklists prevent common onboarding delays and support audit evidence.

Contractor Onboarding

A midsize firm required access for a contractor to a dev environment; manual checks delayed start by a week

The checklist forced a single submission with ID, device details, and consent
Final approvals arrived within 48 hours, enabling timely provisioning and billing accuracy while documenting risk decisions.

Third-Party Vendor

An external vendor needed API keys and database read access; stakeholders disagreed on scope initially

The checklist captured requested endpoints, justification, and attorney review
With approvals recorded, the vendor received limited credentials, and the security team scheduled quarterly reviews.

Frequently Asked Questions About the IT Screening Checklist

Answers to common questions about legality, signatures, notarization, and retaining completed checklists for audits.

Need help? Contact support

Is an electronic checklist legally binding?
Yes. Electronic signatures and records are generally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted; ensure intent, consent, attribution, and retention are documented to meet the four ESIGN elements.
Do I need notarization for screening documents?
Typically no. Most screening checklists do not require notary acknowledgement. Notarization is only necessary if a specific affidavit or legal attestation is required by contract or a state law.
Can I accept signatures via a document platform?
Yes. Use a platform that provides an audit trail with timestamp, signer identity, and IP details. For higher-assurance needs consider multi-factor or certificate-based authentication.
What if a candidate refuses background checks?
If consent is refused, you cannot lawfully perform the check. Document denial and apply your policy consistently; for regulated roles, refusal may prevent hiring or access.
How are remote notarizations treated?
Remote online notarization (RON) rules vary by state; some states allow permanent RON while others impose conditions. Verify with the applicable state notary authority before relying on RON.
How long must I keep completed checklists?
Retention depends on applicable laws and internal policy: IRS records three years (IRC §6501(a)), HIPAA six years (45 CFR §164.530(j)), and company policy may extend retention for litigation or audit reasons.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now