The Direct Answer: Two Statutes, Two Protected Groups, One Compliance Framework
VEVRAA (the Vietnam Era Veterans' Readjustment Assistance Act of 1974, codified at 38 U.S.C. § 4212) and Section 503 of the Rehabilitation Act of 1973 (29 U.S.C. § 793) are the two affirmative action statutes that govern federal contractors and subcontractors. They are structurally similar on purpose: both are administered by the Office of Federal Contract Compliance Programs (OFCCP), both require written affirmative action programs (AAPs), and both impose identical annual AAP update cycles, identical data collection obligations, and identical self-identification mechanics. The core difference is who each statute protects. VEVRAA protects protected veterans — specifically veterans with service-connected disabilities, recently separated veterans (within three years of discharge), Active Duty or wartime campaign badge veterans, and Armed Forces Service Medal veterans. Section 503 protects individuals with disabilities, regardless of veteran status. A veteran with a service-connected disability is covered by both statutes simultaneously, which is why contractors often conflate the two.
Also worth reading: How Do Federal Contractors Prepare for the 2026 VETS-4212 Filing? · How Does Veteran Affirmative Action Compliance Software Actually Help Federal Contractors Meet Their OFCCP Obligations? · How do you perform a continuous vetting enrollment status check for defense contractors?
The practical consequence is that a covered contractor must run two parallel AAP programs with different benchmarks, different data elements, and different outreach obligations. Under Section 503, the utilization goal is a fixed 7 percent of the workforce in each job group. Under VEVRAA, there is no fixed percentage; instead, contractors set their own hiring benchmarks annually, either using OFCCP's published benchmark (updated periodically based on Bureau of Labor Statistics and VA data, historically hovering in the 5-6 percent range) or developing one using their own data and applying five enumerated factors from 41 CFR 60-300.45. Getting this distinction wrong is one of the most common findings in compliance reviews.
Statutory Origins and Why They Diverged
VEVRAA grew out of the Vietnam-era problem of returning servicemembers facing employment discrimination and high unemployment. Originally enacted in 1974 as an amendment to the Veterans' Readjustment Assistance Act, it required government contractors to take affirmative action to employ and advance qualified protected veterans. Section 503, by contrast, was added to the Rehabilitation Act of 1973 and modeled on the civil rights contracting framework — it extended the nondiscrimination principle to people with disabilities and, through regulations finalized in 2013, added a mandatory 7 percent utilization goal. The 2013 rules for both statutes (published September 24, 2013, effective March 24, 2014) deliberately aligned their mechanics: both now require annual AAPs, quantitative benchmarks or goals, self-identification invitations at the pre-offer and post-offer stages, data collection on applicant and hiring rates, and specific recordkeeping.
The alignment was intentional regulatory design. OFCCP wanted contractors to treat both programs as a single compliance workflow with two data tracks. That is why the invitation to self-identify can be combined, why the recordkeeping retention period is two years for both (one year for smaller contractors), and why the audit trail requirements mirror each other. But the alignment has limits. The protected-class definitions, the benchmark-setting methodology, and the specific outreach requirements differ, and OFCCP evaluates each program separately during a compliance review.
Side-by-Side Comparison
| Feature | VEVRAA | Section 503 |
|---|---|---|
| Statute | 38 U.S.C. § 4212 | 29 U.S.C. § 793 |
| Protected group | Protected veterans (4 categories) | Individuals with disabilities |
| Benchmark/goal | Contractor-set hiring benchmark (5 factors) or OFCCP's published benchmark (~5-6%) | Fixed 7% utilization goal per job group |
| AAP update | Annually | Annually |
| Self-ID timing | Pre-offer invitation; post-offer invitation | Pre-offer invitation; post-offer invitation |
| Data collected | Applicant, hire, and benchmark progress data by veteran category | Applicant, hire, and goal progress data; voluntary self-ID rate |
| Outreach | Specific listing with local employment service delivery systems (e.g., state workforce agencies, JVSG partners) | Outreach to disability organizations, plus documented annual evaluation of outreach effectiveness |
| Threshold (post-2024) | $150,000+ contract | $150,000+ contract |
| Recordkeeping | 2 years (1 year if under 150 employees) | 2 years (1 year if under 150 employees) |
| Subcontract coverage | Covered subcontract over threshold | Covered subcontract over threshold |
The Four Categories of Protected Veterans Under VEVRAA
VEVRAA's protected class is not a single group but four defined categories, and contractors must track hiring data for each. Veterans with service-connected disabilities are veterans entitled to compensation under laws administered by the VA, or discharged or released from active duty for a service-connected disability. Recently separated veterans are those discharged within the preceding three years. Active Duty or wartime campaign badge veterans are veterans who served on active duty during a war or in a campaign or expedition for which a campaign badge was authorized. Armed Forces Service Medal veterans are those who participated in a U.S. military operation for which an Armed Forces Service Medal was awarded pursuant to Executive Order 12985. A single veteran can fall into multiple categories, and OFCCP expects contractors to capture that overlap in their data.
The benchmark-setting process under 41 CFR 60-300.45 requires contractors to consider five factors when establishing their own benchmark: the veteran population in the surrounding labor area, the number of veterans seeking employment, the contractor's workforce composition, its hiring projections, and the effectiveness of its outreach. Alternatively, contractors can simply adopt OFCCP's published national benchmark, which OFCCP recalculates periodically. The self-set benchmark must be applied annually and documented, and contractors must report progress toward it in their AAP. There is no quota and no penalty for missing the benchmark, but a persistent gap combined with weak outreach is a classic trigger for conciliation efforts during an audit.
Section 503's 7 Percent Goal and the Self-Identification Problem
Section 503's utilization goal is deceptively simple: 7 percent of each job group must be individuals with disabilities. But the number is only as good as the self-identification data behind it, and self-identification of disability is notoriously underreported. Studies consistently show that a large share of employees with disabilities choose not to disclose, fearing stigma or career consequences. OFCCP's 2013 rule addressed this by requiring contractors to invite self-identification at both the pre-offer stage (using OFCCP's prescribed form) and the post-offer stage, and by requiring contractors to invite all employees to self-identify every five years using the prescribed language, with reminders that employees may update their status at any time.
Contractors must also collect and analyze data on the ratio of applicants and hires who are individuals with disabilities, conduct annual effectiveness assessments of their outreach and recruitment efforts, and document what they learned and what they changed. The annual assessment requirement is unique to Section 503 in its explicitness — VEVRAA requires outreach but the formal annual effectiveness evaluation with documented conclusions is a Section 503 hallmark. Contractors that treat the assessment as a rubber stamp routinely get flagged, because OFCCP compliance officers look for evidence that the assessment actually changed behavior, such as new partnerships with disability-serving organizations or revised application processes.
The 2024-2026 Regulatory Upheaval: What Changed and What Still Stands
Contractors operating in 2026 need to understand the recent regulatory turbulence. Following executive action in early 2025, OFCCP rescinded the affirmative action regulations under Executive Order 11246, and the agency closed all pending compliance reviews before resuming processing of Section 503 and VEVRAA complaints. Critically, the EO 11246 rescission did not touch Section 503 or VEVRAA. Both statutes rest on their own statutory authority — Section 503 on the Rehabilitation Act and VEVRAA on Title 38 — not on the executive order, so their regulations remain in force and OFCCP continues to process complaints under both. A White House budget proposal has at times targeted OFCCP's Section 503 and VEVRAA enforcement, but as of September 2026 both programs remain legally operative for covered contractors.
The practical takeaway is asymmetric risk. Contractors who dismantled their EO 11246 AAP infrastructure in 2025 often lost the shared data systems, applicant-flow tracking, and outreach documentation that Section 503 and VEVRAA compliance depends on. Rebuilding those systems is now necessary work. Meanwhile, the complaint-driven enforcement model means individual veterans and individuals with disabilities can file complaints directly with OFCCP, which investigates and can pursue remedies including back pay and, for VEVRAA, potential debarment. Contractors should assume that a complaint can arrive at any time and that their AAP, self-ID forms, and outreach records will be the first documents requested.
Practical Steps to Run Both Programs Correctly
First, confirm coverage. Check whether you hold a federal contract or subcontract of $150,000 or more (or serve as a covered subcontractor on one). If yes, both statutes apply unless an exemption applies, such as contracts for work performed outside the United States or certain subcontractor relationships. Second, build a combined AAP calendar: both AAPs update annually, and most contractors align them with the same plan year to share data collection infrastructure. Third, use a single self-identification workflow with the OFCCP-prescribed forms, but keep the data segregated by protected class and, for VEVRAA, by veteran category. Fourth, set your VEVRAA benchmark annually with documented factor analysis, or adopt OFCCP's published benchmark and document that choice. Fifth, run the Section 503 annual effectiveness assessment as a real exercise with written conclusions and at least one concrete change per year.
Sixth, invest in outreach that produces records. Listing jobs with state workforce agencies and veteran employment partners satisfies VEVRAA's listing requirement; partnerships with disability organizations, accessible application systems, and participation in veteran hiring events build the audit trail both programs demand. Seventh, train recruiters to understand that self-ID invitations must be extended at the right stages and that the data flows into the AAP. Platforms like vetwork.app exist partly because this workflow — sourcing protected veterans, tracking outreach, and generating the data contractors need for both AAPs — is genuinely hard to run manually across dispersed hiring teams.
Common Mistakes and How Auditors Catch Them
The most frequent VEVRAA mistake is treating the benchmark as a set-and-forget number. Benchmarks must be revisited annually; a benchmark set in 2022 and never re-evaluated is an audit finding waiting to happen. The most frequent Section 503 mistake is a self-ID process that suppresses disclosure — for example, collecting disability status on a form that also asks for other demographic information, or failing to use the prescribed invitation language. Both mistakes surface quickly because OFCCP compares your reported utilization against regional labor market data and against your own applicant-flow numbers.
Other recurring errors include failing to list job openings with the appropriate employment service delivery system (a technical violation that is easy to prove and hard to defend), not tracking veteran category data separately, treating the five-year employee self-ID invitation as optional, and assuming the 2024 threshold increase means all obligations ended — the increase changed coverage, not the obligations of contractors still covered. Finally, contractors sometimes assume that because EO 11246 enforcement wound down, OFCCP is dormant. The agency's 2025-2026 posture of closing reviews while processing Section 503 and VEVRAA complaints suggests the opposite: enforcement has shifted from proactive audits toward complaint-driven investigations, which concentrate risk on contractors with poor individual-level practices rather than those with weak paperwork alone.
When to Act and What Noncompliance Costs
Act now if any of the following apply: you hold a new federal contract of $150,000 or more (the AAP must be in place within 120 days of contract commencement and updated annually thereafter); you crossed the threshold through a new subcontract; you have not updated your VEVRAA benchmark within the last 12 months; or you have not completed a Section 503 annual effectiveness assessment for the current plan year. The cost of noncompliance ranges from conciliation agreements with corrective action to back pay awards, and in egregious VEVRAA cases, debarment from federal contracting — an existential risk for contractors whose revenue depends on government work. Legal defense costs alone for a contested compliance review routinely run into six figures.
The economics favor prevention. A combined Section 503/VEVRAA AAP, whether built in-house or through a consultant (typical consultant fees range from $5,000 to $25,000 annually depending on workforce size and number of establishments), is far cheaper than a single adverse finding. And beyond compliance, the underlying talent case is real: protected veterans and individuals with disabilities represent substantial, underutilized labor pools, and contractors who build genuine pipelines — rather than paper compliance — tend to see the data problem solve itself, because utilization rates rise when hiring practices actually reach these candidates.