top of page
  • R.D. Lieberman,Consultant

Confidence Decreasers

In a recent technical evaluation in a procurement by the Department of Homeland Security for cybersecurity services, instead of assigning strengths and weaknesses in each technical area, the the agency assigned “confidence increasers” and “confidence decreasers.” Zermount protested the confidence decreasers in three separate areas, but the Government Accountability Office (“GAO”) ruled that all three were consistent with the terms of the solicitation. Zermount, Inc. B-420174, Dec. 27, 2021. The GAO denied Zermount’s protest.

The three areas where the agency assigned confidence decreasers were as follows, along with the GAO’s disposition:

· Success statements and technical approach. The agency assigned confidence decreasers because of spelling and typographical errors (typos), and the typos prevented the agency from understanding the proposal. The agency stated that the errors undermined the clarity of Zermount’s proposal and were viewed as an indicator that government intervention would be required for successful performance. The GAO agreed that because offerors were responsible for submitting a well-written proposal that clearly demonstrated compliance with solicitation requirements, that the mis-spelling and typos were properly assigned as confidence decreasers.

· Unclear Federal Identity Credential Access Management (“FICAM”). The agency that the offer’s FICAM submission was lacking a strategic plan, failed to establish how Zermount’s plan would accomplish the work and was also conclusory. The GAO agreed with the agency’s confidence decreaser because the proposal was inadequately written.

· Technical Approach Criterion. The agency assigned a confidence decreaser because Zermount’s technical approach contained misleading and inaccurate statements. These statements indicated that Zermount might not understand the work involved, and therefore the offeror had introduced a performance risk.

There were other issues in the evaluation, but the GAO agreed that the agency had properly evaluated the technical portion, and then awarded the contract to Favor TechConsulting, LLC, whose price was approximately $2 million lower than Zermount’s.

Takeaways: (1) Scour all proposals for spelling and typographical errors. Use spell-check, and then re-read.

(2) Ensure that your proposal is adequately written and contains the detail required by the solicitation.

(3) Never include misleading or inaccurate statements in your proposal. Every assertion must be provable.

For other helpful suggestions on government contracting, visit:

Richard D. Lieberman’s FAR Consulting & Training at, and Mistakes in Government Contracting at

3 views0 comments

Recent Posts

See All

Can an exchange of electronic documents (such as emails) between a contracting officer (“CO”) and a Contractor’s Contracts Manager create a binding contract modification? The issue was recently explor

Does a board of contract appeals or the Court of Federal Claims have jurisdiction over a breach of a government contract government if negligence is alleged in a claim, or does the Federal Tort Claims

When you read about best value (tradeoff) decisions in Government Accountability Office (“GAO”) bid protests, you may wonder why so many higher technically rated proposals with higher prices end up be

bottom of page