Your Tender Lost. It Wasn't Your Capability. 

Most contractors don’t lose tenders because they can’t do the work. They lose because their submission doesn’t clearly show that they can.

​

There’s a difference between saying you’re capable and proving it. Evaluators are trained to score one of those things. It’s not the claim.

​

This is the most common issue I see when I review unsuccessful submissions. Good businesses, solid track record, plenty of relevant experience. But the way it’s written doesn’t give the evaluator anything they can actually score.

 

What evaluators are really doing when they read your tender

When someone is assessing your submission, they’re not reading it to get a feel for your business. They’re working through a scoring sheet.

​

For each criterion, they’re looking for clear evidence that meets a defined standard. Something they can point to, justify, and allocate marks against. If they can’t find it, they can’t score it.

​

It doesn’t matter how capable you are in reality. If it’s not clearly written in the submission, it doesn’t exist in the evaluation.

​

That’s why the job of a tender response is not just to explain what you do. It’s to make it easy for the evaluator to find and score the right information. Clear structure, direct language, and alignment to the question all matter. If something is buried, vague, or implied, it will be missed.

​

The pattern that costs marks

I recently reviewed two submissions from a Canberra based construction contractor that had been delivering ACT Government education work for over ten years. They had strong compliance, real project history, and a solid hit rate across panel work. The capability was clearly there.

​

But in one submission, every project description relied on language like “comprehensive delivery”, “successful outcomes”, and “demonstrated our capability”. The projects listed the value and duration, which is a good start, but there were no actual delivery outcomes.

​

Nothing about programme performance. Nothing about how variations were managed. Nothing that showed what actually happened on the job.

​

That submission lost.

​

Not because the contractor wasn’t capable, but because the evaluator had nothing they could confidently score. “Successful delivery” doesn’t mean anything in an evaluation context. Every bidder says the same thing, so it doesn’t help you stand out.

​

If you’re trying to improve your overall approach, this is covered in more detail in how to win government tenders.

​

What changed and why it worked​

On the next submission, the same contractor changed how they presented their past performance.

Instead of general statements, they included specific detail. Each project listed the client, key personnel, value, duration, and most importantly, what actually happened during delivery.

​

One project included a major structural redesign that was managed without impacting the programme. They also included a full variation register showing the value and reason for each variation.

​

That is the kind of information an evaluator can work with. It’s specific, it’s credible, and it can be assessed against the criteria.

​

That submission won.

​

Same contractor, same capability. The difference was that this time, the evidence was clearly in front of the evaluator.

​

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

How to fix this in your next submission​

A simple way to test your own content is to strip out the generic language.

​

Take one of your project descriptions and remove words like “successful”, “high quality”, or “delivered to a high standard”. Then read what’s left.

​

If there isn’t much there, that’s where you’re losing marks.

​

For example:

​

Claim:

“We successfully delivered the project to a high standard and the client was very satisfied.”

​

Evidence:

“Delivered over 8 weeks with three client requested design variations, including a structural redesign. No impact to programme. Variations delivered within approved budget.”

​

One of those gives the evaluator something they can score. The other doesn’t.

​

It’s not just your project examples​

The same issue shows up across most submissions.

​

Methodologies often describe intent instead of actual steps. Risk sections talk about general approaches instead of specific controls. WHS responses describe company systems without linking them to the actual site and the real risks involved.

​

If your content could be copied into another tender without changing the detail, it’s too generic. And if it’s too generic, it won’t score well because it doesn’t prove anything about this job.

​

The same principle applies to capability statements. If they rely on general claims instead of specific evidence, they won’t stand out. Here’s how to write a capability statement that actually works.

​

The issue isn’t capability. It’s consistency​

​The contractor in this example didn’t suddenly become more capable. What changed was how clearly and consistently that capability was presented.

​

When the evidence was specific, structured, and easy to find, the submission competed well. When it wasn’t, marks were left on the table.

​

That’s what most businesses are dealing with. Not a capability problem, but a presentation problem.

​

If your submissions depend on how much time you have that week, or who happens to be writing it, the result will always be inconsistent.

​

If you want to understand where you’re losing marks​

If you’re not sure where your submissions are falling short, the YCM 8 Point Tender Health Check is a good place to start. It takes a few minutes and will highlight where evidence gaps are most likely costing you points.

​

If you’d rather put a proper system in place so your capability is presented clearly every time, you can get in touch and we can talk through it.

​