The Office of Federal Contract Compliance Programs has proposed a major rewrite of the disability compliance rules for federal contractors and a much narrower, primarily procedural update to the regulations protecting veterans. Although the two proposals arrived together, they are not regulatory twins. They are more like cousins who happened to show up at the same family reunion wearing similar jackets.
The proposed Section 503 changes would eliminate mandatory disability self-identification invitations, the 7% utilization goal, utilization analyses, and certain disability-related data collection duties. The proposed VEVRAA changes, by contrast, would largely preserve contractors’ existing affirmative action responsibilities while relocating enforcement procedures that previously depended on regulations associated with the now-revoked Executive Order 11246.
For federal contractors, the practical message is simple but important: these are proposals, not permission slips to delete records, disable applicant forms, or send the affirmative action plan to the recycling bin. Existing Section 503 and VEVRAA regulations remain effective unless and until final rules change them.
Why OFCCP Proposed the Rule Changes
On July 1, 2025, the U.S. Department of Labor published separate notices of proposed rulemaking for Section 503 of the Rehabilitation Act and the Vietnam Era Veterans’ Readjustment Assistance Act, commonly known as VEVRAA.
The proposals followed President Donald Trump’s January 2025 revocation of Executive Order 11246. That executive order had supplied the regulatory foundation for federal contractor affirmative action requirements involving race, color, religion, sex, sexual orientation, gender identity, and national origin.
Section 503 and VEVRAA did not disappear with Executive Order 11246 because both are based on federal statutes. Section 503 prohibits disability discrimination and requires covered contractors to take affirmative action to employ and advance qualified individuals with disabilities. VEVRAA provides comparable nondiscrimination and affirmative action protections for categories of protected veterans.
The regulatory plumbing, however, had a problem. Parts of the Section 503 and VEVRAA enforcement systems incorporated procedures found in regulations implementing Executive Order 11246. Once that order was revoked, OFCCP needed to separate the surviving statutory programs from the retired executive-order framework.
A Quick Comparison of the Proposals
| Compliance Area | Section 503 Proposal | VEVRAA Proposal |
|---|---|---|
| Written affirmative action programs | Remain required for covered contractors | Remain required for covered contractors |
| Mandatory self-identification | Proposed for elimination | No comparable elimination proposed |
| Numerical measurement | 7% utilization goal and analysis would be removed | Veteran hiring benchmark remains intact |
| Outreach evaluation | Continues, but with less applicant-flow data | Continues |
| Enforcement procedures | Moved into the Section 503 regulations | Moved into the VEVRAA regulations |
| Overall effect | Substantial deregulation | Mostly technical and procedural cleanup |
Major Proposed Changes to Section 503
Eliminating Mandatory Disability Self-Identification
Current Section 503 regulations require covered contractors to invite applicants and employees to voluntarily self-identify as individuals with disabilities. Contractors generally issue invitations during the pre-offer and post-offer stages and periodically resurvey employees using OFCCP’s approved Form CC-305.
The proposed rule would remove the regulation requiring these invitations. OFCCP argues that disability inquiries may conflict with restrictions under the Americans with Disabilities Act, particularly the prohibition on pre-offer questions about whether an applicant has a disability.
This position has generated substantial debate. Long-standing EEOC materials state that employers may request voluntary disability self-identification when the information supports a legally required or genuinely beneficial affirmative action program. Those materials also emphasize confidentiality, voluntariness, separation from the employment application, and protection against adverse treatment.
Disability-rights advocates therefore argue that the current system does not violate the ADA because it uses a voluntary, confidential process specifically designed for affirmative action. OFCCP’s proposal takes a more restrictive view and questions whether the existing regulatory exception should continue.
Removing the 7% Disability Utilization Goal
The existing regulations direct contractors to apply a 7% utilization goal for qualified individuals with disabilities to each job group. Contractors with 100 or fewer employees may apply the goal to their entire workforce instead.
The goal is not formally a quota. Missing it does not automatically prove discrimination or require an employer to hire an unqualified applicant. Instead, it acts as a diagnostic benchmark. When representation falls below 7%, contractors examine personnel practices, recruiting efforts, internal audits, and possible barriers to equal opportunity.
Under the proposal, the utilization goal and the accompanying analysis would be removed. The Department of Labor says the goal is not expressly required by the statutory language of Section 503 and may exert pressure on employers to make decisions based on disability status.
Supporters of the change see the goal as paperwork-heavy and legally awkward. Critics view it as one of the few measurable tools available for determining whether disability recruitment programs are producing results rather than merely producing attractive policy statements and heroic quantities of stapled paper.
Ending Certain Disability Data Collection Requirements
The proposal would also remove the requirement to maintain annual totals for applicants, applicants who self-identify as individuals with disabilities, total hires, and hires who self-identify as individuals with disabilities.
Without mandatory self-identification, much of that data would be impossible to collect consistently. The proposed removal is therefore a logical companion to eliminating Form CC-305 invitations and the utilization analysis.
The tradeoff is significant. Contractors could spend fewer hours maintaining applicant-flow reports, but they would also have less information for measuring whether people with disabilities are entering, advancing through, or quietly vanishing from the hiring pipeline.
Outreach Duties Would Not Completely Disappear
One easy mistake is to read “remove the numbers” as “remove affirmative action.” That is not what the proposal says.
Covered contractors would still be expected to maintain written Section 503 affirmative action programs, review employment practices, provide reasonable accommodations, prohibit harassment and discrimination, communicate relevant policies, and evaluate external recruitment and outreach efforts.
The proposed rules retain the annual requirement to review whether outreach efforts are effective in identifying and recruiting qualified individuals with disabilities. When efforts are ineffective, contractors would still need to consider alternatives.
The awkward question is how an employer evaluates effectiveness without reliable disability applicant and hiring data. A contractor may know that it attended three disability-focused career fairs and partnered with two community organizations, but measuring actual results becomes harder when the dashboard has lost several gauges.
Creating Standalone Enforcement Procedures
The Section 503 proposal would copy relevant administrative hearing and enforcement procedures into the Section 503 regulations themselves. This would remove their dependence on Part 60-30, which was built around Executive Order 11246.
OFCCP would retain enforcement tools such as complaint investigations, compliance evaluations, conciliation, referrals to the Solicitor of Labor, back-pay remedies, injunctive relief, sanctions, and formal administrative hearings. The proposal streamlines the legal architecture; it does not erase the agency’s authority to investigate disability discrimination.
What the Proposed VEVRAA Changes Would Do
The VEVRAA proposal is far less dramatic. OFCCP has not proposed eliminating the core affirmative action program for protected veterans, veteran self-identification, annual hiring benchmarks, applicant and hiring data, job-listing obligations, or outreach evaluations.
Moving Enforcement Rules Into the VEVRAA Regulations
Like Section 503, the current VEVRAA regulations refer to administrative procedures located in the Executive Order 11246 rules. OFCCP proposes to place those procedures directly into Part 60-300, making VEVRAA enforcement self-contained.
The proposed revisions would also remove obsolete cross-references, including a reference to the Uniform Guidelines on Employee Selection Procedures and an unnecessary citation to the statutory authority for Section 503.
Core Veteran Compliance Duties Remain
Covered contractors would still need to develop annual VEVRAA affirmative action programs, invite applicants and employees to self-identify as protected veterans, assess veteran outreach, retain required records, establish a veteran hiring benchmark, and list most employment openings with the appropriate state employment service delivery system.
Contractors subject to the separate reporting requirement would also continue filing the annual VETS-4212 report. In other words, the VEVRAA proposal rearranges the filing cabinet but does not throw away its contents.
Current Coverage Thresholds for Federal Contractors
The dollar figures stated in the original July 2025 proposals were later affected by government-wide inflation adjustments. Effective October 1, 2025, the basic Section 503 coverage threshold increased from more than $15,000 to more than $20,000 in federal contract or subcontract value.
A formal Section 503 affirmative action program is generally required when a contractor has at least 50 employees and a covered contract or subcontract of at least $50,000.
The VEVRAA coverage threshold increased from $150,000 to $200,000. Because the written VEVRAA affirmative action program threshold is tied to the statutory coverage amount, contractors generally need at least 50 employees and a qualifying contract or subcontract of $200,000 or more.
Organizations should analyze individual legal entities, contract values, employee counts, subcontracting arrangements, and establishment structures rather than assuming the parent company’s answer automatically applies to every subsidiary.
Arguments Supporting the Proposed Changes
Supporters emphasize reduced administrative burden. Disability self-identification campaigns involve applicant-tracking-system configuration, employee communications, confidentiality controls, data validation, recurring surveys, utilization calculations, and documentation of corrective steps.
Removing those duties could reduce compliance costs while allowing contractors to redirect resources toward accommodations, accessible technology, recruiting partnerships, and manager training.
Supporters also raise privacy concerns. Disability information can be sensitive, and some applicants may distrust an employer’s promise that the information will remain separate from selection decisions. Eliminating federally required collection could reduce both perceived and actual risks associated with storing medical-status data.
Finally, the Department argues that affirmative action should focus on individual qualifications rather than numerical outcomes. From this perspective, a well-intentioned utilization target can begin to feel like a quota when managers believe they will be criticized for failing to reach it.
Arguments Against the Proposed Section 503 Rollback
Opponents respond that voluntary self-identification data is necessary for accountability. An employer cannot identify a disability hiring gap, promotion bottleneck, or retention problem when it has no consistent data describing the affected population.
They also stress that the 7% utilization figure is a goal rather than a hiring command. It does not require preference for unqualified candidates, mandate a particular decision, or establish automatic liability when representation is lower.
Another concern is that process-based compliance can become too easy to satisfy. A contractor may document career fairs, outreach emails, and recruitment partnerships while having no reliable way to determine whether those activities led to applications, interviews, hires, promotions, or retention.
The debate therefore extends beyond paperwork. It asks whether affirmative action can remain meaningful without standardized measurements and whether privacy can be protected without eliminating the data needed to detect unequal opportunity.
What Federal Contractors Should Do Now
Contractors should continue following the regulations currently in force. The Department of Labor continues to state that Section 503 and VEVRAA obligations remain effective. OFCCP’s certification period may be closed, and the agency’s operational structure may be changing, but neither fact independently repeals a regulation.
Compliance teams should preserve existing records, continue required self-identification processes, prepare applicable affirmative action programs, maintain outreach documentation, complete utilization and hiring analyses, file VETS-4212 reports when required, and monitor official rulemaking developments.
At the same time, organizations can prepare a transition plan. That plan might identify which applicant-tracking fields, forms, reports, policies, vendor feeds, and internal procedures would change if the Section 503 proposal becomes final.
Contractors should also consider whether they would voluntarily continue collecting disability data if the federal mandate disappears. Any voluntary program must have a legitimate affirmative action purpose, appropriate notices, limited access, strong confidentiality protections, and careful coordination with legal counsel.
Practical Experience: Navigating the Proposed OFCCP Changes
A useful way to understand the real-world impact is through a composite example based on common contractor compliance experiences. Consider a technology and engineering company with 2,400 employees, several federal contracts, a centralized applicant-tracking system, and separate Section 503 and VEVRAA affirmative action plans for multiple establishments.
When news of the proposed rules reaches the company, the first reaction from an operations manager is predictable: “Excellent, we can stop doing the disability survey.” The compliance director gently interrupts before anyone presses the large imaginary button marked DELETE EVERYTHING. A proposed rule is not a final rule, and the current obligations still apply.
The company creates a small working group involving compliance, human resources, recruiting, information security, procurement, accessibility, and employment counsel. Its first task is not changing forms. It is mapping the current process.
The team documents where Form CC-305 appears, how responses move from the recruiting platform into a restricted database, which employees can access the information, how the 7% utilization analysis is produced, and how outreach results are evaluated. It also reviews veteran self-identification separately so that no one accidentally treats the Section 503 and VEVRAA proposals as identical.
This exercise reveals a familiar compliance surprise: the official report is not the only system using the data. Disability information also feeds an accessibility dashboard, while veteran data supports recruiting partnerships and the annual VETS-4212 report. Turning off one field without tracing downstream connections could break several reports and create conflicting records.
The company therefore develops two operating models. Model A preserves the current process while the proposed rules remain pending. Model B describes the future workflow if the Section 503 rule is finalized substantially as proposed.
Under Model B, mandatory disability self-identification invitations and utilization calculations would stop after the new rule’s effective date. Historical information would remain protected and retained according to applicable requirements. The company would continue maintaining its written affirmative action program, accommodation procedures, accessibility standards, outreach partnerships, and annual evaluation of recruiting efforts.
The most difficult discussion concerns measurement. Without standardized applicant and employee disability data, how will the company determine whether outreach works? The recruiting team suggests counting event attendance and referral sources. Compliance points out that activity is not the same as outcome. Sending 200 invitations to a career fair proves that email works; it does not prove that employment barriers disappeared.
The company ultimately designs a voluntary inclusion framework that can be activated only after legal review. It considers confidential workforce surveys, accessibility feedback, accommodation-response times, website testing, candidate-experience reviews, retention trends, and partnerships with disability employment organizations. None perfectly replaces utilization data, but together they provide a more informative picture than counting brochures.
Meanwhile, the veteran program continues largely unchanged. Recruiting maintains state job-bank listings, protected-veteran invitations, hiring benchmark calculations, outreach assessments, records, and VETS-4212 reporting. This becomes the clearest lesson from the project: regulatory changes that arrive together do not necessarily travel in the same direction.
The experience also demonstrates the value of preserving institutional knowledge. Compliance teams often know why a field, report, or policy exists, while software administrators may see only an old configuration. Removing requirements without documenting their purpose can create costly confusion when regulations change again.
The best transition strategy is therefore neither panic nor premature celebration. It is disciplined version control: follow today’s law, model tomorrow’s possibilities, protect historical data, and change production systems only when a final rule supplies an effective date and clear instructions.
Conclusion
OFCCP’s proposed Section 503 and VEVRAA rule changes reflect a narrower federal contractor enforcement environment following the revocation of Executive Order 11246. Yet the proposals differ sharply in substance.
The Section 503 proposal would remove major measurement tools, including mandatory disability self-identification, the 7% utilization goal, utilization analyses, and applicant and hiring data requirements. Written affirmative action programs, nondiscrimination protections, accommodation duties, outreach evaluations, and enforcement authority would remain.
The VEVRAA proposal is primarily procedural. It would create a standalone enforcement framework while preserving the substantive responsibilities contractors already know: affirmative action planning, job listings, self-identification, outreach, data collection, hiring benchmarks, and veteran reporting.
Until final rules are published and become effective, contractors should continue complying with existing requirements. Regulatory proposals may point toward the future, but they do not operate as time machines.
