In brief
You lost the tender, and the award decision says you were not the most economically advantageous submission. What you really want to know is missing: which answer lost points, why the winner scored higher, and what you should change next time. An award decision is a legal document, not a coaching report. It explains the outcome and the main reasons, not every weak sentence.
The useful lesson is this: the real improvement happens before the next deadline. Read the decision, learn from patterns, and review your next submission before you send it.
Over the past year we spoke with more than 300 bid managers and tender professionals. The quotes in this article come from those conversations, anonymised.
The pain: you lost, but you do not know exactly why
A tender can take weeks of work. Then the letter arrives: you came second, the contract went to someone else. Often the feedback is too thin to act on. You may see a lower score, but not the precise missing proof, weak explanation or overlooked requirement.
That is frustrating because the feedback arrives when it is too late. The submission is fixed. You can only use the lesson next time.
What an award decision is
An award decision tells bidders who won and why. It also starts the standstill period in which rejected bidders can ask questions or object before the contract is final.
It usually contains:
- your score per criterion;
- the winner’s score;
- a short explanation per part;
- the final ranking and score difference;
- the formal reasons for rejection.
It usually does not contain:
- the winning text;
- a line-by-line explanation of your answer;
- exact wording you should have used;
- a full coaching report for the next tender.
That distinction matters. The decision is there to justify the award, not to teach you how to win.
Why the same answer can score differently
Many teams recognise the pattern: a similar answer scores well in one tender and poorly in another. That does not always mean the process is random.
Several things change:
- the evaluation panel;
- the exact wording of the question;
- the strength of competitors;
- the weighting of the criteria;
- what you left implicit instead of writing down.
You cannot control the panel. You can control how explicit, proven and criteria-led your answer is.
How to use the feedback anyway
One award decision is often too thin. Five decisions together can show a pattern.
- Collect recent award decisions. Do not analyse only one loss.
- Compare scores by criterion. Where do you repeatedly lose points?
- Ask for clarification during the standstill period. Be specific: where was the largest gap?
- Translate the lesson into your library. If you under-explain implementation every time, build a stronger reusable block.
- Apply the lesson before the next submission. Do not wait for the next rejection.
That last step is the important one. Feedback becomes valuable when it moves forward into your next draft.
Review before submission, not after rejection
The award decision comes too late to improve the lost tender. The only moment feedback can win points is before the deadline.
That is why many teams review their submission as if they were the buyer. They place the answer next to the award criteria and ask: where are we missing points?
AI can help here, but only if it is strict and traceable. A useful review:
- reads the award criteria from the tender documents;
- checks each answer against the relevant criterion;
- prioritises weaknesses by likely point loss;
- explains why a weakness matters;
- links comments back to the source.
AI should not replace your judgement. It should surface the weak parts early enough for you to fix them.
Checklist after losing a tender
- Read the award decision as a legal document, not a full feedback report.
- List your scores per criterion.
- Ask targeted clarification questions during the standstill period.
- Compare several losses to find patterns.
- Add the lesson to your tender library.
- Make implicit assumptions explicit in the next answer.
- Review the next draft before submission.
How TenderRender helps
TenderRender brings the feedback moment forward. It reviews your draft against the award criteria before you submit. You see which parts are weak, which requirements are missing and where you need proof.
It also learns from previous submissions and feedback, so patterns from lost tenders can improve the next draft. The review is not a promise that you will win. It is a way to find likely point loss while you can still do something about it.
Frequently asked questions
Why is the award decision so vague? Because it is a legal justification of the award, not a coaching report.
Can I see the winning submission? Usually not. It is confidential. You can ask for clarification, but not for the full winning text.
Why did the same answer score differently elsewhere? The question, panel, competitors and weighting may all have changed.
Can AI predict whether I will win? No. It can identify likely weaknesses against the criteria, not reproduce the exact evaluation panel.
