The E-Verify grant requirement buried in OMB’s proposed rewrite of 2 CFR Part 200 has produced a lot of advice that reduces to one word: enroll. That advice skips the part that matters. Enrolling in E-Verify is not a precaution you can take back if the rule narrows, slips, or dies in litigation. It is a signed agreement with the Department of Homeland Security that runs on DHS’s clock, not on your grant’s.

The Four Duties Hiding in a Single Paragraph

The E-Verify grant requirement does not get its own section. It is folded into proposed §200.303, which sits under the heading "internal controls" — the section that already tells you to keep effective internal control over your federal award. OMB’s addition would require recipients and subrecipients to enroll in and use E-Verify to confirm employment eligibility for individuals working on or supporting a federal award.

Read plainly, that single paragraph creates four separate obligations. Enroll the organization before drawing down award funds. Run covered individuals through E-Verify within three business days of hire. Retain the case records for the longer of three years or your federal award retention period. Report every Final Nonconfirmation — the result E-Verify returns when it cannot confirm someone is authorized to work — to the awarding agency.

The fourth duty is the genuinely new one. Under E-Verify as it operates today, an employer who receives a Final Nonconfirmation terminates the worker and documents the decision internally. Nobody sends that outcome to a grants officer. The proposal would route it upward, and the rule does not specify a reporting window or say what the agency does with the data. The reasonable inference is that it feeds the pre-award risk picture agencies build before issuing discretionary awards, which means a string of nonconfirmations becomes part of how a funder reads your organization on the next competition.

None of this comes with a size carve-out. The Federal Acquisition Regulation clause that has governed contractors since 2008 applies to contracts over $150,000 and exempts small businesses below certain thresholds. No equivalent threshold appears anywhere in the grants proposal, a gap that labor and immigration counsel flagged within days of publication. If you receive federal money, directly or as a subrecipient, you are in scope.

Contractors Get an Exit. The Grant Rule Doesn’t Describe One.

Here is the asymmetry almost nobody covering this rule has named, and it is the reason the "just enroll early" advice is incomplete.

The E-Verify Memorandum of Understanding is the actual instrument you sign. Article V governs modification and termination, and it draws a sharp line between ordinary participants and federal contractors. Article V.B.3 says a federal contractor may terminate the MOU when the contract requiring participation is terminated or completed — and it warns that a contractor who fails to give DHS written notice "will remain an E-Verify participant, will remain bound by the terms of this MOU that apply to non-Federal contractor participants, and will be required to use the E-Verify procedures to verify the employment eligibility of all newly hired employees."

That clause exists because a contract is a discrete thing with an end date. A federal award portfolio usually is not. Most organizations working in federal grants hold overlapping multi-year awards, no-cost extensions, and continuation applications that make "the award that required participation is complete" a date that never quite arrives. Article V.B.1 does let any employer terminate on 30 days written notice, so exit is technically available. But the practical exit for a grantee only opens when the federal money stops, and for a going concern that is the whole point of the organization.

There is a second scope problem. Once enrolled, you cannot cleanly limit E-Verify to the grant-funded slice of your payroll. Partial use is a leading DHS audit finding, and the system is designed around an employer running every new hire. So an organization that enrolls to satisfy a $40,000 subaward is, in practice, adopting an organization-wide hiring control for as long as it stays enrolled. That is a real operational change, and it should be a deliberate decision rather than a hedge against a rule that has not been finalized.

Reversible Prep Worth Doing This Week

The distinction that should drive your response to the E-Verify grant requirement over the next 60 days is not urgent versus not urgent. It is reversible versus irreversible. Everything below costs you nothing if the rule is withdrawn or rewritten, and saves weeks if it lands as proposed.

Inventory who would actually be covered. Pull your payroll and mark every person whose salary touches a federal award directly, plus anyone charged through your indirect cost pool who could be read as "supporting" the award. That second group is where the ambiguity lives, and knowing its size tells you whether this is a 6-person problem or a 300-person problem.

Audit your Form I-9 file. E-Verify cases are built from I-9 data, and the system’s known error concentration is among naturalized citizens and workers holding recently issued employment authorization documents. Organizations that will feel this hardest — refugee resettlement agencies, immigrant legal services groups, community health centers, farmworker services — are exactly the ones whose I-9 files most need to be clean before any case is ever created. Fixing I-9 defects is good practice regardless of what OMB finalizes.

Read your existing award terms. Some agencies already impose E-Verify as a programmatic condition in specific funding streams. If you are already obligated somewhere in your portfolio, your decision calculus is different from an organization starting at zero. This is also the moment to check whether your state already mandates E-Verify for entities receiving state funds, which a growing number do — a wrinkle worth checking against your state-level funding as well as your federal awards.

Name two candidate program administrators. The three-business-day case window is rigid, and a single designated person on vacation is how organizations miss it. Deciding who those people would be costs nothing today. For nonprofit grant recipients running lean back offices, this staffing question is usually the binding constraint, not the software.

Three Commitments Worth Holding

Now the other column. These are the moves that are hard or impossible to unwind, and the case for waiting on each is straightforward.

