GovCon Strategy|May 4, 2026|13 min read

A Go/No-Go Scoring Framework That Cuts Wasted Proposal Effort

A quantitative go/no-go scoring model with weighted criteria, hard gates, and kill dates that separates winnable contracts from resource drains.

Projectory team

Picture a proposal team that just spent 14 weeks and $87,000 on an agency modernization bid (an illustrative scenario). The solution was strong. The writing was sharp. The technical rating was good. And the team lost to an incumbent that had been embedded in that program office for nine years.

That loss was predictable. Not in hindsight, but before you ever opened a blank page. The signals were there: no pre-RFP contact with the contracting officer, no insight into the incumbent's performance issues (or lack thereof), and a vague "we've done similar work" answer on the customer relationship question during your internal gate review. A scored go/no-go framework would have flagged this pursuit as a likely loss before you burned a single billable hour.

A quantitative scoring model, properly weighted and honestly applied, turns that gut feel into a decision you can defend and audit. The goal is to win more by bidding less. This article gives you a framework, starting weights, hard gates, and an implementation playbook you can begin using this quarter, then calibrate against your own results.

A Low Win Rate Is a Strategy Problem, Not a Volume Problem

Look at your own win rate for competed proposals. Every loss is labor, SME time pulled from billable work, reviews, and late nights that produce zero revenue.

Many BD leaders respond to low win rates by increasing volume. The logic feels intuitive: if we win 1 in 5, we need to bid 50 to win 10. But this math ignores a critical variable. Not all opportunities carry equal probability of winning, and a stretched team gives the truly winnable bids the same diluted attention as the long shots.

The real fix is subtraction: stop bidding on contracts you are unlikely to win, and put the saved effort into the ones you can. The framework below makes those no-go calls defensible and repeatable.

The 12-Factor Scoring Model

The framework evaluates every opportunity across four categories, each containing three scored factors. Every factor is rated 1 through 5 using defined anchors (not gut feel), then multiplied by a weight of 1x, 1.5x, or 2x based on how strongly you expect it to drive the outcome.

The Four Categories

Customer Access covers your relationship with the buying organization, your understanding of the agency's priorities, and whether you have had pre-RFP engagement. These three factors carry the highest combined weight.

Solution Fit evaluates how closely your existing capabilities match the stated requirements, whether you can articulate verifiable proof points, and how your technical approach compares to what the agency actually needs (which is often different from what the solicitation says).

Competitive Position scores incumbency status, known competitors and their strengths, and pricing position relative to the market. If you are bidding against an entrenched incumbent with no intelligence on their weaknesses, your score here will be low, and it should be.

Execution Readiness measures your team's availability to write the proposal, your access to the required contract vehicle (OASIS+, GSA Schedule, agency-specific IDIQ), and compliance prerequisites like security clearances and certifications. With the FAR overhaul shifting toward commercial-first acquisition approaches, Solution Fit scoring now needs to account for whether your offering aligns with commercial buying preferences, not just traditional government specs.

Score Bands

Convert the weighted total to a 100-point scale. These starting bands are a recommendation; adjust them once you have scored enough of your own pursuits to see where wins and losses actually fall.

Score BandClassificationWhat It MeansRecommended Action
70-100GoAccess, fit, and position all support a winFull proposal investment, assign A-team
55-69Conditional GoWinnable only if specific gaps closeMust improve 2-3 factors before RFP drop or kill
40-54No-GoToo many gaps to close in timeDo not bid unless strategic override approved in writing
Below 40Hard NoLittle basis for a winNo exceptions, no overrides

