GAO recently sustained protest to an agency’s FAR Part 13 procurement that relied exclusively on CPARS-generated assessment chart rating percentages to evaluate vendors’ past performance. The agency’s goal was to “maximize competition” by considering all past work, rather than just relevant work. While there is no FAR Part 13 regulatory prohibition on doing so, GAO found the CPARS charts incomplete and misleading and the evaluation inconsistent with the terms of the solicitation.Continue reading
The Department of Defense awarded contracts to an average 30,806 small businesses each year in fiscal year 2016, 2017, and 2018. A proposed rule to update the DFARS may lead to these same businesses receiving payments from the government, or prime contractors, within 15 days of invoicing.
The proposed rule is found at 84 FR 25225. It was published on May 31, 2019 and comments close on July 30, 2019 if you’d like to put in your two cents.Continue reading
The FAR generally favors the Government clients’ entitlement to data and software rights in federal procurements. This has commonly—and understandably—led to disgruntled contractors who didn’t realize what they were truly giving up when they opted to use their own software in performance of contracts without including regulation-compliant markings and protections.
But recently—thanks to a first-of-its-kind decision by the ASBCA—it seems the tide may have turned in favor of protecting these contractor-inventors from the standard Government windfall in its data rights acquisitions. Let’s take a closer look.Continue reading
Imagine that you’re a manufacturer of appliances, and respond to a solicitation seeking one of your appliances (on a brand name basis). You, of course, propose to provide your appliance. But you lose out on an award to an offeror that submits an offer for a different appliance that admittedly does not comply with the solicitation’s minimum requirements.
In this situation, you’d probably be fairly upset. And as a recent GAO decision acknowledged, you’d likely have a successful basis of protest—that is, if you could establish that you were prejudiced by the government’s award decision, and if you understood what exactly the GAO means by “prejudice.”
An offeror’s proposal was properly rejected as late because the proposal exceeded the agency’s email file size limit.
In a recent bid protest decision highlighting the importance of not submitting electronic proposals at the last minute, the GAO held that a small business’s proposal was late because the emails transmitting the proposal exceeded 10 MB–even though the solicitation didn’t mention a file size limit.
Competition is the touchstone of federal contracting. Except in limited circumstances, agencies are required to procure goods and services through full and open competition. In this regard, an agency’s decision to limit competition to only brand name items must be adequately justified.
GAO recently affirmed this principle in Phoenix Environmental Design, Inc., B-413373 (Oct. 14, 2016), when it sustained a protest challenging the Department of the Interior, Bureau of Land Management’s decision to restrict its solicitation for herbicides on a brand name basis.
One of the first questions a contractor must ask itself before filing a bid protest with the GAO is whether its protest would be timely filed. But as a recent GAO decision highlighted, the answer to that question might not be so clear.
Contrary to a common misconception, a protest is not always timely if filed within 10 days of a debriefing. As one prospective protester learned, if the debriefing is not “required” under applicable law, a GAO protest filed within 10 days of a debriefing might be untimely.