Direct Answer: Which Veteran Rules Still Apply to Federal Contractors?
Federal contractors and their subcontractors generally must comply with the Vietnam Era Veterans’ Readjustment Assistance Act of 1974, as amended, rather than the former Executive Order 11246 framework. Current VEVRAA obligations include affirmative action for qualified protected veterans, outreach to employment pools of such veterans, and annual reporting to the Office of Federal Contract Compliance Programs when a covered contract contains the applicable clause. These are federal contracting requirements, not a general requirement that every American employer hire veterans or maintain a numerical veteran quota. The obligations are triggered by covered federal contracts and subcontracts, while the consequences of noncompliance can include payment withholding, contract termination, debarment, and other remedies.
Also worth reading: VETS-4212 Processing Time: How Long Does Federal Contractor Reporting Take in 2026? · How Can a Veteran Talent Network for Employers Transform Your Hiring Strategy? · What Are the Latest Veteran Retention Rate Benchmarks for Employers in 2026?
The legal position changed materially in 2025. President Donald Trump signed Executive Order 14173 on January 21, 2025, directing the administration to cease enforcement of Executive Order 11246, and OFCCP published a final rule on April 11, 2025, removing several affirmative-action and disability-related provisions from 41 CFR Chapter 60. VEVRAA, however, was not eliminated because it is a separately enacted statute enforced through the same compliance system. An organization should therefore use the contract date, solicitation terms, subcontract flow-down language, and current agency guidance to determine its obligations rather than assuming that the 2025 EO 11246 changes also canceled veteran rules.
| Covered activity | What generally applies in 2026 | What does not automatically apply |
|---|---|---|
| Prime federal contract with VEVRAA clause | Veteran affirmative action, outreach, and annual reporting | A statutory nationwide veteran hiring percentage |
| Covered subcontract with VEVRAA flow-down clause | Subcontractor compliance through contractual requirements | Automatic coverage merely because a private company serves another government contractor |
| Purely commercial or non-covered employer | No federal VEVRAA obligation from private work alone | A universal duty to collect veteran status or report to OFCCP |
| Disabled veterans or employees with disabilities | Separate disability protections may apply | Former EO 11246 disability self-identification and utilization goals |
| Small business seeking SDVOSB status | Separate DoD and SBA program criteria | Preferred status under every federal procurement |
Before 2025, many contractors viewed OFCCP regulation as one combined system under Executive Order 11246, which addressed race, sex, disability, and veteran participation. Executive Order 14173 and OFCCP’s 2025 final action removed the regulatory provisions implementing EO 11246, including requirements associated with those former equal-opportunity clauses. The practical lesson is that a company should not continue representing a rescinded 11246 clause, reporting template, goal, or self-identification procedure as a current federal requirement without checking the contract and current regulations.
Veteran obligations survived that restructuring. VEVRAA generally requires covered contractors to make affirmative action to hire and advance qualified protected veterans without regard to race or color and to notify applicants of their employment opportunities in military service bases, state employment offices, and United States Employment Service offices. Covered entities must also submit an annual employment report to OFCCP, historically Form 0950, using the veteran data collected through the employment opportunity report. These duties do not amount to reserving a fixed percentage of jobs, and they do not authorize a contractor to hire an unqualified veteran merely to satisfy a quota.
The term “protected veteran” comes from 38 U.S.C. § 4212 and is narrower than every person who has served. A qualifying veteran must have at least four years of active duty, service under a qualifying call to active duty, or service as a qualifying National Guard or Reserve member, subject to the statute’s discharge provisions. The definitions and verification process also matter when contractors classify applicants, calculate statistics, or select veteran-related employees for compliance purposes.
Contract Coverage and Reporting Thresholds
The first factual question is whether a particular prime contract or subcontract contains the VEVRAA clause. A contractor is not automatically subject to every OFCCP reporting rule because it is incorporated, licensed, licensed by, or performs work for the federal government. Coverage depends on the contract terms, the statutory threshold, and whether the contract or subcontract is covered. Prime contractors ordinarily pass certain clauses down to subcontractors under FAR clause 52.222-35, Equal Opportunity for Veterans, and clause 52.222-36, Equal Opportunity for Small Business Concerns Pertaining to Disabled Veterans.
A commonly used VEVRAA coverage threshold is $150,000 for a prime contract or subcontract, but a dollar figure alone is not enough to establish coverage. The clause must be present, the contract must satisfy the relevant exception rules, and the contractor must determine whether its performance or workforce falls within the reporting criteria. Federal procurement professionals should examine the actual solicitation and award instrument rather than relying on a blog stating that every contract over $150,000 is covered. The old $2,500 threshold frequently seen in summaries referred to a different requirement and should not be substituted for the current VEVRAA analysis without checking the governing clause.
The applicable OFCCP employment opportunity report is still a central control, although exact forms and instructions can change through rulemaking, system migration, or enforcement guidance. A compliant process ordinarily collects whether the applicant is a protected veteran, whether the veteran is disabled, and whether the applicant is covered by the definition without creating barriers to employment. Employers should be able to explain why the information was requested, how it is stored, who may access it, and how it contributes to the required workforce calculations. A vendor promising a generic “OFCCP survey” without distinguishing current law from obsolete templates creates compliance risk.
What Small and Veteran-Owned Businesses Should Understand
Service-Disabled Veteran-Owned Small Business status is different from VEVRAA compliance. An SDVOSB is a small business concern at least 51 percent owned by one or more qualifying service-disabled veterans, as defined by 38 U.S.C. § 1401, who also hold the required controller and management roles. An SDVOSB must also satisfy the applicable size standard and the Department of Defense program’s additional requirements, including ownership, control, and documentation rules. Owning a business because of military service does not, by itself, create eligibility.
Program eligibility can create a competitive advantage in suitable federal solicitations, but it is not a universal preference over all commercial competitors. Set-aside competition is limited to properly structured opportunities, while an eligible contractor may compete as an incumbent or other bidder in an unrestricted procurement. The Small Business Administration administers SBA Mentor-Protégé and small-business programs, while DoD administers the SDVOSB program for its particular contracting mission. A company should obtain a current decision from the relevant agency rather than assuming that a state registry listing or self-awarded certificate establishes federal status.
There is also a practical distinction between veteran hiring, subcontracting, and acquisition preferences. VEVRAA concerns employment practices for covered federal work; an SDVOSB designation concerns ownership and control; and a mentor-protégé agreement concerns the treatment of certain small-business subcontractors. These programs may intersect, but one does not prove satisfaction of the others. Employers pursuing a veteran-owned supplier network should record the exact certification requested, the government customer, and the procurement vehicle instead of treating “veteran-owned” as one undifferentiated procurement category.
| Objective | Relevant mechanism | Main eligibility feature | Typical limitation |
|---|---|---|---|
| Meet veteran employment obligations | VEVRAA and contract clause | Contract contains the applicable requirement | No fixed national hiring quota |
| Compete in an SDVOSB set-aside | DoD SDVOSB certification | At least 51% qualifying veteran ownership plus control and size rules | Applies only to covered programs and contracting channels |
| Find experienced veteran suppliers | Acquisition search and supplier outreach | Supplier meets the buyer’s capability requirements | A self-description does not establish a set-aside status |
| Build a talent pipeline | Employer recruiting and network services | Candidates match defined job requirements | Network reach cannot waive employment qualifications |
| Diversify federal subcontractors | SBA or other small-business programs | Applicable small-business and program criteria | Program-specific rules and limitations |
A company should begin by assembling its federal contracts, modifications, solicitations, and subcontracts, then search them for 52.222-35, 52.222-36, and related provisions. Legal and procurement teams should identify every covered entity, the contracting officer’s point of contact, the applicable reporting period, and any option years or modifications that affect the agreement. Vendors should not ask a prime contractor to treat a commercially private agreement as federal solely because the end customer may be a government agency; the contractual chain and terms determine responsibility.
The next step is to test recruiting, applicant tracking, and reporting systems against current instructions. This includes reviewing protected-veteran data fields, consent and privacy language, retention settings, role-based access, export controls, and audit logs. HR should train recruiters to ask the statutory question consistently and to avoid discriminating against veterans, applicants with disabilities, or applicants based on protected characteristics. Systems should not manufacture a result by converting self-identification data into unsupported utilization goals that current rules no longer require.
A useful operational approach is to define owners and review dates. The contracts manager can own clause interpretation, HR can own applicant and workforce records, legal can own retention and dispute risk, and finance can own payment consequences. Quarterly internal reviews are often more practical than waiting for an annual report, because missing a hiring report, losing records, or placing a vendor flow-down clause in the wrong agreement may create problems before year-end. Documentation should show what was checked, who made the determination, and which version of the rule or contract was used.
There is no universal federal price for a compliant veteran-compliance system. Costs depend on the number of records, contracts, applicants, reporting entities, and integrations, so a market quote can range from several hundred dollars for a small manual configuration to tens of thousands of dollars for a multi-entity applicant-tracking implementation. OFCCP filing itself may be available without a fee, but advice, software, outreach events, recruiting, and legal review are separate cost categories. Organizations should price a defensible process rather than purchase a large package of obsolete 11246 goals merely because a vendor labels them mandatory.
Common Mistakes and Misleading Compliance Claims
The most common error is treating all veteran-related federal programs as one rule. A contractor may correctly comply with VEVRAA while using an SDVOSB name that is not accepted for a particular procurement, or it may be small and eligible for a contract without filing an OFCCP employment report. Another error is assuming that rescission of EO 11246 means veterans are no longer relevant to federal contractors. That conclusion is incorrect because VEVRAA is a statute and the contract clauses can remain enforceable.
A second problem is confusing a reporting obligation with a hiring target. Historical data may show veteran representation rates, and contractors may use internal goals for management purposes, but the statute does not impose a simple federal percentage such as 5%, 7%, or 8% on all covered employers. Any statement that a particular numerical target is mandated should be tied to a specific clause, contract, program, or verified rule. Vendors that promise automatic “OFCCP utilization” calculations should be asked to identify the current legal basis and explain how they account for contract coverage.
The third mistake is ignoring former disability and self-identification requirements. Disabled veterans may still receive protections under the Rehabilitation Act, the Americans with Disabilities Act, and the applicable contract provisions, even when the former EO 11246 self-identification and utilization framework is not current law. Employers should not collect more sensitive information than needed, and they should not delete a legally required applicant data point simply because an old screen says it belongs to a rescinded program. A privacy-compliant process must reflect the actual remaining purpose for collection.
Finally, companies often fail to separate official certification from marketing language. “Veteran-owned,” “service-disabled veteran-owned,” “SDVOSB certified,” “small business,” and “SBA-certified” are not interchangeable terms. Buyers and talent platforms should request the agency, certification number where applicable, expiration or renewal information, ownership evidence, and the exact procurement use for which the claim is valid. This is especially important for workforce SaaS providers that display veteran-related labels without knowing whether the underlying business is a government contractor, a veteran employer, or a veteran-owned small business seeking set-aside access.
When to Act and How to Evaluate Workforce-SaaS Support
A prospective bidder should act during procurement preparation rather than after award. Contract clauses may be reviewed during market research, and a prime contractor may need a vetted subcontractor network before performance begins. Organizations should confirm their position before a solicitation is issued, negotiate a proper flow-down clause, and assign responsibility for reporting. Waiting until the first annual filing or an OFCCP complaint can leave insufficient time to correct records, notify decision-makers, or resolve a subcontracting gap.
A workforce platform can help by mapping veteran-related talent, recording verified applicant preferences, and measuring outreach to veterans, but software is not a substitute for legal interpretation or hiring decisions. For a B2B veteran-talent network, the strongest product claim is not that it guarantees federal compliance. It is that it helps employers identify relevant candidates, communicate outreach activity, preserve a traceable recruiting record, and produce the data needed for a contract-specific compliance process. Buyers should test those functions with a realistic vendor scenario and sample data rather than relying on a generic feature count.
Evaluate SaaS vendors using a short evidence-based test. Ask whether the vendor distinguishes VEVRAA from EO 11246, understands current OFCCP instructions, supports subcontract flow-down documentation, and allows data minimization. Confirm whether it can export records for a covered reporting entity, segregate self-reported veteran information, document consent, and support an audit. Also ask what the vendor cannot do, since a tool that will not determine contract coverage, provide legal advice, or certify SDVOSB status should not be marketed as if it can.
As of September 26, 2026, organizations should use the current CFR and agency instructions as the controlling source because regulations and implementation systems can change. Contract text remains important, and archived third-party summaries can be stale. Before purchase or implementation, have procurement counsel or a compliance specialist compare the proposed workflow against the actual award, current 41 CFR Chapter 60, the applicable FAR clauses, and 38 U.S.C. § 4212. That review is more reliable than any one promise of automatic compliance.
Bottom Line for Federal Contracting and Veteran Talent Programs
Federal contractor veteran rules in 2026 are best understood as a contract-specific employment framework, not a blanket veterans-only hiring mandate. VEVRAA remains the central statute for covered federal contractors and subcontractors, including affirmative-action, outreach, and reporting duties. The 2025 changes affecting Executive Order 11246 altered the former race, sex, and disability program provisions, but they did not create a blanket exemption from veteran contracting requirements.
The right response is precise documentation: identify covered contracts, understand the applicable clause, collect necessary data carefully, and distinguish employment compliance from SDVOSB ownership status. Employers can improve veteran access to suitable jobs without promising unlawful quotas or collecting unnecessary personal information. For a B2B workforce platform, that distinction is commercially valuable and operationally sound because it supports evidence, recruiter consistency, and defensible decisions without implying that software alone can guarantee government contracting success.