Skip to content

Search RFP.co

Pages across the product, solutions, opportunities and resources.

Type to search. Press Enter to open the full results page.

Start free trial
Proposal practice

The 30-day response, budgeted backwards

The FAR sets a 30-day floor on the response window. Most teams spend it in a shape that puts review at the end, where there is no room left — and the cost of a slipped day turns out to be lumpy rather than linear.

Eric LamannaDirector of Business Development4 min read

Federal solicitations above the simplified acquisition threshold come with a floor on the clock: except for commercial products and services, agencies must allow at least 30 days for receipt of proposals from the date the solicitation is issued. Thirty days is what the rule guarantees. It is not a plan, and most teams treat it as one.

What follows is a worked example rather than a survey — one 30-day calendar, spent two ways. The numbers are ours and the arithmetic is visible, which is the only claim being made for them.

The same thirty days, spent two ways

The first column is the shape a response drifts into when nobody budgets it: a long, comfortable decision period, a short outline, and drafting that expands to fill whatever is left. The second is the same month budgeted backwards from the deadline, where review is booked first and drafting gets what remains.

Figure 1
Two ways to spend a 30-day response window
Decide to bidDecide to bid — How it drifts: 6 days6Decide to bid — Budgeted backwards: 2 days2Outline and questionsOutline and questions — How it drifts: 3 days3Outline and questions — Budgeted backwards: 4 days4DraftDraft — How it drifts: 13 days13Draft — Budgeted backwards: 12 days12ReviewReview — How it drifts: 5 days5Review — Budgeted backwards: 8 days8Produce and submitProduce and submit — How it drifts: 3 days3Produce and submit — Budgeted backwards: 4 days4
  • How it drifts
  • Budgeted backwards

A worked example on a 30-day calendar, not measured data. Both columns total 30 days — this is an argument about order, not about needing more time.

The numbers behind this chart
PhaseHow it driftsBudgeted backwards
Decide to bid6 days2 days
Outline and questions3 days4 days
Draft13 days12 days
Review5 days8 days
Produce and submit3 days4 days

Four days move, and they move out of the two phases that feel like they can absorb it. The decision to bid loses four of its six days, which is uncomfortable and correct: a go decision made on day six is a decision made with the same information available on day two, taken four days later. The outline gains a day, because the questions you submit to the contracting officer are due long before the proposal is, and an outline written after the question deadline is an outline you cannot ask about.

Review is not a phase you can compress

Drafting compresses. A writer given nine days instead of twelve writes a thinner draft, and a thinner draft is still a draft. Review does not work that way, because a review pass is a whole unit: somebody reads the volume against the evaluation criteria, writes comments, and the writer works them in. Call that a day and a half, and hold back two days for production and submission.

Then the number of review passes that fit is a step function of the day the draft is finished, and the steps are what make late drafts expensive.

Figure 2
Complete review passes that still fit, by the day the draft is done
02468Two passes: one for compliance, one for scoreDay 20: 5 passes5Day 20Day 21: 4 passes4Day 21Day 22: 4 passes4Day 22Day 23: 3 passes3Day 23Day 24: 2 passes2Day 24Day 25: 2 passes2Day 25Day 26: 1 passes1Day 26Day 27: 0 passes0Day 27Passes

Arithmetic, not measured data: a review pass is assumed to take 1.5 days and two days are reserved for production, on a 30-day window. Change either assumption and the steps move — the shape does not.

The numbers behind this chart
Draft completeDays left after production reserveComplete passes
Day 2085
Day 2174
Day 2264
Day 2353
Day 2442
Day 2532
Day 2621
Day 2710

Two things fall out of the steps. Slipping from day 21 to day 22 costs nothing at all, and slipping from day 22 to day 23 costs a whole pass — so "we are one day behind" is not a statement anybody can price without knowing which day. And the drop from two passes to one is the one that changes what the submission is: with two, one pass can be spent purely on compliance against the instructions and the other on how the thing scores. With one, those two jobs are done by the same tired read, and the compliance one usually wins because it is the one with a checklist.

What to do with the shape

Book review before drafting. Put the colour-team dates in the calendar on the day the go decision is made, with names against them, and let the draft deadline be whatever those dates leave — rather than scheduling review into the gap that remains once drafting has taken what it wants.

Make the bid decision early and cheaply. Most of the information that decides it — the incumbent, the set-aside, the evaluation weighting, whether you can meet the mandatory requirements — is in the solicitation on day one. The days after that are usually spent looking for permission rather than looking for facts.

And treat the question deadline as the real first milestone. It is the only date in the window where the government will answer you, and it arrives while the calendar still feels roomy — which is exactly why it gets missed.

Eric Lamanna

Director of Business Development

Eric Lamanna is Director of Business Development at RFP.co, where he works with the teams on the other side of a solicitation — the capture leads, proposal managers and small-business owners deciding what is worth chasing this quarter. Most of his time goes on the unglamorous half of that problem: how an opportunity gets qualified, who has to sign off, and what a response actually costs to produce once the reviews are counted honestly.

He came to procurement through digital sales and product work, with a long-running interest in automation and security — the two places where a manual process quietly becomes a liability. He is a believer in workflows that hold up when somebody is out sick, which is most of what proposal operations is.

Eric holds a degree in multimedia design from Olympic College and lives in Denver, Colorado, with his wife and children.

More writing

Bid/no-bid is arithmetic before it is judgment

Expected value is one line of arithmetic, and the break-even win rate it implies is a division on two numbers you already have. Both are worth doing before the part of the decision that needs judgment.

See what you are not bidding on.

Connect a source, describe what your company does, and look at the opportunities that come back before deciding whether any of this is worth your time.