Federal contractors looking for the “DEI issue” in FAR 52.222-90 may be looking in the wrong place. Yes, the clause is about what Executive Order 14398 calls “racially discriminatory DEI activities.” But that’s only the starting point. The new clause also reaches subcontract flowdowns, records access, reporting obligations, bilateral modifications, suspension and debarment, and False Claims Act (FCA) risk. This isn’t just an HR issue, and it isn’t just a DEI issue. It is a contract-administration issue, a supply-chain issue, and an invoice issue all at once.

Since taking office, the Trump administration has made contractor DEI compliance a priority. Earlier executive action addressed DEI-related programs and certifications across federal awards. But this executive order goes further by creating a contractor-specific prohibition, an implementation schedule, and an enforcement framework aimed at what the order defines as “racially discriminatory DEI activities.” It doesn’t simply announce a policy. It directs agencies to insert a new clause into covered contracts, subcontracts, and lower-tier subcontracts that prohibits covered conduct; requires access to records and reports; imposes subcontractor reporting obligations; allows cancellation, termination, or suspension; creates suspension and debarment exposure; and expressly ties compliance to payment decisions under the FCA.

That is why contractors should resist the urge to park this with one office. The April 17 OMB-led implementation memo, issued with DOD, GSA, and NASA, includes the draft FAR clause and puts the issue squarely in the procurement bloodstream. Legal, HR, compliance, procurement, finance, supplier management, program leadership, and business teams all get a piece of this. FAR 52.222-90 starts with DEI, but it doesn’t stay there for long.

Dates Contractors Need to Know

April 17, 2026:	OFPP, DOD, GSA, and NASA issued joint implementing guidance and model FAR deviation text introducing FAR 52.222-90.
April 24, 2026:	Agencies were to begin inserting FAR 52.222-90 into new solicitations and resulting contracts above the micro-purchase threshold, including commercial products and commercial services, where delivery or performance is in the United States. Open solicitations must be amended under FAR 1.107(d).
July 24, 2026:	Agencies are directed to make every effort to bilaterally modify covered existing contracts by this date. EO 14398 also requires agency heads, within 120 days of the order, to review the implementation of Section 3 and report compliance to the Assistant to the President for Domestic Policy.
December 31, 2026:	Modifications to covered contracts expiring on or before this date are discretionary under the guidance.

What the Clause Actually Prohibits

FAR 52.222-90 prohibits contractors from engaging in “racially discriminatory DEI activities.” EO 14398 defines that phrase as “disparate treatment based on race or ethnicity” in recruitment, employment, contracting, program participation, or the allocation or deployment of an entity’s resources. “Program participation” includes access to training, mentoring, leadership development programs, educational opportunities, clubs, associations, and similar opportunities sponsored or established by the contractor or subcontractor.

That definition matters. The clause isn’t written as a ban on everything a company has ever called “DEI.” It targets race- or ethnicity-based disparate treatment. But it is broad enough to require a serious review of programs that use race or ethnicity in eligibility, selection, sponsorship, funding, access, targets, or resource allocation. That could include race-conscious sponsorships, fellowships, supplier-diversity spend targets, mentoring cohorts, leadership programs, ERG eligibility rules, scholarship programs, and association support where race or ethnicity is used as a condition, preference, or selection criterion.

This means that the practical point is to not manage this by title. Manage it by function. A program with “diversity” in the name may be neutral and open to all. A program with a neutral name may not be. What matters is how the program actually works.

The Supply-Chain Piece Is Where Things Get Interesting

Importantly, and intentionally, the clause flows down to subcontracts at any tier on the same basis, including commercial products and commercial services, where delivery or performance is in the United States. That makes FAR 52.222-90 a supply-chain clause as much as a DEI clause.

But, here again, precision matters. The clause doesn’t expressly require prime contractors to continuously monitor or audit subcontractors. It doesn’t prescribe a cadence for reviews, require blanket questionnaires, or mandate a standing audit program. Instead, what it does require is reporting of subcontractor conduct that is “known or reasonably knowable” and may violate the clause, along with any remedial actions directed by the contracting agency. That phrase, “reasonably knowable,” does a lot of heavy lifting.

