What Are the SBA's SDVOSB Joint Venture Rules Under 13 CFR 125.18?

An SDVOSB Joint Venture is a separate legal entity formed by a Service-Disabled Veteran-Owned Small Business (SDVOSB) and one or more partners to pursue federal contracts. Under 13 CFR 125.18, the SDVOSB partner must own at least 51% of the JV, must control it, and must perform at least 40% of the JV's work. Specific rules differ for Mentor-Protege JVs. This guide covers the regulatory baseline.

Read the complete guide: How Do Primes Evaluate, Structure, and Contract with an SDVOSB IT Subcontractor? For the broader vehicle-selection question (NDA, Teaming Agreement, CTA, or JV), see NDA vs. Teaming Agreement vs. CTA vs. Joint Venture.

When Does the SBA Treat a JV as a Small Business?

Joint Ventures are generally subject to affiliation under 13 CFR 121.103, which means the combined size of the JV partners normally counts against the JV's small-business size determination. The SBA's general rule is that a JV between a small business and a large business is not itself small.

Two narrow exceptions allow a JV to qualify as small: an SBA-approved Mentor-Protege JV under 13 CFR 125.9, and a JV among small businesses where each partner is small under the size standard for the relevant North American Industry Classification System (NAICS) code. The first exception is the structural mechanism behind almost every large-prime + SDVOSB JV that pursues a major Indefinite Delivery, Indefinite Quantity (IDIQ) vehicle.

The three-in-two rule, codified at 13 CFR 121.103(h), limits a JV to three contract awards over a two-year period from the first contract award. After the third award or the close of the two-year window, the JV cannot receive additional contract awards as a small business under that JV vehicle. Partners who want to continue pursuing work after the limit form a new JV.

The three-in-two rule applies per JV vehicle, not per partner pair. The same two firms can form a new JV after their first one hits the limit and continue pursuing work. Each JV is subject to its own three-in-two limit, its own SAM.gov registration, its own UEI, and its own operating agreement. The administrative overhead is real, but it is not a structural barrier; it is a forcing function for periodic JV refresh that the SBA built into the rule.

What Are the SDVOSB-Specific JV Requirements?

13 CFR 125.18 imposes four SDVOSB-specific requirements on top of the general JV rules. Each is independently enforceable, and failing any one disqualifies the JV from SDVOSB set-aside competition.

51% ownership by the SDVOSB. The SDVOSB partner must own at least 51% of the JV. The remaining 49% may be held by one or more partners, including a non-SDVOSB partner. The SDVOSB ownership must be unconditional and may not be subject to arrangements that effectively dilute it (buyout provisions tied to performance, supermajority voting requirements that give a minority partner control, or financing structures that transfer economic ownership over time).

SDVOSB managing member. The JV must designate the SDVOSB partner as the managing member of the JV operating agreement. The managing member has authority over the day-to-day management of the JV. The managing-member designation is not a paper formality; the SBA will examine actual operating practice if challenged.

Designated responsible manager. The JV must designate a service-disabled veteran of the SDVOSB partner as the JV's responsible manager. This individual must have direct, day-to-day involvement in the management and decision-making of the JV. The responsible manager cannot be an employee of the non-SDVOSB partner. The SBA examines this designation closely on protests.

40% performance-of-work on the SDVOSB partner. The SDVOSB partner must perform at least 40% of the JV's work. This is a separate test from the 50% rule under FAR 52.219-14, which applies to the JV as a whole. Both tests must be satisfied. The SDVOSB-specific 40% rule is what prevents a JV from being structured as a vehicle that uses SDVOSB qualifying status to access the contract while passing the actual work to a non-SDVOSB partner.

For SDVOSB set-aside competitions, the JV itself must be certified as an SDVOSB JV in the SBA VetCert program. The SDVOSB certification of the individual partner does not automatically extend to the JV. The JV's SDVOSB certification is a separate application.

What Is the Difference Between a Populated and Unpopulated JV?

A populated JV has its own employees and pays them through its own payroll. The JV operates as a self-contained entity with all of the labor relationships, tax filings, and insurance obligations of an employer. Populated JVs are administratively heavier but produce a cleaner accounting story when the JV's revenue and expenses are entirely contained within its own books.

An unpopulated JV does not have its own employees. Each partner contributes labor under its own employment relationship and bills the JV for the cost of that labor. The JV pays the partners; the partners pay their own employees. Unpopulated JVs are the predominant structure for SDVOSB-prime federal IT JVs because they avoid the cost of standing up a separate employment infrastructure for what may be a temporary entity.

The choice has tax implications, indirect-cost implications, and federal employer-of-record implications. 13 CFR 125.18(b)(2) allows both structures. Most agency contracting officers are familiar with both. Tax treatment for partnerships is governed by Internal Revenue Service (IRS) rules at irs.gov/businesses/partnerships. The JV operating agreement should explicitly state which structure has been chosen and how labor, indirect costs, and profit are accounted for under the chosen structure.

How Does the Mentor-Protege Program Change the JV Rules?

