E-Verify

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

E-Verify builds on Form I-9

The employer first completes Form I-9 through the applicable physical or authorized alternative document-examination route. It then creates an E-Verify case using the Form I-9 information.

The E-Verify employer page describes the program as an electronic verification tool. E-Verify does not replace Form I-9, a background check, professional licensure, payer credentialing, or role qualification.

Participation depends on the employer and location

Participation is voluntary for many employers. A covered federal contract with the FAR E-Verify clause, state law, local requirement, or court order may require it. Obligations can vary by hiring site, contract, and worker cohort.

Map every legal entity and hiring site before enrollment. Record why each site participates, its effective date, account access method, program administrators, covered employees, required posters, and recheck trigger.

Cases follow hire rather than applicant screening

The E-Verify user manual says the case follows Form I-9 and generally must be created no later than the third business day after the employee starts work for pay. A late case requires the correct delay reason and immediate correction.

Do not create cases for applicants as a screening tool. Existing employees generally fall outside ordinary new-hire verification unless a covered federal-contractor or other authorized route applies.

Employees choose their I-9 documents

The employee chooses acceptable documentation from Form I-9’s lists. Employers should not request more, different, or specific documents because of citizenship, immigration status, or national origin.

When E-Verify applies and the employee presents a List B identity document, program rules require a document with a photograph. Follow the current manual and preserve the employee’s choice among acceptable options.

A mismatch starts a protected process

A tentative nonconfirmation, often called a mismatch, can result from a data-entry error, name change, agency record, or other issue. It is not a final conclusion about work authorization.

Follow the system prompts, review entered data, privately give the employee the Further Action Notice, obtain the employee’s decision, provide referral information when the employee takes action, and track the case to final resolution.

The Department of Justice IER FAQ states that an employer may not fire, suspend, delay the start, or limit hours because an employee is resolving a mismatch. The employer must await final resolution even when the process takes longer than usual.

Consistency is an anti-discrimination control

Use E-Verify for every employee within the enrolled and required cohort. Selective verification based on citizenship, accent, name, national origin, or perceived immigration status creates serious risk.

Train users to copy Form I-9 information accurately, avoid duplicate cases, protect confidentiality, and escalate mismatches through the prescribed route. Managers need only the operational status necessary to avoid prohibited action.

A fictional new-hire cohort

A fictional multi-site practice locks 18 new hires whose E-Verify case deadline falls during the week. Seventeen cases are created by the deadline: 17 of 18, or 94.4%. One late case is created immediately with the truthful system delay reason and corrective review.

Two cases return a mismatch. Both employees receive private notice. One chooses to take action and continues working while the case remains pending; the other chooses not to take action and the practice follows the final case instructions.

Report timely creation, mismatch notice, employee decision, referral, resolution, and closure as separate states. A case that is still pending cannot be counted as employment authorized or final nonconfirmation.

Control account access and case evidence

Use named accounts, least-privilege roles, timely access removal, multifactor authentication where available, and periodic user review. Restrict Form I-9 and case details from general personnel and scheduling systems.

Preserve the case number, creation time, hire date, result, notices, employee decision, referral date, resolution, closure reason, and operator. Follow the current retention and privacy terms for the system and Form I-9.

Test exceptions before they occur

Create written paths for missing Social Security numbers, acceptable receipts, delayed system availability, corrected Form I-9 data, duplicate cases, rehired employees, remote hires, name differences, federal-contract assignment, and account outage.

The program has specific instructions for several of these situations. A generic “hold start” rule can violate the person’s rights or mishandle the Form I-9 process.

Useful measures

• cases created by deadline divided by cases due
• Further Action Notices delivered correctly divided by mismatches received
• employee decisions recorded divided by notices delivered
• referrals completed divided by employees choosing to take action
• final cases closed correctly divided by final results received
• overdue open cases by count and oldest age

Keep error corrections visible. A high confirmation percentage says little about whether the employer followed the process lawfully.

Questions owners should ask

• Why does each entity or site participate?
• Which employee cohort is covered?
• Was Form I-9 completed before case creation?
• Are cases created by the third business day?
• Can managers identify prohibited adverse action?
• Are notices private and accessible?
• Who owns pending cases, closure, access, and audit evidence?