How Long Do You Actually Get to Respond to a SLED RFP? We Measured 33,096 of Them

The median response window on a state, local, and education RFP is 22 days. That is the number across 33,006 public postings that had a valid window, collected between August 2024 and July 2026 in Settle's RFP Hunter corpus. A quarter of those postings gave vendors fewer than 14 days. Three quarters gave fewer than 30.

The short version: a SLED response window is the gap between the day a solicitation is published and the day submissions are due. Half of them close inside 22 days, geography moves that number by nearly three weeks from end to end, and the deadline that actually governs your work (the last day to submit written questions) typically lands 11 days before the one on the cover page.

Where does the industry's "21-day turnaround" number come from?

If you have sold into state and local government for any length of time, you have heard that RFPs sit on the street (industry slang for the window between posting and deadline) for about three weeks. The figure is repeated in sales trainings, capture plans, and vendor webinars as though it were census data.

As far as we can tell, it traces to a 2017 Government Technology article citing the Center for Digital Government. The Center for Digital Government is Government Technology's own research arm, and it does serious work. But the article names no dataset, no sample size, and no method. There is nothing to check, and nothing to update as procurement practice has changed over the following decade.

We are not calling the number wrong. Our own measurement, a median of 22 days, lands close to it, which is a point in its favor. We are saying two other things. An entire market has been planning capacity around a figure nobody can audit. And a single midpoint, however accurate, hides the spread that actually determines whether you can bid: the quarter of postings that close inside two weeks behaves nothing like the quarter that runs past 30 days.

One other public check exists. RFPgo, a vendor blog, sampled 274 Pacific Northwest RFPs posted between January and May 2025 and found a median of 24 days, two days above our 22-day median across the full corpus. Their sample is small, regionally concentrated, and disclosed openly, and it points in the same direction as ours.

How long do you get to respond to a government RFP?

Here is the full distribution across the corpus. The remaining quarter of listings (25.5%) allow 30 days or more.

And the percentiles:

The shape matters more than the midpoint. The distribution is not a tidy bell curve centered on three weeks. It is front-loaded and long-tailed: a dense cluster of short windows, a hard wall at 30 days where a large share of agencies standardize, and a thin tail of genuinely long solicitations that pull the average up without helping anyone.

Practically, that means one in four opportunities arrives with less than two weeks of runway. If your qualification process, executive approval, pricing sign-off, and partner coordination take longer than that combined, one quarter of the market is closed to you before you read the first requirement.

Which states give vendors the least time?

Geography moves the number far more than anyone discusses. Among states and the District of Columbia with at least 150 listings in the corpus, the median window ranges from 14 days to 33 days.

Just outside the fastest five: Mississippi and Ohio at 18 days, Hawaii at 19, Massachusetts at 20. Just outside the slowest five: Maine, Kansas, Vermont, and Wyoming at 26, and Connecticut at 25.5.

The gap between Alabama and Indiana is 19 days. That is not a rounding difference. It is the difference between a solicitation you can respond to properly and one you triage.

Two consequences follow. First, a national team running one uniform pursuit process is systematically underperforming in the fast states, because the process was built for the slow ones. Second, territory design and quota setting that treat all states as equivalent are quietly asking some reps to do the same work in half the time.

It is worth noting where the volume actually sits, because volume and speed do not track together. The five highest-volume states in the corpus are California (3,869 listings), Texas (3,045), New York (2,343), Florida (1,613), and Maryland (1,197). Two of the five biggest markets (Florida and California) are also among the slowest, while Maryland is among the fastest. There is no shortcut here. You have to know your states.

Does the type of buyer change the window?

Somewhat, and in the opposite direction from what most people guess.

Government agencies, the buyers with the heaviest procedural overhead, actually give the most time. Universities, districts, and non-profit issuers move faster. The variance between issuer types is four days. The variance between states is nineteen. If you are going to segment your pursuit process on one dimension, segment on geography.

Why the question deadline is the real deadline

The submission date on the cover page is not the date that governs your work.

Just under half of listings (46.5%) publish a deadline for written questions. In those listings, the question deadline falls a median of 12 days after posting and 11 days before submission.

Read that again in operational terms. On a median opportunity, you have 12 days to read the solicitation closely enough to know what you do not understand, decide whether to bid, and submit questions in writing. After that date, the requirements are frozen. Any ambiguity you failed to surface is now a risk you carry into your pricing or a compliance gap you discover during final review.

So the real clock is not 22 days. It is 12 days to a decision point, and then 11 days of execution against requirements you can no longer influence.

