A go/no-go decision framework is a scored evaluation system that helps government contractors decide whether to bid on an RFP before committing proposal resources. Score the opportunity against 5 criteria – capability match, relevant experience, agency relationships, incumbency, and team capacity – then set a minimum threshold. Below it, walk away.
Every proposal your team writes costs somewhere between 40 and 200 hours of effort.
For a small GovCon shop – where the same people doing BD are also managing contracts, handling client calls, and running the business – that is not a rounding error. That is weeks of capacity committed to a single opportunity.
And yet most small contractors make the Go/No-Go decision the same way: someone senior sees an RFP on SAM.gov, it looks like a fit, and the team starts writing.
No scoring. No criteria. No honest conversation about whether the opportunity is actually winnable. The result is predictable: teams that chase everything win nothing, burn out, and wonder why their proposal win rate sits at 15 percent.
A formal Go/No-Go process does not guarantee wins. What it does is protect your most valuable resource – team capacity – and concentrate your effort on the opportunities where you have a real competitive advantage.
This guide walks you through how to build one.
Why Small GovCon Teams Skip the Go/No-Go – and Why Does That Hurt Them?
Enterprise BD departments have formal stage-gate processes. Color team reviews, capture plans, Pwin assessments – the whole machinery. The decision to bid is made weeks before the RFP drops, based on months of pre-positioning.
Small teams do not have that infrastructure. When an RFP hits the street, the instinct is to react: assess quickly, decide fast, start writing. Slowing down to run a formal evaluation feels like overhead they cannot afford.
This is the wrong trade-off.
The cost of a bad Go decision is not just the hours spent on the proposal. It is the opportunity cost – the other bids you did not pursue, the contract work that slipped, the team morale that erodes when you go 0- for-4 in a quarter because you spread effort across unwinnable opportunities.
A lightweight, consistent Go/No-Go process – one that takes 30 minutes to run, not 3 days – pays back that time many times over.
What Is a Go/No-Go Decision Framework – and What It Isn’t?
A Go/No-Go is not a prediction of whether you will win. It is a structured answer to a simpler question: Is this worth our effort given what we know right now?
You are assessing competitive position, not guaranteed outcomes. A strong Go means you have a legitimate shot. A No-Go means you are likely writing a proposal that will train the competition.
Done well, a Go/No-Go process does three things:
- Forces explicit criteria – instead of gut feel, you are evaluating on the same factors every time
- Creates accountability – the decision is documented, so you can review it post-award and learn
- Protects bandwidth – No-Go decisions are not failures; they are capacity returned to winnable work
A formal Go/No-Go process does not guarantee wins. What it does is protect your most valuable resource – team capacity
What is the MERIT Framework for Bid/No-Bid Decisions?
Across five criteria, the strongest Go/No-Go models ask versions of the same questions: Do we fit the requirement? Can we win the competition? Can we afford to play?
The MERIT framework organizes those questions into categories that small GovCon teams can evaluate consistently in under an hour.
M – Match
E – Experience on the Evaluator’s Terms
R – Relationships
I – Incumbency
T – Team and Capacity
Score each category 1-3. A total of 12 or higher is a strong Go. 8-11 warrants a conditional Go with a
defined risk. Below 8 is a No-Go.
M – Match: Does Our Capability Align With the Requirement?
This is the most basic filter, and the one most often glossed over.
Match is not “could we do this work if we had to.” Match is “do we have directly relevant, documentable experience that an evaluator reading our technical volume will score highly?”
Score 3: You have two or more past performance examples that map directly to the scope, size, and complexity of this requirement. You can point to specific contracts with similar deliverables, similar agency types, and comparable dollar values.
Score 2: You have adjacent experience. The work is in the same domain but not an exact mirror – different agency type, different scale, or the match is strong on one area of the scope but thin on another.
Score 1: Your capability is plausible but not evidenced. You believe your team can do the work, but you cannot point to past performance that proves it to an evaluator.
Red flag: If you are scoring 1 on Match, the proposal will be evaluated on potential rather than performance. Against incumbents or competitors with direct experience, potential rarely wins.E – Experience on the Evaluator’s Terms
Technical capability and competitive relevance are different things. Having done similar work is not the same as being positioned to win this competition. This criterion asks a more precise question: Given how this specific solicitation will be evaluated, how does our experience score against the likely competition?
Every RFP tells you how the award decision will be made. The evaluation factors section spells out what the government cares about most – typically a combination of technical approach, past performance, management plan, and price – and assigns each a relative weight or order of importance. Before you score yourself on E, read that section carefully.
If past performance is the most heavily weighted factor and you have three directly relevant contracts, your E score is strong. If technical approach is weighted highest and your approach relies on a methodology your competitors pioneered, your E score is weak – regardless of how good your actual delivery has been.
This distinction matters because small teams often conflate “we’re capable” with “we’re competitive.” You may be fully capable of doing the work. But if your capability does not translate into a high score on the criteria that drive the award decision, capability does not help you.
Score 3: Your experience maps directly to the stated evaluation criteria. You can construct a technical narrative or past performance submission that demonstrates specific, quantified outcomes on closely similar work. The evaluator is likely to score you high on the dimensions that carry the most weight in this solicitation.
Score 2: You are competitive on most evaluation criteria but have a visible gap on at least one weighted
factor. You can address the gap through teaming, creative framing, or a strong technical approach – but it
will require deliberate effort and honest self-assessment before writing begins.
Score 1: Your experience is genuine but does not translate well to the evaluation structure. The factors that
favor you are weighted low. The factors weighted highest play to your competitors’ strengths. You will
spend most of the proposal writing around your weaknesses rather than leading with your strengths.
R – Relationships: Do We Have a Footprint at This Agency?
In federal contracting, relationships do not decide awards – but they inform them. An incumbent who has been briefing the Contracting Officer for 24 months has intelligence your team does not have. A bidder who has never interacted with the agency is writing blind.
Relationships in this context means: pre-solicitation engagement, industry day attendance, prior contracts with the agency, a warm contact in the program office, or teaming with someone who has that footprint.
Score 3: Your team (or a teaming partner) has an existing relationship with this agency – prior contract, industry day engagement, or a contact who can provide legitimate market intelligence. You understand the program’s priorities beyond what is written in the RFP.
Score 2: You have limited but not zero footprint. You may have done work in an adjacent office or with a related agency. You are not bidding completely cold.
Score 1: You have no prior engagement with this agency and no teaming partner who does. You are relying entirely on the RFP document to understand the requirement.
Note: A Score 1 on Relationships is not automatically disqualifying - especially for set-aside competitions where the field is narrow. But it should raise the bar for your score on other criteria.I – Incumbency: Who Are We Really Competing Against?
Incumbents win federal recompetes at rates between 70 and 85 percent, depending on the study and the agency. That is not a reason to never compete against an incumbent – but it is a reason to know what you are walking into.
Score 3: There is no strong incumbent, or the incumbent has demonstrable performance issues (protest history, CPARS concerns, poor agency relationship). This is an open competition where past performance quality will differentiate.
Score 2: There is a known incumbent with a reasonable performance record, but the competition is genuinely open. The agency has signaled interest in alternatives, the set-aside status creates an opportunity, or your competitive position is strong enough to overcome the incumbency advantage.
Score 1: A well-performing incumbent is deeply embedded. The agency has not signaled dissatisfaction. The RFP structure strongly favors the incumbent’s experience profile. You are competing for second place and a protest posture, not a win.
T – Team and Capacity: Can We Write a Competitive Proposal?
This is the criterion most teams skip entirely — and the one that kills the most proposals quietly.
A Go/No-Go is not just about competitive position. It is about whether your team can execute a proposal that reflects your actual capability. An underfunded proposal effort that produces a thin technical volume does not just lose – it leaves an impression on the evaluators you will face again.
Score 3: You have the capacity to staff this proposal properly. The subject matter experts are available, the proposal manager’s schedule is clear, and the timeline is workable. If teaming is required, the agreements are in place or can be executed quickly.
Score 2: Capacity is tight but manageable with prioritization. You will need to defer other work or bring in support, but you can produce a competitive proposal without compromising quality.
Score 1: Your team is already at capacity. This proposal would require pulling resources from active contract work, rushing sections, or submitting without a proper review cycle. The proposal would not represent your best work.
How Do You Score an Opportunity and Make the Final Call?
Run MERIT on every opportunity before you commit resources. Here is the scoring guide:
| Score | Action |
| 12-15 | Go – strong competitive position, commit full resources |
| 8-11 | Conditional Go – document the risks and what would need to be true to win |
| 5-7 | No-Go – unless circumstances change materially before the RFP drops |
| Below 5 | Hard No-Go – do not start writing |
For Conditional Go decisions, write down the specific condition that would change the assessment. “We go if we can secure a teaming partner with direct DHS experience by Friday.” A condition without a deadline is not a condition – it is wishful thinking.
What Are Automatic No-Go Triggers for RFP Opportunities?
Some situations override MERIT scoring entirely. If any of the following are true, do not write the proposal:
- Scope surprise: The RFP released with a materially different scope than expected, and you have not worked in that area
- Incumbent protest shield: The procurement has been protested previously and reinstated with no scope changes — this often signals a wired award
- Price ceiling problem: The Independent Government Cost Estimate (IGCE) – the government’s internal estimate of what the contract should cost – or a previous award ceiling is below your realistic cost to perform the work
- Teaming failure: You need a specific partner to be competitive and they are unavailable or have already committed to a competitor
- Compliance gap: The RFP requires a certification, clearance, or registration status your team does not currently hold
These are not scored – they are stops. Document the reason and move on.
What are the Three Most Common Go/No-Go Mistakes Small Teams Make?
- Treating it as a formality after the decision is already made. If your senior leader has already told the team “we’re bidding this,” running MERIT scoring serves no purpose. The Go/No-Go works only if there is genuine willingness to say No. Build that culture before you build the scoring sheet.
- Scoring against your best-case assumptions. MERIT scoring is only as honest as the people filling it out. Teams consistently score Incumbency too high (“we’ll overcome it with a superior technical approach”) and Relationships too low (“we know someone who knows someone”). Score against your realistic position, not your optimistic one.
- Skipping the post-award review. After every award decision – win or loss – pull your Go/No-Go score and compare it against the outcome. Over time, this gives you calibration data: which criteria were you systematically over- or under-weighting? Which opportunities that scored borderline did you win? This is how a scoring framework improves.
What Should Your Team Do After Making a Go Decision?
A Go decision is a commitment, not a hope. Once MERIT clears the threshold, the proposal effort should be treated with the same seriousness as a client deliverable.
That means:
- Assigning a proposal manager (even if it is the same person as the BD lead)
- Building a compliance matrix within the first 48 hours of RFP release
- Scheduling review milestones before the deadline, not after the writing is done
- Protecting the SMEs’ time so they are not pulled back into delivery work mid-proposal
The Go/No-Go framework does not write the proposal for you. But it makes sure that when you sit down to write, you are doing it for an opportunity worth your team’s time.
How Do You Get Started with Go/No-Go When Your Team Has Never Done It?
If you have no Go/No-Go process right now, do not try to implement the full framework on your first attempt. Start with one rule:
Before anyone on the team writes a single word, document why you are pursuing this opportunity and who you are competing against.
That single step – a five-minute conversation turned into two written sentences – will surface more No-Go decisions than any scoring matrix. It forces the question most teams skip: Why are we confident we can win this one?
The full MERIT framework builds from there.The teams that win consistently in GovCon are not the ones who bid the most.
They are the ones who bid smart – who know which competitions favor them, protect their capacity for the work worth chasing, and walk away cleanly from the ones that do not. A Go/No-Go framework is how you build that discipline before
the next RFP drops.
Written by Tom B. “We build AI-powered RFP response software”.
Leave a Reply