E-Verify for Construction Subcontractors: Who Has to Use It and What the Flow-Down Rules Require
E-Verify is the US government's internet-based system for confirming an employee's eligibility to work in the United States. Using it is optional for most employers — they can rely on the Form I-9 alone as required under the Immigration Reform and Control Act. But for some employers, E-Verify is mandatory: federal contractors under the FAR E-Verify clause, employers in states that have mandated it for all or some employers, and any employer whose contract requires it.
For construction firms, the E-Verify question comes up in two contexts. First, when the firm itself is a federal contractor or state-mandated employer required to enroll. Second, when the firm is a sub on a project where the prime contractor is E-Verify-required and the requirement flows down to subs. The compliance mechanics are the same in both cases; the contract obligations are what differ.
The Federal Acquisition Regulation includes an E-Verify clause, FAR 52.222-54, that applies to most federal contracts over $150,000 with a performance period greater than 120 days. When the clause is in a contract, the prime contractor is required to use E-Verify to confirm employment eligibility for all employees newly hired after enrollment, and for all existing employees assigned to the federal contract.
The clause also requires the prime to include equivalent flow-down provisions in subcontracts for services or construction valued above $3,000. That threshold is low — it effectively covers every construction subcontract of meaningful size. So on a FAR-subject federal construction project, every sub down the tier should be E-Verify enrolled and following the same process.
The flow-down obligation is one of the places where pre-subcontract compliance review matters. A GC bidding a FAR-subject federal project needs subs who are already enrolled or willing to enroll; a sub that refuses to enroll can't be awarded the subcontract. Identifying this at bid time avoids awkwardness at subcontract execution.
A number of states have passed their own E-Verify laws. The details vary significantly:
State E-Verify landscape (sample — always verify current law)
- Arizona — requires E-Verify for all employers as a condition of doing business in the state
- Florida — requires E-Verify for employers with 25+ employees hiring after July 1, 2023
- Georgia — requires E-Verify for public contractors and most private employers with 11+ employees
- Mississippi — requires E-Verify for all employers
- North Carolina — requires E-Verify for employers with 25+ employees
- South Carolina — requires E-Verify for all employers
- Tennessee — requires E-Verify for employers with 50+ employees
- Utah — requires E-Verify for employers with 15+ employees for state contracts
- Several other states require E-Verify for public contractors or for specific programs
The specifics change; verifying the current state law is essential before relying on any summary. The compliance team should maintain a state-by-state matrix that's refreshed at least annually against the current statutes and regulations.
Mechanically, E-Verify is a web-based tool maintained by USCIS. An enrolled employer, after completing Form I-9 with a new hire within the required timeframe, enters the I-9 information into the E-Verify system. The system checks the data against Department of Homeland Security and Social Security Administration databases and returns one of three responses: authorized (work is permitted), tentative nonconfirmation (the data doesn't match and needs review), or final nonconfirmation (the employee is not authorized for employment).
A tentative nonconfirmation gives the employee a chance to contest — the employee can go to the SSA or DHS and provide additional documentation to resolve the discrepancy. During that contest period, the employee can continue working; the employer cannot terminate based on the tentative response. A final nonconfirmation after the contest period allows the employer to terminate based on E-Verify's determination.
The timing on E-Verify submission is specific. The Form I-9 must be completed no later than the third business day after hire. The E-Verify case must be created by the third business day. The employer can't E-Verify before the offer is made and the employee has accepted; pre-hire E-Verify of applicants is not permitted.
An employer signs a Memorandum of Understanding with the Department of Homeland Security, identifies which locations are enrolled, and trains the HR personnel who will use the system. Enrollment is free. For a federal contractor enrolled specifically to satisfy the FAR requirement, the enrollment happens at the company level or at the location level depending on the employer's structure.
A federal contractor enrolled under the FAR rule must verify all new hires and, optionally or as required, existing employees assigned to federal contracts. The options for existing employees on the federal contract depend on the specific contract terms — some require verification of all employees assigned, some require only new hires assigned post-enrollment.
On a FAR-subject federal construction project, the GC's subcontract with each sub typically includes a flow-down clause substantially identical to FAR 52.222-54. The clause obligates the sub to enroll in E-Verify, verify new hires, and include the same flow-down in their own lower-tier subcontracts. The sub certifies compliance as a condition of payment.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
When E-Verify certifications are a condition of payment, the AP team gets involved. The certification might be a separate monthly form the sub submits with their pay application, or it might be built into the lien waiver and certification package. Either way, receipt of the certification becomes a pay application prerequisite. Missing certifications can hold payment.
For prime contractors on FAR projects, the flow-down is not optional. If the prime's subcontract doesn't include the E-Verify flow-down clause and the sub isn't verifying, the prime is out of compliance. Standard subcontract templates for federal work should carry the clause automatically.
E-Verify enrollment carries recordkeeping obligations. The employer must retain the E-Verify case verification for each employee as part of the I-9 records — typically for the longer of three years after hire or one year after termination. For federal contractors, retention may be longer depending on the contract and applicable audit timeline.
USCIS and DHS audit E-Verify users periodically to ensure proper use. Common findings include: late case submission (after the third business day), missing case submissions for employees who should have been verified, failure to provide the notice of tentative nonconfirmation to affected employees, and failure to maintain records. Fines for noncompliance can be significant, and repeated violations can result in debarment from federal contracting.
A sub considering a federal bid that will require E-Verify should confirm:
Sub-level checklist before a federal project bid
- The sub's E-Verify enrollment status — enrolled, and at which locations
- Who is trained and authorized to submit cases — typically HR or the office manager
- The sub's I-9 file organization — is the E-Verify case number stored with the I-9 for each employee?
- The sub's policy for tentative nonconfirmations — who handles them, what the workflow is
- Whether the sub's existing employees who would be assigned to the federal project need to be verified, or just new hires
- Lower-tier subs' E-Verify compliance — if the sub subs out any portion, those subs also need to be enrolled
For federal contractors, E-Verify noncompliance can result in contract termination, debarment from future federal work, and fines per violation. For state-mandated E-Verify states, noncompliance can result in loss of business license, civil fines, and in extreme cases criminal penalties for knowing employment of unauthorized workers.
Beyond the government-enforcement consequences, noncompliance creates contractual exposure. A sub that certifies E-Verify compliance on pay applications when they're not actually verifying has made a false certification — the exposure includes breach of contract, fraud claims, and in federal work potentially False Claims Act liability.
E-Verify is mandatory for federal contractors on contracts subject to FAR 52.222-54 and for employers in states that have mandated it. The flow-down obligations on federal construction projects mean most subs of meaningful size need to be enrolled. The mechanics — timely case submission, tentative nonconfirmation handling, recordkeeping — are straightforward once the systems are in place, but they require HR discipline. For compliance teams, maintaining a current matrix of federal flow-down status and state mandates, and building E-Verify certification into the pay application workflow on applicable projects, keeps the obligation visible where it needs to be.
Written by
Jordan Patel
Compliance & Legal
Former corporate counsel specializing in construction contracts and tax compliance. Writes about the documentation layer — COIs, W-8/W-9, certified payroll, notice-to-owner deadlines — and the legal backbone behind audit-ready AP.
View all posts