Responsive vs Responsible Bidder: Two Different Determinations

A blank form and a bad reputation are two different problems

A program director at a grant-funded nonprofit opens bids for a renovation paid for in part with a federal award. The lowest bidder left a required form blank. The second-lowest bid is complete, but the director remembers hearing about that firm's trouble on another job. A board member asks two questions in one breath: can we pass over the low bid, and can we pass over the next one?

They sound like the same question, but they are not. The first asks whether the bid meets what the solicitation required. The second asks whether the firm can actually perform the contract. Blurring them is a common way for an award file to lose its logic. The reason written down for setting an offer aside may not match the determination that was really made.

When a monitor or an unsuccessful bidder asks why a firm was rejected, the file must answer in the right terms. This article separates the two determinations, shows how each is made, and lists what to record so the file shows which one was applied, when, and by whom.

Responsive vs responsible bidder: what each determination asks

Responsiveness is a judgment about the bid. It asks whether the submission conforms to the material requirements of the solicitation: the required forms, the stated format, the price schedule, and any terms the solicitation said were mandatory. A bid can be responsive from a firm that could never do the work.

Responsibility is a judgment about the bidder. It asks whether the firm has the capacity, record and standing to perform this contract. A firm can be highly responsible and still submit a bid that fails to conform.

Keep the two separate in your head and in your file. A useful shorthand is this: responsiveness looks at the paper submitted, and responsibility looks at the organization behind it.

Both determinations belong to the issuer. No scoring sheet, template or software makes either one. The people who hold the authority under your written procedures decide, and the file shows what they relied on.

How responsiveness is determined

Responsiveness is checked against the solicitation as issued. That is why the solicitation must say clearly what is mandatory. If a requirement was not stated, it is hard to reject a bid for missing it.

A sound responsiveness review works through the same items for every bid:

• Was the bid received by the stated deadline, by the stated method?
• Are all required forms and certifications present and signed?
• Does the price schedule match the format the solicitation asked for?
• Does the bid take exception to any material term?
• Were any addenda acknowledged, if the solicitation required it?

The idea is a fixed list applied equally. Rejecting one bid for a missing form while waiving the same gap for another is the kind of inconsistency a protest turns on.

Not every deviation is material. Many issuers treat a minor, curable irregularity differently from a failure that affects price, quantity or delivery. Your written procedures and the solicitation should say how irregularities are handled. When in doubt, check with the awarding agency or pass-through entity before you act, and record what you decided and why.

For more on how the two solicitation types differ, see RFP vs IFB.

How responsibility is determined under 2 CFR 200.318

For a federal award, 2 CFR 200.318(h) says the recipient or subrecipient "must award contracts only to responsible contractors that possess the ability to perform successfully under the terms and conditions of a proposed contract." It goes on to list what must be considered: "contractor integrity, public policy compliance, proper classification of employees (see the Fair Labor Standards Act, 29 U.S.C. 201, chapter 8), past performance record, and financial and technical resources." eCFR, where that text is published, is authoritative but unofficial; the official edition is the annual CFR on govinfo.gov.

In practice, a responsibility review looks at evidence about the firm itself, not the bid. Working from that list, the review usually covers:

• integrity and business conduct;
• compliance with public policy requirements, including how the firm classifies its employees;
• past performance on comparable work;
• financial resources to carry the job;
• technical capacity, staffing and equipment;
• whether the firm is excluded from federal awards.

The exclusion check is a distinct step. Under Appendix II to 2 CFR Part 200, paragraph (H), a contract award covered by 2 CFR 180.220 "must not be made to parties listed on the governmentwide exclusions in the System for Award Management (SAM)." Section 180.220 generally covers a contract expected to equal or exceed $25,000, along with some others. Before entering a covered transaction, 2 CFR 180.300 asks you to verify that the firm is not excluded or disqualified, by checking SAM.gov Exclusions, collecting a certification from the firm, or adding a clause or condition to the transaction. Your awarding agency may adopt this guidance in its own regulations, so confirm which method it expects, and record the date and result of whichever check you run. For more on that step, see the guide to SAM.gov suspension and debarment checks.

Responsibility is also tied to conflicts of interest. Under 2 CFR 200.318(c), no employee, officer, agent or board member with a real or apparent conflict may take part in selecting or awarding the contract. That is a separate question from the firm's capacity, but it belongs in the same file.

Why the order and the record matter in sealed bids

In a sealed bid, the award goes to the responsible bidder whose conforming bid is lowest in price (2 CFR 200.320(b)(1)). Sealed bids are described there as preferred for construction services. Those two words, responsible and conforming, carry the two determinations.

Because price is the deciding factor, the sequence matters. Many issuers confirm responsiveness first, since a nonconforming bid is out regardless of price. They then review responsibility for the lowest conforming bidder, and move to the next only if that firm is found not responsible. Local procedures may set a different order. Whatever order you use, write it down in advance and follow it each time.

Under 2 CFR 200.318(i), the file must hold records detailed enough to show the history of the procurement. That includes the rationale for the method, the contract type, the basis for selecting or rejecting the contractor, and the basis for the price. A rejection needs a stated ground that matches the determination. "Rejected as nonresponsive: required bid form not submitted" is a different statement from "found not responsible: record of past performance." The guide to 2 CFR 200.318 records covers this element in more detail.

Under 2 CFR 200.318(k), the recipient settles protests and disputes arising from its own procurements. If a rejected bidder challenges the decision, your own record is the account of what happened.

A worked example: how the two determinations change the ranking

Take a worked example with round numbers. Three firms bid on a fixed-price job at $80,000, $100,000 and $125,000.

On price alone, Firm A at $80,000 is lowest. Under a lowest-price formula (lowest evaluated price ÷ this offer's evaluated price × maximum price points), with 30 price points, the three firms would earn 30, 24 and 19.2 points. That is arithmetic, not a determination.

Now apply the determinations:

1. Firm A omitted a mandatory certification. The issuer records a responsiveness finding, citing the solicitation clause that made it mandatory, and the date.
2. Firm B is the lowest conforming bid. The issuer then reviews responsibility: references, financial information, and the exclusion check, each dated and with its result.
3. If Firm B passes, award goes to Firm B at $100,000. If it does not, the file records the specific ground, and the review moves to Firm C.

If the solicitation allowed alternates or options, decide beforehand whether they are part of the evaluated price. Mixing them into the base price quietly changes who is lowest. For the mechanics of building the comparison, see the bid tabulation guide. The wider sealed-bid logic is in lowest responsive, responsible bidder.

What to record, and where it lives

Keep two separate records for each bidder. One is a responsiveness checklist: each requirement, the finding, the reviewer and the date. The other is a responsibility review: each factor examined, the evidence, the exclusion check date and result, and the determination with its reviewer.

State and local rules may be stricter than the federal ones, and when both apply the stricter one governs. Check your own written procedures and your awarding agency's expectations. Retention follows 2 CFR 200.334, generally three years from the final financial report unless an exception applies, and local public-records rules may require longer.

RFPManagement is built around a per-proposal responsiveness checklist, with scoring and tabulation done by people and the award decision entered by a human. Bids received elsewhere are entered by paste or CSV. The software does not publish solicitations or receive bids.

The Vendor Responsibility Review Log is a store workbook designed to record the factors reviewed, the exclusion check date and the determination for each bidder. See the Vendor Responsibility Review Log page for what it is designed to hold. To hear when the evaluation workspace opens, join the waitlist.

RFPManagement records and computes. It does not give legal or procurement advice. The award decision stays with your organization.