
Concept
The go/no-go decision on a Request for Proposal (RFP) represents a primary control point within an organization’s operational architecture. It functions as a strategic filter, safeguarding the allocation of a firm’s most finite assets ▴ expert personnel, intellectual capital, and time. Viewing this decision as a mere administrative checkpoint is a fundamental misreading of its purpose. Instead, it is the mechanism that aligns tactical pursuits with superordinate strategic objectives.
Each affirmative decision to bid consumes substantial resources, initiating a cascade of events that draws from sales engineering, project management, and subject matter experts. A misaligned pursuit drains this reservoir, diverting energy from core business functions and more promising opportunities. The true function of a rigorous go/no-go protocol is to ensure that the full weight of the organization’s proposal machinery is applied only to opportunities that offer a high probability of success and contribute directly to the firm’s long-term strategic advancement. This process is not about avoiding effort; it is about directing effort with maximum precision and impact.
A disciplined go/no-go decision framework transforms resource allocation from a reactive process into a strategic advantage.
The efficacy of this filtration system depends entirely on the quality of its inputs and the rigor of its logic. It moves beyond intuition-based judgments to a data-centric evaluation. The process systematically deconstructs an opportunity into its constituent parts ▴ financial, technical, relational, and competitive ▴ and assesses each against predefined corporate benchmarks. This analytical discipline provides a defensible rationale for every decision, insulating the process from internal biases or the simple allure of a large contract value.
The output is a binary decision, but the process that generates it is a complex assessment of probabilities and trade-offs. It is the first and most critical line of defense in protecting an organization’s strategic integrity and operational capacity.

Strategy

The Pillars of Evaluation
A robust RFP evaluation strategy rests on a multi-pillar framework that provides a holistic view of the opportunity. These pillars are not standalone criteria but interconnected domains of inquiry. Each one addresses a distinct aspect of the potential engagement, and together they form a comprehensive analytical model.
The objective is to move from a qualitative “feel” for the project to a quantitative and qualitative assessment that balances opportunity against tangible costs and risks. This structured approach ensures all critical facets are examined with the same degree of scrutiny, leading to a more consistent and reliable decision-making process across the organization.

Pillar 1 Strategic and Solution Fit
This pillar assesses the fundamental alignment between the opportunity and the organization’s core purpose. It questions whether the project leverages existing strengths and contributes to the desired market position. A perfect alignment means the required work is central to the company’s mission and expertise, allowing for efficient and high-quality execution.
A poor alignment, conversely, forces the organization into unfamiliar territory, increasing risk and diminishing competitive advantage. It examines if the client’s problem is one your organization is uniquely equipped to solve.

Pillar 2 Financial Viability and Risk
Beyond the top-line contract value, this pillar scrutinizes the underlying financial mechanics and potential liabilities of the project. It involves a realistic assessment of the costs to prepare the proposal and to deliver the project if won. A detailed analysis of potential profit margins, cash flow implications, and contractual risks is essential.
This evaluation ensures that the pursuit is not only potentially profitable but also financially sound from a resource and liability perspective. It answers the question ▴ does this opportunity make sound financial sense for the business?
The strategic objective is to filter opportunities through a matrix of criteria that quantifies alignment and predicts success.

The Decision Matrix a Comparative Framework
To operationalize these pillars, a decision matrix is an effective tool. It translates abstract criteria into a structured format, allowing for a side-by-side comparison of critical factors. The following table illustrates how different opportunity elements can be broken down and evaluated.
| Evaluation Pillar | Key Questions | Ideal Scenario | Warning Signs |
|---|---|---|---|
| Strategic Fit | Does this project align with our 1-3 year strategic goals? Does it enhance our brand or market position? | Project directly supports a core strategic objective and builds on our established reputation. | Opportunity is purely tactical and deviates from our strategic path; it is an “oddball” project. |
| Capability Match | Do we possess the required expertise and technology in-house? Do we have demonstrable past performance? | The required solution is a core competency. We have multiple successful reference cases. | Requires significant new R&D, reliance on unproven partners, or skills we do not possess. |
| Financial Viability | Is the potential profit margin above our minimum threshold? Does the client’s budget align with our delivery costs? | Clear budget alignment and a projected margin that exceeds the corporate target. | The client’s budget is unknown or unrealistic. The projected margin is thin or negative. |
| Competitive Landscape | Who are the likely competitors? Is the incumbent entrenched? Do we have a unique competitive advantage? | We have a distinct advantage, and the competitive field is limited. The incumbent is known to be performing poorly. | The RFP seems wired for a competitor. The market is saturated with stronger rivals. |
| Client Relationship | What is our history with this client? Do we have a champion within their organization? | We have a strong, established relationship with multiple stakeholders and an internal advocate. | We have no prior relationship, and all communication has been strictly formal and one-way. |

Execution