Signing the MOU. Enrollment is free and takes under an hour, which is exactly why it gets recommended so casually. But the DHS enrollment process ends with an electronically signed agreement that takes effect on signature and continues for as long as DHS operates the program. Once you are in, you owe new-hire verification on every hire, not the federally funded subset. If the final rule narrows scope, adds a small-employer exemption, or slips its date, an organization that signed in August is running a compliance program it did not need to run yet.

Rewriting subaward templates. Adding flow-down E-Verify language to your subrecipient agreements now means you are enforcing a requirement that does not legally exist yet, against partners who may reasonably refuse. Draft the clause and hold it. Sending it is the step to defer.

Buying HR systems to automate it. Vendors are already selling E-Verify integration against this rule. Integration requirements depend on final text that does not exist, particularly the undefined Final Nonconfirmation reporting window. Procuring against a proposed rule is how organizations end up with a tool configured for a requirement that shipped differently.

The counterweight is honest: if the rule lands as proposed with an October 1 effective date, an organization starting from zero in late September will be learning the system on its first compliance-relevant hire. That is a genuine risk. The reversible column above is what buys down most of it without the signature.

Pass-Through Entities Are Buying a Monitoring Program

If you make subawards, your exposure is structurally different, and it is worse. Read together with the pass-through obligations at §200.332, the proposal would make you responsible for monitoring each subrecipient’s enrollment status and use — a new duty stacked on top of the risk assessment and single audit work you already owe.

The scale problem is not hypothetical. A state workforce agency may carry dozens of community-based subrecipients. A research university may have thirty subaward institutions on a single center grant. A community action agency running block grant money has a handful of partners with no HR department to speak of. Each of those relationships becomes a place where an immigration compliance system you did not choose can generate a finding against you.

The useful move for pass-through entities is narrow and reversible: add an "E-Verify enrollment status" field to your existing subrecipient monitoring records and populate it. You are not requiring anything. You are finding out which partners are already enrolled, which will enroll easily, and which would struggle. That inventory is the difference between a manageable October and a scramble. Organizations that manage a wide funder base through grant discovery and pipeline tools should treat enrollment status as a standard field on the partner record, the same way they track registration expiration dates.

Law firms advising on this have landed in roughly the same place. Seyfarth’s analysis of where immigration and grant compliance converge notes that the proposal creates no standalone penalty framework — agencies would simply use the existing remedies at §200.339, which run from withholding payments and disallowing costs through suspension, termination, and debarment. That is the actual stake. E-Verify noncompliance would stop being an employment matter and become a grant matter.

Frequently Asked Questions

Is the E-Verify grant requirement in effect right now?

No. It is a proposed rule published May 29, 2026, with the comment period closed as of July 13, 2026. OMB has targeted October 1, 2026 to align with fiscal year 2027 awards, but a proposed rule is not binding until a final rule issues. Nothing obligates you to enroll today unless a specific award term or state law already does. Watch for the final text before treating enrollment as mandatory.

Would it apply to existing employees or only new hires?

This is the biggest unresolved question in the text. The proposal reaches individuals "working on or supporting" a federal award, which reads broader than new-hire verification and would sweep in current staff assigned to covered work. Running existing employees through E-Verify is not a simple extension of new-hire process — it often requires updated I-9 documentation before a case can even be created. Several commenters flagged exactly this ambiguity.

Does a small subaward really trigger it?

As drafted, yes. The FAR contractor clause applies above $150,000; the grants proposal contains no comparable floor. A small nonprofit holding a modest subaward would be in scope on the same terms as a large prime recipient. Whether OMB adds a threshold in the final rule is one of the more plausible changes, given how heavily commenters raised it.

Can we enroll now and withdraw later if the rule changes?

Technically yes, on 30 days written notice under Article V.B.1 of the MOU. Practically, withdrawal is awkward for an organization that intends to keep receiving federal money, and while enrolled you owe verification on all new hires, not just federally funded ones. Treat enrollment as a decision you expect to live with rather than a hedge you can quietly unwind.

The Bottom Line

The right posture on the E-Verify grant requirement is not urgency and not dismissal. It is sequencing. The proposal is real, it is broad, and the effective date OMB picked leaves little runway. It is also unfinished, drew an extraordinary volume of comment on this specific provision, and sits inside a larger rewrite whose timing is genuinely contested. Analyses from firms tracking the rewrite and the Federal Funds Information for States issue brief on the rewrite both flag the October 1 target as ambitious for a rulemaking of this size.

So do the specific thing: this week, produce two lists. One is your covered-population inventory — names, whether they are direct-charged or indirect, and whether their I-9 would survive a case creation. The other is your subrecipient enrollment status field, populated. Both are pure information. Neither commits you to anything. When the final rule publishes, those two lists are what let you move in days instead of weeks, and if the rule narrows, you have lost nothing but an afternoon.

Hold the signature until there is a final rule to sign against. If your team needs help reading how this and the rest of the Part 200 rewrite hit a specific award portfolio, OpenGrants’ grant writing and compliance services can work through your active awards and subaward agreements with you before the October date forces the question.