Is Your Proposal Late If Your Email Was Down? The “Late Is Late” Rule
When Microsoft 365 went down for about a day on November 12 and 13, 2026, a lot of small contractors lost Outlook in the middle of proposal season. That raises a question most firms never ask until it happens to them: if your email fails an hour before the deadline, is your proposal late? In most cases the answer is yes, and the government has very little room to help you.
What the Rule Says
The late-proposal rule lives in the solicitation itself, in FAR clause 52.215-1 for negotiated procurements, with matching language in FAR 15.208. Commercial solicitations carry a similar rule in their own instructions. The offeror is responsible for getting the proposal to the designated government office by the exact time stated. A proposal that arrives after that time is late and will not be considered, unless it is received before award, the contracting officer finds that accepting it would not unduly delay the acquisition, and one of three exceptions applies.
The Three Exceptions
| Exception | What it requires | How often it helps |
|---|---|---|
| Electronic submission sent early | The solicitation authorized an electronic method, and the proposal reached the first point of entry to the government’s systems by 5:00 p.m. one working day before the due date | Only if you submitted the day before |
| Under government control | Acceptable evidence that the proposal was received at the government installation and was under the government’s control before the deadline | Rarely, and its use for emailed proposals is disputed |
| Only proposal received | Yours was the only one | Almost never |
The first exception is the one worth planning around. If your proposal is in the government’s system by 5:00 p.m. the working day before it’s due, a later delivery hiccup on the government side doesn’t make it late. Nothing in the rule protects a proposal you tried to send in the final hours and couldn’t.
On the second exception, the Government Accountability Office and the Court of Federal Claims have not always read it the same way when an emailed proposal reached a government server but not the contracting officer’s inbox. Don’t build your submission plan on winning that argument.
Your Outage vs. the Government’s Outage
The rule treats the two very differently. If your email provider, your internet connection or your laptop fails, that is your risk. Protest decisions have said consistently that the offeror bears responsibility for delivering on time and for leaving enough margin to do it.
If the government’s side fails, there is a separate provision. When an emergency or unanticipated event interrupts normal government processes so that proposals cannot be received, and there isn’t time to amend the solicitation, the deadline is treated as extended to the same time on the first work day that normal processes resume. That covers a government office or system that can’t receive anything. It doesn’t cover an outage at a commercial service that only you depend on.
What a Contracting Officer Can Do
Before the deadline, a contracting officer can extend the due date by amendment for everyone. That is the realistic remedy during a widespread outage, and it’s the reason to pick up the phone early. After the deadline has passed, the contracting officer’s hands are largely tied by the rule above, however sympathetic the facts.
If you see trouble coming, contact the contracting officer and the contract specialist by every channel the solicitation lists, say what is happening, and ask for an extension in writing as soon as you’re able. A request made two hours before the deadline has a chance. An explanation sent the next morning usually doesn’t.
How to Protect a Submission
Submit a full working day early. That is the one habit that brings you inside an exception. It also leaves time to fix a rejected file.
Know the delivery method. Email, SAM.gov, an agency portal and a GSA system each record receipt differently. Read the instructions for file size limits, naming rules and the exact address or upload point. Our guide to reading a solicitation covers where those instructions sit.
Have a second way to send. Keep the final files somewhere that doesn’t depend on your email platform, and have a tested alternate way to transmit them from a company account.
Keep proof. Save sent-message headers, portal confirmations and timestamps. If you ever need the government-control exception or a protest, evidence is everything.
Confirm receipt. Ask for an acknowledgment, and follow up by phone if you don’t get one.
These belong in the same checklist as the items in your proposal compliance matrix and the common failures listed in why government proposals get rejected.
If You’ve Already Been Rejected as Late
Ask the contracting officer in writing to reconsider, and attach your evidence of when and how the proposal was sent and what failed. If the failure was on the government’s side, say so specifically. Protest deadlines are short, generally measured in days from when you knew the basis for protest, so talk to counsel right away if the contract matters. Our bid protest overview explains the forums and timelines, and our debriefing guide covers what you’re entitled to ask.
Bottom Line
An outage on your side almost never excuses a late proposal. An outage on the government’s side can, under a narrow emergency rule. The dependable protection is to submit a full working day early and keep a second way to send. Our proposal writing guide builds that margin into the schedule from the start.
Official sources: FAR 52.215-1 — Instructions to Offerors, Competitive Acquisition · FAR 15.208 — Submission, modification, revision, and withdrawal of proposals