Skin of Its Teeth: Mentor-Protégé Joint Venture Survives SDVOSB Status Protest Despite Missing Required Provisions in Joint Venture

Key Takeaways

• SDVOSB JV missed explicit 128.402 reporting clause.
• OHA accepted “applicable regulation” language as compliance.
• Mentor‑protégé rules differ from standard SDVOSB JV rules.
• Missing language could have triggered award cancellation.
• Precise SBA clause drafting prevents costly protests.

Summary

The SBA Office of Hearings and Appeals upheld Sugarloaf Technologies, an SDVOSB mentor‑protégé joint venture, after GSA protested its award for missing the specific reporting language required by 13 C.F.R. § 128.402(c)(11)‑(12). Sugarloaf’s agreement instead contained a clause stating reports would be submitted “as required by applicable regulation,” which OHA interpreted as satisfying the statutory requirement. The decision underscores a regulatory quirk: SDVOSB joint‑venture rules differ from mentor‑protégé rules, and the omission could have jeopardized the award. Contractors must meticulously align JV agreements with all SBA reporting mandates to avoid similar challenges.

Pulse Analysis

Federal contracting officials often treat SBA joint‑venture regulations as a uniform set, applying the same standards across 8(a), SDVOSB, WOSB, and HUBZone programs. In reality, subtle divergences exist—particularly between the SDVOSB‑specific reporting requirements of 13 C.F.R. § 128.402(c)(11)‑(12) and the mentor‑protégé provisions of 13 C.F.R. § 125.8. These nuances dictate distinct language for quarterly and project‑end financial statements, and overlooking them can create compliance gaps that trigger protests or disqualification.

In the recent VSBC protest, GSA challenged Sugarloaf Technologies’ award after discovering the joint‑venture agreement lacked the explicit SDVOSB reporting clauses. Sugarloaf relied on a broader provision that it would submit reports “as required by applicable regulation.” The OHA concluded that this catch‑all language effectively incorporated the missing statutory requirements, allowing the award to stand. The decision illustrates OHA’s willingness to interpret contractual language flexibly when the intent to comply is evident, but it also signals that such outcomes are not guaranteed and hinge on the agreement’s overall context.

For contractors, the lesson is clear: embed the exact phrasing mandated by each applicable CFR section, and cross‑reference all relevant regulations within the JV agreement. Including explicit statements about quarterly financial statements and project‑end profit‑and‑loss reports eliminates ambiguity and reduces protest risk. Engaging experienced federal‑contracting counsel during JV formation can ensure that mentor‑protégé and SDVOSB requirements are harmonized, safeguarding awards and preserving the competitive advantage of small‑business set‑aside programs.