Why Customer Relationship Deserves 2x Weight (and Past Performance Usually Doesn't)

The starting weights put customer relationship and incumbency above past performance relevance. The reason is straightforward. Past performance matters for clearing the compliance bar. Evaluators check that you have relevant experience, that your CPARS ratings are acceptable, and that you have not been flagged for performance issues. But in a competitive field of four or five bidders, three or four of them clear that bar. Past performance becomes table stakes, not a differentiator.

Customer relationship, on the other hand, directly affects evaluation in ways that are harder to replicate. The team that has been meeting with the program office quarterly, that understands the unwritten pain points, that has shaped the requirements through RFI responses and industry day participation, that team writes a proposal the evaluators recognize. They are not guessing at what the agency wants. They know.

Here is an illustrative comparison. On an IT modernization contract, Company A has stronger past performance (three directly relevant contracts of similar size and scope). Company B has weaker past performance but has engaged with the program office for over a year before the RFP, attended both industry days, and submitted detailed RFI responses that shaped the final SOW language. Company B's proposal is far more likely to read as a clear understanding of agency priorities and operational constraints. That understanding does not come from a past performance volume. It comes from relationship.

Pre-RFP engagement can be logged, which makes customer access measurable. You can now score relationship quality based on specific, trackable interactions: meetings attended, RFI responses submitted, and contacts identified within the program office. This turns a squishy "gut feel" factor into something defensible.

Hard Gates vs. Scored Criteria: The Fields That Should Kill a Bid Instantly

Not every factor belongs on a 1 to 5 scale. Some are binary: you either meet the requirement or you do not, and no amount of strong writing can compensate for the gap.

CMMC status is the clearest example in 2026. When a DoD solicitation includes the CMMC notice provision, an offeror is not eligible for award without the current CMMC status entered in SPRS at the required level and a current affirmation of continuous compliance [1]. Bidding without the required status, or one you can achieve before award, is burning money. Since the Department of War suspended CMMC Phase 2 on July 13, 2026, the required level is generally a self-assessment status, with Phase 1 self-assessments, SPRS postings, and annual affirmations still in effect [4][5]. Read the solicitation for the level it actually requires. This is not a scored criterion. It is a hard gate. If you cannot demonstrate the required status, the answer is no-go.

The stakes go beyond losing a bid. The False Claims Act reaches anyone who knowingly makes or uses a false record or statement material to a false or fraudulent claim [2], and an inaccurate cybersecurity affirmation can become exactly that. If you represent compliance you do not have, you are not just risking a loss. Honest self-assessment on CMMC status is a legal necessity.

Other hard gates in the current environment:

  • Security clearance gaps: If the SOW requires TS/SCI and your proposed key personnel lack active clearances, no go. Clearance processing rarely fits inside a proposal schedule.
  • Set-aside ineligibility: Bidding on a small business set-aside as a large business (or without the correct socioeconomic certification) is a compliance violation, not a competitive disadvantage.
  • Contract vehicle access: You cannot bid an OASIS+ task order without an OASIS+ contract. If your migration strategy from legacy OASIS is incomplete, this is a gate, not a factor.
  • GSA schedule reporting: TDR is mandatory for all Multiple Award Schedule SINs, with transactional data due within 30 days after the end of each month [3]. If open reporting problems put your schedule's standing in question, resolve them with your contracting officer before you bid a GSA-vehicle opportunity.

Run hard gates before you run the scoring model. There is no point scoring 12 factors if a hard gate eliminates the opportunity in seconds.

Running the Score: A $15M OASIS+ Task Order Walkthrough

Here is an illustrative scoring exercise on an OASIS+ task order for enterprise cloud migration at a mid-sized civilian agency.

The Opportunity

The task order calls for migrating 14 legacy applications to a FedRAMP-authorized cloud environment over 24 months, with a ceiling of $15.2M. The agency published a draft SOW 60 days before the anticipated RFP drop.

The Score

Customer Access (Weight: 2x, 1.5x, 1.5x)

  • Agency relationship quality: 3/5 (attended one industry day, no direct CO contact) = 6
  • Understanding of agency priorities: 2/5 (limited insight beyond public documents) = 3
  • Pre-RFP engagement level: 2/5 (submitted RFI response but no follow-up dialogue) = 3

Solution Fit (Weight: 1.5x, 1.5x, 1x)

  • Technical capability match: 4/5 (strong cloud migration practice, 3 similar projects) = 6
  • Proof point density: 3/5 (can articulate 4 verifiable proof points, need 5+) = 4.5
  • Commercial alignment: 3/5 (solution uses commercial cloud tools, moderate fit with FAR reform direction) = 3

Competitive Position (Weight: 2x, 1.5x, 1x)

  • Incumbency/competitive intel: 2/5 (not incumbent, limited intel on competitors) = 4
  • Pricing position: 3/5 (competitive but not advantaged on rates) = 4.5
  • Differentiation clarity: 3/5 (one clear differentiator, need two or three) = 3

Execution Readiness (Weight: 1x, 1x, 1x)

  • Proposal team availability: 4/5 (team available, no competing deadlines) = 4
  • Vehicle access: 5/5 (hold OASIS+ in correct pool) = 5
  • Compliance prerequisites: 5/5 (clearances, certifications all current) = 5

Total: 51 of a possible 82.5 weighted points, or 62 on the 100-point scale. Conditional Go.

The Conditional Go Process

A score of 62 is not a green light. It is a yellow light with a timer. The capture manager must identify the two or three factors that can realistically improve before RFP release and assign owners with deadlines.

In this case: (1) Schedule a meeting with the program office within 15 business days to improve Customer Access. (2) Develop two additional proof points with quantified outcomes to bring Proof Point Density to 4/5. (3) Conduct a competitive black hat session to improve Incumbency/Competitive Intel.

If these actions have not produced results 10 days before expected RFP drop, the pursuit converts to a no-go. This is the kill date. Without it, conditional go becomes "we will figure it out later," which is just go with extra steps.

The Kill Date Is Non-Negotiable

Every conditional go must have a written kill date, typically 7 to 14 days before expected RFP release. If the conditions have not been met by that date, the pursuit dies automatically. No meeting required. No re-vote. Without a kill date, a conditional go quietly becomes a go. The kill date is what separates disciplined conditionality from wishful thinking.

How AI-Evaluated Proposals Change What "Solution Fit" Means in Your Score

Agencies are expanding their use of AI, and some evaluation teams may use AI tools to help review proposals. Whether a human or a tool reads first, the same writing serves both: a specific feature, a beneficial outcome, and a verifiable proof point in each strength statement. "Our team has extensive experience in cloud migration" gives a reader nothing to verify. "Our engineers migrated [number] applications to AWS GovCloud for [Agency X], reducing hosting costs by [measured percentage]" (with your real figures) does.

This changes how you should score Solution Fit in your go/no-go framework. The old question was "Can we do this work?" The new question is "Can we prove we can do this work in plain, verifiable language?" A Solution Fit score below 3 out of 5 is a warning sign either way.

Consider adding a sub-criterion to the Solution Fit category: "Can we articulate 5 or more verifiable proof points for the core requirements?" Score it 1 through 5. If the answer is 1 or 2, that is a powerful signal. You may technically be able to perform the work, but you cannot prove it in the format evaluators (human or AI) now expect. That gap is often the difference between a 62-point conditional go and a 55-point no-go.

The Politics of Saying No: Getting Leadership to Trust the Score

The framework is the easy part. The hard part is the first time your VP of Business Development stares at a $40M opportunity that scored a 48, and says "We are bidding this anyway."

This happens. The emotional pull of a large dollar value, a familiar customer, or a board presentation that needs pipeline numbers is strong enough to override any spreadsheet. You will not win the argument with logic in the moment. You win it over time with data.

Three tactics that work:

  1. Track hypothetical outcomes quarterly. Every no-go decision gets logged. At the end of each quarter, check the award results. When leadership sees that most no-go opportunities went to competitors who were clearly advantaged, the pattern builds credibility.
  1. Show cost-per-proposal-dollar-won improving. This is the metric that translates proposal discipline into language executives understand. As an illustration, if you spent $1.2M on proposals last year and won $18M in contracts, your cost per dollar won is $0.067. If a year later you spend $780K and win $22M, it drops to $0.035. That is a story the CFO tells at board meetings.
  1. Require written override justification. Anyone can overrule the score, but they must document why in writing, with their name attached. Track how overridden bids perform against framework-approved bids, and print your own numbers on the override form. People think twice when the record is in front of them.

Start building this habit with contracts under $5M where the emotional stakes are lower. Once the framework proves itself on smaller pursuits over two or three quarters, extending it to large opportunities becomes a conversation about evidence, not about trust.

Implementing the Framework This Quarter Without a Six-Month Process Overhaul

You do not need a transformation initiative to start making better bid decisions. You need a spreadsheet, a 30-minute meeting slot, and the willingness to say no.

Phase 1: First 90 days. Start with a simplified 8-factor version that covers the two highest-weighted factors from each category. This reduces scoring time to 15 minutes per opportunity and gets your team comfortable with the mechanics. Use forced rankings (you must assign a score, you cannot leave blanks) and require one sentence of evidence per factor. "Strong relationship" is not evidence. "Met with PM Garcia twice in Q1, attended industry day, referenced our RFI input in the draft SOW" is evidence.

Phase 2: Days 91 through 180. Expand to the full 12 factors. More importantly, calibrate the weights to your own data. The 2x weight on customer relationship is a starting assumption, and your company may find that pricing position or vehicle access is a stronger predictor in your specific market segment. Review your last 20 to 30 pursuits and adjust weights based on which factors most reliably separated wins from losses.

Phase 3: Ongoing. Schedule a 30-minute go/no-go review for every opportunity above $2M before any proposal work begins. Not after the RFP drops. Before. The capture manager presents the score, the evidence, and the recommendation. The room votes. The decision is logged.

Track three metrics starting this week:

  • Bid volume: Total number of proposals submitted per quarter
  • Win rate: Awards divided by submissions
  • Cost per proposal dollar won: Total proposal costs divided by total awarded contract value

Go back to the illustrative $87,000 modernization bid at the top. A 15-minute scoring exercise would have flagged the customer access deficit and the incumbency disadvantage before a single writer opened a template. That is not hindsight. That is a framework. Build it, enforce it, and track what happens over the next two quarters. The numbers will make the case for you.

References

Related articles