When submitting bids, contractors should always double check their proposal submission methods, whether it be a designated portal, email, or any other method, and do so well before the deadline.
GAO recently had the opportunity to examine proposal submission issues related to a US Navy procurement, and did not show sympathy for the contractor who experienced proposal submission issues right at the deadline.
A protester recently lost an effort to get an agency to consider a late proposal arguing that it was emailed to the agency on the due date.
Even though the quote would have been less expensive than the awardee’s and this was a lowest-price technically-acceptable procurement, GAO denied the protest finding that the email was a few hours late and did not include the attached quotation.
When a bidder submits a bid under a sealed bid procurement, it is responsible for ensuring that the bid is timely submitted. But what happens if a bidder wants to revise a bid that’s already been submitted?
As a recent GAO case shows, even a revised bid must be timely submitted in order for it to be considered. If a bidder tries to revise its bid too late in the process, it might end up costing itself the award.
You might think that if you send an email with the delivery receipt option and the delivery receipt comes back, the email was delivered. But when an offeror submits a proposal by email, does a delivery receipt mean that the agency necessarily received the proposal in its inbox?
At least under the facts of one recent GAO bid protest, the answer was “no.” In that case, the GAO held that an email delivery receipt wasn’t sufficient to demonstrate that the agency received the electronic proposal.
You’ve hit send on that electronic proposal, hours before the deadline and now you can sit back and feel confident that you’ve done everything in your power – at least it won’t be rejected as untimely – right?
Not so fast. If an electronically submitted proposal gets delayed, the proposal may be rejected–even if the delay could have been caused by malfunctioning government equipment. In a recent bid protest decision, the GAO continued a recent pattern of ruling against protesters whose electronic proposals are delayed. And in this case, the GAO ruled against the protester even though the protester contended that an agency server malfunction had caused the delay.
An offeror’s proposal was properly rejected as late because the proposal exceeded the agency’s email file size limit.
In a recent bid protest decision highlighting the importance of not submitting electronic proposals at the last minute, the GAO held that a small business’s proposal was late because the emails transmitting the proposal exceeded 10 MB–even though the solicitation didn’t mention a file size limit.
An agency’s spam filter prevented an offeror’s proposal from reaching the Contracting Officer in time to be considered for award–and the GAO denied the offeror’s protest of its exclusion.
A recent GAO bid protest decision demonstrates the importance of confirming that a procuring agency has received an electronically submitted proposal because even if the proposal is blocked by the agency’s own spam filter, the agency might not be required to consider it.