How to Request a Tender Debrief (And What to Do With It)

After a lost tender, most teams move on within 48 hours. They shouldn't. A well-requested debrief is the single most valuable piece of feedback you can get in public-sector bidding, it tells you exactly which sections cost you the contract, what the winner scored, and where your evaluators agreed with you. And in the UK, you are legally entitled to receive one.

Your legal right under the Procurement Act 2023

Under the Procurement Act 2023 (and previously under the Public Contracts Regulations 2015), contracting authorities running above-threshold procurements must issue an assessment summary to unsuccessful tenderers. This summary must include your own scores, the scores of the winning bid, and the contracting authority's reasons. You have an 8-day standstill window during which to scrutinise it.

What you should ask for

1. Your scores for every quality question, with the evaluator narrative for each.
2. The winning bidder's scores for the same questions (you are entitled to this).
3. The price submitted by the winning bidder.
4. Any moderation notes or scoring rationale where your score deviated significantly from the average.
5. A meeting (call or in-person) to walk through the assessment, most authorities will grant this if you ask politely.

How to write the request

Keep it short, professional, and reference the specific procurement. Thank the authority for the opportunity, confirm you have received the outcome notification, and ask for the full assessment summary plus a debrief meeting. Avoid any tone that could be read as preparing for a legal challenge, that often closes the door to candid feedback.

What to do with the feedback

The mistake is to read the debrief once, feel briefly demoralised, and file it. The discipline is to extract three things: (a) which specific questions cost you most points, (b) what evaluator language they used, and (c) what the winner appears to have done differently. Tag this against the contract form and sector, and you build a compounding library of evaluator preferences.

The patterns you will see across debriefs

• Social value answers are the most common low scorers, generic commitments without measurable outputs.
• Method statements that re-state the question rather than answering it are penalised heavily.
• Evidence claims without dated examples or named projects routinely lose marks.
• Pricing narratives that focus on the price rather than the rationale leak quality points.

When to challenge, and when not to

If the debrief reveals a procedural error (scoring outside the published methodology, undisclosed evaluation criteria, a clear arithmetic mistake), you may have grounds to challenge during the standstill window. But the vast majority of debriefs reveal that the winner simply wrote better answers. Use them to write better answers next time, that's where the value compounds.