VA's Ambiguous Solicitation Leads to Successful Protest

By: Edward T. DeLisle

Over the last several years, the scrutiny over federal small business programs has grown. That scrutiny has led to changes in policy and legislation designed to curb potential fraud in the procurement process. Because these changes have been implemented in such a short period of time, however, it is not unusual for the government to issue solicitations for small business set-aside contracts that are confusing, or even contradictory. In Commandeer Construction Company, Inc., B-405771, December 29, 2011, that is precisely what occurred resulting in a successful protest.

Commandeer Construction involved a solicitation that was set aside for Service-Disabled, Veteran-Owned Small Businesses (SDVOSBs), a program that has experienced much change in recent years. In 2006, the VA was given the authority to restrict competition to SDVOSBs as part of the Veterans Benefits, Health Care, and Information Act (the "Act"). 38 U.S.C. 8127(d). As the GAO explained in Commandeer Construction, pursuant to the Act, an SDVOSB set-aside contract may only be issued to entities listed in a database of veteran-owned small businesses maintained by the VA. The VA has chosen to use what it has termed its "Vendor Information Pages" ("VIP"), which can be found at www.vetbiz.gov, as its official listing of veteran-owned and service-disabled, veteran-owned concerns.

Subsequent to issuance of the Act, the VA issued VAAR 804.1102, which states that all VOSB and SDVOSB entities must be listed in its VIP database by January 1, 2012 in order to be eligible for set-aside contracts for such entities. By December 31, 2011, all VOSB and SDVOSB entities must not only be listed, but must also be "verified," in order to receive new contract awards under the Veteran's First program, a program operated exclusively by the VA. While firms were once permitted to self-certify their status as VOSBs and SDVOSBs, as part of Veterans Benefits Act of 2010, the VA instituted a more rigorous qualification process. Consistent with this new review procedure, which was designed to weed out fraud, the VA's "Center for Veterans Enterprise" ("CVE") was given the authority to render eligibility determinations for these programs. If a firm wished to obtain a set-aside contract as a VOSB or a SDVOSB entity, it would have to be verified by CVE.

In an effort to assist in the transition from a self-certifying system to one requiring government approval, the VA issued what it called its "Memorandum from VA Acting Associate Deputy Assistant Secretary for Procurement Policy, Systems Oversight and Accompanying Class Deviation from VA Acquisition Regulation" (the "Memorandum"). The Memorandum referenced what the VA described as a "class deviation." Based upon this class deviation, any "apparently successful offeror" that had not already been verified by CVE, could become verified on an expedited basis, and obtain an award of a VOSB or SDVOSB set-aside contract, provided CVE approved its status. Later, the VA clarified its position regarding who may qualify for a “class deviation,” taking the position that a company was not eligible for “either award or Fast Track Verification," unless it was visible in the VA’s VIP database. Commandeer Construction addressed the interplay between the class deviation identified in the Memorandum and the VA’s attempt to subsequently clarify what it meant.

In Commandeer Construction, the VA issued an IFB for a construction contract that was set aside for eligible SDVOSB firms. The solicitation stated that the award would be made to an SDVOSB firm that had “been verified for ownership and control and [was] so listed in the [VIP] database.” The IFB also included the “class deviation” language referenced above. What was not included as part of the IFB, however, was the Memorandum (and accompanying deviation), or the clarification made to the deviation, which was issued after the fact.

On August 8, 2011, the protesting party, Commandeer Construction, submitted an application to the CVE for approval as an SDVOSB. Thereafter, on August 30, 2011, Commandeer submitted its bid. As its bid was the lowest of those submitted, Commandeer was in line for an award. As it was not listed in the VIP database, however, the contract specialist for the VA intended to contact Commandeer for purposes of explaining the process of obtaining expedited verification.

Prior to contacting Commandeer, the VA contract specialist apparently learned of the clarification for the first time and discussed its meaning and significance with other VA officials. Based upon these discussions, the VA contract specialist decided that Commandeer was ineligible for award and informed it of such by letter dated August 31, 2011. At the time, CVE had not rendered a final decision on Commandeer’s SDVOSB eligibility.

Commandeer protested VA’s decision, taking the position that rejecting its bid was improper based upon the expedited review procedures outlined in the solicitation. The VA countered that the deviation clause, upon which Commandeer relied for potential eligibility, was never meant to apply to entities that were absent from the VIP database. According to the VA, the deviation clause was merely an effort to provide assistance to those firms that had already self-certified, but had not yet been CVE verified under the new review procedures. Commandeer Construction at 4.

