A federal contractor that wins a contract worth more than $150,000 now has a hard deadline it cannot negotiate away: enroll in E-Verify within 30 calendar days of award or fall out of compliance with the clause the government just put in its contract. That obligation comes from FAR 52.222-54, Employment Eligibility Verification, the clause contracting officers are required to insert under FAR Subpart 22.18 once a contract crosses that dollar threshold. The clause is not a formality bolted onto the paperwork — miss the deadlines inside it, and a contractor is in breach of an express contract term, not just a labor-law technicality.
The 30-Day Enrollment Clock Starts at Award
For a contractor that is not already enrolled in E-Verify, the clock starts the moment the contracting officer signs the award. FAR 52.222-54(b)(1)(i) states the requirement in plain terms: the contractor must "enroll as a Federal Contractor in the E-Verify program within 30 calendar days of contract award." There is no grace period built in for contractors who assumed they had until performance actually began, and the clause does not distinguish between a prime that has never touched E-Verify before and one that simply let an old enrollment lapse. Thirty calendar days means thirty calendar days, weekends and holidays included.
Contractors that are already enrolled skip this step, but they are not off the hook entirely — they move straight to the verification-timing requirements described below, which run on a separate clock tied to contract award rather than enrollment.
Which Contracts Actually Trigger the $150,000 Rule
FAR Subpart 22.18 directs contracting officers to include the E-Verify clause in solicitations and contracts once the value exceeds $150,000, but the rule carves out three specific situations where the clause does not apply. It is not required when the contract's work will be performed entirely outside the United States, when the period of performance is under 120 days, or when the contract is solely for commercially available off-the-shelf (COTS) items. That COTS exception is broader than a plain reading suggests — it also covers minor modifications to COTS items, COTS items sold as bulk cargo, and services from a COTS provider that are bundled with the COTS item itself. A contractor bidding on a mixed contract — say, COTS hardware plus custom integration services above the threshold — should not assume the COTS exception covers the whole award; the clause attaches based on what the contract actually requires the contractor to deliver.
The threshold and exceptions matter most at proposal time, because a contractor that misjudges whether a solicitation will carry the clause can be caught flat-footed at award with a 30-day enrollment deadline it never planned for.
The 90-Day Verification Window for Assigned Employees
Enrollment is only the first gate. Once enrolled, the contractor has to actually run employees through the system, and the deadline for that depends on whether the contractor was already enrolled before the award. For a contractor enrolling because of this specific contract, FAR 52.222-54(b)(1)(iii) requires the contractor to "initiate verification within 90 calendar days after date of enrollment or within 30 calendar days of the employee's assignment to the contract, whichever date is later." For a contractor that was already enrolled at the time of award, FAR 52.222-54(b)(2)(ii) sets a parallel but distinct rule: the contractor must "initiate verification within 90 calendar days after date of contract award or within 30 days after assignment to the contract, whichever date is later."
The practical effect of the "whichever date is later" language is that a contractor cannot game the clock by delaying an employee's formal assignment to the contract. If an employee starts contract work on day 10 but the contractor's own enrollment only happened on day 5, the 90-day-after-enrollment date still governs if it falls later than 30 days after assignment. Program managers staffing up quickly after award are the ones most likely to blow this deadline, because the verification obligation attaches to specific employees the moment they are assigned to contract work — not to the workforce in general.
Exempt Entities and the Subcontractor Flow-Down
Not every enrolled contractor has to run its entire workforce through E-Verify. FAR 22.1802 exempts institutions of higher education, state and local governments, federally recognized Indian tribal governments, and sureties from company-wide verification, limiting their obligation to employees actually assigned to the covered contract. That is a meaningful distinction for a university or a state agency holding a federal award: the clause does not force them to verify every employee on payroll, only the ones doing the contract work.
The clause also travels downstream, and at a much lower bar than the $150,000 prime-contract threshold. FAR 52.222-54(e) requires a prime to flow the clause down into any subcontract for services (other than commercial services bundled with a COTS purchase) or construction that is worth more than $3,500 and includes work performed in the United States — so a subcontract far too small to independently trigger the $150,000 prime-contract rule can still carry its own E-Verify obligation. A prime that fails to flow the clause down to a subcontractor above that $3,500 line is exposed to the same compliance gap as if it had never enrolled itself, because the government's interest is in every employee performing covered work being verified, not just the prime's direct hires.
What It Means for Contractors
The operational fix is to build E-Verify enrollment into the same checklist as insurance certificates and SAM.gov registration — something confirmed before an award is even signed, not after. Contractors that already hold federal work should keep their enrollment active continuously rather than letting it lapse between contracts, since a lapse converts them back into a "not already enrolled" contractor facing a fresh 30-day clock on the next award. Contracts administrators should flag the $150,000 threshold during proposal review so business development teams know in advance whether a bid will carry the clause, and HR or compliance staff should track employee assignment dates to the contract separately from hire dates, since the 90-day verification clock runs from assignment, not from employment. For primes managing subcontractors, remember that the flow-down trigger is $3,500, not $150,000 — confirming subcontractor E-Verify enrollment should be a standard part of subcontract award whenever a subcontract clears that much lower bar, not something checked only if a question comes up during an audit.
