Best and Final Offers in RFP Evaluation: Shortlists, Orals and BAFO

When the file stops explaining itself

A grants manager is asked by a funder's monitor to explain why a third-ranked firm was invited back to present while a second-ranked firm was not. The scoresheets from the written round sit in one folder. The notes from the oral presentations are in an email chain, and the revised prices arrived as attachments that someone pasted into a new tab of the spreadsheet. The shortlist itself was set in a meeting, and nobody wrote down the cut line or who proposed it.

Nothing in that story requires bad intent. Each added round, whether a shortlist, orals or a request for final offers, is a decision point, and each decision point needs its own record. When the file shows only the written scores and the final award, a reviewer has to guess what happened in between.

This guide walks through how to set shortlist rules, score oral presentations and re-run price scores after final offers, so you can show why each firm was kept or cut.

What 2 CFR 200.320(b)(2) says about these steps, and what it leaves out

Under 2 CFR 200.320(b)(2)(i), a request for proposals must identify all evaluation factors and their relative importance. 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. Both provisions sit in the Uniform Guidance as revised effective October 1, 2024. Federal agencies could choose to apply that revision to earlier awards but were not required to, so check which version your award follows.

Neither provision describes a competitive range, an oral presentation or a best and final offer RFP step. The competitive range and final proposal revisions appear in the Federal Acquisition Regulation (48 CFR 15.306 and 15.307), which governs federal agencies' own purchases and is not written for grant recipients. The FAR now speaks of a "final proposal revision" rather than a best and final offer, though many issuers still use the older term. Do not treat any federal agency acquisition rule as binding on your organization unless your award, your funder or your own policy adopts it. Your written procedures, your funder or pass-through entity, and any state or local law set the steps. Where more than one set of rules applies, follow the stricter one, and cite the rule you rely on in the file by section and date.

The award basis still anchors everything. 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."

That is why added rounds should apply the factors and weights you announced rather than new ones.

Setting shortlist rules before any proposal is scored

A shortlist, sometimes called a competitive range determination, narrows the field before the costlier rounds begin. The rule for the cut belongs in your written procedures, and where the solicitation announces it, the file should point to that language. Decide in advance whether the cut is a score threshold, a fixed number of firms or a natural break approved by the committee chair, and write down which.

Record three things for every firm at the cut: its score on each criterion, the rule that was applied, and a sentence or two of rationale. A firm that is dropped needs a reason a reviewer can read without having attended the meeting. The same applies to a firm that is kept despite scoring below one that was cut.

Two decisions are easy to forget. State whether price is opened before the shortlist is set, because that changes what the cut reflects. Set the tie rule in advance as well, so a tie at the line is resolved by a rule and not by whoever speaks first. Criteria and weights stay exactly as announced, as covered in our guide to weighted scoring for RFPs.

Scoring oral presentations as a separate, documented round

Treat orals as a new round with its own record, not as a conversation that quietly adjusts earlier scores. Before the first presentation, fix the criteria being scored, the rating definition for every point on the scale, and the questions every firm will receive. Giving each firm the same questions, the same time allowance and the same scoring form is what lets the file show equal treatment.

Decide and record whether oral scores replace the written scores on the same criteria, add to them, or cover only criteria the written proposal could not show. The choice should follow from the solicitation and your procedures. A vague carry-forward is where totals stop being reproducible.

Evaluators should score on their own before comparing notes. The consensus discussion should then end with a written rationale for each final score, as described in our consensus scoring guide.

If new people join for orals, such as a subject-matter advisor, collect their conflict-of-interest attestations first. 2 CFR 200.318(c) bars anyone with a real or apparent conflict of interest from taking part in the selection, award or administration of a contract supported by the federal award. That applies to a late addition as much as to the original panel.

Re-running price scores after a best and final offer RFP request

A request for final offers invites the firms still in the competitive range to revise their proposals, usually on price and sometimes on terms. Your procedures should say what may change, who sends the request, what deadline each firm gets and how a late response is handled. The request goes out from your office, and the file should hold a copy of exactly what each firm received and when.

Because the lowest evaluated price may change, every firm's price points must be recomputed, not only those of firms that revised. The common lowest-price formula is lowest evaluated price ÷ this offer's evaluated price × maximum price points. Here is a worked example with round numbers and 30 price points:

• Initial prices of $80,000, $100,000 and $125,000 yield 30, 24 and 19.2 points.
• After final offers of $76,000, $88,000 and $100,000, the lowest price is now $76,000. The three firms receive 30, 25.91 and 22.8 points.

The first firm's own points did not change, yet the other two moved because the baseline did. Our guide to the price scoring formula covers the arithmetic and the alternatives in more detail.

Keep two other records straight. Under 2 CFR 200.324(a), a cost or price analysis is required for every procurement transaction, including contract modifications, above the simplified acquisition threshold, and, as a starting point, independent estimates must be made before bids or proposals are received. Leave that original estimate unchanged when final offers arrive, and record any later update as a separate, dated entry. Treat alternates and options the same way in both pricing rounds, excluding them from the evaluated price consistently.

RFPManagement is designed so that a locked scoring round cannot be reopened, scoresheets stay hidden until the lock, and an append-only, hash-chained audit trail records the order of events. Staff enter revised prices by paste or CSV after receiving them elsewhere. The tool does not send the request or receive offers.

A final-offer round does not fit every selection. For architectural and engineering professional services, 2 CFR 200.320(b)(2)(iv) allows a qualifications-based method in which the most qualified offeror is selected without price as a selection factor, and fair and reasonable compensation is then negotiated. Federal agencies' own A/E selections follow the Brooks Act (40 U.S.C. 1101 and following sections). State qualifications-based selection laws vary, so check yours.

What the file should show for each round

2 CFR 200.318(i) requires records detailed enough to show the history of each procurement. They must include the rationale for the method, the contract type selection, the contractor selection or rejection, and the basis for the contract price. Shortlists, orals and final offers each touch the selection-or-rejection and price-basis elements. For each round, the file should hold:

• the rule or procedure the round followed, with its section and date;
• the criteria, weights and rating definitions fixed before scoring;
• each evaluator's independent scores and conflict attestation;
• the consensus rationale for each final score;
• the cut line, the tie rule and who confirmed the result;
• the final-offer request, receipt times and recomputed price points.

Our guide to RFP evaluation documentation shows how to organize these pieces. The file also matters after the award. Under 2 CFR 200.318(k), the recipient settles source evaluation, protests, disputes and claims arising from its procurements, so its own record is its response. GAO's fiscal year 2025 bid protest report (GAO-26-900695, December 12, 2025) names unreasonable technical evaluation, unreasonable cost or price evaluation and unreasonable rejection of a proposal as the most prevalent reasons for sustaining protests that year. Those figures describe federal agency procurements, not grant-recipient or local ones, but they show where evaluation records get challenged. A firm that asks for an explanation is better served by a clear record, as discussed in our guide to debriefing unsuccessful offerors.

Retention matters too. 2 CFR 200.334 sets three years from the final financial report unless an exception applies, and local public-records rules may require longer.

The Shortlist, Oral Presentation and BAFO Workbook is designed to record the shortlist cut-line and rationale, oral presentation scores and recomputed price points on final offers. It is available now on its store page. 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.