You won the grant, so now you have to run every new hire through E-Verify, right? For most grant recipients today, the answer is no. The E-Verify grant requirement that everyone assumes exists has historically applied to federal contractors, not to the broad universe of organizations that receive federal grants and cooperative agreements. That gap is exactly what a new federal proposal is trying to close — and the rules are about to get more complicated.

The Default Answer Today: A Grant Alone Doesn’t Trigger E-Verify

Start with the surprising baseline. According to the federal government’s own guidance, an organization is required to use E-Verify “if the terms and conditions of your grant contain the FAR E-Verify clause” — and most grants do not. The plain-language answer on the official E-Verify program FAQ for grant recipients tells organizations to review their award for that clause and check with their grant official if unsure. In other words, accepting federal money does not automatically pull you into the program.

That is because E-Verify’s mandatory reach was built on the procurement side of federal spending, not the assistance side. Since a 2009 rule, the Federal Acquisition Regulation has required covered federal contractors to verify employment eligibility through the Department of Homeland Security’s system. Grants and cooperative agreements run under a different rulebook — the Uniform Guidance at 2 C.F.R. Part 200 — which, until now, has not carried a blanket E-Verify mandate. If you run a nonprofit, a research lab, or a small business living on grant dollars, your starting assumption should be that you are covered only if something specific says so. Use our federal grants overview to confirm what program your award falls under before you assume anything about its terms.

The Four Triggers That Actually Pull You In

Instead of asking “do grants require E-Verify,” ask which of these four sources applies to you. Any one of them creates an obligation; none of them is the same as “I got a grant.”

1. The FAR contract clause. If your award is a federal contract (or your grant incorporates FAR 52.222-54), you must enroll. The clause at FAR 52.222-54 requires a contractor that is not already enrolled to sign up as a federal contractor in E-Verify within 30 days of award, then begin verifying new hires within three business days of their start date. This clause is inserted in contracts that exceed $150,000, with carve-outs for work performed entirely outside the U.S., short jobs under 120 days, and commercially available off-the-shelf items.

2. State law. Even with no federal trigger, your state may require it. More on that below.

3. The proposed grant rule. The May 2026 OMB proposal would make E-Verify a condition of receiving federal financial assistance — the change that would finally make a true “grant requirement” real.

4. Work-permit and other DHS rules. Separate immigration rules can require certain employers to use E-Verify in connection with employees’ work authorization. These move independently of your grant.

Why the distinction matters

Treating “grant” and “E-Verify trigger” as the same thing causes two opposite mistakes: organizations that are genuinely required to enroll ignore the clause buried in their award, while organizations with no obligation burn staff time setting up a program they don’t need. Read the source, not the rumor. If you manage multiple awards, our grant database can help you keep each program’s terms straight in one place.

What the May 29 Proposed Rule Would Actually Change

On May 29, 2026, the Office of Management and Budget published a proposed rule revising the Uniform Guidance, and the immigration piece is sweeping. As summarized by HR Dive’s coverage of the proposal, it would require recipients and subrecipients of federal grants and similar assistance to participate in E-Verify for employees and contractors performing work under a federal award. OMB frames it as an “additional safeguard” against employing unauthorized workers under federal funds.

Two details make this bigger than it sounds. First, there is no dollar threshold. Federal contractors only hit the FAR mandate above $150,000, but Bloomberg Law’s analysis notes the grant proposal sets no such floor — a small community group with one federal grant could be covered the same as a major university. Second, the rule adds a reporting duty: grantees would have to send Final Nonconfirmation notices — the notice issued when E-Verify cannot confirm a worker’s eligibility — to the funding agency or pass-through entity. Failure to comply could lead to enforcement up to and including termination of the award.

The reach is also broader than the grantees themselves. Legal analysts reviewing the proposal point out that it would extend to a wide range of organizations that have never touched E-Verify — hospitals, universities, state parks departments, and local child-services providers among them — because it ties the obligation to federal funding rather than to a contract. And because the proposal does not define “subrecipient,” the requirement could flow further down the funding chain than many organizations expect. Comments are due July 13, 2026, so the window to weigh in is short. Anyone running a nonprofit grants program should read the proposal closely now, not after it is finalized.

State Mandates: The Patchwork That May Already Cover You

