The Space Force Bought A Whole Base Worth Of IT On A Help Desk Contract, And GAO Told It To Tear The Order Up

Two separate scope findings in one decision, and the second one is the one every small business on a contractor teaming arrangement needs to read. Being on the team does not let the government order work off somebody else’s schedule contract. Each team member is a prime, and only for its own labor categories.

LOLSBA · Federal contracting desk · September 11, 2026

The Government Accountability Office headquarters at 441 G Street NW in Washington, D.C., which sustained the Ares Enterprise protest against the Space Force. Photo: AgnosticPreachersKid, CC BY-SA 3.0, via Wikimedia Commons

GAO sustains about one protest in seven. It recommends terminating an order and starting over considerably less often than that. On September 9 it published a decision that does both, and the reasoning in it is the kind that reaches a lot further than the one base it is about.

The case is Ares Enterprise, LLC, B-424548, B-424548.2, B-424548.3, decided September 3, 2026 and released on the 9th.

What was bought

The United States Space Force needed IT services for the 61st Communications Squadron at Los Angeles Air Force Base in El Segundo. On May 29, 2026 it placed an order with Vision Information Technology Consultants LLC of San Antonio, a small business, for a nine month base period, two one year options and a six month extension under FAR 52.217-8.

It placed that order under the Enterprise Information Technology as a Service Wave 1 blanket purchase agreement, and it placed it without competing it.

Ares Enterprise, LLC of Fairfax, Virginia, also a small business, protested. It said the order was sole sourced improperly, that it exceeded the scope of the EITaaS BPA, and that it exceeded the scope of Vision’s own Federal Supply Schedule contract.

The first sustain: wave 1 meant wave 1

The whole case turns on what the EITaaS BPA said it covered. The performance work statement described wave 1 as end user device support and enterprise help desk services. On cybersecurity it was explicit:

Wave 1 will focus on the End User Device and Data Protection capability, with other service areas being provided in future waves.

That sentence is the reason this decision exists. The agency wrote down the boundary itself, in its own document, and then ordered straight through it.

GAO went task by task and sustained on seven of them.

TaskWhat it actually called forResult
4. Network and system operationsEnterprise infrastructure, not end user devicesBeyond scope
5. CybersecurityBroad cybersecurity governance, not end user device protectionBeyond scope
6. IT planning and supportRequirements analysis and technical solution developmentBeyond scope
7. Knowledge and records managementRecords management well past the BPA’s data retention lineBeyond scope
9 and 10. ApplicationsDevelopment elementsBeyond scope on development, maintenance and enhancement acceptable
18. ConWrite supportArgument abandoned by the protesterDenied
19. Intelligence and threat supportGovernance roles and network operations managementBeyond scope

Read that table as a list of what a help desk contract is not. Running the network is not supporting the laptop on the desk. Writing the cybersecurity governance is not protecting the data on the laptop. Analyzing requirements and building applications is not a help desk at all.

The second sustain, and this is the one to save

The other ground is narrower on its face and much wider in practice. Vision is on a contractor teaming arrangement. The agency argued that because Vision was part of a CTA, the order could reach services that sat on a teammate’s FSS contract rather than on Vision’s own.

GAO said no, and said why in one sentence:

each team member is a prime contractor and in privity of contract with the government with respect to its underlying FSS contract

The agency’s reading, GAO wrote, is at odds with the very notion that each team member is a prime contractor.

A CTA is a way for several schedule holders to offer a combined solution. It is not a shared schedule. The government has to be able to point at the specific labor categories on the specific contract of the specific company doing the work, and here the agency could not do that for the LAAFB requirements.

If you are a small business sitting on a teaming arrangement and somebody tells you the team can cover a requirement none of your own labor categories reach, this decision is the answer.

What Ares lost

Not everything went the protester’s way and that part is worth reading too.

The conflict of interest ground was dismissed. Ares pointed at a July 2025 briefing CACI gave the agency. GAO found no factual or legal basis, because the agency plainly understood the briefing as promotional material rather than as objective analysis.

Task 18 was denied outright because Ares did not respond substantively to the agency report on it, and GAO treated the argument as abandoned. That is a recurring way to lose a ground that might have been live.

What Ares survived

Timeliness. The agency argued Ares knew about the coming order earlier, because Ares had seen recruiting activity for the work. GAO held that recruiting chatter is not notice. The clock started on May 29, when the order was actually placed, and the ten day window under 4 C.F.R. 21.2(a) ran from there and from the denial of the agency level protest.

Interested party status. The agency argued Ares could not compete anyway. GAO held that a protester challenging whether an order should have been competed at all is an interested party, because a sustain produces the competition it wants to enter.

The remedy

GAO recommended that the Space Force terminate the order to Vision, issue a new solicitation on a full and open basis, and reimburse Ares for its protest costs including reasonable attorneys fees, with the claim to be filed within 60 days of receiving the decision.

That is the full menu. Most sustains end with a reevaluation and a document. This one ends with the order going away.

What to take from it

One. An agency’s own scoping language is the best evidence against it. Nobody had to prove what wave 1 meant. The BPA said what wave 1 meant, in writing, and then the order did something else.

Two. Scope protests do not require you to be next in line. You have to be able to compete if the order is undone, and that is a much lower bar than showing you would have won an evaluation.

Three. A contractor teaming arrangement is not a shared FSS contract. Each member is a prime for its own contract and its own labor categories, and an order that reaches past them is outside the schedule.

Four. Answer every ground in the comments on the agency report. Task 18 was dropped for silence, not for being wrong.

Five. Being told about work informally, through recruiters or industry talk, does not start the protest clock. The order does.

A nine month base with two options and a six month tail, placed without competition on a help desk vehicle, is now going back out for full and open competition, and the agency is paying the protester’s lawyers for the privilege.