Agencies have some discretion to seek clarification of a question after reviewing a proposal. But when must the agency do so? GAO allows agencies substantial discretion in choosing whether or not to seek proposal clarifications. But the Court of Federal Claims has a dramatically different standard than GAO for reviewing when an agency must seek clarification for a proposal.
A recent Court of Federal Claims decision confirms (as in a 2016 decision) that agencies should seek clarification for obvious proposal errors. But according to the court, there is a difference between an obvious proposal error and a calculated decision on the contractor’s part. This decision was about how to tell the difference.
In late 2017, we wrote that the VA was considering using tiered evaluations to simultaneously 1) comply with the VA’s statutory Rule of Two (and Kingdomware), and 2) address situations in which SDVOSBs and VOSBs might not offer “fair and reasonable” pricing.
Since then, the VA has instituted the tiered evaluation process for certain solicitations, using one of three approaches:
Oral arguments are to be held today (March 27, 2019) on a U.S. Supreme Court case that may dramatically reduce federal agency power.
The case, Kisor v. Wilkie, asks the Supreme Court to overturn longstanding precedent which established that an agency’s interpretation of its own regulation deserves deference so long as it is reasonable. If the Supreme Court overturns this precedent, it could change the balance of power—in favor of government contractors—in certain disputes with agencies.
An offeror provided a procuring agency with only the first pages of its teaming agreements with proposed subcontractors–and received a “Marginal” score on the small business participation factor as a result.
In a recent decision, the Court of Federal Claims held that the agency reasonably downgraded the offeror for failing to provide its entire teaming agreements, saying that the agency correctly determined that it was unable to determine what work would be performed by the subcontractors.
A government contractor must include certain details in a certified claim, including a sum certain, signature, and a request for a final decision. With regards to the “sum certain,” a contractor cannot avoid this requirement by attempting to portray its claim as one not for monetary relief, when the contractor is really just asking for money.
While most of the rules for SDVOSB eligibility now reside with the SBA, the VA is still responsible for verification of entities for inclusion into its database of verified SDVOSBs and VOSBs. A recent Court of Federal Claims case describes what sort of conduct might get a business removed from the VA’s database–even if that conduct doesn’t run afoul of the SBA’s SDVOSB rule.
While the conduct in this case is somewhat egregious, it is a good reminder that VA has the power to thoroughly investigate the eligibility of an SDVOSB and can revoke the verified status based on inaccurate statements in an application.
A recent court case details the aftermath of a bid protest battle lasting over four years. During that period, the agency’s requirements had changed, and the court held that the agency was required to amend its solicitation as a result.