The 2017 National Defense Authorization Act makes some important adjustments to the criteria for ownership and control of a service-disabled veteran-owned small business.
The 2017 NDAA modifies how the ownership criteria are applied in the case of an ESOP, specifies that a veteran with a permanent and severe disability need not personally manage the company on a day-to-day basis, and, under limited circumstances, permits a surviving spouse to continue to operate the company as an SDVOSB.
The 2017 National Defense Authorization Act will essentially prevent the VA from developing its own regulations to determine whether a company is a veteran-owned small business.
Yes, you heard me right. If the President signs the current version of the 2017 NDAA into law, the VA will be prohibited from issuing regulations regarding the ownership, control, and size status of an SDVOSB or VOSB–which are, of course, the key components of SDVOSB and VOSB status. Instead, the VA will be required to use regulations developed by the SBA, which will apply to both federal SDVOSB programs: the SBA’s self-certification program and the VA’s verification program.
An SDVOSB set-aside contract was void–and unenforceable against the government–because the prime contractor had entered into an illegal “pass-through” arrangement with a non-SDVOSB subcontractor.
In a recent decision, the Civilian Board of Contract Appeals held that a SDVOSB set-aside contract obtained by misrepresenting the concern’s SDVOSB status was invalid from its inception; therefore, the prime contractor had no recourse against the government when the contract was later terminated for default.
A protester’s failure to be specific enough in an SDVOSB status protest will result in dismissal of the protest.
The decision of the SBA Office of Hearings and Appeals in Jamaica Bearings Company, SBA No. VET-257 (Aug. 9, 2016), reinforces the SBA’s rule concerning specificity in filing a service disabled veteran-owned status protest. The rule provides, “[p]rotests must be in writing and must specify all the grounds upon which the protest is based. A protest merely asserting that the protested concern is not an eligible SDVOSB, without setting forth specific facts or allegations is insufficient.”
SDVOSB joint venture agreements will be required to look quite different after August 24, 2016. That’s when a new SBA regulation takes effect–and the new regulation overhauls (and expands upon) the required provisions for SDVOSB joint venture agreements.
The changes made by this proposed rule will affect joint ventures’ eligibility for SDVOSB contracts. It will be imperative that SDVOSBs understand that their old “template” JV agreements will be non-compliant after August 24, and that SDVOSBs and their joint venture partners carefully ensure that their subsequent joint venture agreements comply with all of the new requirements.
The VA is proposing a major overhaul to its SDVOSB program regulations–including the rules governing ownership and control.
In a proposed rule released today, the VA is seeking to “find an appropriate balance between preventing fraud in the Veterans First Contracting Program and providing a process that would make it easier for more VOSBs to become verified.” And while the proposal isn’t perfect, it looks like a step in the right direction.
The U.S. Supreme Court has agreed to hear an appeal filed by Kingdomware Technologies, Inc.
News outlets are reporting that the Supreme Court will take on the question of whether the VA’s “Veterans First” rules permit the VA to circumvent SDVOSBs by using the Federal Supply Schedule. The case is an appeal from a 2014 decision of the U.S. Court of Appeals for the Federal Circuit, in which a three-judge panel ruled 2-1 in favor of the VA.
The Supreme Court grants only a small fraction of the petitions for certiorari filed with it, so just getting in the courthouse door is a victory of sorts for Kingdomware.
Much more on the pending Supreme Court case as I get the details.