RFP vs IFB: Choosing Between Competitive Proposals and Sealed Bids

One quarter, two purchases, two possible methods

A finance manager at a grant-funded nonprofit is preparing to buy a building renovation and a managed IT service in the same quarter. The program director wants one solicitation template for both. She starts drafting and realizes she cannot decide whether the renovation should go out as a request for proposals or as an invitation for bids. The IT service looks like a proposals job, but the renovation has a finished design and a clear scope. Whichever method she chooses, a monitor may later ask why, and the file has to answer.

The two methods are not interchangeable labels for "a competitive solicitation." They award on different bases, they are evaluated in different ways, and they leave different records. This article compares an RFP and an IFB under 2 CFR 200.320(b), so that you can choose a method deliberately and show the reasoning in the file.

How 2 CFR 200.320 sorts the methods

2 CFR 200.320 sets out three types of procurement method: informal (micro-purchases and simplified acquisitions), formal (sealed bids or proposals) and noncompetitive. An IFB and an RFP both sit in the formal category. They are the two routes the regulation describes for procurements above the simplified acquisition threshold that are competed.

Sealed bids are covered in 2 CFR 200.320(b)(1). Proposals are covered in 2 CFR 200.320(b)(2). Each paragraph has its own requirements, and a file should cite the one that matches the method used. For a wider view of the method categories, see 2 CFR 200.320 procurement methods.

Two points frame everything that follows. First, the choice of method belongs to the issuer, not to the regulation or to a vendor. Second, state and local law may add conditions, and where both apply your solicitation may need to satisfy both. Confirm how those rules apply to your award with your awarding agency or pass-through entity.

What an IFB asks of the evaluation

Under 2 CFR 200.320(b)(1), sealed bids are publicly solicited, and a firm fixed-price contract goes to the responsible bidder whose conforming bid is lowest in price. The regulation also notes that sealed bids are "preferred for procuring construction services."

The mechanism is narrow by design. The invitation states the requirement completely, bidders respond with a price, and the evaluation asks two questions. Is the bid responsive, meaning it conforms to the invitation? Is the bidder responsible, meaning able to perform? Among the bids that pass, the lowest price wins.

That narrowness has consequences for the file:

• Little room for judgment on quality. Under 2 CFR 200.320(b)(1)(ii)(D), factors such as discounts, transportation cost and life-cycle costs must be considered in determining the lowest bid when they are specified in the invitation for bids. State them in the invitation if they are to count.
• Responsiveness decisions carry the weight. The record has to show why a bid was accepted or rejected as non-conforming, since the price ranking is otherwise mechanical.
• Price tabulation is the core exhibit. A clean tabulation of every bid received, with alternates handled the way the invitation said, is the center of the file. See the guide to bid tabulation.

For the detailed mechanics of the lowest responsive, responsible bidder standard, see sealed bid: lowest responsive, responsible bidder.

What an RFP asks of the evaluation

Proposals work differently. Under 2 CFR 200.320(b)(2)(i), an RFP requires public notice and must identify every evaluation factor and its relative importance. Proposals must be solicited from multiple qualified entities. Under 2 CFR 200.320(b)(2)(ii), an entity using the proposals method must have written procedures for conducting technical evaluations and making selections.

Under 2 CFR 200.320(b)(2)(iii), contracts must be awarded to "the responsible offeror whose proposal is most advantageous to the recipient or subrecipient considering price and other factors." Price is one factor among several, weighted against the rest.

That makes the evaluation a scoring exercise rather than a sort. The file needs to show:

1. the factors and weights published in the solicitation;
2. how each rating point was defined before anyone scored;
3. each evaluator's independent scores;
4. the rationale behind each consensus score;
5. how price was converted to points; and
6. how the final ranking was reached.

The difficulty is that a weighted evaluation invites questions an IFB never faces. Why did one offeror receive a higher technical score than another? Did evaluators see each other's scores first? Did the weights match what the solicitation announced? For the building blocks, see how to build RFP evaluation criteria.

