How to Score Go/No-Go Bid Decisions on Government RFPs

Most contractors do not lose proposals in the writing. They lose them the day they decide to bid. If you are winning fewer than one in five of your submissions, the fastest fix is almost never a better proposal writer. It is a better bid decision. This post gives you a weighted go/no-go scorecard you can run in 30 minutes, a set of automatic no-bid tripwires, and a worked example so you can see how the math plays out on a real-looking opportunity.

Why gut-feel go/no-go decisions fail

When the decision is a conversation instead of a scorecard, three predictable things happen:

• The loudest voice wins. Usually the person who found the RFP and is already emotionally invested in it.
• Revenue hunger overrides fit. A slow quarter makes every opportunity look winnable.
• Nobody owns the loss. When you lose, the post-mortem is vague because the original reasoning was never written down.

A scorecard fixes all three. It forces you to answer the same questions every time, it produces a number you can compare across opportunities, and it creates a paper trail you can review after wins and losses to calibrate your own judgment.

There is also a hard cost argument. Every full proposal you write consumes real money in labor and overhead, and a no-bid is the only decision that costs nothing. We broke down those numbers in how much it costs to bid on government contracts. Read that first if you have never priced your own proposal effort. The scorecard below is how you protect that budget.

The seven-factor scorecard

Score each factor from 0 to 5, multiply by the weight, and sum. Maximum possible score is 100.

How to score each factor honestly

Customer relationship (20). This is weighted highest because it is the best single predictor of a win. If your first contact with the agency is the solicitation itself, score yourself 0 to 1 and do not talk yourself upward. Attending a pre-proposal conference is worth a point. Having responded to the Sources Sought notice and had a follow-up conversation is worth 3 or 4.

Technical fit (20). Score against the actual scope of work, not your marketing materials. Pull the performance work statement apart section by section, the same way we describe in how to read an RFP, and ask what percentage of the tasks you have performed in the last three years.

Past performance match (15). Evaluators want same scope, similar dollar size, and recency, usually within three to five years. Three loosely related projects score lower than one dead-on match.

Competitive position (15). Is there an incumbent? Is the incumbent recompeting? Check award history on SAM.gov and USAspending. If a healthy incumbent is defending work they have performed well, score 0 to 2 unless you have specific intelligence that the customer wants change.

Price competitiveness (10). You do not need a full cost model at this stage. You need an honest answer to one question: given your wrap rates and the likely budget, can you land within roughly 10 percent of the probable winning price?

Team availability (10). If the RFP requires named key personnel with resumes, and your candidates are billable on other contracts, score low. "We will hire after award" reads as risk to every evaluator who has seen a staffing plan collapse.

Strategic value (10). A contract that gets you into a target agency, earns a past performance reference in a new category, or puts you on a vehicle can justify bidding at a slightly lower score. This factor is capped at 10 points on purpose so strategy cannot rescue a fundamentally bad pursuit.

Set a threshold and honor the tripwires

A scorecard only works if the threshold is fixed before you score. A sensible starting rule set:

• 70 or above: bid, and resource the proposal fully.
• 55 to 69: bid only if you can raise a specific factor before submission, for example by adding a teaming partner who brings the past performance you lack. Name the factor and the fix in writing.
• Below 55: no-bid, no debate.

On top of the score, apply automatic tripwires. Any one of these is a no-go regardless of the total:

1. A mandatory requirement you cannot meet by the due date, such as a certification, clearance, or bonding level.
2. Fewer days remaining than your minimum proposal timeline for that document type.
3. Customer relationship and past performance both score 0 or 1. Two zeros in your top factors means you are column fodder.
4. You cannot name a proposal manager who actually has the hours.

A worked example

Here is a fictional example, invented for illustration. A 12-person IT services firm sees a help desk support RFP from a federal agency they have never worked with. They browse similar open opportunities on the IT and software RFP feed and this one looks like the best fit on paper. Then they score it:

A 61 lands in the conditional zone. The named fix: team with a firm that holds a current contract at that agency, which would raise customer relationship to 3 and past performance to 4, pushing the total to roughly 72. If the teaming call does not produce a partner within a week, the answer is no-bid. Notice what the scorecard did here. Without it, "perfect technical fit" would have carried the room. With it, the team saw that fit alone was not enough and turned a vague hope into a concrete, testable condition.

Run it in 30 minutes

• One person reads the full solicitation and fills in a draft scorecard. 20 minutes for most RFPs.
• A second person challenges every score of 4 or 5. Optimism inflation lives in the top scores.
• The decision maker applies the threshold and tripwires and records the result, the score, and the reasoning in one paragraph.
• Every quarter, compare scores against outcomes. If you are losing bids you scored above 75, your scoring is inflated somewhere. Adjust.

If your pipeline is thin, the temptation to lower the threshold will be constant. Resist it by widening the top of the funnel instead. Contractors in crowded markets like Virginia, or in broad categories like professional services, usually have more qualifying opportunities available than they realize. A daily scan of fresh postings, whether you do it manually or let a service like RFPhound deliver fit-scored matches each morning, means you can afford to say no to the 61s because a 78 is coming.

The payoff

A no-bid is not a failure. It is capacity reclaimed for the opportunity you can actually win, plus a data point that sharpens every future decision. Contractors who score every pursuit tend to bid less, win more, and know exactly why. That is the whole game.