The corpus offers one more relevant detail: 58.5% of listings name a procurement contact, 53% include an email address, and 34% include a phone number. On more than half of postings, there is a named human you can reach before the question window closes. That is a low bar that a surprising number of pursuit processes never clear.

What does the calendar actually look like?

Submission deadlines are not spread evenly across the week. Fridays absorb 23.5% of them; Mondays take 16.9%.

That skew compounds a problem teams already feel. In our conversations with SLED sales teams, one group described dreading Monday mornings, when 200 to 300 opportunities have accumulated over a weekend nobody was watching. Postings land, question windows begin ticking, and the review happens after the fact.

Two other patterns came up repeatedly in those conversations. Teams told us that paid aggregators frequently surface a posting three to six days after the agency published it on its own portal. On a 14-day window, that is a fifth to nearly half of the available time consumed before the opportunity reaches the person who would act on it. And one enterprise team had codified an internal rule: on a two-week window, they cannot afford to lose more than 24 to 48 hours to internal routing. Everything past that comes out of writing time.

Neither of those is a data point from our corpus, and we present them as what they are: anonymized field color from customer conversations, not measurements. But they describe the mechanism by which a 22-day median becomes a 10-day reality.

Buyers take a year. Vendors get three weeks.

For contrast, look at the same process from the buyer's side. New York City publishes citywide procurement indicators, and in FY2025 the median full RFP cycle, from pre-solicitation through contract registration, was 387 days.

The agency spends more than a year on the procurement. The vendor gets three weeks of it.

That asymmetry is the entire story of public-sector sales, and it is why response speed is the wrong thing to optimize. During those 387 days, the agency is scoping the need, consulting the market, drafting requirements, and forming a view of what a good solution looks like. The 22-day window is the last chapter, not the book.

What this means if the posting is your first contact

If the day an RFP appears is the day you first learn the buyer exists, the window is not short. It is likely unwinnable, and no amount of internal process improvement fixes that, because the decision that mattered was made months earlier by people you were not talking to.

The work happens 6 to 18 months before the posting: budget lines appearing in proposed appropriations, board and council agendas naming a problem, contracts approaching expiration, leadership hires who arrive with a mandate, consultants engaged to write a needs assessment. Those are visible, public, and largely ignored. By the time the solicitation posts, a vendor who was in those conversations has already shaped what the requirements ask for.

That is the premise Settle is built on. We work directly with public-sector sales teams to build a signals system around the workflows they already run: connecting the sources they already monitor, matching what surfaces against what they can actually win, and attaching a next step to every signal, so early evidence becomes action instead of a bookmark. The 22-day window is not the problem to solve. It is the symptom of solving the wrong problem.

If this is useful, three places to go next: the full state of public RFPs report for the broader dataset, our breakdown of which pre-RFP signals actually predict a solicitation, and RFP Hunter, where you can find current public postings for free.

Methodology

The dataset is Settle's RFP Hunter corpus: 33,096 public RFPs, RFQs, RFIs, and comparable solicitations posted between August 2024 and July 2026, collected from public sources across US state, local, and education issuers.

The response window is calculated as the number of days between the posting date and the submission deadline. Listings without both dates, or with a computed window outside 0 to 365 days, were excluded as data-quality failures; 33,006 listings remained, and every statistic here is drawn from that set. State-level medians are reported only for states and the District of Columbia with at least 150 qualifying listings, with n shown for each.

Medians are used throughout rather than means, because the long right tail of multi-month solicitations pulls averages away from the typical experience. Issuer type is classified from the issuing organization. Question-deadline statistics are calculated on the 46.5% of listings that publish one.

Two caveats we would like to share. First, the corpus reflects what is publicly discoverable, so agencies that post only to closed or paywalled portals are underrepresented. Second, coverage varies by state, which is why we set a floor of 150 listings before reporting a median. No corpus of public procurement is complete, and we do not claim ours is.

Frequently asked questions

How long do you typically get to respond to a government RFP? The median is 22 days from posting to submission, based on 33,006 public SLED solicitations posted between August 2024 and July 2026. The 25th percentile is 13 days and the 75th percentile is 30 days. About one in four postings gives vendors fewer than two weeks.

Which states have the shortest RFP response windows? Among states with at least 150 listings, Alabama and the District of Columbia are fastest at a 14-day median, followed by Maryland and West Virginia at 15 and Oklahoma at 16. Indiana is the slowest at 33 days, with Florida, Georgia, and Nevada at 27.

Is the submission deadline the deadline that matters? Usually not. On listings that publish a question deadline, that date falls a median of 12 days after posting and 11 days before submission. Once it passes, requirements are effectively frozen, so the practical decision point arrives roughly halfway through the stated window.