A contractor could not file a valid bid protest challenging an agency’s decision to terminate the contractor’s task order, according to the U.S. Court of Federal Claims.
In a recent decision, the Court agreed with the GAO, which also held that the contractor’s challenge involved a matter of contract administration–something outside the bid protest process.
One might think that when an electronic proposal is received by a government server before the solicitation’s deadline, the proposal isn’t late. A government server is under government control, so the proposal is timely, right?
Not necessarily, at least the way the GAO sees it. As one contractor recently learned, waiting until the last minute to submit a proposal electronically carries significant risk that the proposal will not be considered timely, even if the proposal reaches the government server in time.
An offeror submitting a proposal under a solicitation designated with the Information Technology Value Added Resellers exception to NAICS code 541519 must qualify as a small business under a 150-employee size standard–even if the offeror is a nonmanufacturer.
In a recent decision, the U.S. Court of Federal Claims held that an ITVAR nonmanufacturer cannot qualify as small based solely on the ordinary 500-employee size standard under the nonmanufacturer rule, but instead must also qualify as small under the much smaller size standard associated with the ITVAR NAICS code exception.
A large business couldn’t demonstrate that it was eligible to pursue a bid protest challenging a VA SDVOSB sole source contract award.
In a recent decision, the U.S. Court of Federal Claims held that a protester, which was a large business under the NAICS code assigned to the SDVOSB sole source contract, had not demonstrated standing to challenge the contract award. The sole source contract in question wasn’t just any contract, either–but a contract to oversee the VA’s verification process for SDVOSBs and VOSBs.
An agency’s solicitation was not unreasonably vague where the solicitation defined “relevant” past performance to include projects of “a similar dollar value and contract type.”
In a recent bid protest decision, the U.S. Court of Federal Claims rejected a protester’s assertion that the solicitation was required to identify a specific dollar value associated with relevant past performance, finding that the solicitation’s phrasing was sufficient to allow offerors to compete intelligently.
A contractor’s attempt to challenge an adverse Contractor Performance Assessment Report was not a bid protest subject to the bid protest jurisdiction of the U.S. Court of Federal Claims.
In a recent decision, the Court rejected a protester’s creative attempt to challenge a CPAR as part of a bid protest. Instead, the Court held, a CPAR ordinarily must be challenged through the FAR’s claims and appeals processes–although the Court appeared to leave the door open to bid protest challenges in limited circumstances.
Past performance evaluations are a vital part of many federal procurements. Generally, the evaluation of an offeror’s past performance is a matter within the discretion of the contracting agency. But if an agency fails to adequately support its past performance evaluation, its findings cannot be upheld.
The United States Court of Federal Claims recently applied this rule, when it sustained a protest to an agency’s past performance evaluation because the evaluation failed to address the stated evaluation factors. In doing so, the Court provided guidance to both offerors and agencies as to a proper past performance evaluation.