How the 2025 FAR Part 19 Overhaul Lets You Direct-Award AI Work to an SDVOSB

What exactly changed in the FAR text?

Old FAR 19.1406(a) listed five conditions for an SDVOSB sole-source award. The third was the problem. It read, in part: the requirement “is not currently being performed by an 8(a) participant … or has been accepted as a requirement by SBA under subpart 19.8.” In plain terms: if an 8(a) firm had the work, or SBA had pulled the requirement into the 8(a) program, you couldn’t hand it to an SDVOSB on a sole-source basis. Full stop.

The Revolutionary FAR Overhaul deleted that condition outright and moved the SDVOSB sole-source authority to new FAR 19.106-3. The surviving conditions are the ones you already know: no reasonable expectation of two or more SDVOSB offers, within the dollar threshold, a responsible contractor, and a fair and reasonable price. The 8(a) entanglement is simply no longer one of them.

One quieter wording change matters too. The old text said a CO “shall consider” an SDVOSB sole-source “before considering small business set-asides.” The new 19.106-3 says a CO “may consider” it. The mandatory priority cascade among the socioeconomic programs is gone; SDVOSB sole-source is now a discretionary tool you weigh on its merits, not a box you’re forced to check in a fixed order.

What does the 8(a) “automatic release” actually do for you?

This is the part that changes your week, not just your reading.

Under the old regime, moving a follow-on requirement out of the 8(a) program and into an SDVOSB set-aside meant requesting a formal release from SBA — the procedural expression of the “once 8(a), always 8(a)” doctrine. That request, SBA’s review, and the back-and-forth could eat months. For a program office trying to inject AI engineering scope into an existing 8(a) application-support footprint, it was often the single longest step in the whole acquisition.

New FAR 19.108-11 flips it. A follow-on requirement is automatically released from the 8(a) program when it will be set aside under the SDVOSB, HUBZone, or WOSB programs. No release request. No waiting on an SBA letter. You make the decision, document it, and move.

Concretely: if you have a long-running 8(a) IT-sustainment contract and you want to carve off a discrete AI scope — model evaluation, a RAG pipeline build, an agentic workflow, MLOps tooling — and place it with a certified SDVOSB AI specialist, the old “release request → SBA review → set-aside decision” sequence collapses into a contracting-officer decision. That is the practical mechanism behind the headline.

One caution worth carrying into your file: the automatic-release rule may run ahead of SBA’s own regulations at 13 C.F.R. § 124.503(d)(1), and SBA is expected to conform its rules but hasn’t yet. Both Holland & Knight and PilieroMazza flagged the conflict in their 2025 analyses. Document your release decision cleanly until SBA catches up.

Do you still need a J&A? Yes — but not the one you think.

This is the single most-misunderstood mechanic in SDVOSB sole-source, and getting it right is what keeps your award off the protest docket.

SDVOSB sole-source is an exception to full and open competition, authorized by the Veterans Benefits Act of 2003 at FAR 6.302-5(b)(6). Because it’s a 6.302-5 exception, FAR 6.302-5(c)(2) requires a written justification and approval per 6.303 and 6.304 — SDVOSB awards are not on the short list of actions exempt from that requirement. So yes, you write a J&A.

But here’s the distinction that saves you weeks of unnecessary work: it is not a FAR 6.302-1 “only one responsible source” justification. You do not have to demonstrate that a single firm is the only one capable of performing. That showing is expressly not required. Your J&A documents the statutory authority (15 U.S.C. 657f), the four conditions of 19.106-3, your market research, and your fair-and-reasonable price determination — and that’s it. It’s a fundamentally lighter document than a uniqueness justification. The end-to-end pricing and market-research workflow lives in sole-sourcing AI to an SDVOSB: the $5M direct-award path.

Approval authority follows the ordinary 6.304 dollar tiers: at or below $900,000, the contracting officer; above that up to $20 million, the procuring activity’s competition advocate (non-delegable). Since SDVOSB sole-source caps at $5M for services and $8.5M for manufacturing, you’ll sit in the CO or competition-advocate tier every time.

What’s the threshold — and what’s the catch?

The current sole-source thresholds are $5 million for services and any non-manufacturing NAICS, and $8.5 million for manufacturing NAICS. These are the standing, statutorily-indexed ceilings under 41 U.S.C. 1908 — in place since the 2020 inflation-adjustment cycle, not newly raised. The October 2025 governmentwide adjustment (FAC 2025-06) moved other thresholds — the simplified acquisition threshold, micro-purchase, and TINA — but left these untouched.

The catch: the FAR Part 19 model deviation text still recites the old $4M/$7M figures, an unharmonized conflict the FAR Council had not fixed for Part 19 as of mid-2026. The statutory inflation-adjusted thresholds govern — they implement a five-year CPI adjustment required by law — but if your shop is working directly off the deviation text, you may see the lower numbers. Confirm with your policy office before you scope a requirement against the higher ceiling.

