Why Good Contractors Lose Tenders They Should Have Won

The hardest part of chairing an evaluation is scoring a contractor you know is good, and watching the submission in front of you fail to demonstrate it.

It happens constantly. The company is capable, the price is competitive, the team is right for the job — and the document scores in the middle, because a panel can only assess what is written down.

Below are the seven failures that come up most often. None of them are about capability. All of them are fixable before lodgement, and none of them are fixable afterwards.

1. You answered the question you wished had been asked

A criterion says: "Demonstrated methodology for delivering the works while maintaining operational access for the adjoining facility."

The response describes the contractor's general construction methodology, thoroughly and well, and mentions operational access in one sentence near the end.

The panel is scoring the criterion as written. Everything that does not address it is, for scoring purposes, filler — and worse, filler pushes the material that does count further down the page, past the point where an assessor on their fourth submission of the day is reading closely.

The fix: before writing anything, restate each criterion and its assessment requirements as a list of questions. Then check that every question has an answer with a heading of its own. This is mechanical work, it takes an hour, and it is worth more than a week of polishing prose.

2. Your claims have nothing behind them

"We have extensive experience delivering complex civil works in live operational environments."

A panel member cannot score that above the middle of the band, because there is nothing to defend if a colleague pushes back. It is an assertion about yourself, and every competing submission contains a version of it.

The same content as evidence: two named projects, the client, the value, the specific operational constraint each one shared with this job, and what your approach was.

The distinction is not stylistic. In moderation, consensus scores get argued out, and the panel member advocating for you needs something to point at. Give them a page number.

The fix: read every sentence that describes your capability and ask what an assessor would point at. If the answer is only "the sentence", it is not yet evidence.

3. The methodology is about your company, not about this job

This is the most common reason a competent submission lands mid-band on the criterion that usually carries the most weight.

Generic methodology is not badly written — it is usually the most polished section in the document, because it has been refined over dozens of submissions. That is precisely the problem. Refined-over-dozens means it contains nothing about the site the panel is standing on.

Meanwhile a competitor has written three paragraphs about the specific access constraint, the specific stakeholder, and the specific sequencing problem this job has. Their prose may be worse. Their score will be higher, because the panel can see they read the documents.

The fix: budget the majority of your writing time for the highest-weighted criterion, and spend it on specificity rather than polish. Name the constraints the tender documents describe. If you cannot name three things about this project that would not apply to any other, you have not written a project-specific methodology.

4. You missed a sub-requirement

Criteria frequently carry assessment requirements underneath them — sometimes as bullets, sometimes as a schedule elsewhere in the documents, sometimes buried in a paragraph that begins "Tenderers should also address…".

Miss one and you do not lose the criterion. You lose a portion of it, silently, with no mechanism to recover the points. Nobody tells you. It surfaces only in the written justification, which you never see.

This is also a place where the tender's own numbering can betray you. Requirements are not always listed in a tidy sequence — schedules get referenced from three places, letters and numbers skip, and an item that appears once in an annexure carries the same weight as one on the front page.

The fix: build a compliance matrix that lists every criterion, every assessment requirement, every schedule and every stated "must address" — with the page of your response where each is answered. It is tedious and it catches more lost points than any amount of writing skill.

5. Addenda did not make it into the response

Tenders change after they are issued. Scope gets clarified, dates move, a criterion is reworded, an additional schedule is issued.

Responses are usually well underway by then, and the addendum arrives as an email attachment on a Wednesday afternoon. It gets acknowledged on the form and never worked back into the content — so the submission answers a version of the tender that no longer exists.

Panels notice this immediately, because they are reading against the current documents. It reads as carelessness, and it costs credibility across every criterion, not just the one affected.

The fix: treat every addendum as a rework trigger, not a filing task. Re-check the criteria, the schedules and the parts of your response the change touches, and record that you have.

6. The evidence exists but the panel cannot find it

Assessors are reading multiple submissions of several hundred pages each, against a deadline, usually alongside their actual job.

If your answer to criterion 3 is spread across a narrative in section 4, a drawing in appendix B and a table in a separate attachment with no cross-references, some of it will not be found. Not because the assessor is careless, but because they are on their fourth document and yours requires assembly.

Navigability is not presentation polish. It is a scoring factor, and it is the cheapest one to fix.

The fix: mirror the tender's criteria structure in your headings, use the tender's own language and numbering, and cross-reference every attachment from the narrative that relies on it. Make it possible to score you without hunting.

7. Nobody read it as an evaluator would

The response is reviewed for typos, for brand consistency, for pricing accuracy, and sometimes by the estimator who wrote most of it.

It is almost never read the way it will actually be read: cold, by someone who does not know your company, with the criteria in front of them and a scoresheet to fill in, immediately after reading three competitors.

That reading produces completely different feedback from an internal review. Internal reviewers know what you meant. Evaluators only know what you wrote.

The fix: have someone score it against the published criteria before you lodge — someone who did not write it, using the criteria and nothing else. If they cannot find the evidence for a criterion in under a minute, the panel will not either.

The pattern underneath all seven

Every one of these is the same failure in a different costume: a gap between what the contractor knows and what the submission demonstrates.

Capability is not the constraint for most contractors losing tenders. Demonstration is. And demonstration is a document problem — which means it is a solvable one, and it is solvable before you lodge rather than discovered eight weeks later in a debrief that comes too late to matter.

Getting the read you cannot get internally

That last fix — someone scoring your response the way a panel will, before you lodge — is what ProcureHQ was built to give you.

The Digital Evaluation Committee assesses your response against the evaluation criteria extracted from your own tender documents, using an Evaluation Engine built on how government panels assess submissions, including circa 150 recurring Decision Signals. You get a current score and a potential score, findings for each criterion — strengths, weaknesses and missing evidence — the evidence the assessment relied on, and a recovery plan that tells you where the points are.

Then you revise and run it again, before lodgement, while it can still change the outcome.

We assess the non-price criteria; price and value for money remain the agency's judgement. And we do not run a line-by-line compliance check against your specifications — the assessment is scoped to the published criteria and assessment requirements, read in the context of the tender's scope and technical documents.

Your first tender is free. One full evaluation and one complete Smart Submission Blueprint per organisation, at no cost. If the score comes back lower than you expected, you have found that out at the only point where it is still useful.

---

Frequently asked questions

Should I ask for a debrief after an unsuccessful tender? Yes — always request one. It will not give you the scoresheet, and it arrives after the decision, but it tells you something about how your submission read. Ask specifically which criteria you scored weakest on and what evidence would have been expected.

Does a lower price always win government tenders? No. Most Australian government procurements assess price alongside weighted non-price criteria and reach a value-for-money judgement. A low price against weak non-price scores loses regularly.

How much of my tender writing time should go into methodology? Disproportionately more than the other criteria. It is frequently the highest-weighted non-price criterion and produces the widest spread of scores between tenderers, which makes it the highest-return section in the document.

Can I fix a submission after lodgement? No. Once lodged, your submission is what it is — clarifications may be sought at the agency's discretion, but you cannot add evidence you left out. Everything in this article has to be done before the deadline.