The SBA's Mentor-Protege Program (MPP) at 13 CFR 125.9 is the affiliation safe harbor that makes large-prime + SDVOSB JVs structurally workable. The All-Small MPP merged into a single program in 2020 (replacing the prior 8(a) MPP and All-Small MPP as separate programs) and is now the primary mechanism for SDVOSB JVs that include a non-SDVOSB partner above the small-business size standard.

Under an SBA-approved Mentor-Protege Agreement (MPA), the mentor (large) and the protege (SDVOSB) may form a JV that is exempt from affiliation. The JV is treated as a small business for size purposes even though one of its partners is a large business. The exemption is the principal reason large primes invest in the MPP: it converts a non-viable JV structure into a viable one.

The protege-specific JV rules from 13 CFR 125.18 still apply: the protege must own at least 51% of the JV, must designate a service-disabled veteran of the protege as the responsible manager, and must perform at least 40% of the JV's work. The three-in-two rule still applies. The MPP exemption removes affiliation; it does not remove the structural SDVOSB-specific requirements.

MPA approval is an administrative process that takes time. Applications are filed through the SBA's MPP portal at sba.gov. Approval requires a substantive mentor-developmental plan describing how the mentor will develop the protege's capability over the course of the relationship. Approvals can take several months. Plan the approval timeline backward from the first JV pursuit.

What Goes in the JV Operating Agreement?

13 CFR 125.18(b)(2) lists 12 mandatory provisions that must appear in an SDVOSB JV operating agreement. Each is independently enforceable. A JV operating agreement that omits any one of them is a defective agreement and may be cited in a size protest.

1. Purpose of the JV, including the specific contract or contracts the JV will pursue
2. SDVOSB partner identification and 51% ownership designation
3. Designation of the SDVOSB partner as the managing member with authority over day-to-day management
4. Designation of a service-disabled veteran of the SDVOSB partner as the responsible manager
5. Itemized list of major equipment, facilities, and resources each partner will contribute, with quantification
6. Source of labor for each contract, including identification of the partners that will provide labor
7. Performance-of-work split, with the SDVOSB partner performing at least 40% of the JV's work
8. Profit distribution commensurate with each partner's contribution to the JV
9. Bank account requirements (typically the JV's own bank account in the JV's name)
10. Accounting and audit rights for each partner
11. Procedures for amending the operating agreement, including the SDVOSB partner's controlling vote
12. Procedures for dissolution and distribution of assets at JV termination

Most JV operating agreements add project-specific addenda for each contract the JV pursues. The addenda detail the labor split, the performance-of-work allocation, and the indirect-cost allocation specific to that contract. The addenda are subordinate to the operating agreement; they cannot override the 13 CFR 125.18(b)(2) provisions.

The operating agreement is an SBA-reviewable document. On a size protest or an SDVOSB status protest, the SBA's Office of Hearings and Appeals at sba.gov/oha will examine the operating agreement against the 13 CFR 125.18 requirements. OHA's published decisions are the authoritative case law on what counts as compliant drafting.

How Does Past Performance Carry Over from a JV?

13 CFR 125.18(e) addresses past performance attribution from JVs. Each partner can claim the JV's past performance as its own, provided the claim is consistent with the partner's actual contribution to the JV's performance. The rule allows a smaller partner to leverage a JV's past performance into its individual proposal record, which is one of the structural reasons SDVOSBs participate in JVs in the first place.

The limit is that a partner cannot inflate its own past performance based on the JV's performance beyond what the partner actually contributed. An SDVOSB partner that performed 40% of a JV's work cannot present the full JV past performance as its own work in a future proposal; it can present its share of the work, with appropriate attribution. Inflated past-performance claims are reviewable in the source-selection process and can result in adverse evaluation findings.

The Contractor Performance Assessment Reporting System (CPARS) at cpars.gov is the federal source for verifiable past performance. CPARS evaluations are recorded against the JV's identifier (UEI). When a JV partner cites JV past performance in a future proposal, the partner should reference the JV's CPARS record explicitly and identify the partner's specific role and contribution.

Frequently Asked Questions

Does the SDVOSB JV need its own UEI and SAM.gov registration? Yes. A Joint Venture is a separate legal entity and must obtain its own Unique Entity Identifier (UEI), register in SAM.gov, and complete any certifications required to compete on the target solicitation. For an SDVOSB JV pursuing SDVOSB set-aside competitions, the JV itself must be certified as an SDVOSB JV under 13 CFR 125.18 in the SBA VetCert program. The individual SDVOSB partner's certification does not automatically extend to the JV.

How long can the JV remain a small business after its three-award limit? Under 13 CFR 121.103(h), a JV may receive up to three contract awards over a two-year period from the first contract award. After the third award or the close of the two-year window (whichever comes first), the JV cannot receive additional awards as a small business under that JV vehicle. The partners may form a new JV to continue pursuing work. The three-in-two rule is the SBA's mechanism to prevent a JV from operating indefinitely as a small business when its constituent firms are not.

Can the same SDVOSB form multiple JVs with different mentors? Yes, with limits. Under 13 CFR 125.9, an SBA-approved protege may have up to two simultaneous mentor-protege relationships, but only one at a time with any given mentor. The protege may form a JV with each approved mentor. Each JV is subject to its own three-in-two limit and its own performance-of-work obligations. The protege itself is also subject to limits on the number of times it can participate in the Mentor-Protege Program.