Most losing bids do not lose because they were bad. They lose because they were not written for the people who score them. Evaluators are working through a stack of submissions against a defined rubric, on a deadline, with limited tolerance for guesswork. Understanding how that rubric works — and how evaluators actually use it — is the difference between a bid that places and one that wins.
This is not a secret. It is documented in every formal procurement process, public or private. The reason so many bids miss the mark is not that the rules are hidden; it is that bidders rarely read the rules with the same attention they read their own answers.
Evaluators score bids against a rubric, not a vibe
The first thing to internalise is that an evaluator’s job is to assign a score, not to form an opinion. In serious procurement — public sector, regulated industries, large corporates — every bid is read against a published evaluation framework. There is a list of criteria, a weight against each, and a scoring scale. Evaluators sit down with that framework and a copy of the bid, and they work through it section by section.
What that means in practice is that your bid is not being read as an essay. It is being read as a series of answers, each tied to a specific criterion, each contributing a measurable amount to the final score. A beautifully written passage that does not map cleanly to a criterion may not earn a single mark. A plain but precisely targeted answer can sweep the section.
This is why winning bids often look less polished than losing ones. Polish is invisible to the scoring matrix. Coverage is not.
What the rubric actually contains
A typical evaluation framework has three or four layers. It is worth understanding each, because the layer you are in determines what the evaluator is looking for.
Mandatory or pass/fail criteria. These are the first filter. Insurance certificates, financial accounts, certifications, declarations of conflict, eligibility statements. Get any of these wrong and the bid is rejected before the substantive scoring begins. It does not matter how good the rest of the response is. Evaluators have no discretion at this stage.
Technical or quality criteria. This is where most of the scoring lives. Methodology, experience, team, approach, quality assurance, risk management, project plan, references. Each criterion has a weight, and each has a scoring scale — usually 0 to 5 or 0 to 10, with descriptions for each level.
Commercial criteria. Almost always price, sometimes alongside other measures like value engineering or whole-life cost. Commercial scoring is usually formulaic, not subjective. The lowest compliant price scores full marks, and other prices are scored proportionally.
Social or strategic criteria. Increasingly common, especially in public sector procurement. Local employment, environmental impact, accessibility, diversity, community benefit. The weighting here has grown steadily over the last decade.
The relative weights — say, 60 per cent quality, 30 per cent price, 10 per cent social value — tell you exactly where the bid will be won or lost. If quality is weighted at 60 per cent, that is where to spend your time. Many bidders spend disproportionate effort on price when the rubric is telling them, in plain numbers, that quality is twice as important.
How a scoring matrix actually works
The scoring scale is the part most bidders ignore, and it is the part most evaluators rely on. A typical scale looks like this:
- 0 — No response, or response fails to address the criterion.
- 1 — Poor. Response addresses the criterion but raises significant concerns.
- 2 — Adequate. Response addresses the criterion but with minor concerns.
- 3 — Good. Response addresses the criterion fully, with no concerns.
- 4 — Very good. Response addresses the criterion fully and provides additional evidence of capability.
- 5 — Excellent. Response addresses the criterion fully, with strong evidence and clear added value.
Notice what the difference between a 3 and a 5 actually is. It is not better writing. It is evidence and added value. An evaluator giving a 5 is not saying “this was nicely written.” They are saying “this answer demonstrably exceeds what was asked for.” Bidders who write fluently but stop at the question are leaving marks on the table.
Notice also what an evaluator cannot do. They cannot award marks for things you did not say. If you delivered a similar project successfully but did not mention it, you get no credit. If you have a risk management process but did not describe it, you get no credit. Bids are scored on the page, not on the company.
What evaluators are bored of seeing
Sit through enough evaluation panels and patterns emerge. There are a handful of bid habits that consistently fail to earn marks, and a handful of patterns that consistently do.
The most common failure is bidders restating the question. The brief asks “describe your approach to quality assurance.” The bidder writes a page about how quality assurance is important. Important is not the question. The question is what you specifically do. Evaluators read this kind of response and award the minimum.
A related failure is the generic methodology section. A long account of project management practice that does not reference the actual project, the actual client, or the actual constraints. The evaluator can tell, because the section reads exactly the same as the section in the last three bids they scored.
The third common failure is unsupported claims. “We have extensive experience in this sector.” Compared to what? Evidenced how? Quantified how? An unsupported claim gets you maybe a 2. A claim with two named projects, two client references, and a sentence on outcomes can earn a 4 or a 5.
The patterns that win marks
Winning answers tend to share a structure, even when they are written by different teams in different sectors. The pattern is roughly:
- A direct statement of what you do, in the language of the question.
- A short explanation of how you do it, with enough specificity that an outsider could follow.
- Evidence: a named project, a named client, a metric, a quote, a deliverable.
- Tailoring: a sentence or two showing why this approach suits this specific bid.
- A reference to risks or limitations, handled honestly.
The last point catches a lot of bidders by surprise. Acknowledging risk does not lose you marks; it usually gains them. Evaluators are trained to be wary of bids that present everything as effortless. A bid that says “the principal risk on this project is X, and our mitigation is Y” reads as a bid from people who have done this work before.
The structure of the bid itself
One of the simplest improvements any bidder can make is to mirror the structure of the evaluation framework in the structure of the response. If the rubric is laid out as eight criteria, the response should have eight sections, in the same order, with the same headings as the criteria themselves. Not “Section 3 — Our Approach,” but “Section 3 — Methodology for Service Delivery (Criterion 3.1).”
The reason is purely practical. An evaluator is scoring twenty bids against the same rubric. A bid that follows the rubric is one they can score quickly and confidently. A bid that uses its own structure forces the evaluator to hunt for the relevant content under each criterion, and a hunting evaluator is a frustrated evaluator. Frustrated evaluators do not award generous marks.
Reading the RFP like an evaluator
Most of the information you need to write a winning bid is in the procurement documents themselves. The evaluation criteria, the weightings, the scoring scale, the format requirements, the page limits, the mandatory information. Read them before you start writing — not during, and definitely not after.
A useful exercise is to take the evaluation framework and turn it into a checklist. For each criterion, write down the weight, the scoring scale, and the specific evidence the rubric asks for. Then write your draft against the checklist. You will catch the gaps that bidders normally only catch in the debrief.
And ask for the debrief. Public sector procurement entitles unsuccessful bidders to a structured explanation of why they did not win, broken down by criterion. Private sector procurement increasingly offers the same. The information in those debriefs is more useful than any general advice on bid writing, because it tells you exactly what you missed against the rubric you were scored on.
The short version
Winning bids are not the most eloquent. They are the ones written for the rubric they will be scored against. That means understanding the weightings, mirroring the structure, answering the question the question asks, and backing every claim with evidence. The rest is craft, and craft helps — but craft applied to the wrong target is just decoration on a low score.
