Skip to content
CONTRACT COMMANDPowered by BizCom
Resources

The Bid/No-Bid Decision: A 12-Criteria Go/No-Go Framework for Government Contractors

Every proposal is a bet of your team's scarcest hours. Here is a weighted, 12-criteria Go/No-Go framework that makes the bid/no-bid decision fast, consistent, and honest.

9 min read · October 6, 2026

The most expensive proposal is the one you never should have written. A small contractor might have two or three people who can actually write, price, and review a bid. Every hour spent on a long-shot pursuit is an hour taken from one you could win, or from delivering the contracts you already have.

Most small firms don't lose because they write weak proposals. They lose because they chase too many solicitations, spread thin, and submit rushed work against competitors who picked their battles. A disciplined bid/no-bid decision fixes that. This guide covers the framework we use: twelve weighted criteria, scoring, hard knockouts, red flags, and a decision log that sharpens your judgment over time.

Why a written Go/No-Go process beats gut feel

Gut feel is fine when you bid twice a year. Once you're looking at several solicitations a week, gut feel turns into whoever argues loudest, or into 'we should bid everything in our NAICS code.' A written process gives you three things:

  • Consistency. The same opportunity gets the same answer no matter who is in the room or how the week is going.
  • Speed. A scorecard takes 20 to 30 minutes once you know the opportunity. Debating without one can take days you don't have.
  • A record. When you log the score and the outcome, you can see which criteria actually predict your wins, and adjust.

Run the decision at least twice: a first look when the opportunity appears (a sources sought notice, a forecast, or a presolicitation notice), and a final gate when the actual solicitation drops. Requirements, evaluation criteria, and timelines often change between the two, and a Go on the forecast is not a Go on the RFP.

The 12 criteria and how to weight them

Score each criterion from 0 to 5 and multiply by its weight. The weights below add up to 100. Adjust them to your business. A firm with a cleared workforce may weight clearance lower; a firm entering a new agency may weight customer familiarity higher. Whatever you choose, write the weights down and keep them stable for at least a quarter so your scores mean something.

1. Set-aside fit (weight 10)

Is the opportunity set aside for a program you qualify for, such as small business, 8(a), HUBZone, service-disabled veteran-owned, or women-owned, and are you eligible today rather than after a pending certification? A set-aside you qualify for narrows the field. A full-and-open competition against large businesses is a different game. Confirm you are small under the size standard for the NAICS code assigned to this solicitation, not just your primary code.

2. NAICS and capability fit (weight 12)

Can you do this work, with your current people and suppliers, at the level the statement of work describes? Read Section C (or the performance work statement) line by line. A 5 means you do this exact work every week. A 2 means you would need a teaming partner or new hires to cover major pieces.

3. Incumbent position (weight 8)

Is there an incumbent, and how are they doing? Pull award history from USAspending.gov or federal procurement data to see who holds the current contract, its value, and when it ends. A satisfied customer with a strong incumbent is hard to unseat. A recompete where the agency changed the requirements, the incumbent outgrew the size standard, or performance problems are on the record can be a real opening. If you are the incumbent, score it high, and don't get complacent.

4. Relevant past performance (weight 12)

Do you have recent, relevant projects similar in size, scope, and complexity? Many evaluations weight past performance heavily, and 'relevant' is defined by the solicitation, so read exactly how the evaluation factors describe it. If your own record is thin, check whether the solicitation lets you cite past performance of key personnel, subcontractors, or teaming partners.

5. Competitive field (weight 6)

How many credible competitors will show up? Sources sought results, industry day attendee lists, and interested vendor lists on SAM.gov give you a sense of the field. Fewer qualified competitors means a higher score.

6. Price-to-win confidence (weight 10)

Do you know roughly what the government expects to pay, and can you be competitive at that number while still making money? Look at the prior award value, any disclosed government estimate, labor rates on similar contracts, and the evaluation method. Under lowest price technically acceptable (LPTA), a higher-cost firm is at a structural disadvantage. Under a best-value tradeoff, you have more room, though not unlimited.

7. Response capacity (weight 10)

Who will write, price, and review this, and what will they stop doing to make room? Name the people. If the answer is 'the same two people already working three other bids,' score it low. Capacity is the criterion most teams overestimate.

8. Timeline (weight 6)

Is the response window realistic for the size of the proposal? A 15-page capability response in ten days is doable. A three-volume technical, management, and price proposal in two weeks is a sprint, and it usually shows. Check the period of performance start date too: can you actually mobilize by then?

9. Geography (weight 5)

Where is the work performed? On-site work far from your people adds travel cost, hiring risk, and competition from local firms. Some solicitations favor or require a local presence. Remote or delivery-based work scores higher.

10. Clearance and compliance requirements (weight 6)

Does the work require a facility clearance, cleared personnel, specific licenses or certifications, or cybersecurity controls for handling Controlled Unclassified Information? Requirements you already meet score a 5. Requirements you can't meet in time aren't a low score; they're a knockout, covered below.

11. Contract value fit (weight 7)

Is the contract the right size for you? Too small, and the cost of the proposal eats the margin. Too large, and you may struggle to finance performance, staff up, or satisfy the contracting officer that you can perform. A rule of thumb many small firms use: be careful bidding a single contract that would more than double your current annual revenue unless you have a real plan for cash flow and hiring.

12. Customer familiarity (weight 8)