And the rule that predates all of this still applies: you cannot split or subdivide a single requirement to squeeze it under the threshold. If the genuine need is $12 million, decompose it into honest phases — discovery, build, sustainment — and sole-source the first real tranche while you compete the rest. Don’t slice one coherent requirement into $4.9M salami; it won’t survive thirty seconds of protest scrutiny.

Has your agency actually adopted it yet?

Don’t assume. The rewrite lives in class deviations, not the codified FAR — agencies opt in one at a time, and a final rule has not published. As of mid-May 2026, FAR Case 2026-004 (the rulemaking that would codify these Part 19 changes) was still a draft rule under OFPP review, with no proposed or final rule in the Federal Register.

Adoption is nonetheless effectively governmentwide as of Q1 2026:

• GSA — Class Deviation RFO-2025-19, effective November 3, 2025.
• DoD / Department of War — Class Deviation 2026-O0037, effective February 1, 2026.
• DOE — Policy Flash PF 2026-10, December 2025.
• VA — Part 19 class deviation, while preserving the Veterans First program at VAAR Part 819.
• SEC — class deviation dated February 25, 2026; NASA revised its FAR Supplement; and DHS, Treasury, HHS, DOJ, EPA, USDA and most civilian agencies have filed deviations.

To check your own house: the FAR Overhaul deviation guidance page at acquisition.gov lists every agency that has filed a Part 19 class deviation. If yours hasn’t, the codified FAR 19.1406 — including the old (a)(3) 8(a) blocker — still controls, and you’re back to a competitive set-aside or a formal SBA release.

The five-minute version: how to run the award

For a CO under an agency that has adopted the deviation:

1. Scope it under the ceiling

   ≤$5M services / $8.5M manufacturing, without artificially splitting the requirement.

2. Do real market research

   Sufficient to support the “no reasonable expectation of two SDVOSB offers” finding — a documented SAM and SBA certification-database lookup in the relevant NAICS (commonly 541512, 541511, 541519, 541715), plus capability-statement review. Reasonable expectation, not certainty; you needn’t prove only one firm can do it.

3. Verify SBA-certified SDVOSB status in SAM

   Self-certification ended December 22, 2024 — the firm must be SBA-certified in VetCert.

4. Write the J&A under 6.302-5

   Statutory authority 15 U.S.C. 657f, not 6.302-1. Route for approval per the 6.304 tier.

5. Synopsize and post

   Per FAR Part 5, and post the J&A within 30 days of award (screen for proprietary data first).

6. Determine fair and reasonable price

   Analysis appropriate to value and complexity.

7. Include the clauses

   FAR 52.219-27 (SDVOSB sole-source notice) and 52.219-14 (Limitations on Subcontracting: the SDVOSB self-performs at least 50% of a services contract, with similarly-situated SDVOSB subs counting toward the 50%).

Where contracting officers get this wrong

Four traps, in order of how often they bite:

• Thin market research. This is the number-one reason an SDVOSB sole-source J&A fails at GAO. Document the certified-vendor lookup and the basis for your two-offer finding. “I knew a firm” is not market research.
• Citing the wrong authority. Don’t write a 6.302-1 uniqueness justification. You’re holding yourself to a standard the law doesn’t require and inviting a protester to argue you failed to meet it.
• Forgetting SBA’s appeal right. New FAR 19.106-3(b) preserves SBA’s right to appeal a CO’s decision not to make an SDVOSB sole-source award. There’s no symmetric challenge to a decision to make one — the asymmetry favors using the authority, not avoiding it.
• Ignoring the Rule of Two. It survives above the simplified acquisition threshold. If your market research turns up two or more capable certified SDVOSBs, you set aside competitively — you don’t sole-source. The Court of Federal Claims’ Tolliver Group decision is a reminder that a Rule-of-Two analysis is expected before acquisition decisions, and skipping the documentation is how agencies lose.

If your money is VA money, the governmentwide rewrite doesn’t displace the Veterans First Contracting Program. VAAR 819.7008 keeps the VA’s own SDVOSB sole-source authority at the same $5M threshold, the VA Rule of Two under 38 U.S.C. 8127(d) still applies even on Schedule orders per Kingdomware, and the VA J&A posture is slightly more formal — confirm against VAAR Part 819 before you proceed. For the broader credentialing argument, see SDVOSB is leverage. Use it. and the spend-policy mapping in OMB M-25-21 reads like a buying spec. And to keep year-end timing realistic, year-end funds, fast walks the calendar.

Working with Truvisory

If you’ve identified an AI/IT modernization requirement that fits this lane, the vendor side of the equation is straightforward to verify. Truvisory is a Denver-based, SBA-verified Service-Disabled Veteran-Owned Small Business that builds and ships production AI systems on Cloudflare’s edge under fixed-scope, 30-to-90-day delivery.

You can confirm all of it in SAM.gov and SBA’s certification database before you write a line of the J&A. When you’re ready, start with our federal capability statement and a scoping call — and for the wider modernization picture, the federal AI pillar lays out the full path.