Peak summer travel season has jet fuel moving by the millions of gallons, so there is a certain irony in a fuel-supply dispute that turned on an email no one at the agency ever opened. A contractor sent its proposal a day early, got an automated message saying the email was delivered, and lost the competition anyway. The agency never saw the bid. That is the short version of Rick Aviation, Inc. v. United States, No. 25-1604 (Fed. Cl. June 17, 2026), a post-award protest recently decided at the Court of Federal Claims. The opinion is a useful—and painful—refresher on what “received” actually means under the Federal Acquisition Regulation and on how little sympathy a court will extend when the offeror caused the problem.

Key Takeaways

  • The Court confirms that an electronic proposal is not “received” under the FAR late proposal rule unless it reaches the government office or inbox designated in the solicitation before award.
  • A “delivered” email notification is not enough. If the proposal never reaches the agency’s designated inbox, it may still be treated as a late proposal.
  • The FAR’s Electronic Commerce and Government Control exceptions cannot rescue a proposal that was never received before award.
  • Contractors submitting proposals electronically should verify SPF, DKIM, and DMARC authentication and confirm receipt with the contracting officer before the submission deadline.
  • A late proposal can do more than eliminate a contractor from the competition—it can also eliminate standing to challenge the award.

What Happened

The Defense Logistics Agency (DLA) was administering an aviation fuel procurement for commercial airports.  The work was parceled into 122 line items, one per airport, each to be awarded separately on a lowest-price, technically acceptable basis. Proposals were due May 23, 2025, at 1:00 p.m. EST. The solicitation listed two DLA email addresses for submission, told offerors they “assume[d] all risk for any delay in transmission,” and encouraged them to confirm receipt with the contracting officer before the deadline.

The protester submitted its bid for Line Item 75 on May 22, a day ahead of the deadline. A minute later, the protester received a “delivered” notice. But the message never reached either DLA inbox. The Defense Information Systems Agency (DISA), which filters DLA’s incoming mail through its Enterprise Email Messaging Secure Gateway, quarantined the email because the protester’s domain failed Sender Policy Framework (SPF) authentication. DLA awarded the contract to another company on August 19, 2025, and did not even learn that the protester had submitted a bid until it surfaced to protest in late September, well over a month after award.

The Decision

The Court thoroughly rejected each of the protester’s three central arguments.

Receipt has to happen at the designated office before award. Everything turned on FAR 52.212-1(f)(2)(i). That provision says an offer arriving at “the Government office designated in the solicitation” after the deadline is late and “will not be considered” unless two things are true first: The offer was “received before award is made,” and the contracting officer finds that accepting it would not unduly delay the acquisition. Only then does the regulation’s “Electronic Commerce” exception, FAR 52.212-1(f)(2)(i)(A), or its “Government Control” exception, FAR 52.212-1(f)(2)(i)(B), come into play at all.

The protester tried to argue its way into those exceptions, contending that DISA’s interception meant the proposal was within the government’s control before award. The Court did not bite. It read the two opening conditions as gates that must be cleared before any exception matters, and it read “received before award” to mean received where the rest of the clause points: the inboxes named in the solicitation, not an e-mail screening gateway that one agency runs for another. Because the proposal never landed in either DLA inbox before award and may never have been received at all, the analysis ended there. The Court did not have to decide whether either exception applied.

SPF was not a hidden evaluation factor. The protester’s fallback was that DLA had secretly graded bids on SPF compliance, a requirement that never appeared in the solicitation. The Court explained that evaluation factors under FAR 15.304 are the things an agency uses to compare proposals—here, the evaluation factors were technical acceptability and price. SPF authentication happens before a proposal ever reaches the inbox, and an agency cannot evaluate a bid it never received. If anything, the Court suggested, a working email setup is simply part of submitting an electronic proposal, something a sophisticated offeror is expected to handle.

No timely bid, no standing. Finally, the protester challenged how DLA evaluated the awardee’s fixed-base-operator arrangement. The Court held it could not reach that argument. A disqualified, late offeror cannot win the contract, so it suffers no injury that a favorable ruling could fix. That is a standing problem—and standing is jurisdictional—so the Court dismissed the claim outright. With no chance on the merits, the request for an injunction failed too.

Why This Matters

There is a recurring tension in this area. Several Court of Federal Claims opinions have used the Government Control exception to shift the risk of a lost email onto the government once the message reaches a government server. This decision does not pick a fight with those cases so much as route around them. It holds that you never get to the exceptions unless the offer cleared the threshold first, meaning it actually reached the designated office before award. An email that dies in a security gateway never cleared that threshold, so the exception arguments never get a hearing.

The other theme is fault, and the summer calendar only sharpens it. With the end-of-fiscal-year award rush heating up over these next several months, agencies are issuing and closing solicitations at a brisk pace, and the margin for a sloppy submission shrinks accordingly. The breakdown here was on the sending side. The protester’s own SPF record was misconfigured, the government did nothing wrong, and the agency had no duty to go hunting for a bid it did not know existed. Courts have shown some give when a government glitch causes the lateness, but they show virtually no mercy when the contractor is at fault.

Five Key Lessons

  1. A “delivered” notice proves nothing, and reaching a government screening gateway does not count either. What counts under FAR 52.212-1(f)(2)(i), and under the parallel rule for negotiated buys at FAR 52.215-1(c)(3), is arrival at the specific office or inbox the solicitation names, before award.
  2. Confirm receipt, and keep proof. The solicitation invited it, the Court hammered the protester for skipping it, and DLA even conceded the bid might have been timely had the company been more proactive. Make a receipt confirmation a nonnegotiable step in your proposal process, and do not let it slide.
  3. Your email authentication is your responsibility. SPF, DKIM, and DMARC are sender-side settings. Confirm that your domain authorizes whatever server you actually send from, and test against a government recipient before it counts for real. Federal gateways drop a striking share of inbound mail.
  4. Do not build your submission plan around the exceptions. The Electronic Commerce exception’s “one working day prior” safe harbor and the Government Control exception are useless if the bid never reached the designated office before award. Treat them as a backstop, not a strategy.
  5. Get in the door before you fight about the room. A late bid does not just lose on timeliness; it strips you of standing to challenge anything else about the award. Every other protest ground you might have depends on a timely proposal landing where it belongs.