Recent GAO Bid Protest Lessons

GAO Bid Protest Lessons: Proposal Compliance and Past Performance Matter

Two recent U.S. Government Accountability Office (GAO) bid protest decisions provide important lessons for small businesses competing for federal contracts. Together, the decisions reinforce a fundamental principle of government contracting: offerors must carefully follow solicitation instructions, and agencies must evaluate proposals and past performance in accordance with the solicitation’s stated criteria.

ProteQ: A Missing Document Can Eliminate an Otherwise Competitive Proposal

GAO Decision B-424419.2, ProteQ — July 24, 2026

KENTCO Corporation, doing business as ProteQ, protested the Department of the Navy’s decision to find its proposal ineligible for award under a competition for professional, administrative, engineering, and technical support services.
The solicitation included a contract documentation factor evaluated on a pass/fail basis. The RFP specifically warned offerors that failure to satisfy any pass/fail requirement would make the proposal ineligible for award.

ProteQ received a “Fail” because the Navy identified missing required information, including ProteQ’s corporate policy for resolving Organizational Conflicts of Interest (OCIs). The solicitation required offerors to provide this policy even when they believed no OCI existed.

Because ProteQ failed the contract documentation factor, the Navy did not evaluate its technical proposal, past performance, or proposed cost. GAO concluded that the Navy reasonably determined that the proposal was ineligible for award.

ProteQ also argued that the Navy should have allowed it to correct the omission through clarifications. GAO disagreed. Clarifications may address certain minor or clerical matters, but they cannot be used to cure a material proposal deficiency. Adding the required OCI policy would have required ProteQ to revise its proposal, which would constitute discussions rather than a simple clarification. The solicitation permitted the Navy to make award without discussions.

Contractor Takeaway: Build a Compliance Matrix Before You Submit

The ProteQ decision is an important reminder that proposal compliance comes before proposal quality.

A company can have excellent technical capabilities, strong past performance, and competitive pricing and still be eliminated if it fails to submit a required document.

Before submitting a federal proposal, contractors should create a compliance matrix identifying:
• Every required proposal volume and section
• Required representations and certifications
• Required forms and attachments
• Organizational Conflict of Interest requirements
• Subcontractor documentation
• Required signatures
• Page limitations and formatting requirements
• Required proposal “fill-ins”
• Submission instructions and deadlines
• Pass/fail or go/no-go requirements

Do not assume that the contracting agency will contact you to correct something that was omitted. When a solicitation states that award may be made based on initial proposals without discussions, contractors should operate under the assumption that the proposal submitted at the deadline may be their only opportunity to demonstrate compliance. Read GAO Decision B-424419.2 — ProteQ

Veros Real Estate Solutions: Past Performance Must Actually Be Relevant

GAO Decisions B-423965.2, B-423965.3, B-423965.4 — July 22, 2026

In another significant decision, GAO sustained a protest filed by Veros Real Estate Solutions, LLC, a small business challenging a Department of Veterans Affairs contract award to Lynch Consultants, LLC, an SDVOSB.

The procurement involved automated appraisal management services supporting the VA’s Loan Guaranty Service.

The solicitation required offerors to provide recent and relevant past performance. Relevance depended on how closely the scope of the previous contract aligned with the requirements contained in the current Performance Work Statement (PWS). The VA could also consider past performance information obtained from other sources, including the Contractor Performance Assessment Reporting System (CPARS). 

Neither Veros nor Lynch provided the requested Past Performance Questionnaires in accordance with the solicitation instructions. The VA therefore relied on CPARS information for the offerors and Lynch’s major subcontractor. (GAO)
The problem was not simply that the VA used CPARS. The problem was how the agency interpreted and documented the information contained in those records.

For one Lynch contract with the Department of Health and Human Services, the VA credited Lynch with experience involving records management, training, change management, and process improvement and used those activities to establish relevance to portions of the VA PWS.

