Why the Lowest Price Rarely Wins Government Tenders

Every tender season, capable contractors sit in pricing meetings shaving margin off a bid because "we have to be competitive." Then the award goes to a tenderer who was more expensive — sometimes considerably more expensive — and the debrief offers little explanation beyond "the successful tender represented better value for money."

Having chaired hundreds of government evaluations, I can tell you that outcome isn't an anomaly or agency politics. It's the evaluation model working exactly as designed. Government agencies do not award contracts to the lowest price. They award them to the best value for money — and I saw the non-cheapest bid win regularly. If you've never seen the mechanics from the inside, you're probably competing on the wrong variable.

### Your price isn't even in the room when your capability is scored

As I covered in [how panels actually run your evaluation], structured government evaluations run in two stages. The panel scores every qualitative criterion — organisational capability, personnel, technical capability and methodology, management systems, social procurement — before anyone sees a price. Your technical response is judged purely on its merits. Only after those scores are locked does the commercial assessment happen, and the two are combined under published weightings into a final ranking.

Here's the part that should change how you bid: in most weighted government evaluations, the non-price component typically carries the majority of the total score — commonly somewhere in the region of 60 to 70 per cent, depending on the procurement. Price, for all the anxiety it generates in bid rooms, is usually the minority share of the decision.

### The maths of losing cheaply

A simplified illustration shows how this plays out. Take an evaluation weighted 60 per cent non-price, 40 per cent price, and two tenderers:

Contractor A submits the cheapest conforming price and a competent, unremarkable technical response — the kind that meets requirements without building real confidence. It earns middling scores across the qualitative criteria.

Contractor B prices about 15 per cent higher, and submits a technical response that is specific to the project, evidences every claim, and confronts the delivery risks head-on. It scores a couple of points higher on the scale across the heavily weighted criteria.

Contractor A wins the price component outright — the cheapest conforming price typically earns the maximum price score, with more expensive bids scoring proportionally less. But B's advantage on 60 per cent of the model outweighs A's advantage on 40 per cent of it, and B ranks first overall. A was never really in the contest: its fate was sealed in stage one, before its price was opened.

That is the pattern I saw repeatedly from the chair. The lowest-priced tender loses whenever its technical scores sit at "satisfactory" and a competitor demonstrates even marginally stronger capability. In a weighted model, a one-point difference on a heavily weighted criterion is not marginal — it compounds across the calculation, and a tenderer who is consistently one point stronger can lock in first place before price is even considered.

### What a low price actually says to a panel

Here's the perspective tenderers almost never hear: from the chair, the cheapest bid was rarely read as the best deal. It was read as a question.

A price conspicuously below the field usually meant one of two things. Either the contractor hadn't priced the work properly — which implies real risk in engaging them, because no agency wants a contractor struggling and suffering financially mid-delivery; that's how strained working relationships, disputes and delivery failures happen. Or the contractor knew their non-commercial response was limited, and was competing on price because it was the only variable left to them — which implies the same risk from a different direction.

The agency is always considering risk in its assessment, and your price is itself evidence. A strong submission at a sensible price reads as a well-run business that understands the work. A thin submission at a rock-bottom price reads as a problem the agency would be volunteering for. As long as the stronger tender's price sat within the budget envelope, I saw the higher price recommended without hesitation — repeatedly.

### What this means for margin

Follow the logic one step further and it gets commercially interesting. If stronger technical scores can outweigh meaningful price differences, then technical excellence doesn't just win contracts — it protects margin. The contractor who wins on capability doesn't need to be cheapest, which means they're winning work at sustainable prices while their competitors race each other to the bottom on a variable that carries the minority of the score — and that actively signals risk when pushed too low.

Cutting price is the most expensive way to become competitive, because you pay for it whether you win or lose. Lifting your technical scores costs you effort once, and pays on every subsequent tender.

### The honest caveat

None of this means price is decorative. Agencies operate within budget envelopes, and a price materially above market expectations or the project budget can justify setting aside a technically stronger tender in favour of the next-ranked one — value for money is a balance, not a formula that rewards gold-plating. The strategy this article argues for is not "price high." It's compete on technical excellence first, and price competitively rather than cheapest — because the model is built to reward exactly that combination, and it is not built to reward price cuts from tenderers whose capability scores are ordinary.

### Where the points actually are

If the majority of the decision is made before your price is read, the question stops being "how low can we go?" and becomes "where do we gain a point?" In my experience the answer is rarely *more* content — it's more specific, evidenced, project-relevant content on the criteria that carry the heaviest weightings, and the elimination of the quiet doubts that surface when a panel moderates. The most common of those doubts — the recurring patterns that hold good submissions at "satisfactory" — are the subject of another article in this series.

The uncomfortable truth is that most tenderers never find out what their submission scored at all — consensus scores are never released to tenderers, and the debrief rarely offers more than "competitive" or "not competitive." The winners treat scoring as something to engineer before lodgement, because there is no finding out afterwards.