A practical bid/no-bid process for testing hard gates, delivery capacity, buyer fit, economics, and conditions before committing proposal resources.
A useful go/no-go decision framework for government contracts starts with the current solicitation and your organization's real constraints. Test confirmed hard gates first. Then review delivery capacity, buyer fit, proof, commercial terms, and proposal workload. Choose GO, No Go, or Go With Conditions, record why, name the person who owns each condition, and set a date to revisit the call. Do not let a generic score or an invented win probability make the decision for you.
Research reviewed August 13, 2026. This is an operating framework, not legal advice or an award prediction. The current solicitation, addenda, buyer portal, and your approved company rules remain controlling.
| Decision | Use it when | Record before moving on |
|---|---|---|
| GO | No confirmed disqualifier is known, the team can support the response and performance plan, and the remaining uncertainty is acceptable | Decision owner, evidence reviewed, resource commitment, and next checkpoint |
| Go With Conditions | The opportunity may deserve pursuit, but a specific fact, approval, teammate commitment, or mitigation must be resolved | Each condition, owner, due date, evidence needed, and automatic stop point |
| No Go | A confirmed eligibility, deadline, capacity, commercial, or company-rule conflict makes pursuit unacceptable | The controlling fact, who confirmed it, and whether any future change could reopen the decision |
These labels are a management tool, not a buyer rating. Federal agencies evaluate proposals against the factors and subfactors stated in the solicitation, and those factors can use different rating methods. Your internal scorecard should therefore help allocate seller resources; it should not imitate an undisclosed buyer score or claim to calculate a win probability. (FAR 15.305)
Collect the base solicitation, scope, attachments, forms, pricing files, sample contract, official questions and answers, and every current addendum. Record the source and version of each file. If a material buyer file is missing, locked, or unreadable, the correct status is usually Needs review, not a clean GO.
This discipline applies beyond federal work. Oregon's official competitive-proposal guidance treats the RFP document as the RFP plus attachments, the sample contract, exhibits, addenda, and supplemental information posted through the official system. It also describes minimum proposer, submission, evaluation, and responsibility requirements as distinct parts of the procurement. (Oregon Department of Administrative Services)
If the opportunity came from a search or market-intelligence platform, keep the official notice URL and current files with the handoff. Discovery evidence helps you find the work; the buyer's current documents control the decision. See the distinction in our guide to government contract search platforms versus bid-readiness software.
A hard gate is a confirmed fact that your organization has decided makes pursuit unacceptable. It should be narrow, documented, and tied to the actual opportunity. Common categories include:
The Federal Acquisition Regulation's general responsibility standards provide a useful reality check. They address financial resources, schedule capacity in light of existing commitments, performance and integrity records, organization and technical skills, equipment and facilities, and legal eligibility. These are government responsibility standards, not a universal seller scorecard, but they show why qualification must cover ability to perform—not just the attractiveness of the opportunity. (FAR 9.104-1)
Do not convert an inference into a disqualifier. “The document may require a license we have not confirmed” is a condition to investigate. “The solicitation requires the license, our approved company rule treats it as mandatory, and the accountable owner confirmed we cannot obtain it in time” is a documented stop.
After hard gates, review the opportunity using questions that produce evidence rather than a decorative score.
| Decision area | Questions to answer | Useful evidence |
|---|---|---|
| Buyer and requirement fit | Do we understand the buyer's problem, scope, constraints, and evaluation model? | Official notice, solicitation sections, Q&A, site-visit notes, evaluation factors |
| Ability to perform | Can the prime and named subcontractors deliver the work on schedule and under the proposed terms? | Staffing plan, capacity commitments, licenses, facilities, delivery plan |
| Proof and positioning | Can we support the required claims with relevant evidence? | Past-performance records, references, resumes, work samples, technical approach |
| Commercial fit | Are pricing, cash flow, risk allocation, insurance, bonding, and contract terms acceptable? | Estimate, terms review, approval record, risk and assumption log |
| Response readiness | Can the team produce the required package without damaging higher-priority work? | Proposal calendar, owner map, requirement inventory, review and submission plan |
For federal negotiated procurements, evaluation is based on the solicitation's stated factors and subfactors. FAR 15.305 separately addresses cost or price, past performance, technical evaluation, and other solicitation-defined considerations. The practical implication is simple: qualify against what this buyer says it will evaluate, not a standard list copied from the last pursuit. (FAR 15.305)
Use three columns in the decision record:
This separation prevents a confident narrative from hiding a missing decision fact. A useful condition is testable: “The proposed electrical subcontractor must confirm bonding capacity by 3:00 p.m. Friday; otherwise the pursuit becomes No Go.” “Find a partner” is not enough.
Early buyer exchanges can help resolve uncertainty when the procurement permits them. Federal guidance encourages exchanges from early requirement identification through proposal receipt, within procurement-integrity limits, and lists methods such as market research, draft RFPs, RFIs, conferences, and site visits. After solicitation release, the contracting officer is the focal point for federal exchanges. (FAR 15.201)
Follow the communication rules in the actual solicitation. For state and local work, use the buyer's named contact and official system rather than treating the federal process as universal.
The prime normally owns the buyer-facing decision and final response, but subcontractors can own facts that determine whether the team can proceed. For each teammate, identify:
A conditional GO should state which company owns the condition. Do not let the prime's optimism stand in for a subcontractor's actual approval, and do not treat an unsigned teaming assumption as committed capacity.
The decision record should be short enough to use and specific enough to audit:
Avoid universal weights such as “customer relationship is always 25%” or fixed thresholds such as “3.0 always means proceed.” If a score helps your team compare opportunities, define the scale, evidence standard, and decision authority internally. Keep confirmed hard gates outside the weighted total so a high average cannot erase an actual disqualifier.
A go/no-go decision is a checkpoint, not a lifetime label. Reopen it when:
For federal negotiated procurements, amendments issued before proposals are due go to all parties that received the solicitation, and the contracting officer may extend the due date when needed. That is why every material amendment should trigger a deliberate impact review rather than a silent file replacement. (FAR 15.206)
Use a controlled RFP addendum tracking process and update the public-sector compliance matrix before confirming that the original decision still holds.
GreenLight can start from current opportunity files supplied from an official portal or an approved discovery tool. It can apply documented organization rules and gaps to a GO, No Go, or Go With Conditions result, while surfacing confirmed disqualifiers, unresolved blockers, and conditions for review.
The boundary matters: a person owns the final pursuit decision. A model-asserted blocker remains a review item unless a company rule or a person confirms the disqualifier, and an unreadable material buyer file prevents a clean GO. GreenLight supports a documented decision; it does not predict an award, guarantee buyer acceptance, or make the call autonomously.
After a GO, build the solicitation-specific requirement inventory and use the state and local RFP response checklist to carry the decision into response planning. If the pipeline itself needs a reset, start with the 2026 government contracting forecast framework and treat every forecast as a planning signal rather than a promise.
Teams often use the terms interchangeably. The important distinction is operational: early qualification may decide whether to keep learning, while the bid decision authorizes the specific estimating, capture, technical, and proposal resources needed for a response.
Only after the requirement and the gap are confirmed. First verify the controlling source, applicability, addenda, and whether an allowed teammate or other approved mitigation can satisfy it. If the requirement is mandatory and cannot be met, document the stop instead of hiding it in an average score.
Yes, if the scale, evidence rules, weights, and decision authority fit the organization. Keep hard gates separate, show assumptions explicitly, and do not present the score as a win probability or as the buyer's evaluation.
Set the expiration from the actual proposal calendar and dependency. Every condition needs an owner, evidence requirement, due date, and defined consequence. If the condition is unresolved at the stop point, the team should pause or change the decision.
No. It means the opportunity currently deserves the approved level of pursuit effort under the organization's rules. Buyer evaluation, competition, price, performance, and award remain uncertain.
See how GreenLight helps your team qualify the opportunity, organize the buyer's requirements, and check the package before you submit it.