An 8(a) cyber-training competition just produced the first Government Accountability Office test of a new small-business favor written into the Defense Federal Acquisition Regulation Supplement — and the office never reached the question everyone in the small-business bar wants answered. In a decision dated June 30, 2026, the office dismissed the pre-award protest of Tyonek Technical Innovations, LLC, an 8(a) firm in Anchorage, Alaska, on two independent procedural grounds. Tyonek had argued that the Air Force wrote its affiliate past-performance rule in a way that violates DFARS 215.305(a)(2)(C). GAO said the challenge came too late on one theory and too early on the other, and left the underlying regulatory conflict untouched.
Background
The dispute grows out of Section 865 of the Fiscal Year 2024 National Defense Authorization Act (Pub. L. 118-31), a provision Congress passed to make it easier for small firms to compete on experience they do not yet own outright. Small businesses routinely lack the long past-performance record that agencies demand, so they lean on parents, affiliates, and teaming partners. Section 865 pushed that reality into regulation. The implementing text, DFARS 215.305(a)(2)(C) on acquisition.gov, tells contracting officers that when evaluating the past performance of an offeror that is a small business concern, they "shall consider relevant past performance information provided for affiliates of the offeror." The word "shall" is the point. The provision imposes no condition on that consideration — it does not say the affiliate must perform any part of the resulting contract.
Against that backdrop, the Department of the Air Force issued RFP No. FA8773-25-R-0002, an 8(a) set-aside for cyber operations training support services. The solicitation told offerors that it would credit an affiliate's past performance only if that affiliate "would perform significant and critical aspects of the contract." To Tyonek, that qualifier was exactly the kind of gate Congress and the DFARS drafters had removed. A small business could hold a corporate family full of relevant experience, but under the Air Force's phrasing that experience would count for nothing unless the affiliate was written into the work. For an 8(a) firm chasing a cyber-training award against larger, more seasoned competitors, the distinction was not academic — it could decide whether the company's strongest evidence of capability reached the evaluators at all.
Key Details
Tyonek filed a pre-award protest challenging the solicitation's terms. No final award decision had been made, and Tyonek remained an active competitor for the contract. Its central argument was clean: the RFP's affiliate condition conflicts with DFARS 215.305(a)(2)(C), which orders consideration of affiliate past performance for small businesses without any "will perform" trigger.
GAO dismissed the protest on two separate grounds, either of which was enough on its own. First, the office found the challenge untimely. Under GAO's bid-protest regulations at 4 C.F.R. § 21.2(a)(1), a protest based on alleged improprieties in a solicitation that are apparent on the face of the document must be filed before the deadline for receipt of proposals. GAO treated the affiliate-performance clause as a patent — unambiguous — term of the RFP. The requirement was printed in the solicitation for every offeror to read, so any objection to it had to come before proposals were due, not while the competition was still running.
Second, GAO found the evaluation challenge premature. To the extent Tyonek complained about how the Air Force would apply the affiliate rule to its proposal, that grievance was speculative. No final award decision had been made, and Tyonek had not been eliminated. GAO does not entertain protests built on predictions of how an agency might evaluate a proposal that has not yet reached a final decision. If the Air Force ultimately credited Tyonek's affiliate experience, there would be nothing to protest; if it did not, Tyonek could raise the issue then.
The consequence is that GAO never decided whether the Air Force's clause actually conflicts with the DFARS. The office resolved the case entirely on procedure. The regulatory question — whether an agency may still condition affiliate past-performance credit on the affiliate's role in the contract, notwithstanding the unconditional "shall consider" language of 215.305(a)(2)(C) — remains open for the next protester who raises it on time.
What It Means for Contractors
The practical lesson lands before the merits ever come into view: timing governs. A small business that reads a solicitation term it believes violates the DFARS cannot wait to see how the evaluation shakes out. Under 4 C.F.R. § 21.2(a)(1), a facially apparent solicitation defect is a use-it-or-lose-it objection. File before the proposal deadline or forfeit the argument. Tyonek's regulatory theory may well have force, but it arrived on GAO's docket in a posture the office would not hear.
The strategic tension is real. Filing a pre-award protest against a solicitation you are also bidding on is uncomfortable — it can sour the customer relationship and telegraph your read of the competition. Yet the alternative, raising the issue only after a disappointing evaluation, may be procedurally dead on arrival for anything the solicitation put in plain view. Small businesses relying on parent or affiliate experience should scrub set-aside solicitations early for any clause that narrows the affiliate past-performance mandate, and decide before the due date whether the term is worth a formal challenge.
For contracting officers, the decision is a reprieve, not a ruling. The Air Force's "significant and critical aspects" condition survived this protest, but only because GAO declined to reach it. Nothing in the decision blesses the clause on the merits. An agency that reads Tyonek as permission to keep conditioning affiliate credit is reading a procedural dismissal for more than it holds. The first time a protester lands the same argument before the proposal deadline, GAO will have to decide whether Section 865 and DFARS 215.305(a)(2)(C) mean what their unconditional text says. Until then, the affiliate past-performance rule remains a live fault line in small-business source selection — tested once, and left unresolved.