It isn’t intended to make primes omniscient. But it may make a purely passive flowdown hard to defend if the prime ignores red flags or fails to ask reasonable questions in higher-risk circumstances. For most primes, the better answer will be documented risk-based diligence: targeted certifications, focused questionnaires, escalation channels, red-flag reviews, and a record of what the prime asked, reviewed, escalated, and did in response.

Subcontractors should expect the same issue from the other side. Some primes will flow down the clause as written. Others may add certifications, audit language, indemnities, termination rights, cooperation duties, or reporting obligations that go beyond the clause. Subcontractors should ask for the exact language, compare it to FAR 52.222-90, and decide what can be accepted, what needs to be narrowed, and what needs to be escalated.

8(a) Is Not DEI, but FAR 52.222-90 Still Wants a Word

One related point deserves special attention: 8(a) small business participants and entity-owned firms are not automatically the problem. Nothing in EO 14398 or FAR 52.222-90 expressly repeals the 8(a) program, disturbs SBA-recognized status, or makes tribal-owned, ANC-owned, NHO-owned, CDC-owned, SDB, or other socioeconomic contracting statuses unlawful. But status and conduct are not the same thing. Primes should be careful not to treat lawful SBA program participation as suspect, and subcontractors should be ready to push back on overbroad certifications or flowdowns that blur the line between recognized contracting status and race- or ethnicity-based disparate treatment. The right question isn’t whether a company is 8(a), an SDB, tribal-owned, ANC-owned, NHO-owned, or CDC-owned; it’s whether a particular recruiting, mentoring, supplier, association, scholarship, or resource-allocation practice uses race or ethnicity as an eligibility, a preference, a selection, a funding, an access, or an allocation criterion.

Facing Cross-Border Collision

Contractors with EU supply chains should also avoid one-size-fits-all flowdowns. EU-based suppliers may be subject to separate equality, pay-transparency, board-diversity, sustainability-reporting, or nondiscrimination obligations, some of which use DEI-adjacent terminology but do not necessarily involve race- or ethnicity-based disparate treatment. That distinction matters. FAR 52.222-90 shouldn’t be read to prohibit an EU supplier from complying with applicable EU or member-state law, but primes and subcontractors should avoid certifications that blur the line between lawful foreign-law compliance and conduct covered by the clause. For EU suppliers, the right question isn’t whether a policy is called diversity, inclusion, equality, or ESG. The right question is whether the relevant contract activity involves race- or ethnicity-based eligibility, preference, selection, funding, access, or allocation criteria and whether the flowdown language accounts for mandatory local-law obligations.

The FCA Hook Is Not Window Dressing

The clause’s FCA language is the enforcement hook contractors need to read and heed. The clause states that the contractor recognizes compliance with the clause as “material” to the government’s payment decisions for purposes of 31 U.S.C. § 3729(b)(4). EO 14398 also directs the Attorney General, in consultation with relevant agencies, to consider FCA actions against contractors or subcontractors that violate the clause.

As watchers of FCA cases clearly understand, that language is designed to matter. FCA materiality is the crux of litigated implied-certification cases. By writing materiality into the clause, the government strengthens its hand in future enforcement actions. While this doesn’t mean every disputed program becomes an FCA case, it does mean contractors should treat acceptance of the clause, continued performance, and the submission of invoices as linked compliance events. Once the clause is in the contract, internal complaints, hotline reports, subcontractor disputes, program documents, and invoice approvals may all become part of a future FCA narrative.

This is a fact that finance and program personnel need to understand. This isn’t just a contracts or HR review. If payment is tied to compliance, the people submitting and approving invoices need to know what has been accepted, what has been reviewed, and what issues have been escalated.

Existing Contracts Create Their Own Problem

For existing contracts, the guidance directs contracting officers to make “every effort” to secure bilateral modifications by July 24, 2026. If a contractor refuses, contracting officers are directed to consider whether, without the modification, the contract no longer meets the agency’s needs and should be terminated for convenience. That isn’t a routine paperwork exercise.

Signing may preserve the work, but it also accepts new compliance obligations, records-access language, subcontractor reporting duties, possible debarment consequences, and FCA materiality language. Refusing may create termination-for-convenience pressure. And while a termination for convenience isn’t a default, it can still create cost, disruption, and business consequences.

Contractors need to have a position before the contracting officer calls. That means thinking through reservation language, audit-scope limits, consideration, implementation timing, subcontractor flowdowns, and escalation if termination is raised.

Litigation Is Already Here, but Contractors Still Need a Plan

Litigation over EO 14398 is already underway. On April 20, 2026, a coalition of nonprofits, university professors, and contractor organizations filed suit in the District of Maryland challenging the order on First Amendment (free speech, free association, overbreadth, content-based discrimination, and unconstitutional condition) and ultra vires grounds. The complaint argues that the order’s definition of “racially discriminatory DEI activities” is overbroad, imprecise, and not limited to conduct that violates federal antidiscrimination law. That litigation matters, and contractors should watch it closely. But unless and until a court blocks enforcement, the clause is moving into solicitations, contracts, and subcontracts. Contractors shouldn’t assume litigation will solve the immediate compliance problem; it simply adds to the confusion.

What Contractors Should Do Now

The playbook isn’t complicated, but it does need to be coordinated.

1. Find the contracts. Identify prime contracts, subcontracts, task orders, delivery orders, purchase orders, teaming agreements, joint venture agreements, and lower-tier arrangements above the micro-purchase threshold where delivery or performance is in the United States. Flag open solicitations, pending awards, contracts expiring after December 31, 2026, and existing contracts likely to receive modification requests before July 24, 2026.
2. Put one team in charge. This shouldn’t be managed separately by HR, legal, compliance, procurement, finance, and supplier management. Create one decision process for program reviews, certifications, contracting officer communications, prime/sub communications, invoice controls, and escalation.
3. Review programs by operation, not label. Look at recruitment, hiring, promotion, mentoring, leadership development, training, educational opportunities, ERGs, association sponsorships, supplier programs, vendor selection, fellowships, scholarships, community programs, and resource-allocation decisions. The key question is whether race or ethnicity is used as an eligibility, a preference, a selection, a funding, an access, or an allocation criterion.
4. Don’t overcorrect. The goal isn’t to delete every program with “diversity” in the title. Programs built around open-access outreach, geography, socioeconomic status, first-generation status, veteran status, disability, small-business status, professional development need, or other facially neutral criteria may present a different risk profile than programs that condition participation or benefits on race or ethnicity.
5. Control the flowdowns. Primes should update templates where required but avoid adding unnecessary obligations that go beyond the clause. Subcontractors should request the exact flowdown language and review any added certification, audit, indemnity, termination, cooperation, or reporting language.
6. Use risk-based subcontractor diligence. The clause doesn’t expressly mandate continuous monitoring or routine subcontractor audits. But because primes must report subcontractor conduct that is “known or reasonably knowable,” primes should be able to show reasonable diligence. That may include targeted certifications, focused questionnaires, red-flag reviews, escalation channels, and a record of what was asked, reviewed, escalated, and resolved.
7. Protect privilege and prepare for records requests. Identify what records exist regarding covered programs, certifications, complaints, subcontractor diligence, and program changes. Use privilege protocols before conducting sensitive legal reviews or creating unnecessary written analyses.
8. Treat invoices as compliance events. Once the clause is accepted, payment requests may carry added FCA risk. Add pre-invoice checks, make sure finance and program personnel understand the clause, and route complaints or hotline reports through a process that can assess contract and FCA implications.
9. Prepare for modification requests. Existing contracts may be targeted for bilateral modification by July 24, 2026. Contractors should prepare positions on reservation language, audit scope, consideration, implementation timing, subcontractor flowdowns, and escalation if termination for convenience is threatened.
10. Watch the moving pieces. Track litigation, agency deviations, OMB Paperwork Reduction Act clearance, contracting officer instructions, and any changes to the guidance. Also document concrete program impacts and compliance costs. Those facts may matter later.

How Best to Proceed

The best response isn’t panic. It is also not performative overcorrection. The better approach is disciplined execution: Find the affected contracts, understand the clause, map programs by how they actually work, preserve neutral programs where appropriate, control flowdowns, document reasonable subcontractor diligence, tighten invoice controls, and be ready for modification requests.

FAR 52.222-90 may be called a “DEI clause,” but contractors should treat it as a multifront compliance event. The contractors that manage it best will not necessarily be the ones that delete the most. They will be the ones that understand the real risk universe: what they do, what their subcontractors do, what they know, what they sign, and what they invoice.