I-9 and E-Verify for Federal Contractors: Getting the Timing Right

A contractor's new network engineer clears her background investigation, signs her offer letter on a Friday afternoon, and reports to the government site Monday morning. By Wednesday, the FSO realizes nobody initiated her E-Verify case. The three-business-day clock started Monday. It is now day three. The case gets submitted late, a Tentative Nonconfirmation (TNC) surfaces because of a name discrepancy, and the employee is locked out of the facility while the referral process runs. The project is short-staffed for two weeks.

That scenario is not hypothetical. It plays out regularly at firms that treat I-9 and E-Verify as an HR afterthought rather than a sequenced compliance operation. For federal contractors, the stakes are higher than for commercial employers: FAR E-Verify clauses, facility access dependencies, and cleared-personnel timelines compress every margin for error.

The Regulatory Stack Federal Contractors Actually Face

Most employers know they must complete Form I-9 for every new hire. Federal contractors subject to FAR 52.222-54 carry an additional layer: they must enroll in E-Verify and run every new employee hired after the contract's effective date through the system, plus every employee assigned to work on a covered federal contract. That second category, the "existing employee assigned to a contract," is where firms most often miscalculate.

The FAR clause requires E-Verify enrollment within 30 days of contract award for firms that are not already enrolled. Once enrolled, the employer must initiate an E-Verify query within three business days of the employee's first day of employment. Section 1 of the I-9 must be completed no later than the end of the employee's first day of work for pay, with Section 2 completed by the end of the third business day. These two clocks run in parallel, and they do not always start on the same calendar date.

The Three-Day Clock: Where It Starts and Where It Ends

Section 1 of Form I-9 must be completed by the employee no later than the first day of employment. Section 2, where the employer examines documents and certifies them, must be completed by the end of the third business day after the first day of work. E-Verify must be initiated within those same three business days.

The practical trap: many onboarding workflows treat document collection as a pre-hire task completed during orientation on day one, then route the paperwork to an HR coordinator who may not open it until day two or three. If that coordinator is out sick, or if the new hire's start date falls before a holiday weekend, the three-day window closes fast.

For remote hires, the complexity compounds. The employer must use an authorized representative to physically examine documents, or use a DHS-authorized alternative procedure if the employer qualifies. As of mid-2023, employers who were enrolled in E-Verify and in good standing became eligible to use the remote document examination alternative procedure. That option requires retaining a clear copy of each document presented. Firms that have not updated their I-9 procedures since 2023 may still be running an unauthorized hybrid process without realizing it.

Existing Employees Assigned to a Covered Contract

The FAR E-Verify clause requires contractors to run existing employees through E-Verify if those employees are assigned to perform work on a covered federal contract. The employer has 90 days from the contract award date (or from the employee's assignment date, whichever is later) to complete those queries.

This is the provision that surprises program managers. A firm wins a new task order, assigns six employees who have been on staff for three years, and assumes their original I-9s are sufficient. They are not, for E-Verify purposes. Each of those six employees needs an E-Verify query unless the employer can document that they were previously verified under a prior covered contract.

Tracking which employees have been E-Verified, under which contract, and when, requires a record-keeping discipline that spreadsheets handle poorly at scale. When an auditor or contracting officer requests documentation, the firm needs to produce case numbers, query dates, and final results, not just a folder of I-9 copies.

Tentative Nonconfirmations: Process, Not Panic

A TNC is not a finding of unauthorized status. It means the data in E-Verify did not match SSA or DHS records. Common causes include name changes after marriage or naturalization, data entry errors, and SSA record delays for recently naturalized citizens.

When a TNC is issued, the employer must notify the employee in private, provide the Further Action Notice, and give the employee eight federal government working days to contest. The employer cannot take any adverse action, including delaying start date, reassigning duties, or terminating, during the referral period. Doing so exposes the firm to a discrimination charge under the anti-discrimination provisions of the Immigration and Nationality Act, enforced by the Immigrant and Employee Rights Section of DOJ.

The operational implication: do not initiate E-Verify on the last possible day if the employee has a facility access dependency. A TNC issued on day three of employment, with an eight-workday referral window, means the employee may not have confirmed work authorization status for nearly two calendar weeks. For a cleared position requiring daily site access, that is a significant operational gap.

Document Retention and Audit Readiness

I-9 forms must be retained for three years from the date of hire or one year after termination, whichever is later. E-Verify case numbers and results should be stored alongside the corresponding I-9, not in a separate system with no cross-reference.

ICE Form I-9 audits typically begin with a Notice of Inspection giving the employer three business days to produce all I-9s. Fines for substantive violations range from roughly $281 to $2,789 per violation as of the most recent adjustment, and each missing or incomplete form is a separate violation. For a firm with 200 employees and systemic Section 2 errors, the exposure is material.

Federal contractors also face the possibility of contracting officer review. FAR 52.222-54 gives the government the right to examine the contractor's E-Verify records. A firm that cannot produce organized, complete records risks a cure notice or, in serious cases, contract termination for default.

Building a Timing-Compliant Workflow

The following sequence reflects minimum compliant practice for a federal contractor onboarding a new hire assigned to a covered contract:

1. Send Section 1 instructions before or on the first day of employment. The employee completes Section 1 no later than end of day one.
2. Conduct document examination (in-person or via authorized remote procedure) and complete Section 2 no later than end of business day three.
3. Initiate the E-Verify query no later than end of business day three. Do not batch queries at end of week.
4. If a TNC is returned, notify the employee the same day and document the notification date and method.
5. Store the E-Verify case number and final result with the I-9 record, tagged to the contract number if the hire is assigned to a specific covered contract.
6. For existing employees newly assigned to a covered contract, calendar the 90-day E-Verify deadline from the assignment date and verify it has not already been satisfied under a prior covered contract.

Firms using an onboarding platform should confirm that the system enforces these deadlines rather than merely recording them after the fact. A system that flags overdue I-9s on day four is not a compliance control; it is a late notification.

Takeaway

I-9 and E-Verify compliance for federal contractors is a timing problem as much as a documentation problem. The three-business-day window, the 90-day existing-employee window, and the TNC referral period each create operational dependencies that affect facility access, project staffing, and audit exposure. Map the sequence, assign ownership, and build the deadlines into your onboarding workflow before the next contract award, not after the first TNC.

Winrove, a product of IT Custom Solution LLC and available at winrove.com, is built around these federal contractor workflows, including I-9 completion tracking, E-Verify initiation prompts, and contract-level employee assignment records. If you want to walk through how your current onboarding process maps to FAR 52.222-54 requirements, reach out for a brief conversation with our compliance team.