The GAO based its decision on a strict reading of the solicitation. The deviation clause in the solicitation specifically stated that “the apparent successful offeror” would be given an opportunity to have its SDVOSB status reviewed on an expedited basis, if it was not “currently listed as verified” in the VIP database. While the VA may not have intended for the deviation to apply to firms not already listed in its VIP database, the GAO concluded that the solicitation itself did not provide that qualification. As such, Commandeer’s understanding that it could qualify for award pursuant to the expedited review procedure was reasonable. Based upon this finding, the GAO recommended that the VA complete its review of Commandeer’s verification documents and, if found to be eligible for SDVOSB status, award it the contract.

As the government continues to alter its approach in exercising control over small business programs, mistakes, such as those in Commandeer Contracting, will happen. Contractors must exercise care in reviewing and responding to any solicitation. If, during the course of the review process, an ambiguity is discovered, bring it to the attention of the contract specialist, contracting officer, or source selection authority immediately. Doing so will benefit all bidders and quite possibly prevent a pre-bid protest. For those ambiguities that are not readily detectible, and are only revealed at the time of contract award, be prepared to discuss your concerns with an attorney familiar with such issues right away, as a protest is likely your only source of recourse. For those participating in the government’s various small business programs, the fast-paced nature of regulatory change has opened these programs up to issues such as those presented in Commandeer Contracting. Bid and beware.

Edward T. DeLisle is a Partner in the firm and a member of the Federal Contracting Practice Group.
 

Senate Bill Introduced to Combat SBA Fraud

By: Edward T. DeLisle

Senator Olympia Snowe, R-Maine, introduced a bipartisan bill on Thursday that is designed to combat fraud and abuse in the world of small business contracting. As we have reported, the General Accounting Office (GAO) has issued a number of reports over the last several years detailing the existence of fraud in the HUBZone, Service-Disabled, Veteran-Owned Small Business (SDVOSB) and 8(a) programs. These reports have generated much discussion about the need to revamp the system and, in certain circumstances, talk has led to action. The implementation of the current SDVOSB verification system is but one example of the government’s response to the current state of affairs. S. 633, entitled the “Small Business Contracting Fraud Prevention Act of 2011” (Fraud Prevention Act), is designed to take the government’s ability to respond to fraud and abuse in small business contracting to a new level.

As reported by Law360, the Fraud Prevention Act contains three key provisions:

     1. It calls for the development of an oversight structure within the Small Business Administration (SBA) that would allow for better enforcement of the rules governing small business contracting;

     2. It would allow for an increase in criminal prosecutions, suspensions and debarments for those who violate the rules; and

     3. It would require the SBA to issue annual reports to Congress regarding those who are suspended, debarred or referred to the Department of Justice for prosecution.

S. 633 is yet another step to close the loopholes that have developed in the federal government’s small business contracting system. We will track this legislation and report any further developments.

Edward T. DeLisle is a Partner in the firm and a member of the Federal Contracting Practice Group.

Past Performance Reporting Overseas: Does it Happen?

By: Edward T. DeLisle

For those who regularly read our blog, you know that we have followed the government’s recent concern about fraud and abuse in the federal procurement process.  The GAO has issued reports that recite such abuse relative to the 8(a), HUBZone and SDVOSB programs.  As those reports indicate, companies have been awarded set-aside contracts through those programs, but were not qualified to receive them.  In certain circumstances, the apparent fraud was so blatant that the hubris, which certainly existed to think such abuses would go unnoticed, puts Charlie Sheen to shame.  Yet, as the GAO reports state, even when the abuses were uncovered, many of these contractors continued to receive government awards.  It appears that some contractors performing work overseas in places like Iraq and Afghanistan may also be receiving awards that they do not deserve.

As reported by Govexec.com, government agencies responsible for overseas contracts are not properly recording past performance history in the CPAR and PPIR electronic databases.  The biggest offenders appear to be the State Department, the Department of Defense and the U.S. Agency for International Development (USAID).  Based upon information supplied to the Commission on Wartime Contracting, congressionally mandated to investigate overseas contracting activities, these agencies have failed to properly report past performance history in up to 90% of the contingency contracts they have issued.  While the failure to report this information is problematic for many reasons, it certainly exposes the government to contractors who are less than ideal for important government contracts.  This is especially an issue as it relates to contractors in line for suspension or debarment.  As former Connecticut Congressman Christopher Shays, who is the chairman of the Commission, stated: “[I]f suspensions and debarments are impeded by bureaucratic decisions or inertia, then companies that have committed fraud may continue receiving taxpayer funds.  In either case, untrustworthy contractors can continue profiting from government work, responsible businesses may be denied opportunities, and costs to taxpayers can climb.”

