A Plain English Guide to BAFO for SME Bidders

What BAFO actually means

BAFO stands for Best and Final Offer. It is the final round in which shortlisted bidders are invited to submit a revised, sharpened offer after an earlier tender, some dialogue, or a set of clarifications. In practice it is the moment a contracting authority says: you have shown us your solution, now give us your best commercial and technical position so we can decide the award. Under the Procurement Act 2023 you will often see BAFO used within a competitive flexible procedure, where authorities have freedom to design rounds that suit the contract.

A few points are worth fixing in your mind before you respond:

• BAFO is a revision, not a brand new bid. You are refining what you already submitted, not rewriting it.
• Everything you offer must be deliverable, internally approved and defensible if the award is challenged.
• The published evaluation criteria still govern how you are scored, so re-read them before you touch a single number.
• Authorities use BAFO to compare final contenders on a common basis and to identify the most advantageous tender, not simply the cheapest.

The scale of the opportunity matters here. Across live tenders that publish a value, the median advertised contract value sits at £400k, and that figure is drawn from a wide sample. When you reach BAFO on a contract of that size, small errors in your final submission can cost you real money over several years, so the stakes justify careful attention. For the concise reference, KimonBids keeps a definition in its glossary. Read the glossary entry at /glossary/bafo.

Why authorities run a BAFO stage

Contracting authorities do not add rounds for fun. Each extra stage costs them time and effort too. When they call for a Best and Final Offer, they usually have specific reasons, and understanding those reasons helps you respond in a way that meets the buyer where they are.

The common motives include:

• Letting bidders improve or clarify their offers after an initial round, especially where earlier submissions were close on quality but varied on price.
• Comparing the final contenders on a genuinely level basis, with the same questions answered by everyone.
• Identifying the most advantageous tender rather than the lowest headline figure.
• Reducing uncertainty and delivery risk before they commit public money to an award.

That last point deserves emphasis. Government training on the competitive flexible procedure cautions that a BAFO stage can drive focus onto price and must be used carefully to avoid abnormally low tenders. In plain terms, an authority does not want a supplier who wins on a price so thin that delivery falls over in year two. So while you may feel pressure to slash your figure, the buyer is often just as worried about you cutting too deep.

That context should shape your judgement:

• If price is the stated weakness, address it, but show your workings so the reduction looks credible rather than desperate.
• If quality carries the higher weighting, protect it. A tiny price cut that damages your quality narrative is a poor trade.
• Read the award criteria carefully so you know exactly where the marks are, and where a change helps or harms you.

Knowing the buyer's motive turns BAFO from a guessing game into a targeted response.

What to do, and what to avoid, at BAFO

The difference between a strong BAFO and a weak one is rarely dramatic. It comes down to discipline: aligning your price with your delivery model, answering exactly what was asked, and removing anything that gives an evaluator a reason to mark you down.

A practical action list looks like this:

• Re-read the evaluation criteria and weightings before you change anything.
• Confirm whether price, quality or whole life cost carries the most influence.
• Make sure your final pricing is sustainable across the full term, not just attractive on day one.
• Align your written responses with your pricing model so the two tell the same story.
• Answer every mandatory question exactly as asked, in the format requested.
• Check for arithmetic errors, buried assumptions and hidden exclusions.

Just as important is the list of things to avoid:

• Do not assume BAFO means lowest price wins.
• Do not cut price so far that delivery becomes unrealistic.
• Do not introduce new promises you cannot evidence.
• Do not ignore social value, quality or implementation requirements.
• Do not leave inconsistencies between your pricing and your method statements.

One discipline that pays off repeatedly is a version check. If you tightened your response but forgot to update the matching cost line, an evaluator sees a bid that contradicts itself, and that reads as delivery risk. Keeping a reusable bid content library helps you pull consistent, pre approved wording into a BAFO fast, so you spend your limited window on the commercial thinking rather than rewriting boilerplate. A neat BAFO makes the evaluator's job easy, and an easy scoring experience tends to score well.

Worked example one, a facilities management contract

Imagine an SME bidding for a three year cleaning contract. Its initial tender priced the work at £240,000. Feedback during the process suggests price is the weak point, and the BAFO invitation confirms that quality remains weighted at 60 per cent and price at 40 per cent.

A disciplined BAFO response would look like this:

• Reduce the price to £228,000, but only after confirming the delivery model still holds at that figure.
• Keep staffing levels realistic rather than trimming hours the site genuinely needs.
• Show the productivity assumptions clearly so the saving looks planned, not fudged.
• Explain any innovation, such as a rota change or equipment upgrade, that lowers cost without lowering service.
• Leave mobilisation timescales unchanged unless the authority has explicitly permitted revisions.

Why does this work? The SME improves its price on the axis that was flagged as weak, while protecting the 60 per cent that carries the most marks. The reduction is evidenced, so it survives scrutiny. Contrast that with a supplier who simply lops off twenty thousand pounds with no explanation. The evaluator cannot tell whether that is genuine efficiency or a promise that will unravel, and uncertainty rarely scores well. The lesson is that a smaller, explained cut usually beats a larger, unexplained one.

Worked example two, a software contract

Now take an SME bidding for a digital case management system. Its initial tender was strong on quality but thin on implementation detail. The BAFO invitation asks for final pricing and a clearer explanation of the support model.

A sensible response:

• Keep the core solution unchanged, because it already scored well.
• Tighten service levels and support response times only where they are genuinely achievable.
• Offer a clearer training package so adoption risk drops.
• Break out licence, implementation and support costs separately rather than bundling them into one opaque figure.
• Avoid hidden extras that could make the bid look risky or incomplete.

Why this works: the SME reduces the evaluator's anxiety about delivery. It is not chasing a lower headline price; it is removing doubt. When 1,152 of the tenders in the recent sample were advertised under £100k, many software buyers are running lean projects where a transparent, low risk implementation plan is worth more than a marginal discount. A clean cost breakdown signals a supplier who has thought the delivery through, and that credibility is exactly what a BAFO is meant to surface.

Before you submit either type of bid, run a short final checklist:

• Does the final offer still meet every requirement?
• Is the price viable for the full contract term?
• Are your assumptions clear and consistent?
• Have you removed anything that could be scored negatively?
• Can you deliver exactly what you have promised, and have you answered every clarification point?

If you can answer yes to all of those, your BAFO is doing its job: clearer, stronger and more credible, not merely cheaper.