A Formalized Go/No-Go Protocol
Executing a go/no-go decision requires a formalized, multi-stage protocol. This system ensures that each opportunity is subjected to a consistent and rigorous evaluation process, moving from an initial screening to a deep analysis by a dedicated committee. The protocol is designed to be efficient, eliminating clearly unsuitable RFPs early while dedicating more extensive resources to the evaluation of promising ones. This structured flow minimizes wasted effort and ensures that key stakeholders provide input at the appropriate stages.
- Initial Screening ▴ Upon receipt, the RFP is subjected to a high-level review by a designated gatekeeper, often within the sales or business development team. This check uses a small set of absolute “no-go” criteria.
- Does the RFP fall within our core lines of business?
- Is the submission deadline realistic?
- Are there any immediate contractual red flags (e.g. unlimited liability)?
If the RFP fails this initial test, it is immediately classified as a “no-go” with minimal resource expenditure.
- Opportunity Analysis ▴ RFPs that pass the initial screen proceed to a more detailed analysis. This stage involves completing a standardized scoring card or evaluation matrix, like the one detailed below. This task is typically assigned to the opportunity lead or capture manager. The goal is to collect the necessary data to inform the final decision.
- Committee Review ▴ The completed scoring card and a summary analysis are presented to a go/no-go committee. This committee should be cross-functional, including representatives from sales, delivery, finance, and management. The committee discusses the analysis, challenges assumptions, and makes the final, collective decision.
- Decision & Feedback ▴ The final decision is documented and communicated. If a “no-go” decision is made, it is valuable to communicate this professionally to the issuing organization, preserving the relationship for future opportunities. A brief, polite declination citing poor fit or resource constraints is sufficient.

Quantitative Scoring Model
To introduce a higher degree of objectivity, a weighted scoring model is a cornerstone of the execution phase.
This model assigns weights to different criteria based on their strategic importance to the organization. Each criterion is then scored on a simple scale (e.g. 0-5), and a weighted total score is calculated. This provides a quantitative basis for the decision, supplementing the qualitative discussion.
The implementation of a weighted scoring model provides a data-driven foundation for what is otherwise a subjective and often political decision.
| Criterion | Weight (%) | Score (0-5) | Weighted Score | Guiding Questions for Scoring |
|---|---|---|---|---|
| Strategic Alignment | 25% | 4 | 1.00 | 5 = Perfect alignment with core strategy. 3 = Supports strategy. 1 = Tangential. 0 = Detracts from strategy. |
| Profitability | 20% | 3 | 0.60 | 5 = High margin (>25%). 3 = Acceptable margin (15-25%). 1 = Low margin (<15%). 0 = Loss. |
| Capability & Solution Fit | 20% | 5 | 1.00 | 5 = We are a recognized leader for this solution. 3 = We have solid experience. 1 = It’s a stretch. 0 = No experience. |
| Client Relationship | 15% | 2 | 0.30 | 5 = Strong incumbent/trusted partner. 3 = Good existing relationship. 1 = Some contact. 0 = Cold call. |
| Competitive Advantage | 15% | 3 | 0.45 | 5 = Clear, sustainable advantage. 3 = Competitive, with differentiators. 1 = At a disadvantage. 0 = Incumbent is locked in. |
| Resource Availability | 5% | 4 | 0.20 | 5 = Team is available and ready. 3 = Key personnel are available. 1 = Would require pulling staff from other projects. 0 = No staff available. |
| Total Score | 100% | 3.55 | Decision Thresholds ▴ >3.5 = Go; 2.5-3.5 = Discuss; <2.5 = No-Go |
This scoring model provides a clear, defensible number that acts as a critical input to the final committee discussion. It focuses the conversation on the areas of greatest weakness or strength and helps remove emotion from the evaluation. The thresholds are not absolute rules but guiding benchmarks that ensure a consistent standard is applied to all opportunities.

References
- Bjeletich, B. & Zunk, B. M. (2016). Analysis of Request for Proposals in Construction Industry. Organizacija, 49 (3), 193-203.
- El-Mashaleh, M. S. (2013). Empirical Framework for Making the Bid/No-Bid Decision. Journal of Management in Engineering, 29 (1), 65-71.
- Enshassi, A. & El-Karriri, M. (2018). Critical Factors Affecting Contractors’ Decision to Bid ▴ A Global Perspective. Buildings, 8 (11), 154.
- Lin, C.-T. (2000). A knowledge-based method for bid/no-bid decision-making in project management. Paper presented at PMI® Research Conference 2000 ▴ Project Management Research at the Turn of the Millennium, Paris, France. Newtown Square, PA ▴ Project Management Institute.
- Wanous, M. Boussabaine, A. H. & Lewis, J. (2000). A neural network bid/no bid model for construction projects. Engineering, Construction and Architectural Management, 7 (2), 165-175.

Reflection

The Decision Protocol as an Intelligence System
Ultimately, a go/no-go protocol transcends its immediate function of filtering individual RFPs. It matures into a dynamic intelligence-gathering system. Each evaluation, whether it results in a bid or not, generates valuable data about the market, competitors, and client priorities. The reasons for a “no-go” decision are as illuminating as the rationale for a “go.” A pattern of declining bids due to misaligned technical requirements may signal a shift in the market that requires a strategic response.
Consistently losing to a specific competitor points to a capabilities gap that must be addressed. Viewing the framework in this light elevates it from a simple administrative process to a vital component of the organization’s strategic learning and adaptation cycle. The discipline of the decision becomes a source of continuous insight, sharpening the firm’s competitive edge with every RFP it evaluates.

Glossary

Go/no-Go Decision

Project Management

No-Go Decision



