Go/no-go decision guide: bid/no-bid criteria and a free scorecard
Short answer: A go/no-go (or bid/no-bid) decision is the point where a team decides whether an RFP is worth responding to, before anyone writes. Make it in two passes: first a handful of knockout questions (can we legally and practically bid at all?), then a weighted scorecard covering relationship, requirements fit, competitive position, value, resources and proof. Score each criterion 0–3, weight it, and set thresholds in advance, for example 70+ = Go, 50–69 = Review, under 50 = No-go. Record the decision and the reason either way.
Who this is for: proposal managers, bid managers, sales leaders and capture managers deciding which RFPs to pursue.
On this page
- What is a go/no-go decision?
- When should you make the bid/no-bid decision?
- What are the knockout questions?
- The bid/no-bid scorecard: criteria, weights and scoring
- Worked example
- How do you run a go/no-go meeting?
- Free go/no-go scorecard template
- How Iris helps
- FAQ
What is a go/no-go decision?
A go/no-go decision is a structured yes-or-no call on whether to pursue an opportunity. In RFP work it's the same thing as a bid/no-bid decision; government contractors sometimes call it a bid decision or, earlier in the cycle, a pursuit decision as part of capture management.
The point isn't to avoid work. It's to put your best people on bids you can win. Every response you write for a deal you were never going to win takes subject-matter-expert time away from one you could have.
When should you make the bid/no-bid decision?
Make it at least twice:
| Gate | When | Question |
|---|---|---|
| Pursuit (if you can) | Before the RFP is released, when you first hear of the opportunity | Is this worth investing sales and capture effort in? |
| Bid / no-bid | Within the first days after the RFP arrives, once you've read it fully | Should we write a response? |
| Final check (optional) | After clarification answers or addenda arrive | Has anything changed that turns a Go into a No-go? |
The biggest mistake is deciding by default: the RFP arrives, someone starts writing, and the decision is never actually taken.
What are the knockout questions?
Answer these first. A single "no" is normally a No-go, however good the rest of the opportunity looks.
- [ ] Mandatory requirements: Can we meet every requirement marked "must", "shall" or "mandatory", or propose an acceptable alternative where the RFP allows one?
- [ ] Eligibility: Do we hold the certifications, licences, insurance, registrations or set-aside status the RFP requires?
- [ ] Deadline: Can we produce a compliant, quality response by the due date with the people available?
- [ ] Terms: Are the contract terms (liability, indemnity, data location, IP) ones we can accept or credibly negotiate?
- [ ] Delivery: If we win, can we actually deliver in the timeframe and geography required?
The bid/no-bid scorecard: criteria, weights and scoring
After the knockouts, score each criterion 0, 1, 2 or 3 using the anchors below. Multiply by the weight, add up, and divide by 3 to get a score out of 100. The weights are a starting point. Adjust them once to fit your business, then keep them fixed so decisions are comparable.
| # | Criterion | Weight | 0 | 1 | 2 | 3 |
|---|---|---|---|---|---|---|
| 1 | Relationship and pre-RFP engagement | 15 | First contact is the RFP | We know a contact but haven't discussed this need | We've discussed the need with the buyer | We helped shape the requirements, or we're a trusted incumbent |
| 2 | Requirements fit | 20 | Many gaps | Most met; several material gaps | Nearly all met; minor gaps with workarounds | All met, with evidence |
| 3 | Competitive position | 15 | Wired for a competitor, or a strong incumbent we're displacing cold | Strong competitors and no clear edge | Competitive, with a clear differentiator | We're the incumbent or the clear favourite |
| 4 | Strategic value | 10 | No strategic value | Minor | Opens a target segment, region or use case | Flagship account or reference |
| 5 | Deal value and margin | 10 | Doesn't cover the cost of bidding | Thin | Healthy | Large, with good margin |
| 6 | Resource availability | 10 | Key SMEs unavailable | Stretched; would delay other work | Available with some juggling | Fully staffed |
| 7 | Evaluation criteria fit | 10 | Lowest price wins and we're not the low-cost option | Price-heavy weighting | Balanced price and quality | Weighted toward our strengths |
| 8 | Proof available | 10 | No relevant references or past performance | Loosely related proof | Relevant proof for most areas | Directly comparable references with permission |
| Total | 100 |
Formula: score = Σ (weight × rating) ÷ 3. A perfect scorecard is 300 ÷ 3 = 100.
Suggested thresholds (set your own before you score anything):
| Score | Recommendation | What it means |
|---|---|---|
| 70–100 | Go | Bid, and staff it properly |
| 50–69 | Review | Bid only if a specific risk can be fixed (a call with the buyer, a partner, an SME freed up); name the fix and the owner |
| 0–49 | No-go | Decline. Consider a courteous no-bid letter that keeps the relationship |
Red flags worth naming explicitly
These don't always change the score, but they should be said out loud in the meeting:
- Requirements that match one vendor's product features or terminology, suggesting the RFP was written around a competitor.
- A very short response window with no prior contact.
- Evaluation weighted almost entirely to price for a product you sell on value.
- Questions you'd answer "no" to that the buyer flags as critical.
- Unusual contract terms (uncapped liability, unrestricted IP assignment).
Worked example
A fictional mid-size software company receives an RFP from a regional bank it has never spoken to. Knockouts all pass. The scorecard:
| # | Criterion | Weight | Rating | Weighted |
|---|---|---|---|---|
| 1 | Relationship | 15 | 1 (one contact, need not discussed) | 15 |
| 2 | Requirements fit | 20 | 3 (all met, evidenced) | 60 |
| 3 | Competitive position | 15 | 1 (strong incumbent, no clear edge yet) | 15 |
| 4 | Strategic value | 10 | 2 (opens banking segment) | 20 |
| 5 | Deal value | 10 | 2 | 20 |
| 6 | Resources | 10 | 2 | 20 |
| 7 | Evaluation criteria fit | 10 | 2 (balanced) | 20 |
| 8 | Proof | 10 | 3 (two comparable references) | 30 |
| Total | 100 | 200 ÷ 3 = 67 |
Result: Review. The weak spots are relationship and competitive position. The team agrees to bid only if the account executive gets a clarification call with the buyer before the questions deadline and can articulate one differentiator against the incumbent. Owner: the AE. Decision date: the day after the questions deadline. If either fails, it's a No-go.
That's the value of the Review band: it turns a vague "maybe" into a specific condition with an owner.
How do you run a go/no-go meeting?
- Prepare a one-page brief before the meeting: buyer, scope, value, deadline, mandatory requirements, evaluation criteria and weights, known competitors.
- Invite a small group: the sales owner, the proposal lead, one delivery or solutions lead, and someone who can say no (a sales leader or bid director).
- Run the knockouts first. If one fails, stop.
- Score independently, then compare. Have each person score before discussing; big disagreements are where the useful conversation is.
- Decide against the thresholds you set in advance. Don't move them for a deal someone loves.
- Record the decision, score and reason. Over time this becomes your best data on which bids you win.
- If it's a Go, start the response immediately: build the compliance matrix, assign owners and set internal deadlines.
Free go/no-go scorecard template
Copy the table below into a spreadsheet.
GO / NO-GO SCORECARD
Opportunity: [buyer, RFP number, title] Due date: [date]
Value: [estimate] Sales owner: [name] Decision date: [date]
KNOCKOUTS (any "No" = No-go) Yes / No
1. Can meet every mandatory requirement (or allowed alternative) [ ]
2. Eligible (certifications, licences, insurance, registrations) [ ]
3. Can submit a quality response by the deadline [ ]
4. Contract terms acceptable or negotiable [ ]
5. Can deliver in the required timeframe and geography [ ]
SCORECARD (rate 0-3) Weight Rating Weighted (= W x R)
1. Relationship / pre-RFP 15 [ ] [ ]
2. Requirements fit 20 [ ] [ ]
3. Competitive position 15 [ ] [ ]
4. Strategic value 10 [ ] [ ]
5. Deal value and margin 10 [ ] [ ]
6. Resource availability 10 [ ] [ ]
7. Evaluation criteria fit 10 [ ] [ ]
8. Proof available 10 [ ] [ ]
TOTAL 100 [sum] / 3 = [score]
THRESHOLDS: 70-100 Go · 50-69 Review · 0-49 No-go
RED FLAGS NOTED: [ ]
DECISION: [Go / Review / No-go]
CONDITIONS (if Review): [what must change] · Owner: [name] · By: [date]
REASON (one sentence): [ ]
Approved by: [name, title]
How Iris helps
Iris's RFP Analyzer is built for this decision. Know if a bid is worth it before you write a word:
- Upload the RFP (PDF, Word or Excel). Iris returns a summary, key dates, contacts, scoring criteria and requirements, each cited to the source document.
- It checks each requirement against your own Knowledge Map and marks it met, partial or likely not met, with the sources it used, which is the evidence behind criterion 2 above.
- It scores your own go/no-go criteria (red and green flags, with weights) into a qualification percentage and a Go, Review or No-Go recommendation.
- Your team can comment on the analysis, and "Start Response" turns a Go into a response project.
Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered.
FAQ
What is the difference between go/no-go and bid/no-bid?
In RFP work they mean the same thing: a decision on whether to respond. Some teams use "go/no-go" for the earlier pursuit decision and "bid/no-bid" for the decision once the RFP is in hand.
What criteria should a go/no-go decision use?
Start with knockouts (mandatory requirements, eligibility, deadline, terms, delivery). Then score relationship, requirements fit, competitive position, strategic value, deal value, resources, evaluation-criteria fit and proof. The scorecard above weights them.
What score should trigger a "go"?
Set it before you score. A common pattern is 70+ Go, 50–69 Review with conditions, under 50 No-go. Review your thresholds every few months against which bids you actually won.
Should we ever bid on an RFP we weren't expecting?
Sometimes, if requirements fit and proof are strong. But an unexpected RFP is a warning sign: someone else may have helped write it. Treat it as a Review and try to talk to the buyer before deciding.
How do we say no to an RFP politely?
Send a short no-bid letter to the named contact: thank them, decline, give a brief honest reason if appropriate, and say you'd welcome future opportunities. It keeps you on the list.
Who should make the final go/no-go call?
One accountable person, usually a sales leader or bid director, after the group has scored. Group scoring, single owner.
See it live
Respond to RFPs
without the grind.
Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.
