Note • Protests and Appeals

Silence is not compliance.

Three lessons from Exail v. NOAA at GAO.

The GAO’s April 30, 2026 decision in Exail Inc., B-424225 (Comp. Gen. Apr. 30, 2026), is the kind of decision that looks routine on the surface and rewards a second read. NOAA was buying Uncrewed Maritime Systems on a fixed-price IDIQ — two to eight craft over five years — and ran a best-value tradeoff with non-price significantly more important than price. Chance Technologies came in at $13.5 million. Exail came in at $28.7 million. Exail also got rated Unsatisfactory on the technical factor, which made it ineligible for award before the price gap even mattered. Three rulings came out of the protest, and each one says something useful.

Training materials

The headline issue is training materials. The SOW and Section L told offerors to provide a comprehensive overview that demonstrated an understanding of all the work required, and Attachment J-2 identified instructor guides (DI-021-01) and student guides (DI-021-02) as data items. Exail’s proposal said almost nothing about either. When the agency assigned a deficiency, Exail responded with three arguments that proposal counsel hear all the time: training is a minor subset of the work, our proposed “DriX Instructor” course necessarily incorporated the materials, and because we never took exception to the requirement the agency had no basis to find a deficiency. GAO rejected all three. The phrase “minor subset” does not survive contact with a solicitation that says “all of the work required.” Saying a training course “necessarily” includes instructor and student guides is not the same as submitting them or describing them. And the absence of an exception is not a substitute for an affirmative showing of compliance. The decision is a clean restatement of the proposition GAO has been making since Six3 Systems — it is the offeror’s burden to write a proposal that demonstrates compliance, and silence is not compliance.

Disparate treatment

The disparate-treatment ruling is where the practical lesson lives. Exail argued that Chance also did not adequately address training, so the agency could not give Chance a pass and ding Exail. GAO reviewed the two proposals side by side and found that Chance had written more — Chance’s proposal described developing the materials and storing them in a product data manager. That was enough. When you challenge unequal treatment, you have to show the ratings did not stem from real differences in the proposals. If the other guy wrote three paragraphs and you wrote zero, you lose that argument before you start. For anyone drafting a proposal under a comparable best-value tradeoff, the message is that “the awardee did not really comply either” is almost never a winning protest theory unless you can put two materially equivalent passages on the table.

The four corners

The third holding is a quieter one but worth flagging. Exail argued the agency improperly looked outside Chance’s proposal — the “too close at hand” line of attack — and pointed to language in the Business Case Memorandum suggesting the source selection board drew on its own knowledge of Chance’s craft. GAO dismissed this as legally insufficient and reaffirmed that an agency’s technical evaluation is not confined to the four corners of the proposal. That is a useful citation to have in the file the next time a competitor tries to argue that the agency cheated by knowing too much.

Technology readiness

There is also a Technology Readiness Level argument in the back half of the decision that contracts lawyers should not overlook. Exail tried to read the solicitation’s RL8 demonstration requirement as a feature-by-feature performance test of every spec in Attachment J-1. The agency said modeling, simulation, and seakeeping analysis can support an RL8 showing, and GAO agreed. If you write proposals or evaluate them in maritime, aviation, or any technology-readiness-driven program, that is a useful data point on what “demonstrated in an operational environment” means.

A few takeaways

First

Walk every CDRL and every data item in Attachment J back into your technical narrative. If the solicitation calls out DI-021-01 and DI-021-02, your proposal needs to address DI-021-01 and DI-021-02 by name or by clearly equivalent description.

Second

If you are relying on existing materials, attach them or describe them with enough specificity that the evaluator does not have to assume. Exail’s “DriX Instructor” course might have been a complete answer, but it was not in the record.

Third

For protest counsel, this is another reminder that GAO is not in the business of reweighing proposals and that disagreement with judgment, without more, is not a ground.

Fourth

When a competitor is roughly half your price, the technical evaluation is doing a lot of work, and an Unsatisfactory rating ends the conversation before tradeoff ever begins.

Routine on its face. A good teaching case underneath.

Cases cited

Exail Inc., B-424225 (Comp. Gen. Apr. 30, 2026)