Comparing the two side by side

Question	IFB (sealed bid)	RFP (proposals)
Regulation	2 CFR 200.320(b)(1)	2 CFR 200.320(b)(2)
Award basis	Lowest price among responsive, responsible bidders	Most advantageous, considering price and other factors
Contract type	Firm fixed-price	Fixed-price or cost-reimbursement
Evaluation	Responsiveness and responsibility, then price	Weighted factors, independent scoring, consensus
Price role	Decisive	One factor among several
Main file exhibit	Bid tabulation and responsiveness findings	Criteria, anchors, scores, consensus rationale, price analysis
Typical fit	Well-defined scope, such as construction	Scope where quality, approach or capability differ

The contrast is easy to state. An IFB removes judgment about quality and leaves a price contest. An RFP admits judgment about quality and requires the file to show that the judgment was structured, consistent and tied to published factors.

Choosing: the facts that point toward each method

The regulation does not hand you a formula for choosing. It sets conditions for each method and leaves the selection to the issuer. In practice, a few facts tend to push one way or the other.

Facts that point toward an IFB:

• the scope can be described completely enough that bidders are pricing the same thing;
• the award can fairly turn on price alone;
• you expect enough bidders for price competition to work; and
• the work is the kind the regulation says sealed bids are preferred for, such as construction.

Facts that point toward an RFP:

• offerors may propose different approaches that you want to compare;
• qualifications, staffing or technical quality matter to the outcome;
• you need to weigh price against other factors rather than rank on price alone; and
• you cannot specify every detail in advance.

The sealed-bid paragraph lists conditions that should be present for sealed bidding to be feasible. Under 2 CFR 200.320(b)(1)(i), they are: a complete, adequate and realistic specification or purchase description is available; two or more responsible bidders have been identified as willing and able to compete effectively for the business; and the procurement lends itself to a firm-fixed-price contract, with the successful bidder selected principally on price. For local governments, the invitation for bids must also be publicly advertised and the bids opened publicly. Record in the file which conditions were present and how you knew.

Two related distinctions come up often. A request for qualifications is not simply a shorter RFP. Where price is not a selection factor, 2 CFR 200.320(b)(2)(iv) allows that approach "only" for architectural and engineering (A/E) professional services: the entity evaluates qualifications, selects the most qualified offeror and then negotiates fair and reasonable compensation. That is a separate method with its own rules, covered in qualifications-based selection for architect-engineer services. For anything other than A/E, price must stay in the evaluation.

What the file should record either way

2 CFR 200.318(i) requires records detailed enough to show the history of each procurement, including four elements: the rationale for the procurement method, the contract type selection, contractor selection or rejection, and the basis for the contract price. The method choice between an IFB and an RFP is exactly the first of those.

A short method-rationale entry might record:

• the procurement and the funding source;
• the method chosen and the regulation paragraph relied on;
• the facts that supported the choice, in plain sentences;
• any state or local rule that added a condition, and which rule governed; and
• the date, the person who made the decision and the version of the rule relied on.

That last point is easy to miss. Thresholds and rules change. The Uniform Guidance was revised effective October 1, 2024 (89 FR 30046), and on May 29, 2026 OMB published a further proposed rule (91 FR 32198) that would revise 2 CFR Part 200 again. As of October 2026 the Federal Register shows no final rule, so check its current status before relying on it. A file that does not record the rule and its date cannot show which rule it followed at the time.

Recording the method choice and moving on

A sound method decision is one you can explain in three sentences and support with the file. Write the rationale before the solicitation issues, cite the paragraph you are relying on, and note any local condition that applies. If a monitor or an unsuccessful bidder later asks why you used proposals rather than sealed bids, or the reverse, the answer should already be sitting in the record.

The Procurement Method Selector workbook is designed to record that choice alongside the rule relied on, with its citation and effective date. See the Procurement Method Selector page for what it is designed to compute and record. 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.