Do you know this buying office? Have you talked with the contracting or program staff (within the rules for communication), responded to their sources sought notices, attended their industry day, or delivered for them before? Proposals written for a customer you understand read differently from proposals written to a document.

Turning scores into a decision

Multiply each 0 to 5 score by its weight, divide by 5, and add them up. You get a number from 0 to 100. Then apply thresholds you agreed on in advance:

  • 70 and above: Go. Assign a capture lead and a proposal manager, and put dates on the calendar.
  • 50 to 69: Conditional. Identify the one or two criteria dragging the score down and decide whether a specific action fixes them: a teaming partner, a key hire, a site visit. If nothing fixes them, it's a No-Go.
  • Below 50: No-Go. Write one sentence on why, log it, and move on.

A quick example. Say you score set-aside fit 5, capability 4, incumbent 2, past performance 4, competition 3, price-to-win 3, capacity 3, timeline 4, geography 5, clearance 5, value fit 4, and customer familiarity 1. The weighted total is 71. That is a Go, but barely, and the weak spots (incumbent position and customer familiarity) tell you exactly where the capture effort needs to go.

Knockouts override the math

Some conditions end the conversation regardless of score. Check these first:

  • You aren't eligible for the set-aside, or you aren't small under the solicitation's size standard.
  • A required clearance, license, certification, or registration can't be in place by the deadline the solicitation sets.
  • Your SAM.gov registration isn't active, or won't be by the time you submit.
  • You can't perform a mandatory requirement, and the solicitation doesn't allow a teaming partner or subcontractor to cover it.
  • No one with the authority and skills to own the proposal is available.

Red flags that should lower your score

Watch for signals that an opportunity is a poor bet. None is automatically disqualifying, but each deserves a hard look:

  • Requirements that read like one company's résumé: oddly specific experience, brand-name equipment, or key personnel qualifications that match the incumbent's team exactly.
  • A short response window on a recompete, especially with no questions period.
  • An evaluation scheme that rewards things you can't show yet, such as heavy weight on past performance with that specific agency.
  • LPTA evaluation when your cost structure is built around quality rather than the lowest rate.
  • Amendments that keep moving the goalposts without answering the questions that matter.
  • A contract type that shifts risk you can't absorb onto you, such as firm-fixed-price on work with unclear scope.

If you see two or more of these, your odds are probably long. Bidding anyway can still make sense, but make it a deliberate choice, not a default.

When to walk away, and how to do it well

Saying no is a skill. The strongest small contractors we know decline more opportunities than they pursue, and their win rates show it. When you walk away:

  • Decide early. A No-Go on day two costs nothing. A No-Go on day twelve wastes the ten days in between.
  • Stay visible. If the customer matters to you, respond to their next sources sought so they know you want future work.
  • Look for a subcontracting seat. A No-Go as a prime can be a Go as a sub to a firm that fits better.
  • Redirect the hours. Put the capacity you just freed onto the opportunity with the highest score.

Log every decision so you get better

The real payoff of a Go/No-Go framework shows up six months in. If you record the score, the reasoning, and the outcome for every decision, patterns appear. Maybe you win often when customer familiarity is 4 or higher and almost never when it's below 2. Maybe your price-to-win scores are consistently optimistic. That evidence is how you tune the weights.

After every award, win or lose, ask for a debrief. For competitive negotiated acquisitions under FAR Part 15, an offeror that requests a post-award debriefing in writing within three days after receiving notice of award is entitled to one under FAR 15.506. For other buys, ask anyway. Write down what the evaluators said and connect it back to your original scores. Over time your scorecard becomes a record of how your customers actually buy.

How Contract Command handles Go/No-Go

We built this framework into Contract Command because we needed it ourselves. Every opportunity in your pipeline has a Go/No-Go scorecard. CommandAI reads the solicitation and drafts a first pass on the criteria the document supports (set-aside, NAICS, timeline, value, evaluation method) with its reasoning shown; your team adjusts the scores and makes the call. Decisions stay with the opportunity, so Compass reviews your pipeline against your real history, and Tally can pressure-test a price-to-win number before you commit.

The takeaway

  • Write down your 12 criteria and weights this week, and keep them stable for a quarter.
  • Check knockouts first. Then score as a team, 0 to 5 per criterion.
  • Use thresholds set in advance: 70 and above is a Go, 50 to 69 is fix-or-fold, under 50 is a No-Go.
  • Decide early, walk away cleanly, and redirect the hours to your best opportunity.
  • Log every decision and every debrief, so your scorecard gets smarter every quarter.

Questions contractors ask

What is a bid/no-bid decision?

A bid/no-bid (or Go/No-Go) decision is a structured choice about whether to pursue a specific government solicitation, based on fit, competitiveness, capacity, and risk. Making it consistently keeps a small team focused on bids it can actually win.

What score should trigger a Go decision?

Many teams use a weighted score out of 100, with a Go at roughly 70 or above, a conditional zone from 50 to 69, and a No-Go below 50. The exact thresholds matter less than setting them in advance and applying them the same way every time.

Should a small business bid against a strong incumbent?

Sometimes. It can make sense when the requirements have changed, the incumbent has outgrown the size standard, or you have a real relationship with the customer. Without one of those, the odds are usually long and the hours are better spent elsewhere.

Your next award deserves a better system.

See your pipeline, your bids and your agents running from one command center. Live, with the founding team, on your workflow.

Start Standard or Plus online today, or apply to the War Room · See plans