E-Verify requirements in Connecticut: no mandate, and no E-Verify bill since 2010

As of October 2026, Connecticut neither requires nor restricts E-Verify. There is no state statute, regulation or executive order telling private employers, state agencies, municipalities or state contractors to use it, and nothing in state law that limits an employer which enrolls voluntarily. The last time the General Assembly gave an E-Verify mandate a hearing was March 2010, and the bill died in committee.

For a Connecticut recruiter, that makes the question mostly federal: is there a federal contract with the E-Verify clause in the chain, and if the company has enrolled, is it following the federal rules for every hire at that site?

The short version by employer type

The two bills, and what they would have done

Senate Bill 221 (2009)

SB 221, titled An Act Concerning the Federal E-Verify Program, was introduced by Senator McLachlan and referred to the Joint Committee on Labor and Public Employees on January 21, 2009. That is its last recorded action.

Senate Bill 240 (2010)

SB 240, a raised bill of the Labor and Public Employees Committee, was more specific. From January 1, 2011, any employer with 50 or more persons employed in the state would have had to register with and use E-Verify for each new hire. The bill's definition of employer expressly included the state and any political subdivision, so towns and state agencies would have been covered, and the Labor Department would have written regulations. The committee held a public hearing on March 2, 2010. The bill's history ends there.

Since then the topic has been close to absent from the General Assembly's record. That is different from New Jersey or New Hampshire, where E-Verify bills are filed most sessions, and it suggests no Connecticut change is imminent. It does not rule one out.

What Connecticut employers do instead

Every employer completes Form I-9: Section 1 by the employee's first day, Section 2 within three business days of the start date. E-Verify, where used, is a second step that runs from the completed form; the difference between the two is laid out in E-Verify vs. Form I-9. Because Connecticut has no state verification statute of its own, the federal penalty schedule is the main exposure for paperwork mistakes; see I-9 penalties.

If a Connecticut employer opts in, the federal memorandum of understanding governs. It applies to every new hire at each enrolled hiring site, not just the roles the employer cares about. Cases are created no later than the third business day after the employee starts work for pay. Applicants cannot be screened, existing employees cannot be run except under the federal contractor rules, and nobody can be suspended or let go while contesting a tentative nonconfirmation.

Federal contract work in Connecticut

Connecticut has a large defense and aerospace manufacturing base and a long tail of machine shops, engineering firms and service vendors underneath it. That is where E-Verify is most likely to become mandatory for a Connecticut company: not through Hartford, but through a federal contract. Under FAR 22.1803, the E-Verify clause goes into prime contracts above $150,000, except contracts performed only outside the United States, contracts shorter than 120 days, and contracts only for commercially available off-the-shelf items. A prime contractor must pass it down to a subcontract for services or construction worth more than $3,500 with work in the United States.

A supplier making a part to a drawing is not supplying a COTS item, so a machine shop several tiers down can find the clause in its purchase order terms. Once a contractor is covered, it has 30 calendar days from award to enroll and must generally verify all new hires company-wide plus existing employees assigned to the contract, with narrower options for some employers such as state and local governments and institutions of higher education.

Neighbors and placements across the line

New England and New York have no state E-Verify mandates, so a Connecticut staffing firm placing workers in Massachusetts, Rhode Island or New York does not pick up a state duty there; see Massachusetts and the regional entries in E-Verify requirements by state. The nearest state with an E-Verify rule for contractors is Pennsylvania, where it applies to public works contracts above $25,000. A firm that also serves clients in the Southeast should treat those placements separately, since several states there require E-Verify of every employer.

Enrolling voluntarily: the tradeoffs in a no-mandate state

Without a state requirement, the decision belongs to each Connecticut employer. The arguments in favor are practical: a confirmed case result is a cleaner record than a photocopied document if ICE ever inspects the I-9 file, and a company that expects to bid on federal work is ready on day one instead of scrambling within the 30-day window. The arguments against are just as concrete:

• Enrollment is site-wide. Every new hire at an enrolled site must be run, including seasonal and part-time workers.
• The employer agrees to the MOU's terms, including federal monitoring of its use of the system and the requirement to give employees the federal notices after a mismatch.
• Someone in HR has to own the tentative nonconfirmation process, including the deadlines for the employee to act and the rule against adverse action while a case is open.

A company that enrolls should write down why, which sites are covered, and who runs cases, so a later manager does not mistake a voluntary choice for a Connecticut legal requirement.

Staffing agencies in Connecticut

• The agency that completes Form I-9 is the one that would run E-Verify. A client's enrollment does not cover the agency's employees.
• If a client's federal contract flows the clause down to the agency's staffing subcontract, the agency enrolls within 30 days of that subcontract, and the federal rules then apply to all its new hires at the enrolled site.
• An agency that enrolls only to satisfy one client should consider registering a separate hiring site for that work, so the obligation does not automatically spread to every placement.
• Licensing is a separate Connecticut question; see staffing agency license requirements in Connecticut.

A worked example

This is an invented example. A New Haven engineering staffing firm supplies two drafters to a manufacturer that builds components under a federal subcontract. The manufacturer's purchase order includes FAR 52.222-54, and the staffing agreement is a subcontract for services worth about $90,000. The firm enrolls in E-Verify within 30 days of signing, registering its New Haven office as the hiring site. From then on it creates a case for every new hire at that office, not only the two drafters, three business days or less after each start date. Its Stamford office, which handles administrative placements and is not part of the subcontract, is a separate hiring site and is not enrolled. No Connecticut law is involved at any step.

A Connecticut checklist

1. Check every federal prime contract, subcontract and purchase order for FAR 52.222-54.
2. If the clause is there, enroll within 30 days of award and decide which hiring sites to register.
3. If it is not, E-Verify is a choice; make it deliberately, knowing the MOU covers every hire at the site.
4. Complete Form I-9 on time for everyone, whether or not you use E-Verify.
5. For workers outside Connecticut, apply the law of the state where they work.