The Revolutionary FAR Overhaul (RFO) may give contracting officers more discretion after a late quotation or offer is received before award. It does not, however, change the fundamental rule that a contractor still must get its submission to the government office designated in the solicitation by the deadline. A sent-message confirmation from the contractor’s own email system is not enough. If an emailed proposal or quotation is stopped by the agency’s security tools before it reaches the designated inbox, GAO will likely treat the submission as not received.
Casey & Company LLC, B-424785 (Oct. 14, 2026) is a useful reminder of the late-submission rule that also raises issues concerning how the RFO may affect such protests. Casey sent its quotation six days before the deadline, but the government’s anti-spam system marked the email as a “High Confidence Phish” and quarantined it. The email reached an agency server, but it never reached the contracting officer’s inbox. GAO denied the protest because receipt by the server was not receipt at the designated email address, and because the record did not show a systemic failure.
What the RFO Changed, and What It Did Not
Before the RFO, the provision at FAR 52.212-1(f) contained the familiar late-offer framework. The offeror bore responsibility for getting the offer to the designated government office on time, and a late offer generally could not be considered unless narrow conditions applied, including the electronic-commerce and government-control exceptions that have driven much of the litigation over email submissions.
The RFO attempted to simplify that approach. RFO Part 12 tells contracting officers to consider timely quotations and offers, and to exercise business judgment in deciding whether to accept a quotation or offer received after the due date or time. The revised RFO 52.212-1 text also moves the late-submission rule to paragraph (c), where the central question is whether the offer was received before award and whether accepting it would unduly delay the acquisition.
As explained below, the RFO change did not save Casey’s quotation.
The Casey & Company Decision
The U.S. National Park Service (NPS) issued RFQ No. 140P1326Q0029 as a small business set-aside under the Department of the Interior’s (DOI) RFO Part 12 class deviation. The RFQ sought leaf removal services for Rock Creek National Park, contemplated a fixed-price purchase order, and made award to the responsible vendor submitting the lowest-priced quotation. Vendors had to email quotations to the contracting officer at the address listed in the solicitation by 12:00 p.m. Eastern Time on July 29. The RFQ warned vendors to account for transmission delays between submission and receipt, and it stated that late quotes or proposals would not be accepted.
Casey sent its quotation to the solicitation email address on July 23 at 8:59 a.m. Eastern Time and received a delivery confirmation from its own Microsoft Outlook system. By the July 29 closing time, the contracting officer had received 15 quotations in his inbox, but not Casey’s. After NPS posted the award notice on August 11, Casey requested a debriefing and attached its quotation to that request. The contracting officer responded that he had no record of receiving Casey’s quote before then, searched his inbox, and then requested an internal IT investigation.
The investigation showed that NPS’s email system received Casey’s email, marked it as a “High Confidence Phish,” and quarantined it under the agency’s anti-spam policy. Casey argued that server-level receipt made the quotation timely. GAO disagreed.
In its decision, GAO reiterated that a vendor must ensure that an electronically submitted quotation is received by, not merely submitted to, the appropriate agency email address before closing. The agency’s quarantine record showed that the email was “Received” by the server but “Not yet released to” the contracting officer’s email address, which meant the quotation never reached the designated recipient.
GAO also rejected Casey’s systemic-failure argument. Although GAO has sustained protests when an agency’s system suffered a systemic failure that kept received quotations from being fairly considered, GAO requires more than an isolated loss or occasional mishandling. In this case, GAO pointed to the fact that all 15 other vendors’ quotations reached the contracting officer’s inbox. For these reasons, GAO denied Casey’s protest.
Practical Takeaways for Contractors
Casey & Company shows that while the RFO may loosen some late-submission rules, contractors remain responsible for ensuring that the government receives their offers at the location set forth in the solicitation (e.g., specific email inbox). Contractors should keep the following points in mind:
- Start with the solicitation, not the general rule. Agencies are implementing the RFO through class deviations and solicitation-specific provisions. Contractors therefore need to read the actual submission instructions, all of the incorporated clauses or provisions, and any late-submission language before assuming that a general FAR exception applies.
- Submit early and confirm actual receipt. A vendor-side delivery confirmationis helpful evidence, but it is not the same as confirmation that the contracting officer received the quotation. Accordingly, offerors should ask the contracting officer to confirm receipt while there is still time to fix a problem.
- Watch for filtering red flags. Emails sent through third-party platforms—or emails with attachments that look unusual to agency security tools—may be filtered before they reach the contracting officer. If prior communications have been quarantined, delayed, or ignored, offerors should assume the same thing can happen to a proposal or quotation and verify receipt directly.
- Use the safest permitted submission method. Large files, compressed attachments, embedded links, and unusual file types can create avoidable delivery risk. If the solicitation permits alternatives, offerors should consider whether a secure file-transfer portal, smaller separate files, or another approved method would reduce that risk.
- Think carefully about protest forum. As this blog has previously discussed, GAO generally takes a strict view of email-submission timeliness, and although the Court of Federal Claims has issued rulings similar to Casey & Company regarding offerors’ emails caught in security filters, it has been more receptive to government-control and related arguments on different records. That forum issue remains important after the RFO because Casey confirms that GAO will still ask whether the quotation reached the solicitation’s designated receipt point.
In short, the main takeaway from Casey & Company is that even under the RFO, getting the offer to the government is the contractor’s job. As a result, contractors should be persistent in confirming, before the deadline, that the agency has actually received their quotation or proposal.