Federal rules are only half the picture. According to the National Conference of State Legislatures’ E-Verify tracker, 22 states already require E-Verify for at least some public or private employers. Nine of them — Alabama, Arizona, Georgia, Louisiana, Mississippi, North Carolina, South Carolina, Tennessee, and Utah — require it for all or most employers, often with small-business exemptions tied to headcount. Another eleven require it mainly for public employers and state contractors.

For a grantee, this means your obligation may have nothing to do with the federal award at all. A nonprofit in Arizona or a contractor in Georgia could already be required to verify every new hire under state law, while an identical organization in a no-mandate state has no obligation until a federal trigger applies. If your organization operates across state lines — or you run programs funded partly by small business grant programs in multiple states — map your headcount obligations state by state before you assume the federal rules are the only ones that bind you.

If the Rule Lands: A Pre-Compliance Checklist

You don’t have to wait for a final rule to get ready, and the existing contractor framework is a useful model for what enrollment looks like. The federal contractor experience, codified at eCFR Subpart 22.18, shows the mechanics: enroll, then verify new hires within three business days, with special options for universities, state and local governments, and tribes to limit verification to employees assigned to the funded work.

Three concrete moves are worth making during the comment window. First, inventory your awards and read each one for the FAR E-Verify clause — if it is there, you may already be out of compliance. Second, confirm your state’s status using the NCSL tracker so you know whether a state mandate already applies. Third, if you decide to enroll proactively, treat it as a process change: E-Verify must be run within three days of a hire’s start, which means it has to be built into onboarding, not handled as an afterthought. Over a million employers are already enrolled in the system, so the operational playbook is well established.

There is also a paperwork dimension that is easy to underestimate. Enrollment requires signing a memorandum of understanding with DHS and the Social Security Administration, designating program administrators, and training the staff who will run cases. Once enrolled, you cannot pick and choose: the program generally expects you to verify every qualifying new hire, and it carries its own recordkeeping and anti-discrimination obligations that sit on top of the standard Form I-9 process. For organizations that run lean, the realistic cost is not the software — E-Verify is free to use — but the staff time to administer it correctly and consistently. Building that capacity before a final rule lands beats scrambling after. If compliance complexity is stretching your team, our managed grant services can help you keep awards in good standing while you focus on the work.

Frequently Asked Questions

Does receiving a federal grant require my organization to use E-Verify?

Not by itself today. You are required to use E-Verify only if your award contains the FAR E-Verify clause or if a state law covers your organization. The official E-Verify guidance tells grant recipients to review their award terms and check with their grant official. A May 2026 proposed rule would change this by requiring all federal assistance recipients to enroll, but it is not yet final.

When would the proposed E-Verify grant requirement take effect?

It is still a proposal. OMB published it on May 29, 2026, and set a public comment deadline of July 13, 2026. A final rule would only take effect after the agency reviews comments and issues final regulatory text, so the exact compliance date is not yet set. Organizations should track the rulemaking rather than assume an immediate obligation.

Is there a dollar threshold for the grant E-Verify requirement?

For federal contractors, the FAR clause applies above $150,000. The proposed grant rule, by contrast, includes no dollar threshold, meaning even small awards could trigger the requirement if it is finalized as written. This is one of the most significant differences between the long-standing contractor mandate and the new proposal.

Do subrecipients have to comply too?

Under the proposed rule, yes. The proposal would apply to recipients and subrecipients of federal financial assistance, so pass-through funding could carry the obligation down to subgrantees. Because “subrecipient” can sweep in a range of entities, organizations that re-grant or subcontract federal funds should pay particular attention during the comment period.

Bottom Line: Read the Trigger, Then Comment

The most useful thing a grantee can do right now is stop treating “E-Verify grant requirement” as a settled fact and start treating it as a question with four possible answers. Today, the obligation is narrow: it bites if your award carries the FAR clause or your state law reaches you. Tomorrow, if the May 2026 proposal is finalized, it could reach nearly every federally funded organization with no dollar floor and a new reporting duty attached.

So do two specific things before July 13. Pull your active awards and read them for the FAR E-Verify clause, and check your state’s mandate status so you know your real baseline. If the proposed expansion would burden your organization, the comment window is your chance to say so on the record — agencies do read and respond to substantive comments. To keep every federal award compliant while these rules shift, start by searching and tracking your opportunities in the OpenGrants grant database.