The Government Tender Evaluation Process: How Agencies Actually Score Your Submission

What actually happens to your tender after you lodge it? A former evaluation chair walks through the process most tenderers never see.

Lewis Heard, Founder, ProcureHQ
6 min read

15 years in government procurement. Hundreds of competitive tender evaluations chaired.

Your team spent six weeks and tens of thousands of dollars preparing the submission. You lodged it four minutes before the deadline, and then — silence. Somewhere between that moment and the award letter, a small group of people read your tender, formed a view about your business, and put a number on it.

Most tenderers never see that process. I spent about fifteen years inside it, chairing hundreds of competitive evaluations for government infrastructure and services procurements. This article explains how it actually works — because almost every avoidable tender loss I've seen traces back to a misunderstanding of what happens in that room.

### Who actually reads your tender

Government tenders are typically assessed by an evaluation panel — sometimes called a Submission Evaluation Committee — of an odd number of members, most commonly three, so no decision can deadlock. Panel members are usually a mix of technical, delivery and procurement people who know the project intimately.

Two things about this group matter more than anything else you'll read today.

First, they score independently before they ever discuss your tender. Each member reads every submission alone and forms their own scores against the published criteria. Only then does the panel meet to moderate — comparing scores, debating differences, and settling a consensus position. In my experience, those disagreements were rarely settled by force of argument. They were settled by evidence — most often one evaluator pointing to something in the submission the others had missed. There is an enormous amount of information for a panel to digest in a competitive evaluation, and even diligent evaluators miss things. The organisations that had tendered and won before clearly understood this: they made the information that mattered most impossible to miss — readily readable, exactly where an evaluator would look for it. If your strongest evidence is buried, you're relying on one evaluator finding it and arguing your case to the others.

Second, they can only score what's on the page. Panels are not permitted to assume capability, fill gaps from reputation, or ring you up to ask what you meant. This is not a theoretical constraint. I watched very capable contractors — organisations the panel knew could deliver — miss required documents, leave out CVs for nominated personnel, or submit programs that made no allowance for the agency's review periods even though the tender documents expressly required it. That last one is quietly fatal: a program that ignores mandated review periods is inherently incorrect, and it tells the panel the contractor hasn't properly read the documents they're bidding under. The committee knew these organisations were capable. We could only assess what was presented. It was never the agency's responsibility to get a contractor across the line — and we could not show preference, or we'd rightly be accused of treating one tenderer better than another.

### The process runs in two stages — and the order protects you

Nearly every structured government evaluation follows the same broad sequence.

Stage one: the non-price assessment.** The panel first checks any mandatory pass/fail requirements — prequalifications, accreditations, minimum experience thresholds, required certifications. There is no partial credit here; you pass or you're out. Then the panel scores your submission against the qualitative evaluation criteria — typically covering organisational capability, personnel, technical capability and methodology, management systems, and social procurement — **without seeing your price.

Stage two: the commercial assessment. Only after the technical scores are settled does the panel evaluate pricing and combine the two into a final ranking.

That sequencing is the single most underappreciated fact in government tendering. Your technical response is judged purely on merit, uncontaminated by your price. Which means a genuinely superior technical submission can justify a higher price — the evaluation model is explicitly designed to allow it. Agencies award on value for money, not lowest cost, and in weighted evaluations the non-price component typically carries the majority of the total score. (Why the cheapest bid so rarely wins is a big enough subject that it gets its own article in this series.)

### What a score actually measures

Most agencies score qualitative criteria on a defined scale — commonly zero to ten — with written descriptions of what each level looks like. The detail varies, but the underlying logic doesn't: every score is a measurement of evaluator confidence.

A middling score doesn't mean your submission was bad. It usually means it was fine — compliant, competent, and unconvincing. In my experience the majority of competitive submissions cluster in the middle of the scale, and what separates them from the small group at the top is not writing quality or page count. It's that the top scorers removed the panel's uncertainty: every claim was backed by specific, verifiable evidence; every risk the panel was privately worried about had already been identified and addressed; and everything was explicitly connected to *this* project rather than projects in general.

Having sat through more moderation discussions than I can count, evaluators are consistently asking five questions of every submission: Will this organisation actually deliver? Have they understood and addressed the real risks? Is this value for money across the life of the project — not just the cheapest number? Does it comply with everything we asked for? And is any of this substantiated, or are we being asked to take it on faith?

Every paragraph of your tender either helps answer one of those questions or it's costing you attention.

### Where good tenders quietly lose

Losses at evaluation are rarely dramatic. In moderation, doubt shows up in quiet phrases — "I had some concerns here," "this felt generic," "I couldn't find where they addressed X." Each of those moments shaves points, and in a weighted model, one point on a heavily weighted criterion can decide the outcome before price is even opened.

The patterns are remarkably consistent: experience listed but never connected to the project at hand; methodologies that could have been written for any project anywhere; risks downplayed instead of confronted with credible mitigations; claimed accreditations without evidence; key information buried where a time-poor evaluator won't find it. Remember the volume problem — a panel digests thousands of pages across a field of submissions. None of these issues make a submission non-conforming. All of them erode confidence — and confidence is the currency the entire process trades in.

### After the decision

Once evaluation concludes, the successful tenderer is engaged and the others are notified — usually only after the contract is executed. And here is the fact that surprises tenderers most: the panel's consensus scores are never divulged. Not at award, not at debrief, not ever. No organisation is ever truly told how it performed against each evaluation criterion — the feedback that does come back is typically as vague as "competitive" or "not competitive." Most agencies offer every tenderer a debrief, and used well it remains the most underused source of competitive intelligence in the industry — but even the best-run debrief operates inside that constraint. How to actually extract value from one is another article in this series.

### The gap between knowing and scoring

Here's the uncomfortable part. Understanding this process is necessary — and not remotely sufficient. The panel doesn't score what you know about evaluation. It scores what your submission demonstrates, criterion by criterion, under the published weightings, through the eyes of people trained to distrust unevidenced claims.

That's the gap most tenderers can't see from the outside: the distance between a submission that *feels* strong to the team that wrote it and one that *scores* strong with the panel that reads it. Closing it means evaluating your own tender the way a panel will — before you lodge, while there's still time to fix what they'd mark you down for.

This article reflects the author's professional experience and general observations of government procurement practice in Australia. It is provided for general guidance only and does not represent the views, policies or official position of any government agency. Evaluation processes, criteria and weightings vary between agencies and procurements — always review the specific Request for Tender documentation applicable to each opportunity. It is not legal, commercial or procurement advice.

This is the evaluation lens ProcureHQ's Digital Submission Evaluation Committee applies to your tender before you lodge — so you see how you're likely to score while there's still time to change it.

Read a complete sample report before you sign up.

A full 15-page fictionalised example generated by the live engine — opens instantly when you submit your email.

Related insights