Every RFP has a deadline printed on the cover page. Vendors circle it, build the response timeline backward from it, and sprint toward it.
The data says they are often watching the wrong date.
For The State of Public RFPs: 2026 mid-year report, we analyzed 29,591 public RFPs posted between August 2025 and July 2026. The headline numbers are tight: the median response window is 22 days, one in four listings allows under two weeks, and three in four close within a month. But the tightest number in the dataset is one almost nobody plans around.
Day 12: The Quiet Cutoff
Nearly half of public RFPs — 46.4% — publish a formal question deadline: the date after which vendors may no longer ask the issuer anything. Across those listings, the median question deadline falls just 12 days after posting. That is the midpoint of the median response window, and it quietly redefines what late means.
Find an RFP on day one and you have nearly two weeks to work the question period: clarify scope, test whether the requirements were shaped around an incumbent, and surface the evaluation criteria behind the evaluation criteria.
Find the same RFP on day 14 — still a week before the submission deadline, still technically in time — and the conversation is over. You can submit. You cannot ask.
It is worse than losing a chance to get answers. Issuer responses to vendor questions typically go out as addenda that every bidder sees, so the vendors who arrived early decided what got clarified, corrected, and reconsidered. Show up after the cutoff and you are responding to a document your competitors helped shape.
The Clock Runs Faster in Some Markets
The 22-day median hides real variation. Maryland and the District of Columbia both run 14-day median response windows — a week faster than the national median — while Florida and Georgia give vendors 27 days. If you sell around Washington, DC, the day-12 math becomes day-7 math.
Category matters just as much. Software, Web & Mobile Development is the largest category in the dataset, at one in five listings, and it is also among the least forgiving: a 20-day median window, question deadlines published only 24.4% of the time, and a disclosed budget on just 4.3% of listings. The biggest market is the one that tells vendors the least.
What This Means for How You Find RFPs
Here is the uncomfortable conclusion: a discovery motion that surfaces RFPs a week or two after they post is not slightly late. It is functionally on time for submission and already too late for positioning.
The teams that win consistently are not writing faster. They knew earlier. Budget approvals, renewal windows, and board minutes appear months before a solicitation posts, and when the RFP finally lands, a strong team's bid/no-bid decision is mostly pre-decided. Days one through twelve go into questions and positioning instead of internal debate.
Three practical moves fall out of the data:
- Measure your discovery lag. Compare the date your team first saw each recent RFP with the date it posted. If the gap regularly exceeds a few days, you are forfeiting the question period before the pursuit starts.
- Treat the question deadline as the working deadline. Put it on the calendar next to the submission date. The submission date decides whether you bid; the question deadline decides how well.
- Move discovery upstream of the posting. The only reliable way to be early on day one is to have known before day zero.
Every number here comes from RFP Hunter, Settle's free public database of open RFPs, and the full breakdown — budgets, categories, and state-by-state windows — is in the complete report.