Surviving Proposal Weaknesses after Discussions: What Not to Do

Albert B. Krachman

With apologies to Paul Simon, this is another in a series of articles on the 50 ways contractors can lose awards on federal contracts. These cautionary tales should inform anyone in a contractor organization with responsibility for authorizing, preparing, or negotiating competitive federal contract proposals.

Like the inverse of Steven Covey’s Seven Habits of Highly Effective People bestseller, the mistakes that lead to lost awards are well known and include: carelessness, greed, lack of attention to detail, procrastination, and cursory (or omitted) red-team reviews. This article highlights another surefire path to disaster: failing to adequately correct proposal weaknesses after discussions.

This lesson arises out of a clash between BNA and Lexis, legal search titans, over a U.S. Treasury contract. The combatants were seeking award of a contract for electronic research services for IRS staff, described in a GAO Bid Protest decision, LexisNexis, a Division of RELX Inc., B-418885; B-418885.2 (October 8, 2020).

Treasury’s solicitation required that offerors both describe their search solutions in technical proposals, and have a working computing solution, active for government testing. After initial proposal submissions and initial evaluations, the government advised offerors of weaknesses and deficiencies in their proposals and in their computing solutions. Treasury advised Lexis that its proposal suffered from a significant weakness due to Lexis’ computing solution’s return of erroneous search results. Discussions were opened and offerors were permitted to submit final proposal revisions. Offerors were also permitted to correct any deficiencies in their computing solutions before another round of government testing.

Continue reading “Surviving Proposal Weaknesses after Discussions: What Not to Do”
%d bloggers like this: