Sealed Bid Award: The Lowest Responsive, Responsible Bidder Explained

A sealed-bid award in three questions

A sealed-bid award turns on three questions, asked of each bid in turn. Does the bid conform to the invitation? Can the bidder actually perform? Is the bid the lowest in price once the arithmetic and alternates are settled? The file has to answer all three, separately and in order. This guide walks through each one and what to record.

What 2 CFR 200.320(b)(1) says about sealed bids

Start with the federal text, because the rest of the file hangs on it. Under 2 CFR 200.320(b)(1), sealed bids are publicly solicited, and a firm fixed-price contract is awarded to the responsible bidder whose bid conforms to all the material terms and conditions of the invitation for bids and is lowest in price. The same section describes sealed bids as "preferred for procuring construction services."

Three phrases in that rule do the work: "responsible," "conforms," and "lowest in price." They map to three separate determinations, and a sound file records each one on its own. The section also frames sealed bidding as a formal method, distinct from proposals, so price is the deciding factor once a bidder clears the other two tests. For how the formal methods differ in practice, see the overview of 2 CFR 200.320 procurement methods and the comparison of RFPs and IFBs.

One related point from the same section. Under 2 CFR 200.320(b)(1)(ii)(D), the contract is awarded in writing to the lowest responsive bid and responsible bidder, and "when specified in the invitation for bids, factors such as discounts, transportation cost, and life-cycle costs must be considered in determining which bid is the lowest." If you intend such factors to count, state them in the invitation. Adding them to the comparison after bids are opened is a change the file will struggle to defend.

State and local codes may be stricter than the federal rules, including on bonds, bid forms and correction of errors. When both apply, follow the stricter one, and confirm how they interact with your awarding agency or pass-through entity.

Responsive and responsible are different tests

Responsiveness asks whether the bid, as submitted, conforms to the material terms of the invitation. Did the bidder sign the form, acknowledge the addenda, supply the required bid security, and price every item the invitation required? Responsiveness is judged from the bid document itself, at the time of opening.

Responsibility asks whether the bidder can actually perform. It looks at the bidder's capability, record and standing, and it draws on information beyond the bid envelope. Under 2 CFR 200.318(h), contracts may be awarded only to responsible contractors that possess the ability to perform successfully under the terms and conditions of the proposed contract, and 200.318(c)(1) requires written standards of conduct covering conflicts of interest. A bidder can be responsive and not responsible, or the reverse, so one checkbox cannot cover both. A closer look at responsive versus responsible bidders walks through the distinction.

What to record for each bid:

• the responsiveness result, with the specific items checked and the reason for any rejection;
• the responsibility determination, who made it, and the information it rested on;
• the date of each determination, so the order of events can be reconstructed.

A rejection needs a stated reason tied to the invitation's own words. "Nonconforming" alone gives a reviewer nothing to test.

Checking the arithmetic before ranking

The tab is only as reliable as its math. Bidders enter unit prices, extensions and totals by hand, and the numbers do not always agree with each other. The invitation for bids should say which controls when they conflict, for example whether unit prices govern over extended totals. That rule comes from the issuer's own bid documents and from local law, and this article states no default.

A sound routine looks like this:

1. Record each bid exactly as read at opening, without correcting anything.
2. Recompute every extension and total in a separate column.
3. Flag each mismatch and apply the rule stated in the invitation.
4. Record the corrected figure, the original figure and the rule applied.

Keeping the as-read figure beside the corrected one matters. If a bidder later asks why its total changed, the file shows both numbers and the sentence in the invitation that authorized the change. Correction of mistakes after opening is also governed by local policy and state law, so check yours before allowing any bidder to alter a price.

Applying alternates in the announced order

Alternates are the most common place a sealed-bid tab goes wrong. An alternate is an add or deduct item that the invitation lists separately from the base bid. The invitation should state two things in advance: which alternates the owner may select, and the order in which they will be applied, usually tied to available funding.

