The short answer
A BAFO (best and final offer) is the revised proposal a buyer requests from shortlisted bidders after negotiations, on the understanding that it intends to award without another round. In US federal rules the term was replaced in 1997 by “final proposal revision” (FAR 15.307(b)). Prepare by setting a walk-away floor first, trading scope that exceeds the requirement before cutting price, keeping compliance and assumptions intact, and documenting every change in a cover letter table.
Key takeaways
- “Final” means final, mostly: A federal request for final proposal revisions must say the government intends to award without obtaining further revisions. Commercial buyers aren’t bound by that, but plan as if they are.
- Floor before figures: Calculate your walk-away price before the request arrives. A BAFO deadline is a terrible time to discover your delivery cost.
- Trade scope before margin: Removing features that exceed the minimum often recovers more price than a discount, and US federal rules explicitly allow the buyer to suggest it.
- Change the price, not the promise: Every price change needs a matching narrative change, and every untouched mandatory requirement must still be met.
- Price is the usual loss reason: Loopio’s 2026 benchmark says price has been the primary reason for bid losses since 2021, so expect the BAFO conversation to be about money.
- The catch: You may never get a BAFO. Many buyers award on first-round proposals, so your initial price has to be one you’d be happy to win at.
What a BAFO is, and where the term came from
“Best and final offer” was the old US federal name for the last written revision bidders submit after negotiations. The 1997 rewrite of FAR Part 15 (FAC 97-02, effective October 10, 1997) replaced it. A 1999 GAO bid protest decision describes the change plainly: the language at FAR 15.307(b) “substitutes the term ‘final proposal revision’ for the previously denominated ‘BAFO’” (GAO B-282373, June 22, 1999).
The old name stuck anyway. Commercial buyers, state and local agencies, and procurement consultants still say BAFO, and so do most bid teams. Whatever the label, the mechanics are the same: you’ve been shortlisted, the buyer has told you what it doesn’t like, and you get one more written chance to fix it.
How US federal final proposal revisions work today
The codified FAR at FAC 2026-01 (effective March 13, 2026) still describes the process in two sections.
FAR 15.306(d) covers discussions, which happen only with offerors in the competitive range. The primary objective is “to maximize the Government’s ability to obtain best value.” At a minimum the contracting officer must raise deficiencies, significant weaknesses and adverse past performance information you haven’t had a chance to answer. Two details matter for pricing:
- Under 15.306(e)(3), the government can’t reveal a competitor’s price, but “may inform an offeror that its price is considered by the Government to be too high, or too low, and reveal the results of the analysis supporting that conclusion.”
- Under 15.306(d)(4), where the solicitation gave credit for exceeding mandatory minimums, the government may suggest that proposals “would be more competitive if the excesses were removed and the offered price decreased.”
That second point is effectively a scope-for-price trade written into regulation. Listen for it.
FAR 15.307(b) then closes the round: “At the conclusion of discussions, each offeror still in the competitive range shall be given an opportunity to submit a final proposal revision.” The contracting officer sets a common cut-off date, and the request must say the revisions are to be in writing and “that the Government intends to make award without obtaining further revisions.”
The RFO version. The FAR is being rewritten under the FAR overhaul (RFO). The Part 15 model deviation text, issued September 30, 2025, renames discussions as negotiations and moves the process to 15.204-2. When negotiations finish, the offeror gets “an opportunity to submit a proposal revision” and a notice requiring it in writing and stating the government intends to award without further revisions. The common cut-off date becomes “an equal amount of time” for each offeror still in the competitive range. Agencies that adopted the deviation will cite the new numbers, so check which text your solicitation references.
And you might not get one at all. The standard instruction at FAR 52.215-1(f)(4) says the government “intends to evaluate proposals and award a contract without discussions,” and therefore the initial proposal “should contain the offeror’s best terms from a cost or price and technical standpoint.” The government RFP guide has more on that sequence.
Commercial BAFO rounds are looser
Private-sector buyers don’t follow the FAR, so a commercial BAFO can look like almost anything: an email asking for “your best number by Friday,” a formal second-round template, a reverse auction, or three “final” rounds in a row. Some will share a target price. Others will tell you that you’re “not the cheapest” without saying by how much.
Before you respond, ask three procedural questions in writing:
- What can change? Price only, or scope, terms and assumptions too?
- What format? A revised pricing workbook, a full replacement proposal, or a letter?
- Is this the last round? You won’t always get a straight answer, but the question costs nothing.
If the buyer won’t say whether more rounds are coming, assume this one is final. Holding back a concession for a round that never happens is how you lose on price with margin still on the table.
Set the walk-away floor first
The floor is the lowest total price you’ll accept, decided before emotion and deadline pressure set in. A simple version:
Floor = fully loaded delivery cost / (1 minus minimum acceptable margin)
Fully loaded means everything you’d actually spend over the contract term: people, hosting, third-party licences, implementation, travel, support, and any subcontractor costs. The minimum margin is a finance decision, not a bid team guess.
Write the floor down, get it signed by whoever owns pricing authority, and don’t reopen it during the BAFO unless the scope changes. If the scope changes, recalculate cost first, then the floor. The bid/no-bid framework uses the same floor as a kill gate.
Price levers versus scope trades
There are two ways to lower the number. Price levers reduce what you charge for the same scope. Scope trades remove or change what you deliver, which lowers your cost as well as the price.
| Move | Type | Margin effect | Watch for |
|---|---|---|---|
| Straight discount | Price lever | Falls by the full cut | Looks arbitrary if large; invites another round |
| Prepayment or multi-year commitment discount | Price lever | Falls, offset by cash and term certainty | Buyer must be able to prepay or commit |
| Lower rates on later years or option periods | Price lever | Falls in out-years | Can look unbalanced (see below) |
| Remove features that exceed the minimum | Scope trade | Often protected | Must not touch a mandatory requirement |
| Change delivery mode (remote instead of on-site) | Scope trade | Often protected | Check the RFP doesn’t require on-site |
| Narrow service levels on non-critical environments | Scope trade | Often protected | Restate the SLA table everywhere it appears |
| Shift tasks to the buyer | Scope trade | Protected | Becomes a new assumption; buyer must agree |
A warning about loading cuts onto a few lines. In US federal evaluations, FAR 15.404-1(g) defines unbalanced pricing as an acceptable total where one or more line items are “significantly over or understated,” notes it “may increase performance risk,” and says an offer may be rejected if the imbalance “poses an unacceptable risk to the Government.” Spread reductions where the cost reduction actually sits.
What must not change
A BAFO is a revision, not a new proposal. Run this list before anything goes out:
- Mandatory requirements: Every pass/fail item in the compliance matrix is still met after the scope trades.
- Assumptions: Nothing new appears without being flagged in the cover letter, and nothing the buyer rejected during negotiations reappears.
- Named people and key personnel: If the original proposal named them, the BAFO doesn’t quietly swap them out.
- Evaluation-scored strengths: If a feature you’re removing earned evaluation credit, you’ll lose that credit. Decide if the price gain is worth it.
- Validity period and terms: Restate the offer validity date; don’t let the original one lapse mid-negotiation.
Keep the narrative and the price consistent
The most common BAFO error is a price that changed while the words didn’t. The pricing workbook says remote training; the implementation section still promises three on-site workshops. Evaluators read both.
For every row in your change table, find every page that mentions it. Search the proposal for the feature name, the service level, the head count and the year. Update each mention or list the replacement pages. The pricing spreadsheet guide has a reconciliation routine that works for BAFOs too, and the version control guide covers keeping the replaced pages straight.
A BAFO cover letter structure
Keep it to two pages. Evaluators should understand what changed without opening the workbook.
- Header: Buyer, RFP reference, “Final proposal revision” or “Best and final offer,” date, and validity period.
- Summary paragraph: Revised total price, the original total, and one sentence on how you got there (“by removing optional scope and moving training to remote delivery”).
- Change table: Item, original, revised, reason, proposal pages or workbook cells affected.
- Compliance statement: All mandatory requirements remain met; list any requirement where your approach changed.
- Assumptions and exceptions: The full current list, with changes marked.
- Responses to negotiation points: One line per weakness or deficiency the buyer raised, pointing to where it’s fixed.
- Replacement documents: File names of the revised workbook and replaced pages.
- Signature: Someone authorized to bind the company.
Leave out complaints about the process, comparisons with competitors, and new marketing claims. The BAFO isn’t the place to introduce a feature the evaluators haven’t scored.
Worked example: An illustrative price and scope trade
Say you’ve bid an illustrative 3-year software and services contract at $1,200,000 total. Your fully loaded delivery cost is $810,000, so your margin is $390,000, or 32.5 percent. Finance has set a minimum margin of 25 percent, so your floor is $810,000 / 0.75 = $1,080,000. During negotiations the buyer tells you your price “is considered too high” and that a reporting module you included goes beyond the requirement.
Option A is a straight discount to $1,034,000. Cost stays at $810,000, margin drops to $224,000, or about 21.7 percent. That’s below the floor. No.
Option B combines trades:
| Change | Type | Price change | Cost change |
|---|---|---|---|
| Remove optional reporting module (exceeds minimum) | Scope trade | minus $60,000 | minus $45,000 |
| Move three on-site training sessions to remote | Scope trade | minus $36,000 | minus $30,000 |
| Standard support tier on the test environment only | Scope trade | minus $30,000 | minus $24,000 |
| Discount for annual upfront payment | Price lever | minus $40,000 | $0 |
| Total | minus $166,000 | minus $99,000 |
Revised price: $1,200,000 minus $166,000 = $1,034,000. Revised cost: $810,000 minus $99,000 = $711,000. Revised margin: $323,000, or about 31.2 percent. The new floor at 25 percent is $711,000 / 0.75 = $948,000, and the revised price clears it by $86,000.
Same headline price as Option A, a 13.8 percent reduction, with margin down 1.3 points instead of 10.8. Before it goes out, three checks: the RFP doesn’t mandate on-site training, the test environment SLA isn’t a scored requirement, and the buyer’s finance team can actually pay annually in advance. Each change then gets a row in the cover letter and an edit everywhere the old scope appears in the narrative.
Where software helps (and where it doesn’t)
Most RFP response tools are built for the narrative side and stop short of pricing. Arphie, for example, lists no capture or pricing modules among its limitations, which is a fair description of much of the AI-drafting segment. For the BAFO, software earns its keep in three places: keeping quote and narrative in sync, controlling who can approve a price, and producing a clean revised document fast.
XAIT pairs XaitCPQ with its proposal authoring, so complex quotes and the narrative stay in step, which is exactly the consistency problem above. QuoteWerks offers centralized quoting with controlled pricing, approvals and a document audit trail, though it can’t import or answer an incoming RFP. DealHub brings configure-price-quote with guided selling for configurable products, but it’s built for outbound quotes, not inbound RFPs. For professional-services firms, Ignition offers AI price insights it says are built on real proposal data. Browse the CPQ tag for the rest.
What no tool can tell you is where the buyer’s real number sits, whether this is truly the last round, or whether a reference logo is worth five points of margin. That’s negotiation judgment, and it stays with the deal owner and finance.
If you see one or two BAFOs a year, skip new tooling. A locked copy of the original workbook, a change table in a spreadsheet, and a second person checking every narrative mention will do the job.
Sources
- Federal Acquisition Regulation; Part 15 Rewrite; Contracting by Negotiation and Competitive Range Determination; Final Rule, Federal Register Vol. 62, No. 189 (September 30, 1997), govinfo.gov, accessed October 2026
- Spectrum Sciences & Software, Inc., B-282373, US Government Accountability Office, June 22, 1999, accessed October 2026
- 15.306 Exchanges with offerors after receipt of proposals, Federal Acquisition Regulation (FAC 2026-01, effective March 13, 2026), acquisition.gov, accessed October 2026
- 15.307 Proposal revisions, Federal Acquisition Regulation (FAC 2026-01), acquisition.gov, accessed October 2026
- 15.404-1 Proposal analysis techniques, Federal Acquisition Regulation (FAC 2026-01), acquisition.gov, accessed October 2026
- 52.215-1 Instructions to Offerors: Competitive Acquisition, Federal Acquisition Regulation (FAC 2026-01), acquisition.gov, accessed October 2026
- FAR Overhaul: Part 15, RFO model deviation text (issued September 30, 2025), acquisition.gov, accessed October 2026
- Average RFP Win Rates & More: 38 Proposal Statistics to Know in 2026, Loopio, March 26, 2026, accessed October 2026