Under Two Equal Employment Opportunity Mandates, OFCCP Raises Thr

If this headline feels like it got cut off mid-sneeze, the legal story behind it is actually pretty clear: the Office of Federal Contract Compliance Programs, or OFCCP, has raised the contract-value thresholds that trigger coverage under two federal equal employment opportunity mandates that still matter a great deal for government contractors. In plain English, some employers now need a slightly bigger federal contract before Section 503 of the Rehabilitation Act or VEVRAA kicks in. But here is the catch, and it is a big one: higher thresholds do not mean the rules disappeared. They mean the coverage lines moved, the compliance map changed, and anyone doing business with the federal government should stop guessing and start checking.

That matters even more because OFCCP is operating in a very different environment than it did just a short time ago. Executive Order 11246, the long-standing federal contractor affirmative action framework for race and sex, was revoked in 2025. That headline grabbed plenty of attention. What got less attention was the follow-up reality: Section 503 and the Vietnam Era Veterans’ Readjustment Assistance Act, better known as VEVRAA, did not vanish. They remained standing. OFCCP resumed activity under those two mandates, even while its older review structure was being unwound and reshaped.

So yes, the compliance world got simpler in one corner and messier in another. Welcome to federal contractor life, where the coffee is strong, the acronyms are stronger, and the threshold chart can quietly change your year.

What changed under OFCCP’s two remaining mandates?

The headline change is straightforward. Effective October 1, 2025, OFCCP adopted updated jurisdictional thresholds tied to inflation adjustments. Under Section 503, the basic coverage threshold increased from $15,000 to $20,000. Under VEVRAA, the basic coverage threshold increased from $150,000 to $200,000. These are not random numbers pulled from a regulatory hat. They reflect the Federal Acquisition Regulation Council’s inflation-adjustment process for acquisition-related thresholds.

In practical terms, a business generally becomes covered by Section 503 if it has a federal contract of more than $20,000. For VEVRAA, a business generally becomes covered if it has a federal contract of $200,000 or more. And yes, “contract” includes subcontract. That means companies working one layer down from the prime contractor cannot safely assume they are invisible. Federal contracting law loves surprises, and subcontractor coverage is one of its favorite magic tricks.

There is also a second threshold that matters: the one for a written affirmative action program, or AAP. For Section 503, the AAP requirement still generally applies when the employer has at least 50 employees and a single contract of $50,000 or more. For VEVRAA, the AAP trigger is now generally 50 employees and a single contract of $200,000 or more.

That distinction is where many organizations stub their compliance toe. They hear “threshold increase” and think every obligation moved at once. Not so fast. A company might be covered for nondiscrimination and affirmative action duties under one threshold, while the written-program requirement follows another. This is why OFCCP compliance so often turns into a group project involving HR, legal, contracts, talent acquisition, data teams, and at least one person whispering, “Wait, are we a subcontractor here?”

Why OFCCP raised the thresholds

The increase was not a policy whim and it was not a brand-new statute. The underlying reason is the federal inflation-adjustment framework for procurement-related laws. Congress required the FAR Council to review certain monetary thresholds every five years and adjust them when inflation warrants it. OFCCP then adopted those adjusted levels for Section 503 and VEVRAA coverage.

That sounds boring, and it is boring, but in a helpful way. This was less a philosophical overhaul than a technical recalibration. The policy signal was not “these laws no longer matter.” The signal was “the dollar amounts now reflect inflation-adjusted procurement rules.” So while the numbers changed, the core message stayed the same: contractors covered by Section 503 and VEVRAA must still avoid discrimination and take affirmative steps to improve opportunity for protected groups.

What Section 503 still requires from covered contractors

Section 503 focuses on individuals with disabilities. At its core, the law prohibits discrimination and requires affirmative action by covered federal contractors and subcontractors to employ and advance qualified individuals with disabilities. That means the compliance conversation is not limited to “don’t discriminate.” It also includes outreach, recruitment, documentation, and internal review.

For employers that meet the written AAP threshold, Section 503 compliance usually includes reviewing personnel processes, documenting outreach and recruitment efforts, maintaining an audit and reporting system, evaluating physical and mental qualification standards periodically, and supporting reasonable accommodation practices. In other words, Section 503 is not a one-page poster and a hopeful smile. It is an operating framework.

Another point worth underlining: Section 503 does not require hiring a less qualified candidate over a better qualified candidate. That misconception has survived longer than many expired breakroom yogurts. The law is aimed at equal opportunity, affirmative outreach, and fair consideration, not mandatory selection of an unqualified or less qualified applicant.

