# RFP Bid or No Bid: A Decision Scorecard for Small Service Firms

<a id="main-content"></a>

B2B Strategy

October 28, 2026  ·  9 min read  ·  Victor Valentine Romo

On this page

1. [Start with the received documents](<#start-with-the-received-documents>)
2. [Put mandatory gates above the score](<#put-mandatory-gates-above-the-score>)
3. [Build the commercial worksheet](<#build-the-commercial-worksheet>)
4. [Use weights to expose preferences](<#use-weights-to-expose-preferences>)
5. [Give the decision one owner](<#give-the-decision-one-owner>)
6. [Fictional pursuit one: clarify, then pursue](<#fictional-pursuit-one-clarify-then-pursue>)
7. [Fictional pursuit two: decline despite strong fit](<#fictional-pursuit-two-decline-despite-strong-fit>)
8. [Budget the response work before approval](<#budget-the-response-work-before-approval>)
9. [Record what would reopen the decision](<#record-what-would-reopen-the-decision>)
10. [Hand the approved pursuit to the writer](<#hand-the-approved-pursuit-to-the-writer>)
11. [Sources](<#sources>)

An [RFP](</articles/rfp-compliance-matrix-service-proposals/>) arrives with a deadline. Before anyone opens the proposal template, someone needs to decide whether the firm can answer it responsibly.

A bid or no-bid scorecard puts that decision on paper. It records mandatory requirements, available evidence, delivery capacity, commercial preferences, and unanswered questions. The output is a decision with an owner: pursue, clarify, or decline.

[APMP's Winning Business Ecosystem](<https://www.apmp.org/Web/Web/About-Us/Winning-Business-Ecosystem.aspx>) places opportunity qualification before proposal development. It also separates requirement review, resource allocation, and submission checks within the proposal stage. That sequence supplies the underlying distinction here. The worksheet and scoring rules below are an editorial method for a small service firm.

Use them for a received request for proposal. Broader [B2B sales qualification](</articles/b2b-sales-qualification-frameworks/>) begins earlier, when the team is still learning about the buying situation.

<a id="start-with-the-received-documents"></a>

## Start with the received documents

Create one pursuit record before evaluating the opportunity. Give it the RFP identifier, received version, submission deadline, clarification deadline, and decision date. Name the person gathering evidence.

Keep the original RFP, attachments, and amendments together. A forwarded summary can help someone locate a requirement. It cannot establish what the buyer requested.

Read the instructions before scoring the work. Look for eligibility conditions, required qualifications, delivery dates, submission methods, and permitted exceptions. Record exact locations so another reader can repeat the check.

The first question is whether a response is feasible under the stated conditions. Enthusiasm for the buyer belongs later in the worksheet.

If the documents disagree, preserve both passages. Record the conflict as a question. An internal preference for the easier interpretation does not resolve it.

<a id="put-mandatory-gates-above-the-score"></a>

## Put mandatory gates above the score

A mandatory gate has three states: pass, fail, or unknown. Each state needs evidence and a reviewer.

A pass means the firm has confirmed that it meets the stated condition. A fail means the firm has confirmed a mismatch. Unknown means the evidence is missing or the requirement needs clarification.

Build the gate list from this RFP. Do not present a generic checklist as the buyer's actual rules.

| Gate | Source location | Evidence to inspect | Current state |
| --- | --- | --- | --- |
| Required supplier qualification | RFP section and paragraph | Current qualification record | Pass, fail, or unknown |
| Required delivery location | Scope section | Confirmed service coverage | Pass, fail, or unknown |
| Mandatory start date | Delivery schedule | Named delivery team's availability | Pass, fail, or unknown |
| Submission eligibility | Instructions and attachments | Required forms and permissions | Pass, fail, or unknown |
| Response deadline | Submission instructions | Feasible review and submission plan | Pass, fail, or unknown |

A failed mandatory gate stops pursuit under the current conditions. A high preference score cannot erase it. If the buyer permits an alternative, document that permission before changing the gate.

An unknown gate puts the decision into clarification. Set a question owner and a resolution date. If no reliable answer arrives before the internal decision deadline, decline under the unresolved conditions.

Keep the language narrow. “Required credential not held” describes a fact. “The buyer will reject us” predicts a decision the firm does not control.

<a id="build-the-commercial-worksheet"></a>

## Build the commercial worksheet

After all mandatory gates pass, compare the opportunity with the work the firm is equipped to deliver. Use the same dimensions across pursuits so exceptions remain visible.

| Dimension | What the reviewer checks | Evidence field | Decision field |
| --- | --- | --- | --- |
| Requirement fit | Requested work versus supported services | Scope comparison and exclusions | Fit rating and reason |
| Evidence readiness | Proof for each proposed capability claim | Approved samples and current records | Ready, missing, or restricted |
| Delivery capacity | People, dependencies, and existing commitments | Named staffing plan | Feasible or unresolved |
| Deadline feasibility | Writing, review, corrections, and submission | Backward response schedule | Feasible or unresolved |
| Commercial alignment | Terms, service model, and scope boundaries | Reviewed assumptions | Preference rating |
| Unresolved questions | Facts that could change the decision | Question log and source location | Owner and due date |
| Decision ownership | Who can commit proposal and delivery resources | Named decision owner | Decision and date |

Evidence readiness concerns what the firm can substantiate. [A relevant project sample](</articles/consulting-case-studies/>) may exist but lack permission for disclosure. Mark it restricted until an approved alternative is available.

Capacity concerns the people who would perform the work. A proposal writer's free afternoon says nothing about the delivery team's next month.

Deadline feasibility concerns the entire response path. Include review, attachment assembly, and the buyer's submission method. An attractive scope cannot create a missing review window.

<a id="use-weights-to-expose-preferences"></a>

## Use weights to expose preferences

Weights express the firm's priorities. They do not measure the buyer's evaluation or [predict a win probability](</articles/sales-forecasting-b2b/>).

One proposed scale uses zero for poor alignment, one for partial alignment, and two for strong alignment. An unresolved fact stays marked unknown. It receives no invented rating.

Score only the preference remaining after a mandatory condition passes. For example, extra approved samples can strengthen evidence readiness after the required sample is confirmed. A missing mandatory sample returns to the gate check. Spare capacity can improve a rating only after the required delivery schedule is feasible.

For a firm prioritizing delivery fit, a starting worksheet could assign requirement fit a weight of three. Evidence readiness and capacity each receive two. Deadline feasibility and commercial alignment each receive one.

Multiply each known rating by its weight, then total the results. This arrangement has a maximum of eighteen points. Record the weights before rating the current pursuit.

A firm could set fourteen as an internal discussion threshold. That number is a management choice, not an industry benchmark. A score below it [prompts](</articles/prompt-libraries-b2b-teams/>) a documented exception or a decline.

If a material dimension remains unknown, stop the scoring exercise and resolve it. A total built from guessed inputs creates a false sense of completion.

Use the score alongside the written reasons. Two opportunities can receive the same total while carrying [different delivery risks](</articles/project-premortem-small-service-team/>). The decision owner needs those differences in view.

<a id="give-the-decision-one-owner"></a>

## Give the decision one owner

The person assembling the worksheet should not have to infer approval from a room of contributors.

[Atlassian's DACI framework](<https://www.atlassian.com/team-playbook/plays/daci>) distinguishes the driver gathering information, one [approver](</articles/consulting-deliverable-acceptance-criteria/>) making the decision, contributors providing expertise, and people informed afterward. Adapt those roles to the pursuit.

The driver checks document versions and gathers missing evidence. Delivery contributors confirm capacity and scope. A commercial contributor examines terms and assumptions. The decision owner authorizes the pursuit or records the decline.

In a small firm, one person may hold several roles. Keep the responsibilities explicit even when the names repeat.

Set the decision date before the response deadline. That creates a defined point where the team stops investigating and makes the call.

Approval should state what it authorizes. “Prepare this response using the confirmed scope and named team” gives the writer a boundary. It does not authorize unsupported claims or changes to delivery commitments.

<a id="fictional-pursuit-one-clarify-then-pursue"></a>

## Fictional pursuit one: clarify, then pursue

Consider a fictional four-person documentation consultancy receiving an RFP for a service manual library. The buyer requests a [content inventory](</articles/b2b-content-review-schedule/>), revised manuals, and a maintenance guide.

The scope fits the consultancy's documented services. Approved samples cover comparable document types. The delivery lead confirms availability for the stated start date. The response schedule includes a separate review day.

One attachment asks for “on-site workshops as needed.” The document does not define the location or frequency. The consultancy cannot determine capacity until that requirement is clear.

The driver marks the location gate unknown. The worksheet records the attachment name and paragraph, a clarification owner, and an internal resolution deadline. The initial decision is clarify.

In this fictional example, a written amendment establishes two remote workshops and removes the undefined on-site requirement. The driver preserves the amendment and updates the gate evidence.

All gates now pass. Requirement fit, evidence readiness, capacity, and deadline feasibility each receive two. Commercial alignment receives one because the firm prefers a different reporting cadence.

Using the proposed weights, the score is seventeen of eighteen. The decision owner approves pursuit with the reporting concern documented. That approval follows resolved requirements and confirmed resources. The score records the remaining preference.

<a id="fictional-pursuit-two-decline-despite-strong-fit"></a>

## Fictional pursuit two: decline despite strong fit

A second fictional RFP requests similar documentation work. The subject matter is familiar, the required samples are available, and the commercial terms suit the firm.

The mandatory start date overlaps an existing delivery commitment. The named delivery team cannot begin then. No qualified alternative team is available for the required scope.

The mandatory start-date gate fails. The decision owner declines the pursuit before assigning proposal sections. There is no reason to calculate a high commercial score around that failure.

The internal rationale reads: “Decline under the current schedule. The mandatory start date conflicts with confirmed delivery commitments. No supported staffing alternative is available.”

This note states the constraint without judging the buyer or guessing the competitive field. It also leaves a clear reconsideration trigger: a confirmed schedule amendment that the delivery lead can support.

The firm should not keep writing in anticipation of that amendment. Reconsideration begins when new evidence arrives and someone reopens the decision.

<a id="budget-the-response-work-before-approval"></a>

## Budget the response work before approval

A pursuit decision also assigns internal work. List the people needed for writing, subject review, evidence approval, and submission preparation. Ask each owner to confirm the assignment.

Use [a backward schedule](</articles/consulting-project-management/>) with concrete outputs. The delivery lead confirms the service approach before the writer describes it. The evidence owner approves samples before those samples enter the response.

Record an internal response-effort limit using the firm's own planning method. Treat it as an allocation decision. Do not convert an invented award probability into a precise expected return.

If the response expands, return to the decision owner. A new attachment or additional review can change feasibility even when the original service scope remains stable.

Compare this allocation with the firm's wider [consulting client acquisition](</articles/consulting-client-acquisition/>) work. A formal pursuit consumes capacity that could serve another qualified opportunity or an existing delivery obligation.

The worksheet should make that trade visible without pretending every alternative has a measurable outcome.

<a id="record-what-would-reopen-the-decision"></a>

## Record what would reopen the decision

Every clarify or decline outcome needs a trigger, an owner, and an expiry. Otherwise it can linger as an unofficial pursuit.

A useful trigger names new evidence: a revised start date, permission to use an equivalent qualification, or a written answer to a scope question. “The buyer seems interested” supplies no changed condition.

When a trigger occurs, preserve the old decision and create a dated revision. Recheck the affected gates and preferences. Confirm that other assumptions still hold.

The response deadline may remain unchanged after an amendment. Reconsidering scope therefore requires another deadline check. A clarified requirement can still leave insufficient time for an approved response.

When the decision expires, close the record. Keep the RFP version, gate results, evidence locations, final rationale, and decision owner. Those details explain the choice without reconstructing a conversation later.

<a id="hand-the-approved-pursuit-to-the-writer"></a>

## Hand the approved pursuit to the writer

A pursue decision should produce a bounded handoff: the received RFP version, passed gates, confirmed delivery assumptions, approved evidence, unresolved minor questions, and response owners.

Use [proposal templates for B2B services](</articles/proposal-templates-b2b-services/>) after that handoff. The template organizes the response. The pursuit record explains why the firm has committed to writing it.

Before drafting begins, ask the writer to identify any claim that lacks evidence. Send a material gap back to the decision owner. Pursuit approval does not turn missing proof into a qualification.

Keep the final decision short enough to read before work starts. Name the opportunity, decision, reason, conditions, owner, and next review trigger.

Commit proposal work after the conditions are clear.

<a id="sources"></a>

## Sources

- [APMP: Winning Business Ecosystem](<https://www.apmp.org/Web/Web/About-Us/Winning-Business-Ecosystem.aspx>). Opportunity qualification and proposal-stage responsibilities. Checked October 28, 2026.
- [Atlassian: DACI decision-making framework](<https://www.atlassian.com/team-playbook/plays/daci>). Decision roles and one approver. Checked October 28, 2026.
