Federal Construction Contracting Lawyer & Attorney : Payne Hackenbracht & Sullivan : Construction Law, Dredging and Claims

A recent GAO decision highlights the need for offerors to fully understand a Request for Proposals (RFP) and to pay close attention to the details when preparing a proposal in response to an RFP.  In C. Martin Company, Inc., the agency rejected the protestor’s proposal, determining that it was technically unacceptable.  The agency discovered that the offeror had referenced outdated regulations, standards, and procedures.  Some of the references were to processes and standards that had been obsolete for at least three years.  It became evident that the offeror had incorporated parts of a prior RFP submission years before on a similar project.

The agency’s technical review team concluded that the proposal was deficient and that the offeror did not have a clear understanding of the RFP’s requirements.  The offeror was not given an opportunity to cure the deficiencies. After the offeror learned of the basis of its rejection during a debriefing, it filed a protest contending that the deficiencies in its proposal were minor and that it should have been given the opportunity to correct its proposal. Its main argument was that its proposal could easily have been corrected. 

The GAO, in denying the protest, stated that neither the ease of the corrective effort nor the “minor” nature of the deficiencies were determinative of whether the proposal should be accepted or rejected. Instead, the GAO held that the need for numerous revisions “evidenced an inherent lack of understanding or awareness of the current RFP’s requirements.”    The GAO succinctly stated in upholding the agency’s rejection of the proposal: “Offerors are responsible for submitting an adequately written proposal, and run the risk that their proposals will be evaluated unfavorably where they fail to do so.”

It cannot be overemphasized that offerors must review and address the RFP’s requirements and that they must be very attentive when drafting their proposals, especially if they copy materials from prior submissions.  If offerors incorporate prior safety, quality control or experience statements in their current submissions, they would be well advised to carefully review and tailor these statements to the RFP. Otherwise, they risk rejection of their proposals, as happened in this case.

• Email This
• Print
• Comments
• Trackbacks

“Discussions” in a negotiated procurement between the government and an offeror are the exception, not the norm, as those of you who have submitted a response to a Request for Proposals know.  Too often the government awards a contract on the basis of the initial proposal, without any discussions or negotiations with the offerors.  The reason that the government refrains from formally opening up negotiations is that if discussions occur between the government and one offeror, then the government must hold discussions with all of the offerors in the competitive range.  (FAR 15.306(d)(1).  That can be time consuming.  (It can be argued that the term “Procurement by Negotiation,” as explained in FAR, Part 15, anticipates that discussions and negotiations will actually occur). 

            Of course, not all communications between the government and an offeror constitute “discussions.”   As the Government Accountability Office stated in a recent case, Overlook Systems Technologies, Inc., Nov 28, 2006, “the acid test is whether an offeror has been afforded an opportunity to revise or modify its proposal.” In Overlook, the contracting officer contacted the successful offeror regarding a perceived organizational conflict of interest because Overlook planned to use a subcontractor that had provided a system to the government that Overlook would now “troubleshoot.”  The GAO determined that the contracting officer’s communications with Overlook were similar to the sort of inquiries the government frequently makes to perform a responsibility determination.  The GAO relied heavily on the fact that the government was required to make such a responsibility determination, citing prior GAO decisions that have held that responsibility inquiries are not “discussions.”

The GAO held that since the dialogue between the contracting officer and the offeror did not result in changes to the proposal, the communications were not “discussions” and the government was not required to have similar communications with the other offerors.  It should be noted that FAR 15.306(b)(2) permits the government to have communications with an offeror to enhance the government’s understanding of, or interpretation of, a proposal without these exchanges being treated as “discussions.”  Contracting officers should be encouraged to make these kinds of inquiries more often rather simply award contracts on the basis of initial proposals and without any communications whatsoever.

• Email This
• Print
• Comments
• Trackbacks