The “old way” of affirmative action is officially dead, but has federal compliance got easier? Not exactly. This “seismic shift” has traded one kind of complexity for another, and it lands squarely in the middle of your hiring funnel.
In early 2026, the revocation of Executive Order 11246 effectively set fire to the compliance playbook federal contracting teams have used for decades. Overnight, the focus shifted from long‑standing affirmative action protocols to a new, high‑stakes “merit‑based opportunity” mandate that forces you to rethink how you document every hiring decision.
And it’s happening at the same time AI and automation are already pushing conventional hiring workflows to their breaking point.
To help recruiting teams navigate the wreckage, JobSync brought together two of the industry’s top compliance experts for a roundtable deep dive: Sheila Abron, Partner at Fisher Phillips, and Amanda Bowman, Principal Consultant at DCI Consulting Group.
The consensus was clear: you can’t afford to treat a “smaller agency” as a weaker one. Federal compliance hasn’t gone away, it has just become more targeted and less forgiving of sloppy processes.
The Ground Really Did Move: What Changed and What Didn’t
For 60 years, Executive Order 11246 served as the North Star of federal contractor compliance. It required companies to take affirmative action based on race, color, religion, sex, and national origin, backed by data‑heavy reporting and highly standardized Affirmative Action Program (AAP) templates.
That era ended with the stroke of a pen when Executive Order 14173 was signed, officially revoking 11246 and instructing the Office of Federal Contract Compliance Programs (OFCCP) to wind down that scheme. This revocation marked the end of race and gender-based AAPs as we knew them. In their place, new “merit-based opportunity” mandates.
Under these new policies, OFCCP is no longer looking for good-faith efforts to reach specific demographic numbers. Instead, it’s looking for proof that your hiring process is tightly anchored to job‑related qualifications and individual aptitude. Any leftover process that smells like the “old way” is now a potential red flag in an audit.
To be clear, discrimination law did not fall away with EO 11246. Title VII remains in full force, with all the familiar prohibitions around using protected characteristics in employment decisions. The OFCCP is still empowered to look for systemic pay discrimination, for example.
So TA teams now occupy an uncomfortable middle ground. The familiar contractor‑specific rules around race and gender are gone. The legal exposure when your outcomes are discriminatory has not gone anywhere. It has simply shifted back into general civil rights enforcement and into narrower, more intense OFCCP programs.
A Leaner, Meaner OFCCP
Rumors of the OFCCP being dismantled have been greatly exaggerated. While the agency is smaller in headcount and footprint, down to a fraction of its former size, it has been restructured and funded to the tune of $100.9 million for 2026.
The restructuring is expected to create a faster, more data-driven enforcement body. With most of their paperwork-heavy staff gone, the agency cannot run audits the way it did ten years ago. It has to lean on data flows and targeted investigations rather than broad, slow reviews.
Essentially, they’ve traded their army for a sniper rifle. If your data submissions or complaint patterns trip certain triggers, you are moving straight to the top of a “bellwether” audit list in their remaining high-priority jurisdictions: Section 503 of the Rehabilitation Act (Disability) and the VEVRAA, the Vietnam Era Veterans’ Readjustment Assistance Act (Veterans).
Two practical points matter for hiring teams.
First, complaint‑based enforcement is very much alive. Individual applicants and employees can still bring issues to OFCCP and the agency is actively investigating those complaints.
Second, the formal audit process is in a holding pattern, not dead. The standard scheduling letter still references expectations that made sense under 11246, so it has to be rewritten and cleared before a new wave of audits makes sense. When that happens, the agency already has a detailed audit framework ready to go for veterans and disability that it can switch back on quickly.
The New Enforcement Frontline: Veterans and Disability
With race and gender‑based AAPs gone, OFCCP’s remaining formal authority is concentrated in two places: Section 503 of the Rehabilitation Act (individuals with disabilities) and VEVRAA, the Vietnam Era Veterans’ Readjustment Assistance Act (protected veterans). This is where enforcement is now most aggressive and where the standards are increasingly outcome‑driven. Two areas are standing out for contractors:
Veteran hiring and the 5.1% “yield” benchmark
The veteran hiring benchmark currently sits at 5.1%. That number is the anchor for how an auditor evaluates your outreach and sourcing decisions.
The agency is now looking for a direct link between your recruitment spending and actual veteran applicants in the pipeline. If you’re paying a “veteran-friendly” job board and your data shows no veteran applicants from that source, you will be expected to adjust. An auditor will ask for your “outreach assessment”—a record showing that you reviewed every source and shifted budget to high-yield partnerships like military transition centers. If you can’t show that, you are at risk of failing the audit for not conducting a meaningful evaluation of your efforts.
Disability and the “interactive process”
On the disability side, many teams still picture accommodations as physical changes to office equipment or physical spaces. In 2026, the more common trigger is your application tech.
If a candidate tells you they’re struggling with an online assessment because of a visual impairment, or that a health condition makes a scheduled interview time unworkable, that is the legal starting point of the interactive process. From that moment, you are required to have a real back‑and‑forth dialogue to find a reasonable solution, and you need a record that shows that happened.
The trap is this: when those conversations happen informally in email or over the phone and are never logged in a structured way, they effectively don’t exist in an audit. If you can’t show that you responded, the default assumption is that you ignored a request for accommodations.
AI and Automated Selection Risk
Using protected characteristics, directly or indirectly, in employment decisions is still unlawful, regardless of whether those decisions are made by humans, rules‑based systems, or generative AI. That has not changed.
The existing framework for selection tools is still the Uniform Guidelines on Employee Selection Procedures. Those guidelines expect employers to break their process into steps, understand where selection happens, and investigate disparities in outcomes at each of those steps. That applies whether the decision is coming from a recruiter, a hiring manager, a scoring rubric, or an algorithm buried in your ATS.
On top of that general obligation, machine‑based selection systems are drawing extra attention as regulators and plaintiffs’ lawyers ask whether they are quietly blocking the very “merit” the administration says it wants.
The responsibility sits with the hiring organization. The software vendor is not the one on the hook when a tool screens people out in a way that creates unlawful impact. If your resume screening model downgrades candidates with gaps in employment history, for example, that can disproportionately affect veterans and candidates with disability‑related absences. If the job can be done by someone with less experience than you list as a minimum, but your tools reject anyone below that number, you may be building unnecessary barriers for younger veterans or disabled candidates changing careers. The OFCCP is looking for “job-relatedness” in every requirement you list.
The cautious path with new tools is to test them in a controlled way on limited roles or segments, with defined baselines and clear criteria for stopping if patterns move in the wrong direction. That lets teams get efficiency gains without committing the entire organization to an unproven selection layer.
To Collect or Not to Collect
One of the hardest operational questions right now is what to do with candidate self‑ID for race and gender. Candidates are visibly fatigued by repeated questionnaires. Many believe their answers will hurt them, whether or not that’s true in your organization.
There are two non‑negotiables for any recruiting team. Demographic questions cannot live inside the application form itself, and the underlying data has to be technically and procedurally fenced off from decision‑makers. If a hiring manager can casually see a candidate’s self‑ID status, it undercuts any “merit‑based” narrative you plan to put forward for that hire.
The tougher call is whether to keep collecting race and gender data at all now that 11246‑style AAPs are gone. Legally, there’s more flexibility. But from a risk and analytics perspective, switching off collection entirely carries its own dangers. Enforcement bodies don’t actually need your internal data to form an opinion. If your own files are empty, they can build an adverse inference analysis instead, looking at where you recruit and what the surrounding labor market looks like, then deriving a theoretical pool of who should have applied and how they should have moved through your funnel. They compare that against your actual outcomes. In that scenario, you’re letting the government tell the story of your hiring process because you didn’t keep the receipts to tell it yourself.
At the same time, you still need demographic data at the employee level. EEO‑1 reporting has not gone away. And several states have layered on their own reporting and pay transparency regimes. You are already in the business of handling this category of information, whether you like it or not.
The most sustainable approach is to treat demographic collection as a conscious design decision. You decide where in the process to ask, how the data will be insulated from decision‑making, how it will be analyzed, and how long it will be kept. And you make that decision with legal, TA, HR, and privacy at the same table, rather than leaving it to whichever team yells loudest.
Why You Don’t Want to Shut the Machine Down
It’s tempting to look at the end of 11246 and the downsizing of OFCCP and conclude that your meticulously‑built compliance infrastructure is overkill. That’s the fast road to being unprepared when expectations expand again.
Other federal programs are already moving toward deeper, longer‑run data. In higher education, for example, the government now expects colleges and universities to submit six years of detailed applicant‑level admissions data through expanded IPEDS reporting. That’s a huge shift from the old “one year, high‑level” model. It shows how quickly regulators can move from snapshots to multi‑year, individual‑level records when they decide it’s worth it.
Contractors should expect similar thinking to reach them. That might mean longer look‑back windows for audits or new expectations around how often you run internal analyses. If you’ve dismantled your data plumbing because the rules felt lighter for a season, rebuilding it under time pressure and scrutiny is going to be painful.
Here’s the tension—privacy regimes are pushing in the opposite direction. Laws like GDPR and stricter provincial rules encourage you to delete as much as you can, as fast as you can, especially for candidates who were never hired. Keep too much, and you take on privacy and breach risk. Keep too little, and you are blind when regulators ask for data.
The pragmatic answer isn’t to hoard everything or delete everything. It’s to define a retention strategy that reflects today’s rules and keeps your core compliance “machine” warm. Disable what you truly don’t need. Don’t tear out the wiring that lets you understand your own hiring behavior over time. As Abron says, “If you stay ready, you don’t have to get ready” – and in this version of OFCCP enforcement, that’s as close to a competitive advantage as you’re going to get.
This post is a summary of the JobSync Roundtable featuring Sheila Abron (Fisher Phillips) and Amanda Bowman (DCI Consulting). You can watch the full roundtable here.
About The Author