The point of announcing the order is that it fixes the comparison before anyone sees the prices. If alternates are chosen after the numbers are known, a different bidder can become low depending on the selection, and the choice itself looks like a way to pick the winner.

A worked example, with round numbers for illustration only. Suppose the invitation lists a base bid and two deductive alternates, applied in order, with funding sufficient to apply Alternate 1 only.

Bidder	Base bid	Alternate 1 (deduct)	Evaluated price
A	$400,000	$15,000	$385,000
B	$390,000	$5,000	$385,000
C	$410,000	$30,000	$380,000

Bidder C is low on the evaluated price. Had the owner ignored the alternate, Bidder B would have been low on the base bid. Because the invitation announced the order, the file can show that the result followed the stated rule rather than a preference.

Record the funding available at opening, the alternates applied, the order, and the evaluated price for each bidder. Keep alternates and options out of the evaluated price unless the invitation says they count. The bid tabulation guide covers how to lay these columns out.

Ties, rejections and the award decision

Sometimes two evaluated prices are identical. As in the example above, a tie on the base bid or the evaluated price needs a rule, and the rule belongs in the invitation or in written policy before opening. Typical rules include a drawing by lot or a stated preference, but the right one depends on local law, so confirm yours. A guide to tie-breaking procedures explains how to document the one you use.

Geographic preferences deserve a note. 2 CFR 200.319(a) requires full and open competition. The specific geographic-preference prohibition that 200.319 carried before the 2024 revision is not in the current text, but program statutes, award terms or state law may still restrict a local-bidder tiebreaker on a federally funded procurement. Confirm with your awarding agency or pass-through entity before using one.

Once the arithmetic is settled, alternates applied and the ties resolved, the sequence for the award file is:

• rank the responsive bids by evaluated price;
• review the lowest bidder for responsibility;
• if that bidder is found not responsible, record why and move to the next;
• record the award to the lowest responsive, responsible bidder.

Responsibility is reviewed in rank order, which keeps the work proportionate. The file does not need a full review of every bidder, only of those the award decision actually reaches.

What the award file should show

2 CFR 200.318(i) requires records detailed enough to show the history of each procurement, including the rationale for the method, the contract type, the contractor selection or rejection, and the basis for the contract price. For a sealed bid, those four elements are concrete. The method rationale cites the sealed-bid conditions in 200.320(b)(1). The contract type is firm fixed-price. The selection or rejection is the responsiveness and responsibility record for each bidder. The price basis is the corrected tab with the alternates applied.

Under 2 CFR 200.318(k), the recipient settles source-evaluation issues, protests, disputes and claims arising from its procurements, so its own record is what it has to work with if a bidder objects. Local protest procedures are set by local policy and should be checked before opening. Retention under 2 CFR 200.334 is generally three years from the date the final financial report is submitted, longer if litigation, a claim or an audit starts before then, and local public-records rules may require longer.

Above the simplified acquisition threshold, 2 CFR 200.324(a) requires a cost or price analysis for every procurement transaction, including contract modifications, and independent estimates made before bids are received. The SAT rose from $250,000 to $350,000 effective October 1, 2025 (FAR Case 2024-001, 90 FR 41872). A local threshold may be lower, and the stricter rule governs. Confirm how the change applies to your award with the awarding agency or pass-through entity.

Keeping the tab and the file together

Most sealed-bid problems are not exotic. They come from a tab rebuilt for each solicitation, a correction made without a note, or a responsibility finding that lives in someone's email. A consistent layout helps. So does recording each step when it happens rather than reconstructing it later.

The Sealed Bid Tabulation and Low-Bid Award Workbook is designed to hold the as-read and corrected figures side by side, apply alternates in the announced order, and record the responsiveness and responsibility determinations for each bidder. It is a workbook for recording and computing, and it does not receive bids. It is available now at the sealed-bid tabulation store page. If you would like to hear when the evaluation workspace opens, you can join the waitlist.

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