- Separate hard prerequisites from risks that can be investigated or reduced.
- Make every conditional bid decision depend on an owner, evidence and a deadline.
- Include the cost of secure delivery and ongoing support in the opportunity economics.
Set the decision before scoring the opportunity
A bid/no-bid review should answer whether this team can responsibly compete for this requirement with the time and resources available. It should not simply turn an attractive revenue figure into a favorable score. Start by identifying who can authorize pursuit spending, who can stop the effort and what evidence those people need.
Use a short gate sheet with four areas: prerequisites, deliverability, proof and economics. Give each a status of confirmed, unresolved or not achievable within the opportunity's constraints. Record the source behind the status. A weighted score can help compare opportunities later, but it should not average away an unmet mandatory condition.
Gate one: can the team meet the actual prerequisites?
Read the eligibility and submission requirements from the current solicitation. Include the required business registrations, relevant set-aside eligibility, contract vehicle access and cybersecurity requirements that apply. Keep each distinct. Having a cybersecurity record does not establish size eligibility, and having an active registration does not demonstrate that a proposed information system meets its requirements.
For unresolved items, write a decision question rather than a hopeful sentence. “Can the proposed environment meet the completed assessment requirement by the required time?” is useful. “We should be fine” is not. If the answer depends on an amendment, a government clarification or work outside the company's control, identify that dependency explicitly.
Gate two: can the work be delivered as proposed?
Ask the delivery lead to explain the first month of performance. Identify information received, people granted access, systems used, subcontracted tasks and deliverables returned. Look for changes needed before the team can operate that way. A narrow, workable delivery approach may be more credible than a broad promise requiring multiple unplanned platform changes.
Use a hypothetical example: a small design firm can perform the technical analysis, but its proposed specialist works through an unmanaged file-sharing account. The gate is not a judgment about the specialist's expertise. It is a decision about whether the team can establish an acceptable information-handling arrangement within the schedule, budget and actual contract requirements.
Gate three: can the proposal demonstrate the claims?
List the evidence needed to support the offer's material assertions. Examples include relevant project experience, named staffing commitments, verified system scope and required identifiers. Distinguish evidence already available from evidence someone expects to obtain. The proposal manager should know which assertions can be drafted now and which must wait for verification.
Connect strengths to the solicitation's evaluation factors. FAR 15.304 places those factors in the solicitation; inventing a different scoring model internally can misdirect writing effort. Avoid substituting a generic cybersecurity capability paragraph for the proof the evaluator actually requests. A concise, supportable response is a better pursuit asset than a long narrative with unverified claims.
Gate four: do the economics survive the delivery plan?
Price the resources required for the proposed operation, including internal staff time, onboarding, software, service providers, training and continuing maintenance. Separate one-time setup from recurring support. Ask finance how shared investments are treated under the company's accounting practices and the anticipated contract structure. Do not assume every security expenditure can be charged directly to this opportunity.
Run a practical sensitivity check. What happens if award slips, a specialist needs replacement or an information-flow assumption changes? These are planning scenarios, not forecasts. Record the cost driver and management response for each. A nominal margin that disappears under a modest operational change deserves attention before the team commits weeks to a proposal.
Use a conditional decision carefully
A conditional go decision is useful only when it contains measurable exit criteria. Name the action, owner, acceptable evidence, spending limit and final decision date. For example, authorize a limited clarification and architecture review before releasing the full proposal budget. If the condition is not satisfied, the default outcome should be clear to everyone.
Record the rationale for a no-bid as well. It may reveal a reusable capability investment, a better teaming role or a future opportunity with a more suitable scope. Keep the gate sheet as a learning record. After award or loss, compare the original assumptions with what happened and improve the next decision without rewriting the old evidence.
Sources & further reading
Official materials and directly relevant resources. Requirements depend on the solicitation, contract, information, and current rules.
This is general educational information, not a determination of compliance, bid eligibility, legal advice, or a certification result. Read our editorial policy.