Winning work

A Go/No-Go Decision for RFPs, with a Scoring Sheet

Sam&Sain Co. · Published · Updated · 7 minute read

A go/no-go decision is a short, recorded decision, made before anyone writes, on whether a pursuit is worth the hours. It aims to raise the win rate by dropping the pursuits least likely to win.

On this page

Terms Used

  • Pursuit: a project the firm is considering proposing for.
  • Go/no-go decision: a short, recorded decision, made before anyone writes, on whether to pursue it.
  • Win rate: projects won divided by proposals decided; also called hit rate.
  • Cost per win: what the firm spends on proposals for every project it wins.

Why Decide First

A proposal for a public RFP can take days of senior time, and none of it is billable. Every pursuit the firm cannot win spends hours that could have gone to one it could. Deltek’s 2026 study found “more firms competing for a smaller share of available opportunities” despite “increasing the volume of project proposals”, and warned that “Firms that continue to increase proposal volume without improving strategy may see diminishing returns” (Deltek, 26 May 2026).

A go/no-go decision is a fifteen-minute check, made before anyone starts writing, of whether this pursuit is worth the hours.

What a Proposal Really Costs

The cost of a proposal is the salary cost of the hours spent on it. Divided by the win rate, it becomes the cost of winning one project. Don’t multiply it by the overhead rate: proposal time is already part of overhead, so that would count it twice. When the people writing it set aside billable work to do it, the real cost is the fees those hours would have earned instead.

Example, round numbersAmount
Senior time: 40 hours at $62 an hour of salary$2,480
Other staff: 30 hours at $40 an hour$1,200
Salary cost of the proposal$3,680
Cost per win at a 35% win rate ($3,680 ÷ 0.35)$10,514
If billable work was set aside: the fees those hours would have billed at a 3.0 multiplier ($3,680 × 3.0)$11,040

In this example, every project the firm wins carries about $10,500 of proposal salary, before the fee for the work itself. Raising the win rate to 50% on the same proposals would bring it down to $7,360 (3,680 ÷ 0.50). In a busy month the last line is the one that counts: each proposal gives up about $11,000 of fees. A go/no-go decision aims to raise the win rate by dropping the pursuits least likely to win, which is cheaper than writing every proposal better.

A Scoring Sheet

Score each question from 0 to 3, multiply by its weight, and add up. The weights below are an example; set your own, then keep them.

Question03Weight
Do we know the client, and do they know us?Never metWorked together recently3
Have we done this kind of project?NeverSeveral times, recently3
Did we know it was coming?First seen on the bid siteDiscussed with the client before it was issued2
Who else will bid, and how do we compare?A favoured incumbentWe are the obvious choice2
Can we staff it with the people we would name?NoYes, with room2
Will it pay?Likely lossMargin above our average2
Does it lead somewhere we want to go?NoA client or sector we are targeting1

The maximum is 45. Set a line, for example 27, below which the answer is no unless a partner records a reason to go ahead anyway. The reason matters: “the client asked us to bid” is a good one; “we haven’t won anything this month” is not.

Set the Weights from Your Own History

The weights and the line should come from the firm’s record, not from a template. Take last year’s pursuits, won and lost, and score each one on the sheet as it looked before the proposal went in. Then look at where the wins sit. If almost every win scored high on knowing the client and almost every loss scored low, that question deserves the most weight. If the line you chose would have dropped pursuits you won, lower it; if it would have kept most of the ones you lost, raise it.

Treat the sheet as a judgment aid, not proof. Your record shows only the pursuits you went after; it can’t show whether the ones you passed on would have been won. Each year’s decided pursuits add to the record, so revisit the weights as it grows.

Red Flags

  • The scope reads as if it was written around another firm’s experience.
  • The deadline leaves too little time to do it properly alongside current work.
  • Price carries most of the weight and the scope is vague.
  • The team you would name is already full for the project’s duration.
  • Questions to the client went unanswered, or no one at the firm can call anyone there.

One red flag is a reason to look harder. Two or more usually decide it, whatever the score says.

Who Decides, and When

Decide within a day or two of the RFP arriving, before anyone starts writing. Two people are enough: the partner responsible for the client or sector, and the person who would lead the project. The proposal lead fills in the sheet, the two of them agree the score, and the decision goes on record with its reason. A firm that decides after a week of drafting has already spent the hours the decision was meant to save.

Keep the Record

Write down each decision, its score and the outcome. After a year you can check the sheet against reality: did high scores win, and did low scores you pursued anyway lose? Adjust the weights and the line accordingly. Track your win rate on the pursuits you chose; if it stays low, the line may be too low. For reference, the SMPS Foundation’s survey of 303 US firms found engineering firms averaging a 44.2% hit rate (reported by BD+C, January 2017).

Saying No Well

Declining a pursuit frees hours for the ones the firm can win. If the client matters, tell them you will not bid this time and why, and ask to hear about the next one early. That conversation can score better on the next sheet than a rushed proposal would have.

Win Before the RFP

The question “did we know it was coming?” carries weight for a reason: a pursuit discussed with the client before the RFP was issued starts with an understanding no rival has. The firm’s best pursuits are prepared months ahead, through the clients and sectors it has chosen. Our article on marketing for engineering firms covers how that work brings the right RFPs to the firm.

What the Hours Buy Instead

The time saved goes to the pursuits that pass: a stronger proposal for each, written to the evaluation criteria. See how to write an RFP response that scores.

Common Go/No-Go Mistakes

  • Deciding after drafting has started. The hours are already spent, and nobody wants to waste them.
  • Changing the weights for each pursuit. A sheet adjusted to justify a decision decides nothing.
  • No record of the reason. Without it, nobody can learn whether the exceptions paid off.
  • Never checking the sheet. Weights that were never tested against wins and losses are guesses.

A Checklist for Each Pursuit

  1. Score the pursuit on the sheet within a day or two of the RFP.
  2. Check the red flags.
  3. Decide with the partner and the project lead, and record the reason.
  4. If it’s a no and the client matters, tell them, and ask about the next one.
  5. If it’s a go, record the proposal hours as they are spent.
  6. Record the outcome.
  7. Once a year, test the weights and the line against the wins and losses.

How We Approach This

Which proposals to write and which to let go, from your own win rates and margins, is part of our growth work. Every recommendation comes with the numbers behind it.

Questions

What Is a Go/No-Go Decision?

A short check, made before anyone starts writing a proposal, of whether the pursuit is worth the hours, recorded with its score and reason.

What Should a Go/No-Go Checklist Include?

Whether you know the client, have done this kind of project, knew it was coming, how you compare with likely rivals, whether you can staff it, whether it will pay, and whether it leads somewhere you want to go.

How Much Does a Proposal Cost?

The salary cost of its hours, and, when those hours could have been billed, the fees they would have earned. For example, 70 hours costing $3,680 in salary come to about $10,514 per win at a 35% win rate (3,680 ÷ 0.35). Don’t add overhead on top: the overhead rate already includes proposal time.

Who Should Make the Go/No-Go Decision?

The partner responsible for the client or sector and the person who would lead the project, within a day or two of the RFP arriving.

What Is a Good Line to Set?

One your own history supports. Score last year’s pursuits, see where the wins and losses fall, and set the line where it would have kept most wins and dropped most losses.

Sources

Updates

  • : Rewritten at full length: what a proposal costs per win, setting the weights from your own history, who decides and when, winning before the RFP, common mistakes and a checklist; Deltek and SMPS re-read.

Discuss Your Project

Topic

We read every application. If we can help, the first 30-minute video call is free. Or contact us.