In 2023, the SBA took over certification for Service-Disabled Veteran-Owned Small Businesses (SDVOSBs) from the VA, a shift that has upended proposal strategies for thousands of firms. The change may seem administrative, but it has introduced new verification hurdles and ownership documentation requirements that can make or break a bid. For proposal teams, the stakes are higher than ever: a single error in your SDVOSB status or joint venture structure can disqualify you from a set-aside contract worth millions.

The Situation: Why the SBA Takeover Matters for Your Bid

For years, the VA's Vets First program handled SDVOSB certification, but the 2023 transition to the SBA's VetCert system aimed to streamline verification. Instead, it created a bottleneck: the SBA now requires more detailed documentation on ownership, control, and economic disadvantage. This is not just a paperwork shuffle—it directly affects proposal writing. If your certification is pending or incomplete, you cannot claim SDVOSB status in a proposal, and the SBA's stricter review means that even minor errors in your application can delay or deny your eligibility.

The practical impact is stark. Proposal teams that once relied on the VA's faster turnaround now face longer waits and more rigorous audits. In a competitive small business set-aside proposal, your certification date becomes a strategic variable. If it's not finalized by the time a solicitation closes, you lose. This is where many firms stumble: they assume the SBA process is a formality, but it is now a gatekeeper.

The Challenge: Ownership and Control Documentation—The SDVOSB-Specific Trap

Unlike 8(a) set-asides, SDVOSB verification requires proof that a service-disabled veteran controls the day-to-day operations and long-term decision-making. This is not just about majority ownership—it is about demonstrating that the veteran has the authority to hire, fire, and manage contracts. In proposal writing, this translates to a need for detailed organizational charts, resumes, and narratives that show the veteran's active role.

Common mistakes include submitting resumes that list the veteran as a passive investor or failing to document how the veteran overrides non-veteran managers. The SBA will reject proposals where the veteran's control is ambiguous, even if ownership percentages are correct. For example, a proposal that highlights a non-veteran COO's experience without clarifying the veteran's oversight can trigger a protest. This is a point where SDVOSB proposal writing diverges sharply from general set-aside strategies: you must explicitly prove operational control, not just ownership.

Another trap is the use of joint ventures. Many SDVOSBs form mentor-protégé agreements to compete for larger contracts, but the SBA requires that the SDVOSB joint venture partner manage at least 40% of the work and control key decisions. Proposals often fail because they allocate the SDVOSB a minor role or fail to document the joint venture agreement's terms. The SBA's regulations (13 CFR § 125.18) are specific: the SDVOSB must be the managing venturer, and this must be reflected in the proposal's management section.

The Opportunity: Leveraging the Mentor-Protégé Program

For SDVOSBs, the SBA's mentor-protégé program is a powerful tool, but it comes with proposal-specific requirements. Under the program, a larger firm can mentor an SDVOSB, allowing them to team on set-aside contracts that would otherwise be out of reach. However, the proposal must clearly demonstrate that the protégé (the SDVOSB) is performing a significant portion of the work and that the mentor is not merely a pass-through.

Successful proposals include a detailed work breakdown structure that assigns specific tasks to the SDVOSB, such as project management, quality control, or technical oversight. They also include a joint venture agreement that specifies the SDVOSB's role as the managing partner. This is where many firms lose points: they submit a generic teaming agreement that does not meet the SBA's standards. The SBA expects the joint venture to be a separate legal entity, with its own accounting and management structure, and the proposal must reflect this.

A specific example: a recent SDVOSB joint venture bid for a $10 million IT services contract was rejected because the proposal did not include a copy of the joint venture agreement or show how the SDVOSB would control subcontractor selection. The SBA's review board found that the mentor firm had too much decision-making authority. This is a lesson in detail: every aspect of the joint venture must be documented and aligned with SBA regulations.

The Strategy: Building a Proposal That Anticipates SBA Scrutiny

To win under the new rules, your proposal must treat certification as a core element of the technical approach, not a checkbox. Start by verifying your SDVOSB status at least 90 days before the solicitation closes. If your certification is under review, include a narrative explaining your application status and a timeline for approval. This may not guarantee eligibility, but it shows the contracting officer that you are proactive.

Next, build an ownership and control narrative that is explicit. Use the proposal's management section to describe the veteran's daily involvement, including specific decisions they make (e.g., approving budgets, hiring senior staff, and directing contract performance). Include an organizational chart that shows the veteran at the top, with dotted lines to non-veteran managers to indicate their advisory role. Avoid generic language like 'the veteran oversees operations'; instead, use concrete examples from past performance.

For joint ventures, attach the signed agreement as an appendix and reference it in the proposal's management plan. Include a table that shows the percentage of work each partner will perform, with the SDVOSB's portion at 40% or more. Also, include a section on how the joint venture will handle disputes, ensuring the SDVOSB has the final say. This level of detail reduces the risk of protest and shows the SBA that you understand the rules.

Finally, consider using a compliance checklist specific to SDVOSB proposals. This should include items like: Is the veteran's service-disability status verified in the SBA's database? Does the proposal include a copy of the VA's verification letter (for pre-2023 certifications) or the SBA's VetCert letter? Are all joint venture documents signed and dated? Many firms overlook these steps and lose points on a technicality.

The Reality: Where Proposal Teams Lose Points

The most common failure points in SDVOSB proposal writing are not about price or technical capability—they are about documentation. The SBA's review process is unforgiving: if your proposal does not include a clear chain of ownership and control, it is likely to be rejected, even if the veteran is the majority owner. This is because the SBA looks for 'negative control'—the veteran's ability to prevent actions they disagree with, which is harder to prove than simple majority ownership.

Another reality is that many proposal teams treat SDVOSB set-asides like general small business set-asides, but the verification process is stricter. For example, the SBA requires that the veteran's service-connected disability be rated by the VA, and this rating must be current. If a veteran's disability rating changes, the SDVOSB may lose eligibility mid-proposal. This is a risk that smart teams mitigate by checking the VA's database before each bid.

Finally, the joint venture issue is a persistent problem. The SBA has become more aggressive in reviewing joint venture agreements, especially for large contracts. They look for 'control' in the form of the SDVOSB's ability to make final decisions on staffing, subcontracting, and budget. Proposals that give the mentor firm veto power over these decisions are often rejected. The only way to avoid this is to draft the joint venture agreement with the SBA's regulations in mind, and then mirror those terms in the proposal.

The Bottom Line

SDVOSB proposal writing under the new SBA rules demands a level of documentation and detail that many firms are not prepared for. The shift from VA to SBA certification has made ownership and control verification the critical battleground, and joint ventures now require explicit legal and operational structure. Proposal teams that treat this as a compliance exercise, rather than a strategic opportunity, will lose bids to those who invest in airtight documentation and proactive status checks.

Your Next Step

If you are tired of losing points on certification errors or struggling to document veteran control in your proposals, it is time to see how AI-grounded tools can help. GovCon ProposalEngine offers a 14-day free trial that lets you test a system designed to catch these gaps and streamline your SDVOSB proposal writing. No commitment required—just a smarter way to bid.