Full Opinion

In the United States Court of Federal Claims Nos. 25-82, 25-95, 25-152, 25-172, 25-225, 25-295 (Filed Under Seal: September 10, 2026) (Reissued for Publication: November 16, 2026) 1 *************************************** BEAT-LDI JV LLC, et al., * * Plaintiffs, * * v. * * THE UNITED STATES, * * Defendant. * *************************************** Alexander Brewer Ginsberg, Fried, Frank, Harris, Shriver & Jacobson LLP, Washington, DC, counsel for Plaintiff, BEAT-LDI JV LLC. With whom were Katherine St. Romain, and Robert C. Starling, of counsel. Elizabeth Newell Jochum, Blank Rome LLP, Washington, DC, counsel for Plaintiff, GenceTek LLC. With whom were Samarth Barot, and Shane M. Hannon, of counsel. Matthew Thomas Schoonover, Schoonover & Moriarty LLC, Olathe, KS, counsel for Plaintiff, OM Partners JV 2, LLC. With whom were Ian P. Patterson, Timothy J. Laughlin, and Haley M. Sirokman, of counsel. Ryan Christopher Bradel, Ward & Berry PLLC, Tysons, VA, counsel for Plaintiff, Assyst, Inc. With whom were P. Tyson Marx, and Mary Pat Buckenmeyer, of counsel. David Bailey Dixon, Pillsbury Winthrop Shaw Pittman LLP, Tysons, VA, counsel for Plaintiff, DevTech Systems, Inc. With whom were Toghrul M. Shukurlu, Aleksey R. Dabbs, and Alexis P. Landrum, of counsel. Tenley Anne Carp, Arnall Golden Gregory LLP, Washington, DC, counsel for Plaintiff, Rigil Corporation. With whom was Sydney Selman, Atlanta, GA, of counsel. 1 This Opinion and Order was filed under seal on September 10, 2026, [ECF 109], in accordance with the protective order entered in this case, [ECF 11]. The parties were given an opportunity to identify protected information, including source selection information, proprietary information, and confidential information, for redaction. The parties filed a joint status report on September 30, 2026, with proposed redactions. [ECF 112]. The Court accepts the proposed redactions. All redactions are indicated by bracketed asterisks, e.g., “[* * *].” Vincent de Paul Phillips, U.S. Department of Justice, Civil Division, Washington, DC, counsel for Defendant. With whom was Carmody G. Daman, Senior Assistant General Counsel, General Services Administration, of counsel. OPINION AND ORDER DIETZ, Judge. In this consolidated post-award bid protest, six disappointed offerors challenge the evaluation of proposals by the General Services Administration (“GSA”) under Request for Proposal (“RFP”) No. 47QTCB22R0001 for the Polaris Government-Wide Acquisition Contract (“GWAC”) Small Business (“SB”) pool. Before the Court are motions for judgment on the administrative record (“MJAR”) filed by Rigil Corporation (“Rigil”) [ECFs 62, 66]; 2 OM Partners JV 2, LLC (“OM Partners”) [ECF 65]; Assyst, Inc. (“Assyst”) [ECF 69]; GenceTek LLC (“GenceTek”) [ECF 70]; DevTech Systems, Inc. (“DevTech”) [ECF 71]; and BEAT-LDI JV LLC (“BLJV”) [ECF 74]. Also before the Court is the government’s cross-MJAR [ECF 86]. For the reasons set forth below, the Court GRANTS the MJARs filed by DevTech and OM Partners, and DENIES the MJARs filed by GenceTek, BLJV, Rigil, and Assyst. I. BACKGROUND GSA designed the Polaris program to address “a governmentwide need to access highly qualified Information Technology (IT) contractors” while also satisfying each government agency’s “need to meet [its] small and socioeconomic small business contracting goals.” AR Tab 30 at 23. 3 The program is separated into four pools. 4 Id. at 24. This protest concerns only the SB pool. See id. at 25. A. Polaris SB Pool RFP History GSA issued the RFP for the Polaris GWAC SB pool for “a multiple award, indefinite- delivery, indefinite-quantity [(“IDIQ”)] contract,” AR Tab 3 at 14, on March 25, 2022, id. at 11. Proposals were due on May 13, 2022. Id. at 74. The RFP contemplated awarding IDIQ contracts to the top 100 highest technically rated qualifying (“HTRQ”) offerors. Id. at 99. It provided that, 2 Rigil initially filed an unsealed version of its MJAR, which the Clerk of the Court subsequently sealed. See [ECF 62]. On the same day, Rigil also filed a sealed version of its MJAR separately on the docket. [ECF 66]. As these are duplicate filings, the Court cites to only [ECF 66] when referring to Rigil’s MJAR. 3 The administrative record filed by the government consists of tabbed documents within three volumes. Each document has its own tab, and most tabs are paginated with a Bates number (e.g., Tab 1 GSAV1_000001). The Court cites to the administrative record by tab and Bates number (e.g., AR Tab 1 at 1). However, the documents within AR Tab 68 are not separately paginated with Bates numbers. See generally AR Tab 68. Each AR Tab 68 file includes a Bates number in the file name (e.g., GSAV2_2_08702_OM Partners JV 2, LLC). Accordingly, the Court cites to documents in AR Tab 68 by the Bates number in the file name and PDF page, if applicable (e.g., AR Tab 68 at 8702, *1). When quoting from the administrative record, the Court omits unnecessary capitalization. 4 The four pools include: a Historically Underutilized Business Zone (“HUBZone”) pool, a Service-Disabled Veteran Owned Small Business (“SDVOSB”) pool, an SB pool, and a Women-Owned Small Business (“WOSB”) pool. AR Tab 30 at 24. 2 “[i]n accordance with 41 U.S.C. [§] 3306(c) and [the] associated GSA Class Deviation CD-2020- 14, cost and pricing information will not be considered at the master contract level.” Id. The RFP was amended seven times based upon industry feedback, and the proposal submission deadline was ultimately extended to October 7, 2022. See AR Tab 43 at 211-12; see also AR Tabs 5, 7-8, 11, 13-16 (Amendments 0001 through 0007). On October 7, 2022, GSA received 569 proposals. AR Tab 43 at 212. On the same day, two small businesses—not parties in the instant case—filed pre-award bid protests in the United States Court of Federal Claims. Id. The protesters alleged that GSA violated Small Business Administration (“SBA”) regulations governing joint ventures (“JVs”) “by subjecting [JVs] to ‘the same’ evaluation criteria as offerors generally . . . [and that GSA violated] 41 U.S.C. § 3306(c) by failing to consider price as an evaluation factor at the IDIQ level.” SH Synergy, LLC v. United States, 165 Fed. Cl. 745, 758 (2023); see AR Tab 43 at 212. On April 21, 2023, the court in that case found that the challenged RFPs for the Polaris pools “violate[d] [SBA regulations] by applying the same evaluation criteria to projects submitted by protégé firms and other offerors alike,” SH Synergy, LLC, 165 Fed. Cl. at 775, and “violate[d] federal procurement law because [GSA] d[id] not adequately ‘feature’ task orders ‘based on hourly rates,’ as contemplated under 41 U.S.C. § 3306(c)(3),” id. at 776. The court enjoined GSA “from evaluating proposals and awarding IDIQ contracts under the current versions of the [RFPs] . . . [and required GSA to] amend the [RFPs], and evaluate proposals under those [RFPs], consistent with and in compliance with [the court’s] Memorandum and Order.” Id. at 786. Following that decision, GSA twice amended the RFP for the Polaris GWAC SB pool. On September 20, 2023, GSA issued Amendment 0008, which requested that offerors agree to extend the minimum acceptance period for their proposals to September 30, 2024, by signing and submitting the Standard Form (“SF”) 30. AR Tab 18 at 1164. This amendment was necessary because otherwise the offerors’ proposals would exceed the minimum acceptance period set forth in the RFP. See AR Tab 3 at 75 (establishing a minimum offer acceptance period of at least 365 days from receipt of proposals). Next, on September 29, 2023, GSA issued Amendment 0009, AR Tab 20 at 1241, which required offerors to provide partially revised proposals with cost/price information, see id. at 1254, and which changed the evaluation methodology from HTRQ to highest technically rated with fair and reasonable pricing (“HTRFRP”), id. at 1254, 1353. GSA amended the RFP three more times, with Amendment 0012 reflecting the most recent version of the RFP. See AR Tab 43 at 213; see also AR Tabs 23, 26-27 (Amendments 0010 through 0012). B. Relevant RFP Terms and Conditions The RFP contained proposal submission instructions. See AR Tab 27 at 1648-49. The RFP advised offerors “to read the entire [RFP], including all attachments in Section J, prior to submitting questions and/or preparing a proposal” and warned that “[o]mission of any information from the proposal submission requirements may result in rejection of the offer.” Id. at 1648. The RFP further informed offerors that “[a]ll proposal information is subject to verification by the government,” id. at 1649, that “[t]he offeror is required to ensure all proposal information submitted is verifiable,” id., and that “[i]f the GSA source selection team detects a high degree of unverifiable, contradictory, or unsubstantiated information submitted in an offeror’s proposal, the government will end the proposal evaluation, and the offeror will be 3 removed from being considered for award,” id. In addition, the RFP required all offerors to submit their respective proposals through the Polaris Submission Portal (“PSP”). Id. at 1648. Regarding the basis for award, the RFP stated that “[t]he source selection process on Polaris will neither be based on the lowest price technically acceptable (LPTA) nor tradeoffs.” AR Tab 27 at 1681. It explained that “[w]ithin the best value continuum, FAR 15.101 defines best value as using any one or a combination of source selection approaches” and that “[f]or Polaris, the best value basis for awards will be determined by the [HTRFRP].” Id. It further explained that “[a]ll evaluation factors other than price, when combined, are significantly more important than price.” Id. The RFP stated that GSA “intends to make 100 awards in the [SB] [p]ool [and,] to be considered as a[n] [HTRFRP] offeror, the proposal must score amongst the 100 highest rated offers . . . [with] all offerors tied at the 100th position [] receiv[ing] an award.” Id. The proposal evaluation process required that each offeror “claim” technical evaluation points from a total possible 95,000 points by self-scoring its proposal in accordance with certain evaluation elements enumerated in the Polaris scoring table. See AR Tab 27 at 1681-83; see also id. at 1685-87 (Polaris scoring table). The specific proposal requirements for these evaluation elements were set forth in Sections L.5.2 Relevant Experience; L.5.3 Past Performance; L.5.4 Systems, Certifications, and Clearances; and L.5.5 Risk Assessment. See id. at 1683, 1685-87. Section L.5.2 Relevant Experience required offerors to submit primary relevant experience projects that were equal to or greater than $250,000 and that demonstrated performance in one of five listed North American Industry Classification System (“NAICS”) codes. 5 AR Tab 27 at 1659-61. Offerors were also allowed to submit emerging technology relevant experience projects that were equal to or greater than $250,000 and that demonstrated performance in one of the six listed emerging technology categories. 6 Id. at 1666-67. For each primary relevant experience and emerging technology project, offerors were required to provide specific verification documentation. Id. at 1661-62 (verification documentation for primary relevant experience submissions for federal government contracts); id. at 1666-68 (verification documentation for emerging technology submissions). Section L.5.5 Risk Assessment, referred to as Organizational Risk Assessment (“ORA”), allowed offerors to “receive additional points for demonstrating that it has previously performed in the same business arrangement” as proposed. AR Tab 27 at 1685; see id. at 1672. Such business arrangements included performing as an individual company, a JV, a prime contractor with proposed subcontractors, or a JV with proposed subcontractors. Id. at 1672. Depending on the proposed business arrangement, offerors were required to satisfy applicable conditions set 5 Section L.5.2.2.1 of the RFP lists the following NAICS codes: 518210 – Data Processing, Hosting, and Related Services; 541511 – Custom Computer Programming Services; 541512 – Computer Systems Design Services; 541513 – Computer Facilities Management Services; and 541519 – Other Computer Related Services. AR Tab 27 at 1660. 6 Section L.5.2.3.1 of the RFP lists the following emerging technologies by RFP section reference: C.3.1.1 – Advanced and Quantum Computing; C.3.1.2 – Artificial Intelligence; C.3.1.3 – Automation Technology; C.3.1.4 – Distributed Ledger Technology; C.3.1.5 – Edge Computing; and C.3.1.6 – Immersive Technology. AR Tab 27 at 1666-67. 4 forth in the RFP and provide verification documentation. Id. at 1672-73 (verification documentation for ORA submissions). Upon receipt of the proposals, the RFP contemplated “ranking the proposals in order from [the] highest total claimed score to [the] lowest total claimed score.” AR Tab 27 at 1681. Thereafter, “[a] screening process of the top 100 w[ould] commence to verify support[ing] documentation for all the applicable evaluation elements submitted into the [PSP] . . . [to] verify the top 100 met all [] the acceptability review requirements[.]” Id. at 1682. Specifically, the acceptability review was designed to evaluate proposals “to determine whether the requested proposal submission information meets the criteria for information requested in Section L.5.1 and is current, accurate, and complete.” Id. at 1683. Such proposal submission information included completed SF33 forms (including acknowledgement of amendments to the RFP on the SF33 or on the SF30 for each amendment), the offeror’s representations and certifications, the offeror’s JV documentation, if applicable, and the offeror’s meaningful relationship commitment letter(s) (“MRCL”), 7 if applicable. Id. at 1651-58. If one of the top 100 highest scoring proposals failed this “acceptability review,” it would be replaced by the next highest scoring proposal outside the top 100 highest scoring proposals. Id. at 1682. Following the acceptability review, the RFP stated that “the evaluation team w[ould] then evaluate and verify the top 100s’ support[ing] documentation for each evaluation element.” AR Tab 27 at 1682. The RFP stated that “[i]n the event a claimed evaluation element is refuted (found to be unsubstantiated or otherwise not credited), the offeror’s claimed score w[ould] have the point value of the refuted evaluation element deducted and the proposal w[ould] be re-sorted based upon the revised score[.]” Id. GSA would continue to evaluate the proposal if it remained in the top 100, but “[i]f the proposal d[id] not remain in the top 100, the evaluation for that proposal w[ould] stop and the next highest rated proposal (based upon claimed score) that provide[d] the required support[ing] documentation for all the applicable evaluation elements and passe[d] the acceptability review w[ould] join the top 100 and evaluation w[ould] begin on that proposal.” Id. After completion of the technical evaluation, “[t]he evaluation team w[ould] check to verify [that] the top 100 have proposed fair and reasonable pricing.” AR Tab 27 at 1682. If it was determined that “an offeror has not provided fair and reasonable pricing, the offeror [would] be eliminated from further consideration for award unless discussions are conducted.” Id. However, the RFP stated that GSA “intends to award contracts without discussions,” that GSA “may conduct clarifications, as described in FAR 15.306(a),” and that GSA “reserves the right to conduct discussions if determined necessary.” Id. at 1681. The RFP explained that “[t]he evaluation process w[ould] continue until the 100 apparently successful offerors [were] identified, representing the [HTRFRP] offerors (based on validated scores, fair and reasonable pricing, and passing the overall responsibility determination).” Id. at 1682. 7 A MRCL is a document that offerors could submit with their proposal that allowed it to “utilize resources from a parent company, affiliate, division, and/or subsidiary . . . to take credit for relevant experience project(s), system(s), certification(s), or clearance(s) . . . so long as there [wa]s a meaningful relationship to the offeror and [a MRCL is] provided to [GSA].” AR Tab 27 at 1657. 5 For the overall responsibility determination, the RFP stated that GSA would make the determination “on a pass/fail basis.” AR Tab 27 at 1687. It explained that GSA could “use any relevant information in its possession or in the public domain, including other past performance information available within the government and in non-government databases[.]” Id. It further explained that GSA would evaluate Professional Employee Compensation Plans (“PECPs”) “in accordance with [S]ection[] L.5.6.1.” Id. Section L.5.6.1 incorporated the full text of FAR 52.222-46 Evaluation of Compensation for Professional Employees (FEB 1993), id. at 1673-74, and stated as follows: The offeror must submit a [PECP] that addresses the offeror’s methodology for determining salaries and fringe benefits for their professional employees in preparation of future task order requirements under Polaris. Submission of the general compensation practices printed in the offeror’s employee handbook including salary and fringe benefits will often be sufficient. Id. at 1673. The responsibility determination also involved a review of each offeror’s financial statements to confirm that the offeror had “adequate financial resources to perform the contract, or the ability to obtain them.” Id. at 1675. Ultimately, “offerors which [we]re not deemed responsible w[ould] not be considered for award.” Id. at 1687. C. Evaluation, Award Decision and Bid Protests In accordance with the RFP, GSA conducted an acceptability review, AR Tab 44, a technical evaluation, AR Tab 45, a responsibility determination, AR Tab 46, and a cost/price analysis, AR Tab 47, and issued a source selection decision memorandum, AR Tab 43. GSA issued clarifications to several offerors during the evaluation process. See generally AR Tab 69. On December 30, 2024, GSA issued a notice of award, which stated that it planned “to make contract awards to 102 offerors (due to a [three-way] tie at the 100th position).” AR Tab 48 at 1; see AR Tab 49. The notice advised that “offerors not identified [] were not within the top 100 [HTRFRP] offerors, based on the evaluation criteria as established in the [RFP].” AR Tab 48 at 1. To be within the top 100 highest scoring proposals and receive an award, an offeror needed a final verified score of 89,800. See AR Tab 71 at 12453-55. The notice of award “encouraged [offerors not selected for award] to login to the [PSP] and review their individual debriefing letter.” AR Tab 48 at 1. On January 17, 2025, BLJV and GenceTek filed bid protests in this court challenging the Polaris GWAC SB pool procurement. See BLJV Compl. [ECF 1]; Compl., GenceTek LLC v. United States, No. 25-95 (Fed. Cl. filed Jan. 17, 2025). On January 27, 2025, the Court issued an order consolidating these protests and designating BLJV’s case as the lead case. [ECF 10]. The Court amended this order three times to consolidate additional bid protests under the lead case. See [ECF 21] (consolidating OM Partners JV 2, LLC v. United States, No. 25-152 (Fed. Cl. filed Jan. 28, 2025) and Assyst, Inc. v. United States, No. 25-172 (Fed. Cl. filed Jan. 29. 2025) under lead case); [ECF 31] (consolidating Network Runners, Inc. v. United States, No. 25-213 (Fed. Cl. filed Feb. 5, 2025) and DevTech Sys. Inc. v. United States, No. 25-225 (Fed. Cl. filed Feb. 6, 2025) under lead case); [ECF 38] (consolidating Rigil Corp. v. United States, No. 25-295 (Fed. 6 Cl. filed Feb. 19, 2025) under lead case). Each protester filed an MJAR on August 29, 2025, 8 see [ECFs 65-66, 69-71, 74], and the government filed its cross-MJAR on December 23, 2025, [ECF 86]. The motions are fully briefed, Pls.’ Replies & Resps.’ [ECFs 87, 89-93]; Def.’s Reply [ECF 103], and the Court held oral argument on April 24, 2026, see [ECF 99]. II. STANDARD OF REVIEW The Tucker Act grants this court jurisdiction “to render judgment on an action by an interested party objecting . . . to a proposed award or the award of a contract or any alleged violation of statute or regulation in connection with a procurement or a proposed procurement.” 28 U.S.C. § 1491(b)(1). This waiver of sovereign immunity “covers a broad range of potential disputes arising during the course of the procurement process,” including “objections to an award” decision. Sys. Application & Techs., Inc. v. United States, 691 F.3d 1374, 1380-81 (Fed. Cir. 2012) (citations omitted). “When proceedings before an agency are relevant to a decision in a case, the administrative record of those proceedings must be . . . filed with the court.” RCFC 52.1(a). Parties may then “file a[n MJAR] for the [c]ourt to assess whether [the agency], given all disputed and undisputed facts in the record, acted in compliance with the legal standards governing the decision under review.” Agile Def., Inc. v. United States, 143 Fed. Cl. 10, 17 (2019) (citation omitted), aff’d, 959 F.3d 1379 (Fed. Cir. 2020); accord Harmonia Holdings Grp., LLC v. United States, 20 F.4th 759, 766 (Fed. Cir. 2021) (noting that the court’s inquiry is limited to “whether, given all the disputed and undisputed facts, a party has met its burden of proof based on the evidence of record” (quoting XOtech, LLC v. United States, 950 F.3d 1376, 1379 (Fed. Cir. 2020))). This procedure allows “parties to seek the equivalent of an expedited trial on a ‘paper record, allowing fact-finding by the trial court.’” Young v. United States, 497 F. App’x 53, 58-59 (Fed. Cir. 2012) (quoting Bannum, Inc. v. United States, 404 F.3d 1346, 1356 (Fed. Cir. 2005)), cert. denied, 569 U.S. 964 (2013). When a party challenges an agency’s contract award decision, the court reviews the decision using the standard of review set forth in the Administrative Procedure Act (“APA”). See 28 U.S.C. § 1491(b)(4) (“In any action under this subsection, the courts shall review the agency’s decision pursuant to the standards set forth in section 706 of title 5.”). This standard provides that “the reviewing court shall . . . hold unlawful and set aside agency action, findings, and conclusions found to be . . . arbitrary, capricious, an abuse of discretion, or otherwise not in accordance with law.” 5 U.S.C. § 706. “In applying the APA to protests . . . [the court] determine[s] whether ‘(1) the procurement official’s decision lacked a rational basis; or (2) the procurement procedure involved a violation of regulation or procedure.’” Weeks Marine, Inc. v. United States, 575 F.3d 1352, 1358 (Fed. Cir. 2009) (quoting PGBA, LLC v. United States, 389 F.3d 1219, 1225 (Fed. Cir. 2004)); see also Motor Vehicle Mfrs. Ass’n of U.S. v. State Farm Mut. Auto. Ins. Co., 463 U.S. 29, 43 (1983) (stating that the court will not uphold an agency decision where the agency “relied on factors which Congress has not intended it to consider, entirely failed to consider an important aspect of the problem, offered an explanation . . . counter to the evidence before [it], or is so implausible [] it could not be ascribed to a difference in view or the product of agency expertise”). “[P]rocurement decisions are subject to a ‘highly deferential rational basis review.’” Safeguard Base Operations, LLC v. United States, 989 F.3d 1326, 1343 8 On the same day, Network Runners Inc. filed a notice of voluntary dismissal, [ECF 61], and its complaint was subsequently dismissed, see Network Runners, Inc., No. 25-213. 7 (Fed. Cir. 2021) (alteration in Safeguard Base Operations, LLC) (quoting PAI Corp. v. United States, 614 F.3d 1347, 1351 (Fed. Cir. 2010)). However, the considerable deference afforded to an agency under the APA “is not a rubber stamp.” Overstreet Elec. Co. v. United States, 47 Fed. Cl. 728, 742 (2000) (quoting Citizens Awareness Network, Inc. v. U.S. Nuclear Regul. Comm’n, 59 F.3d 284, 290 (1st Cir. 1995)); see also FirstLine Transp. Sec., Inc. v. United States, 100 Fed. Cl. 359, 376 (2011) (“Whenever a procurement decision is without a rational basis or is based upon a clear violation of law, that decision must be set aside.”). When reviewing an agency action, “the court must determine if the agency ‘examine[d] the relevant data and articulate[d] a satisfactory explanation for its action.’” Distributed Sols., Inc. v. United States, 104 Fed. Cl. 368, 382 (2012) (alterations in Distributed Sols., Inc.) (quoting Motor Vehicle Mfrs. Ass’n, 463 U.S. at 43); see also Golden IT, LLC v. United States, 177 Fed. Cl. 118, 136 (2025) (recognizing that an agency violates the APA where its “findings or decisions are conclusory or unexplained in the administrative record” because “the APA requires the government to show its work” (first citing Consol. Safety Servs., Inc. v. United States, 167 Fed. Cl. 543, 564 n.11 (2023); and then citing CAN Softtech, Inc. v. United States, No. 24-670, 2024 WL 4434253, at *6 (Fed. Cl. Oct. 4, 2024)). “Further, it is well settled that an agency must explain its action with sufficient clarity to permit ‘effective judicial review.’” Timken U.S. Corp. v. United States, 421 F.3d 1350, 1355 (Fed. Cir. 2005) (quoting Camp v. Pitts, 411 U.S. 138, 142-43 (1973)). If the challenging party persuades the court “that the government’s conduct fail[ed] the APA review,” Bannum, 404 F.3d at 1351, it then “must establish that it was prejudiced by the contracting officer’s action,” CACI, Inc.-Fed. v. United States, 67 F.4th 1145, 1153 (Fed. Cir. 2023). “‘To establish prejudicial error,’ a party must show that ‘but for the error, it would have had a substantial chance of securing the contract.’” Oracle Am., Inc. v. United States, 975 F.3d 1279, 1291 (Fed. Cir. 2020) (quoting Labatt Food Serv., Inc. v. United States, 577 F.3d 1375, 1378 (Fed. Cir. 2009)), cert. denied, 142 S. Ct. 68 (2021) (mem.). “Put another way, to show prejudice a disappointed bidder needs to show that ‘it had greater than an insubstantial chance of securing the contract if successful on the merits of the bid protest.’” REV, LLC v. United States, 91 F.4th 1156, 1163 (Fed. Cir. 2024) (quoting Info. Tech. & Applications Corp. v. United States, 316 F.3d 1312, 1319 (Fed. Cir. 2003)). III. DISCUSSION In this protest, six offerors challenge GSA’s proposal evaluation and award decision under the RFP for the Polaris GWAC SB pool. The Court first resolves the challenges raised by three of the protesters to GSA’s PECP evaluation. The Court then turns to the remaining challenges raised by each of these three protesters and, thereafter, the challenges raised by the remaining three protesters. To the extent that the protesters demonstrate that GSA’s procurement actions were arbitrary, capricious, an abuse of discretion, or otherwise not in accordance with law, the Court will decide whether such protesters were prejudiced by GSA’s errors within the section that addresses the protester’s challenges. 8 A. GenceTek’s, DevTech’s, and BLJV’s Challenges to GSA’s PECP Evaluation GenceTek, DevTech, and BLJV argue that GSA failed to properly conduct an evaluation of each offeror’s PECP as required by FAR 52.222-46. [ECF 70] at 16; [ECF 71-1] at 18; [ECF 74] at 42. 9 GenceTek contends that GSA “did not perform the [PECP] evaluation required by FAR 52.222-46 [because this provision] requires the government to evaluate offerors’ total compensation plan,” and instead GSA only “assess[ed] whether each offeror included [***] in its PECP.” [ECF 70] at 18. GenceTek argues that GSA’s “box-check approach to the PECP evaluation . . . could not evaluate whether offerors will obtain and keep the quality of professional services needed for adequate contract performance without consideration of the differences between the incentives being offered,” id. at 20, and that GSA “did no evaluation of the impact of [] direct labor rates—which correspond directly to employee pay—on the ability to recruit and retain professional employees,” id. GenceTek also contends that GSA “used an unstated evaluation scheme by substituting the evaluation required by the FAR (and therefore the RFP) with a requirement that offerors’ PECPs include [***].” Id. at 22. GenceTek asserts that GSA “used a significantly different basis in evaluating the proposals than was disclosed— limiting the universe of compensation that would be considered to just an undisclosed list and converting the required holistic and qualitative compensation evaluation required by the FAR and RFP to a limited box-check exercise.” Id. at 23-24. Next, DevTech argues that “the record . . . is devoid of any evaluation of the offerors[’] direct labor rates and fringe benefit rates for realism.” [ECF 71-1] at 19 (emphasis omitted). DevTech contends that GSA’s “one-paragraph description of its [PECP] evaluation illustrates that [it] failed to review the direct labor rates as part of [its] evaluation, and merely conducted an analysis of the description of fringe benefits without regard to the rates to be paid to the professional employees.” Id. at 20. According to DevTech, “[s]uch an evaluation, even if it were documented, is woefully deficient and does not meet the requirements of FAR 52.222-46 and the [RFP].” Id. Lastly, BLJV argues that “the record contains no documentation of GSA’s realism analysis pertaining to the awardees’ [PECPs.]” [ECF 74] at 43. The government maintains that GSA evaluated the offerors’ respective PECPs “as part of [its] overall responsibility and [that] GSA has broad discretion in evaluating responsibility.” [ECF 86] at 54; see id. at 74-75, 93-94. According to the government, “the RFP provides that PECPs will initially be evaluated for purposes of assessing responsibility[, and] [t]o assess responsibility, GSA must only look to the general compensation practices to determine whether an offeror is responsible.” Id. at 59. The government contends that a “more detailed evaluation of PECPs will occur at the task order level—when precise information is available on the pricing and fringe benefit[] plans for the professional employees required to complete an individual task order.” Id. at 60; see id. at 75, 95. Additionally, the government argues that the protesters’ challenges to the PECP evaluation are waived because “[t]he terms of the RFP made clear that GSA was not going to perform any cost realism type analysis at all[.]” Id. at 62; see id. at 75-76, 95-96. Regarding GenceTek’s unstated evaluation criteria argument, the government counters that “GenceTek has not established that GSA used unstated evaluation criteria because GSA stated it would evaluate fringe benefits as part of PECP, and it did not deviate from doing so,” id. at 77, and that “GSA did not require offerors to propose a specific amount or type of fringe 9 The Court cites to the filings on the docket using the page numbers generated by the CM/ECF system. When quoting from the filings on the docket, the Court omits unnecessary capitalization. 9 benefits [but] [i]nstead, [] allowed vendors to identify common fringe benefit categories they offer as part of employee compensation,” id. at 78 (citing AR Tab 27 at 1673-74). Based on the record, the Court finds that GSA failed to conduct a proper PECP evaluation in accordance with FAR 52.222-46 and applied an unstated evaluation criterion by requiring offerors’ PECPs to include a [***] fringe benefits from an enumerated list. Section L.5.6 of the RFP contains the following requirement: L.5.6.1 Professional Employee Compensation Plan The government is concerned with the quality and stability of the work force to be employed on this contract. Professional compensation that is unrealistically low or not in reasonable relationship to the various job categories may impair the Contractor’s ability to attract and retain competent professional service employees or may be viewed as evidence of failure to comprehend the complexity of future task order requirements. The offeror must submit a [PECP] that addresses the offeror’s methodology for determining salaries and fringe benefits for their professional employees in preparation of future task order requirements under Polaris. Submission of the general compensation practices printed in the offeror’s employee handbook including salary and fringe benefits will often be sufficient. AR Tab 27 at 1673. Section L.5.6.1.1 incorporates the full text of FAR 52.222-46. Id. This provision, in relevant part, states: (a) Recompetition of service contracts may in some cases result in lowering the compensation (salaries and fringe benefits) paid or furnished professional employees. This lowering can be detrimental in obtaining the quality of professional services needed for adequate contract performance. It is therefore in the Government’s best interest that professional employees . . . be properly and fairly compensated. As part of their proposals, offerors will submit a total compensation plan setting forth salaries and fringe benefits proposed for the professional employees who will work under the contract. The Government will evaluate the plan to assure that it reflects a sound management approach and understanding of the contract requirements. This evaluation will include an assessment of the offeror’s ability to provide uninterrupted high-quality work. The professional compensation proposed will be considered in terms of its impact upon recruiting and retention, its realism, and its consistency with a total plan for compensation. Supporting 10 information will include data, such as recognized national and regional compensation surveys and studies of professional, public and private organizations, used in establishing the total compensation structure. (b) The compensation levels proposed should reflect a clear understanding of work to be performed and should indicate the capability of the proposed compensation structure to obtain and keep suitably qualified personnel to meet mission objectives. The salary rates or ranges must take into account differences in skills, the complexity of various disciplines, and professional job difficulty. . . . *** (d) Failure to comply with these provisions may constitute sufficient cause to justify rejection of a proposal. Id. at 1673-74 (quoting FAR 52.222-46). 10 In connection with its evaluation of each offeror’s PECP, GSA provided its evaluation team with “responsibility review guidance.” See AR Tab 46 at 821-22. The guidance consisted of the following two questions: [***] Id. at 822. In its responsibility determination report, GSA included a table with a column indicating that each offeror selected for award submitted a PECP and that each PECP received a “Pass” from the evaluation team. Id. at 828-30. GSA also included the following statement: The contracting team evaluated the offeror[s’] PECP[s], as described in RFP Section L.5.6.1 and FAR 52.222-46. The evaluation included an assessment of the offeror[s’] ability to provide uninterrupted high-quality work, considering the realism of the proposed professional compensation and its impact upon recruiting and retention. Specifically, the team reviewed the PECPs to verify offerors were providing a sufficient and realistic benefits package including [***] benefits in the areas of retirement, insurance, bonus, leave, flexible working arrangements, or other. The contracting team concluded that each top 100 offeror would obtain and keep a high-quality workforce for contract performance. Id. at 819. 10 Paragraph (c) of FAR 52.222-46 is set forth above as the first paragraph in Section L.5.6.1 of the RFP. 11 This record does not show that GSA conducted the required PECP evaluation. As noted above, the RFP required that each offeror submit a PECP that addressed “salaries and fringe benefits for their professional employees,” AR Tab 27 at 1673, and stated that GSA would evaluate the PECPs in accordance with FAR 52.222-46, see id. 1687. Yet, aside from a conclusory statement that the PECPs were evaluated in accordance with FAR 52.222-46 and a table indicating that each offeror’s PECP passed the evaluation, the record does not contain any indication that GSA conducted such an evaluation. See CRAssociates, Inc. v. United States, 95 Fed. Cl. 357, 378 (2010) (finding that “there is no indication the Army conducted the analysis required by FAR [] 52.222-46” and as such “[t]he Army’s failure to comply with the clause constituted a departure from the evaluation criteria . . . [and is] a violation of both the FAR and the Competition in Contracting Act”). While the record shows that GSA considered each offeror’s proposed fringe benefits, it is devoid of any indication that GSA considered each offeror’s proposed salaries. See CSC Gov’t Sols., LLC v. United States, 129 Fed. Cl. 416, 432 (2016) (stating that FAR 52.222-46 requires the procuring agency to “conduct a rational analysis of the realism of the offerors’ proposed salaries with regard to program continuity, retention, and ‘uninterrupted high-quality work’” (quoting OMV Med., Inc. v. United States, 219 F.3d 1337, 1339 (Fed. Cir. 2000))). 11 Further, by reducing its analy