The Government Accountability Office has turned back a challenge to a Navy training contract, ruling that the service may keep a solicitation requirement that offerors show experience managing five or more Service Contract Labor Standards employees at once. In SPARC JV, LLC, B-424400, decided June 25, 2026 and released publicly the week of July 21, GAO denied the pre-award protest, finding the Navy had documented a rational basis for the five-employee floor and had tied it to the work the winning contractors will actually perform.
SPARC JV, LLC, a small business based in Orlando, Florida, argued the experience bar was unduly restrictive of competition. GAO disagreed on every point. The decision is a clean illustration of how far a protester has to go to prove a qualification specification exceeds an agency's minimum needs.
Background
The procurement, Navy RFP N6134026R10010002, covers pilot and aircrew courseware revision and maintenance services under a program the Navy calls PACRM II. The solicitation contemplates multiple indefinite-delivery, indefinite-quantity awards. Courseware maintenance keeps flight and aircrew training materials current as aircraft, systems, and doctrine change, and much of the labor falls under the Service Contract Labor Standards, the statute that sets wage and benefit floors for service workers on federal contracts.
At the center of the dispute sat a single sentence in the solicitation. To be eligible, an offeror had to demonstrate experience in the direct management of five or more SCLS employees working simultaneously. SPARC filed before proposals were due, arguing the threshold walled off firms that could perform the work but had not happened to run a contract with that particular headcount. In SPARC's telling, the Navy had picked an arbitrary number and dressed it up as a need.
Key Details
GAO measured the argument against a settled standard. A protester challenging a solicitation term as unduly restrictive must show the requirement is not reasonably necessary to meet the agency's needs. Once the agency offers a rational explanation, the burden does not shift to the government to prove the term is the only way to buy what it wants. It shifts to the protester to show the explanation is unreasonable. SPARC never cleared that bar.
The Navy supported the five-employee requirement with a three-part justification, and GAO credited all of it. First, the agency pointed to performance data from the predecessor contract, where managing an inexperienced SCLS workforce had generated real risk to the mission. Firms that had not run this kind of labor pool before struggled with the compliance and supervision the standards demand. Second, the Navy tied the number to its own portfolio: five was the staffing level of the smallest incumbent task order being folded into the new scope, so any awardee would, at a minimum, have to manage a workforce that size from day one. Third, the agency explained that supervising multiple SCLS employees at once is not simply a matter of counting heads. It requires payroll systems, timekeeping discipline, and compliance infrastructure that together signal a contractor has reached a level of organizational maturity. An offeror that had never carried that load was, in the Navy's judgment, a poorer bet.
Against that record, GAO found the threshold reasonable. The agency had connected the requirement to documented past problems, to the actual size of the work being consolidated, and to the operational demands of the labor standards themselves. That is precisely the kind of rational basis the case law asks for, and SPARC offered nothing to show the justification was pretextual or the number plucked from thin air. The protest was denied.
The ruling breaks no new legal ground, and that is the point. It reaffirms a rule contractors have run into for years: an agency gets wide latitude to define its needs, and a term that narrows the field is not automatically improper. The line falls between a requirement the agency can rationally explain and one it cannot. Explanation, not perfection, carries the day.
What It Means for Contractors
For contractors weighing whether to protest an experience or qualification specification, the decision offers a practical checklist. Start by asking what record the agency is likely to have built. Where a requirement traces to predecessor-contract performance, to the size of consolidated task orders, or to a documented compliance burden, the agency will almost certainly be able to articulate a rational basis, and a challenge will struggle. A protest has a fighting chance only where the term floats free of any such justification, where the number or credential appears nowhere in the agency's own history, or where the requirement so exceeds the scope of the work that no reasonable explanation could connect the two.
The five-employee figure here is instructive because it was not round or aspirational. The Navy did not ask for experience managing fifty employees or a decade of courseware work. It asked for the floor set by the smallest piece of work in the consolidated buy. Agencies that anchor a threshold to the actual dimensions of the requirement, rather than to a wish list, give protesters little to grip.
Small businesses eyeing consolidated IDIQ vehicles should read solicitation experience clauses early and honestly. If a firm cannot yet show the managed-headcount experience a recompete demands, the more durable move is often to build that record, through subcontracting or teaming, rather than to bet a protest on persuading GAO that a documented requirement is arbitrary. SPARC filed before award and still lost, which is the timing a protester wants and the outcome it does not.
The decision also underscores the value of the pre-award protest window itself. SPARC did the procedurally correct thing by challenging the terms before proposals were due rather than waiting to see if it lost. That preserved the argument on the merits. The lesson is not that pre-award protests are futile. It is that a well-timed protest still needs a substantive theory, and disagreement with an agency's judgment about its own needs is rarely enough.
For the PACRM II competition, the practical effect is that the field stays as the Navy drew it. Offerors will have to show the managed-SCLS-workforce experience the solicitation demands, and the multiple-award IDIQ moves forward on the agency's terms.