Veros challenged that conclusion, arguing that the CPARS narrative actually described those activities as responsibilities of the government program office, rather than work Lynch itself had performed.
GAO agreed.

GAO concluded that the record appeared to show that the cited activities were responsibilities of the HHS program office—not Lynch’s actual contractual work. GAO also found that the VA had not sufficiently explained how the prior work aligned with specific requirements of the current PWS. Similar problems existed with the agency’s relevancy analysis of the other CPARS reports evaluated for the awardee’s team. 

Because the agency’s relevancy evaluation of the past performance records was unreasonable, GAO also questioned the resulting “Substantial Confidence” past performance rating. The protest was therefore sustained on this ground. 

Contractor Takeaway: Don’t Just List Past Performance—Map It to the PWS

This decision provides an important proposal-development lesson.

When a solicitation asks for recent and relevant past performance, simply identifying a previous federal contract may not be enough. Contractors should clearly demonstrate why that work is relevant.

A strong past performance narrative should identify:

What you performed.
Describe the actual services, products, tasks, and responsibilities your company performed—not merely the overall mission of the agency or program you supported.
Where it matches the new requirement.
Connect previous work directly to the applicable PWS or Statement of Work requirements.
For example:
Current PWS Requirement 4.2 — Training
Previous Contract: ABC Agency Contract No. XXXXX
Relevant Experience: Developed and delivered instructor-led and virtual training to 450 agency personnel, including curriculum development, training materials, scheduling, delivery, and post-training evaluation.

That is much stronger than simply stating:
“We provided program support to ABC Agency, which included training.”
The first statement tells the evaluator exactly what the contractor performed and how that experience relates to the new requirement.

Contractors should also remember that agencies may examine CPARS and other available past performance information. Therefore, proposal narratives should be accurate and consistent with the underlying contract record. Read GAO Decisions B-423965.2, B-423965.3 and B-423965.4 — Veros Real Estate Solutions, LLC

What These Decisions Mean for Small Businesses

Taken together, ProteQ and Veros provide two valuable lessons for government contractors.

First: Compliance can determine whether your proposal is evaluated at all.

ProteQ demonstrates the danger of treating administrative documents as secondary to the technical proposal. A missing required document under a pass/fail factor can eliminate a company before evaluators ever reach its technical capabilities, past performance, or price.

Second: Past performance relevance must be demonstrated—not assumed.

Veros demonstrates that simply finding similar words in a CPARS narrative is not necessarily enough to establish relevance. The prior contract work must reasonably align with the scope of the current requirement, and the evaluation must be adequately supported.

For contractors, the practical strategy is straightforward:

Read the solicitation as both an instruction manual and an evaluation roadmap.

Before submitting your next proposal:

1. Develop a compliance matrix from Sections L and M or the solicitation’s equivalent instructions and evaluation criteria.
2. Identify every pass/fail and go/no-go requirement.
3. Assign responsibility for every required document and attachment.
4. Conduct a final compliance review separate from the technical review.
5. Map each past performance example directly to the applicable PWS/SOW requirements.
6. Describe what your company performed, not simply the mission or activities of the customer you supported.
7. Quantify your experience whenever possible—contract value, personnel, locations, transactions, users, deliverables, response times, or other measurable results.
8. Review CPARS records and other past performance information for consistency with the experience described in your proposal.

Bottom Line
A federal proposal is not evaluated solely on whether a company is capable of performing the work. It is evaluated based on what the company submitted, whether the submission complied with the solicitation, and whether the proposal demonstrates the experience required by the evaluation criteria.

The ProteQ decision shows what can happen when required proposal documentation is missing.

The Veros decision shows what can happen when an agency’s evaluation of past performance relevance is not adequately supported.

For small businesses pursuing federal contracts, both decisions reinforce the same message:

Be compliant. Be specific. Be measurable. And connect every claim in your proposal to the requirement the government is evaluating.