And if you are in construction, here is an important nuance. Section 503 applies to businesses with federal construction contracts, but not to businesses with federally assisted construction contracts. That distinction is legal catnip for contract lawyers and a recurring trap for everyone else.

What VEVRAA still requires from covered contractors

VEVRAA does for protected veterans what Section 503 does for disability status: it prohibits discrimination and requires affirmative action by covered federal contractors and subcontractors. If your organization is covered, VEVRAA is not just a patriotic poster and a handshake. It involves concrete process rules.

Among the better-known requirements are the invitation to self-identify as a protected veteran at the pre-offer and post-offer stages, recordkeeping tied to applicants and hires, and the annual hiring benchmark for contractors that must maintain a written VEVRAA AAP. That benchmark gives contractors a way to measure the effectiveness of outreach and recruiting efforts for protected veterans. Employers can use the national percentage of veterans in the civilian labor force or develop their own benchmark using a five-factor method.

The benchmark is not a quota. It is more like a legal measuring tape. It helps answer a practical question: “Are our recruiting efforts actually reaching protected veterans, or are we just congratulating ourselves for posting jobs into the digital void?”

Like Section 503, VEVRAA generally applies to federal construction contracts but not federally assisted construction contracts. And like Section 503, it reaches subcontractors too. If a company supports a covered federal contract and relevant clauses flow down, coverage questions can become very real very quickly.

The bigger legal context: EO 11246 went away, but OFCCP did not

To understand why this threshold story matters, you have to place it in the 2025-to-2026 OFCCP reset. In January 2025, Executive Order 14173 revoked Executive Order 11246. That was a major change because EO 11246 had long driven OFCCP’s race- and sex-based affirmative action structure for federal contractors. Shortly after, the Department of Labor ordered OFCCP to cease and desist all investigative and enforcement activity under the rescinded order.

For a time, activity related to Section 503 and VEVRAA was also placed in abeyance while the agency separated those statutory programs from the older EO 11246 framework. Later, the Department lifted that abeyance and allowed OFCCP to resume activity under Section 503 and VEVRAA. So the agency’s mission narrowed, but it did not disappear. It shifted from a three-lane highway to a two-lane road.

That shift had practical consequences. OFCCP said it would administratively close pending compliance reviews tied to the previous review format because those reviews had significantly entangled EO 11246 with Section 503 and VEVRAA. The agency also said the Section 503 and VEVRAA AAP certification period would remain closed while it updated systems and processes. Contractors, however, were explicitly reminded that their obligations under Section 503 and VEVRAA remain in effect.

Translation: the portal being quiet does not mean the law is quiet. Compliance obligations do not disappear just because a government website is in its “please stand by” era.

What federal contractors should do now

1. Re-check coverage instead of relying on old threshold charts

If your team still uses a spreadsheet or internal policy memo built around $15,000 and $150,000, it is officially out of date. Review prime contracts, subcontracts, modifications, and renewals to determine whether your company crosses the new Section 503 and VEVRAA thresholds.

2. Separate the rules in your head and in your workflow

Many employers still bundle “OFCCP compliance” into one big bucket. That approach is riskier now. EO 11246 is no longer the anchor it once was, but Section 503 and VEVRAA remain live obligations. Internal checklists, training materials, and compliance calendars should reflect that separation.

3. Keep written AAPs where required, even if certification is paused

The fact that OFCCP’s Section 503 and VEVRAA certification period remains closed does not excuse employers from maintaining the underlying written programs when the thresholds apply. Think of certification as the front desk. Think of the AAP itself as the building. If the receptionist takes lunch, the building does not cease to exist.

4. Review outreach, recruiting, and recordkeeping

Section 503 and VEVRAA are both process-heavy. Covered contractors should assess whether outreach documentation, applicant tracking, self-identification workflows, accommodation procedures, hiring-benchmark support, and subcontract clauses still match current law.

5. Pay attention to proposed regulatory changes without acting like they are already final

In July 2025, DOL proposed changes to the Section 503 and VEVRAA regulations. For Section 503, the proposal included removing disability self-identification requirements and the 7% utilization goal for individuals with disabilities. Those proposals matter, but proposals are not finished rules. Contractors should watch developments carefully and avoid the classic compliance blunder of behaving as though “proposed” means “done.”

A subtle compliance trap: not every veterans-related number moved together

Here is where things get especially sneaky. OFCCP’s updated VEVRAA coverage threshold is now $200,000. But the Department of Labor’s VETS-4212 reporting page still states a $150,000 reporting threshold. That means employers should not assume every veterans-related obligation automatically shifted to $200,000 in the same way at the same time.

