Most suppliers picture tender evaluation as a careful, generous read — an expert sitting with your response, weighing its merits, appreciating the work. That picture is comforting, and it is almost entirely wrong. It leads teams to write for a reader who does not exist, and to be quietly baffled when a strong, compliant bid comes back with a middling score.
Here is the version that actually happens. A panel of evaluators works through a stack of submissions against a published scoring rubric, usually under time pressure, often scoring the same question across every bidder before moving to the next. Each evaluator has to award a mark and then justify it — to their fellow panellists in moderation, and increasingly to the supplier in written feedback. The whole exercise is built around defending a number, not admiring prose.
Understand that, and the way you write a response changes completely.
Award is on value, not price alone
First, the frame. Public contracts are awarded to the most advantageous tender — a blend of price and quality, not the cheapest bid. Under EU-derived rules, which still apply in Ireland, this is “MEAT” (Most Economically Advantageous Tender). In the UK, the Procurement Act 2023, in force since February 2025, renamed it “MAT” (Most Advantageous Tender), deliberately dropping “economically” to let buyers weight quality, social value and innovation more heavily relative to price.
The practical point for you is the same under both regimes: a large share of the marks is qualitative, those marks are decided by how your written responses score against published criteria, and that is the part of the bid most within your control.
The panel can only award what the criteria allow
Evaluators do not score your response against their general sense of a good supplier. They score it against the specific award criteria and their weightings, as published in the tender. If a criterion asks about your approach to risk management, evidence of your brilliant social value programme earns nothing there — it is scored elsewhere, or not at all.
This is the most common own goal in bidding: writing what you want to say instead of what the criterion asks to be marked. Before you write a word, map every criterion and sub-criterion, note its weighting, and treat each as a separate scored question. The weightings tell you where the contract is actually won — and where to spend your effort. (We work through what that looks like in Procurement scoring matrix examples.)
They score in bands — and a band needs a justification
Most qualitative scoring uses a banded scale: a 0–5 or 0–10 range with a written descriptor for each band (“excellent — fully meets the requirement with strong supporting evidence”, “satisfactory — meets the requirement but with limited evidence”, and so on).
Two things follow. The evaluator is not assigning a vibe; they are matching your answer to a band descriptor and then writing the justification — which, under the UK Act, they may have to share with you, including guidance on how you could have scored higher. And a band is a cliff, not a slope: the difference between a 3 and a 4 is often a single missing piece of evidence, not the overall quality of your writing. Bids cluster just below the band they were reaching for, and the authors never know why. (More on that in Why bids lose marks.)
They scan for risk and reward evidence
Because evaluators work at speed and have to defend their marks, two behaviours dominate.
They scan to eliminate risk. Anything ambiguous, unproven, or buried reads as risk, and risk is the fastest, safest thing to mark down. A claim with no evidence behind it is not neutral — it is a flag.
They reward what they can point to. A high mark needs a justification, and the easiest justification to write is “the supplier evidenced this with a named, comparable example and a measurable outcome.” Specifics give the evaluator permission to score you up; generalities leave them stuck in the middle band.
This is why “we have extensive experience delivering similar projects” scores nothing, while “on the [X] contract we reduced processing time by 38% in nine months, verifiable against the reference at Annex C” scores well. Same capability. Completely different score. One is a claim; the other is evidence.
Quality is not what most teams think it is
The hard truth behind all of this: a response can be well written, fully compliant, logically structured, signed off by everyone internally — and still score in the middle of the band. A structurally complete answer with no specific proof is, to an evaluator, exactly a mid-band answer. It does everything asked and gives them nothing to justify a higher mark.
There is a ceiling on generic competence, and it sits frustratingly close to the pass line. Breaking through it is not about writing more or writing better. It is about giving the evaluator scoreable evidence for the criterion in front of them.
What this means for how you write
- Answer the criterion, not the topic. Make it obvious which requirement each paragraph is scoring against.
- Lead with the answer. Don’t bury it under context the evaluator has no time to mine.
- Evidence every claim. A named client, a real figure, a dated outcome, a verifiable reference — at least one per high-weighted answer.
- Write for a tired evaluator with a rubric and a deadline, not for an admirer.
- Score your own bid before you submit, in the evaluator’s band language, and fix what you can’t justify.
That last step is the one most teams skip — and it is the one that most reliably moves a score. There is a structured way to do it; we set it out in Bid review methodology.
See how your live bid scores before the panel does. Run it through BidReview’s free scorecard and get an evaluator’s-eye read on where you’re leaking marks — while there’s still time to fix it. Start free →
