What does an evaluator actually do with your tender?
Suppliers sometimes imagine an evaluator sitting down with a submission and asking:
"Do I like this company?"
That is not how a properly structured evaluation is supposed to work.
The evaluator works against the published criteria and scoring framework.
They need to award a mark and be able to justify it.
That changes how you should write.
Evaluators score against criteria, not general competence
Suppose the criterion asks you to explain your approach to managing service disruption.
Your response includes an excellent section about sustainability.
It may be genuinely impressive.
But if it does not answer the criterion, it does not help you win those marks.
This is why every paragraph should have a job.
Before writing, map the criterion.
Then write directly against it.
Evaluators work with scoring bands
Many procurements use a banded scoring system.
The exact scale varies, but the principle is similar.
A higher band normally requires more than simply satisfying the requirement.
It might require stronger evidence, greater detail, greater assurance or clearer demonstration of understanding.
That creates an important distinction:
Compliance gets you into the scoring conversation. Evidence helps move you up the bands.
BidReview's procurement scoring matrix examples demonstrate how differences between scoring bands often come down to the quality and specificity of evidence rather than the fluency of the writing.
Evaluators need a reason to give you the mark
Imagine two answers.
The first says:
We have extensive experience delivering similar projects and use a proven methodology.
The second says:
On a comparable three-year contract, we reduced average response times by 28% while maintaining 98.7% SLA compliance.
The second answer is easier to score highly.
Why?
Because the evaluator has something concrete to cite.
Specifics give an evaluator permission to award marks.
Generic claims do not.
What triggers a deduction?
Several things make evaluators cautious.
Ambiguity
If the evaluator cannot tell exactly what you will do, confidence falls.
Unsupported claims
A claim without evidence gives the evaluator little basis for awarding additional marks.
Conditional language
"We would aim to..."
"Where possible..."
"Subject to..."
These phrases can introduce uncertainty.
Missing sub-criteria
If the question contains four requirements and you clearly answer only three, the missing element creates a scoring gap.
Buried answers
If the key commitment is hidden inside several paragraphs of background information, the evaluator has to work harder to find it.
Write for a tired evaluator
This is one of the most useful mental models in tender writing.
Do not write for someone who has unlimited time to appreciate your proposal.
Write for someone who has a scoring matrix, multiple submissions and a deadline.
Make the evidence obvious.
Use descriptive headings.
Lead with the answer.
Keep important evidence close to the claim it supports.
Do not make the evaluator assemble your argument themselves.
The evaluator can only score what is in the response
This sounds obvious.
It is not.
Teams frequently assume the buyer knows their reputation.
They assume the evaluator will understand what a particular project demonstrates.
They assume previous relationships will fill in the gaps.
But the written response is what gets assessed.
The evaluator cannot award marks for evidence that exists somewhere else but is not presented where the criterion requires it.
That is why BidReview's why bids lose marks analysis focuses so heavily on evidence, criterion coverage and buried answers.
Make the mark easy to award
The best tender answers do not force the evaluator to interpret them.
They make the scoring case explicit.
Requirement → approach → evidence → outcome → relevance
That structure gives the evaluator a logical path from the criterion to the mark.
Your objective is not simply to write a convincing answer.
It is to make the evaluator's justification easy to write.