This distinction matters because many companies lump OFCCP compliance and VETS reporting into one administrative rhythm. That is understandable. It is also how a filing error gets born. Smart employers treat coverage thresholds, AAP thresholds, and reporting thresholds as separate questions rather than one giant compliance smoothie.

Common mistakes employers should avoid

• Assuming EO 11246’s revocation ended all OFCCP obligations. It did not. Section 503 and VEVRAA still apply.
• Confusing basic coverage with written AAP requirements. Those thresholds are related, not identical.
• Ignoring subcontractor status. If federal clauses flow down, coverage may follow.
• Treating proposed rule changes as already effective. Future-looking is smart; premature is not.
• Using one veterans threshold for everything. Coverage and reporting may not match neatly.
• Letting paused certification lull the organization into noncompliance. A closed portal is not a legal waiver.

Conclusion: the threshold moved, but the responsibility did not disappear

The most important takeaway is not that OFCCP raised thresholds. It is that the agency’s remaining disability and veteran mandates still have real force, even in a reshaped enforcement environment. Section 503 and VEVRAA continue to require nondiscrimination, affirmative action, documentation, and disciplined recruiting practices from covered contractors and subcontractors. The new numbers matter because they define the front gate of coverage. But once you are inside the gate, the old compliance habits still matter: clear documentation, updated workflows, accurate thresholds, and no magical thinking.

For some employers, the raised thresholds may reduce immediate obligations. For others, especially larger contractors and subcontractors, the changes are more of a technical update than a strategic escape hatch. Either way, the safest response is not panic and it is not complacency. It is a clean contract review, a current threshold analysis, and an honest look at whether your Section 503 and VEVRAA practices are built for the version of OFCCP that exists now, not the one that lived in last year’s training deck.

Because in federal contractor compliance, the fastest way to get in trouble is to assume the government stopped caring just because the acronym soup got rearranged.

Experiences Related to the Topic: What This Change Looks Like in Real Life

One common experience inside federal contractors is simple confusion at the leadership level. An executive hears that Executive Order 11246 was revoked and assumes the whole OFCCP compliance universe packed its bags and moved out. Then HR or legal has to deliver the less dramatic but more accurate news: no, Section 503 and VEVRAA are still here, still enforceable, and still capable of creating work for everyone in the building. That conversation is often the first reality check. It feels less like a legal seminar and more like telling someone the sequel they skipped is actually required viewing.

Another frequent experience happens in recruiting operations. Talent acquisition teams update job-posting language, self-identification forms, and applicant tracking workflows only to discover that the rules do not all move together. Some requirements are current. Some are proposed to change. Some thresholds increased. Some reporting obligations appear to sit on a different number. The result is not usually rebellion; it is spreadsheet fatigue. Recruiters want a clean answer. Compliance often hands them a sentence that starts with, “Well, it depends on whether this is Section 503, VEVRAA, AAP coverage, or VETS-4212 reporting.” That is the moment the room gets very quiet.

Subcontractors often have their own version of the experience. A company may think, “We do not sell directly to the federal government, so this is not our circus.” Then someone reviews a subcontract and realizes federal clauses flowed down after all. Suddenly the organization has to answer questions it never expected to ask: Are we covered? How much is the contract worth? Do we have 50 employees? Do we need a written program? Are our recruiting practices documented? The emotional arc usually goes from confidence to curiosity to mild panic to a very long meeting.

Compliance managers also describe a practical tension between portal activity and actual obligations. When the AAP certification period is closed, some internal stakeholders start acting like the assignment has been canceled. But experienced compliance people know better. They keep building the program, collecting the records, checking outreach, and maintaining documentation because they understand a basic truth: government systems can pause; legal duties usually do not. It is not glamorous work. Nobody throws confetti because an audit file is neatly organized. But when enforcement resumes or a complaint arrives, the team that kept its house in order looks a lot smarter than the team that treated silence as permission.

Finally, there is the experience of trying to explain all of this to non-lawyers. That may be the hardest part. The best compliance professionals turn complicated threshold changes into plain-language rules managers can actually use: check the contract value, confirm whether subcontract coverage exists, separate disability obligations from veteran obligations, and do not assume yesterday’s OFCCP rules are today’s OFCCP rules. When organizations get that right, the topic stops feeling like bureaucratic fog and starts feeling manageable. And that may be the most valuable experience of all: discovering that good compliance is not about memorizing every acronym, but about building systems that still make sense when the rules move an inch, a mile, or a mysteriously titled headline with “Thr” at the end.

SEO Tags