Defense Blogs and Articles
  • All Technology
  • AI
  • Autonomy
  • B2B Growth
  • Big Data
  • BioTech
  • ClimateTech
  • Consumer Tech
  • Crypto
  • Cybersecurity
  • DevOps
  • Digital Marketing
  • Ecommerce
  • EdTech
  • Enterprise
  • FinTech
  • GovTech
  • Hardware
  • HealthTech
  • HRTech
  • LegalTech
  • Nanotech
  • PropTech
  • Quantum
  • Robotics
  • SaaS
  • SpaceTech
AllNewsDealsSocialBlogsVideosPodcastsDigests

Defense Pulse

EMAIL DIGESTS

Daily

Every morning

Weekly

Tuesday recap

NewsDealsSocialBlogsVideosPodcasts
HomeIndustryDefenseBlogsOHA Reminder: Compliance with SBA Joint Venture Requirements Is Determined at Final Proposal Revisions
OHA Reminder: Compliance with SBA Joint Venture Requirements Is Determined at Final Proposal Revisions
Defense

OHA Reminder: Compliance with SBA Joint Venture Requirements Is Determined at Final Proposal Revisions

•February 6, 2026
SmallGovCon
SmallGovCon•Feb 6, 2026
0

Key Takeaways

  • •OHA uses final proposal revision date for JV compliance.
  • •MindVen amended JV agreement before Jan 4 2024 revision.
  • •GSA protest denied; award remained with MindVen.
  • •Rule applies to mentor‑protégé, 8(a), WOSB, HUBZone JVs.
  • •Review JV agreements before any proposal revisions.

Summary

The SBA Office of Hearings and Appeals (OHA) clarified that compliance with joint‑venture requirements under 13 C.F.R. § 128.402(c) is judged at the date of a final proposal revision, not the initial offer. In the GSA‑led protest VSBC‑459‑P, OHA ruled that MindVen’s SDVOSB joint venture, which amended its agreement on December 7 2022, was compliant as of its January 4 2024 final revision, leading to a denial of GSA’s protest. The decision underscores that the same timing rule applies to mentor‑protégé, 8(a), WOSB, and HUBZone joint ventures. Contractors must therefore verify JV agreement compliance before submitting any revised proposals.

Pulse Analysis

Federal contracting officials have long relied on the initial‑offer rule to assess size‑and‑status protests, but the SBA’s Office of Hearings and Appeals recently reinforced a narrower provision that shifts the compliance clock to the final proposal revision. This nuance, embedded in 13 C.F.R. § 134.1003(e)(1), means that for joint‑venture agreements—whether SDVOSB, mentor‑protégé, 8(a), WOSB, or HUBZone—the eligibility determination hinges on the most recent revision submitted, not the original offer date. The statutory language explicitly ties eligibility to the final revision for negotiated acquisitions, creating a distinct pathway for protest resolution.

The precedent‑setting case involving MindVen LLC illustrates the practical impact of this rule. After GSA filed a protest alleging that MindVen’s joint‑venture agreement lacked required financial‑reporting clauses, the contractor produced an amendment made months after its initial offer but before the final revision deadline. OHA affirmed that the amendment satisfied 13 C.F.R. § 128.402(c) as of the January 4 2024 revision, leading to a dismissal of the protest and preservation of the award. This outcome demonstrates how timing and documentation can overturn what might otherwise be a fatal compliance deficiency, reinforcing the importance of strategic amendment timing.

For contractors, the decision translates into a clear compliance checklist: verify that joint‑venture agreements meet all SBA reporting and non‑manufacturer requirements before any final proposal revision is filed, and consider proactive amendments when revisions are permitted. Monitoring regulatory updates is equally critical, as a rule change after the initial offer could render a previously compliant JV non‑compliant at the revision stage. By aligning JV documentation with the final‑revision standard, firms can mitigate protest risk, preserve competitive positioning, and maintain eligibility across the full spectrum of SBA‑backed programs.

OHA Reminder: Compliance with SBA Joint Venture Requirements is Determined at Final Proposal Revisions

Read Original Article

Comments

Want to join the conversation?