Over the years, the government has increasingly relied upon “best value” procurement to let contracts.  Past performance is almost always an important factor in determining “best value.” In fact, in most cases, it is the most important factor.  If federal agencies intend to continue issuing contracts in this fashion, a practice that is highly questionable for the purchase of certain services, such as construction, then they must make it a point to create a system that allows those deserving of awards to receive them. In the case of small business set aside contracts, the government has started to slowly move in this direction.  The VA, for example, is now vetting those contractors on its on-line SDVOSB registry to verify eligibility.  If this function is performed correctly, it will greatly enhance the probability that contracts will be let to those who deserve them. With respect to past performance history, there is a system in place.  Federal agencies simply need to use it.  Hopefully, the findings exposed by the Commission on Wartime Contracting make this a reality.

Edward T. DeLisle is a Partner in the firm and a member of the Federal Contracting Practice Group.

New VA Veteran-Owned Small Business Verification Guidelines

A Final Rule governing Service Disabled Veteran-Owned small Business Concerns (“SDVOSB”) was published in the Federal Register on February 8, 2010. This law requires the Department of Veterans Affairs (“VA”) to verify ownership and control of veteran-owned small businesses, including service-disabled veteran-owned small businesses. The final rule also defines the eligibility requirements for businesses to obtain “verified'' status, explains examination procedures, and establishes records retention and review processes.

As reported by Jason Miller, the Executive Director of Federal News Radio in an article published in the SDVOSB Blog, Veteran-Owned and Service Disabled Veteran-Owned Small Businesses must have only one business in the federal contract set-aside program and work in that business full time. The article, entitled “VA Sets Rules for Set-Aside Program,” also emphasizes that “The net effect of this change is that a company that is closely held by veterans would qualify regardless of the size of the employee stock ownership program,” and “Alternatively, a firm that is not closely held by veterans will find it much more difficult to qualify for the Verification Program.”

Veteran-Owned and Service Disabled Veteran-Owned Small Businesses must re-certify annually to the VA that they meet the requirements to obtain set-aside contracts from agencies. The rule comes after the Government Accountability Office told the House Veterans Affairs Committee in December that the service-disabled veteran-owned business program is vulnerable to fraud and abuse. Anyone who seeks to use the services of a disabled veteran, or of an existing SDVOSB, to circumvent the letter and spirit of this program would be well advised to recognize that SDVOSB concerns are under close scrutiny because of the reported abuses.

Michael Payne is a Partner and is the Chairman of the firm's Federal Practice Group.
 

Fraud, Abuse and the Service-Disabled Veteran-Owned Small Business Program

By: Edward T. DeLisle

In recent testimony provided to the House of Representative’s Committee on Small Business, a disturbing fact was revealed: millions of dollars earmarked for Service-Disabled Veteran-Owned Businesses (“SDVOSBs”) have been paid to companies that do not qualify for the program. Compounding the problem is the fact that insufficient fraud-prevention programs exist to effectively combat such abuses. This was the conclusion reached by United States Government Accountability Office (the “GAO”) following a case study that included an investigation of ten (10) companies claiming SDVOSB eligibility.

In 2008 alone, $6.5 billion in federal contracts were awarded to companies that self-certified themselves as SDVOSBs. While this figure only represents 1.5% of all government contracts paid in that fiscal year, it is still a very large number. If the federal government ever attains its mandated goal of 3%, many more billions will become available to qualified SDVOSBs. Given the paucity of work in the private sector over the course of the last eighteen (18) months, many companies are attempting to tap into this potential source of revenue. As the GAO pointed out, however, a number of these companies have misrepresented their credentials, effectively taking contracts away from those that truly qualify to receive them.

The companies identified in the GAO case study received approximately $100 million in SDVOSB contracts, and over $300 million in additional 8(a), HUBZone and other non-SDVOSB contracts through the federal government. Certainly, none of these monies should have been paid to the companies in question. Notwithstanding the same, because there are no requirements to terminate contracts when a firm is deemed ineligible, in certain circumstances, companies were permitted to continue performing, despite the government’s determination that the firm did not qualify as an SDVOSB. Many more were not debarred from receiving federal contracts, even though the transgressions noted were obvious and seemingly blatant.

The GAO did note that Department of Veteran’s Affairs (the “VA”) has taken steps to address this problem by introducing an SDVOSB validation process. That process includes confirming an owner’s status as a disabled veteran, as well as his or her control over day-to-day operations. The problem, however, is that the VA’s certification and validation process is not a government-wide system. It is limited to those contracts issued directly by the VA. Because many other federal agencies issue contracts that are earmarked for SDVOSBs, there are considerable gaps in the SDVOSB program.

If your company is an SDVOSB, or if you are interested in forming a company that qualifies for participation in the program, it is very important for you to comply with applicable SBA and procurement regulations. The fierce competition for federal government contracts exposes many companies to size status protests which, if successful, can cause an SDVOSB to lose an award. Our Federal Contracting Practice Group is available to assist you with these important compliance issues.

Edward T. DeLisle is a Partner in the firm and is a member of the firm’s Federal Contract Practice Group. He is extensively involved in the representation of construction contractors on small business issues.