Many debriefs are read once, filed away, and forgotten. And as a result they become a missed opportunity. A debrief is one of the few moments in the procurement cycle where a contracting authority is legally required to tell you, in writing, what they actually thought of your bid. Treated properly, it is market intelligence that competitors rarely bother to extract.
The debrief process has its own deadlines and legal framework. Yet many bidders either skim the letter looking for grounds to complain, or they read it once, feel deflated, and move on to the next opportunity without learning anything.
What a Debrief Legally Has to Contain, and What It Usually Doesn’t
Under the EU procurement directives and the Remedies Directives, unsuccessful bidders are entitled to certain minimum information: the characteristics and relative advantages of the winning tender, the name of the successful bidder, and your own scores against the award criteria. In practice, most debrief letters meet this bar in the narrowest possible way. They give you a table of scores, perhaps a paragraph per criterion, and a generic line about the winning bid’s relative strengths.
This minimalism is not usually evidence of bad faith and evaluators are often writing under time pressure, mindful of legal exposure, and conscious that anything they put in writing could be scrutinised in a challenge. The result is feedback that is legally sufficient but practically thin. The skill in reading a debrief well is recognising that the thinness itself is information, and learning to extract signal from documents that were not written to be especially informative.
Separate the Scores From the Narrative
The first step is mechanical: lay your scores against each award criterion side by side with the criterion weightings from the original tender documents. This sounds obvious, but it is the step most commonly skipped, because it is unglamorous compared to reading the prose commentary. Yet the scoring pattern often tells you more than the words do.
A bid that scores consistently in the middle across every criterion suggests a different problem than a bid that scores well on technical merit but collapses on price, or one that scores well everywhere except a single criterion where it drops sharply. The first pattern usually points to what evaluators have perceived to be a generic, undifferentiated submission. The second points to a pricing strategy problem rather than a writing problem. The third points to a specific, fixable gap, often a missed requirement, a weak case study, or an area where the evaluators simply did not believe the claims being made. Before reading a single word of the narrative commentary, it is worth asking: if I only had the numbers, what story would they tell?
Read the Commentary for What Is Withheld
Legal teams often review debrief letters before they go out, and the instinct is to say only what is necessary and avoid anything that could be read as criticism with legal teeth. This produces a particular kind of euphemistic language that rewards careful reading.
Phrases like “the response provided limited detail on implementation” or “the methodology would have benefited from further specificity” are doing real work, even though they sound softvague. They typically mean the evaluator wanted concrete detail and got generality instead. “The case study provided partial relevance to the requirement” usually means the evaluator did not believe your example was close enough to the contract in question, even if it was technically responsive. Where commentary is notably brief on a criterion you expected more on, that brevity is often itself meaningful: evaluators tend to write more when they have more to say, whether positive or critical, so a clipped paragraph on a criterion you scored poorly against can indicate either that the gap was so basic it did not need elaboration, or that the evaluator was being careful not to say anything that invited a challenge. Distinguishing between these two readings usually requires looking at the score alongside the comment, not the comment alone. It is also interesting to pay attention to what is conspicuously absent. If the debrief is generous in its commentary on four criteria and silent or perfunctory on a fifth, that asymmetry is rarely accidental.
Use the Winning Bid’s Relative Advantages as a Real Data Point
Most jurisdictions require contracting authorities to disclose the characteristics and relative advantages of the successful bid, even where the winning bidder’s specific pricing or full methodology remains confidential. This is frequently the most underused part of a debrief. Bidders tend to read this section once, register a vague sense of “they were cheaper” or “they had a better team,” and move on.
It is worth instead treating it as a direct comparison exercise. If the relative advantage cited is depth of local delivery experience, that tells you something about how this buyer weighs proximity and prior relationship, information that is useful for the next tender from the same authority even if it does not change anything about this one. If the relative advantage is methodology rather than price, that confirms the contract was not won on cost alone, which is worth knowing if your organisation has a habit of competing primarily on price. Patterns across multiple debriefs from the same buyer, or the same sector, are more reliable than any single data point, so it is worth keeping a simple running record rather than treating each debrief as a one-off.
Ask Better Clarification Questions
Bidders are generally entitled to ask follow-up questions on a debrief, within a reasonable window, and many never do. There is often a perception that asking questions signals dissatisfaction or invites confrontation, but a well-framed clarification request is simply professional, and most evaluators are accustomed to receiving them.
The questions that get useful answers tend to be specific and forward-looking rather than aggrieved. Asking why a particular score was given for a particular criterion, with reference to the specification, tends to produce more useful detail than asking generally for more feedback. Asking what would have moved a particular criterion from the score achieved to the maximum available is sometimes the single most useful question available, because it directly surfaces the gap between what was submitted and what the evaluator was looking for. By contrast, questions that imply the process was unfair, or that focus on relative comparisons with the winning bidder beyond what has already been disclosed, are less likely to be answered substantively, and risk shifting the conversation from feedback into something closer to a dispute. And it is worth noting that this clarification window is also where some genuine grounds for challenge surface, an evaluator’s answer can sometimes reveal a procedural issue. But that is a secondary benefit, the primary purpose of asking is intelligence, not grounds for a complaint.
Building a Debrief Log
A single debrief is a data point: a pattern across debriefs is intelligence. Organisations that bid regularly benefit from keeping a simple log: buyer, contract value, your score by criterion, the winning bid’s relative advantages where disclosed, and any notable commentary. Reviewed after four or five bids to the same sector, or the same buyer, this kind of log tends to surface patterns that are invisible from any single debrief: a recurring weakness in how methodology is articulated, a buyer that consistently rewards social value content more heavily than the published weighting suggests, or a competitor that keeps winning on a particular dimension regardless of who else is bidding.
This is also where debrief intelligence should feed back into the bid-writing process itself, closing the loop between losing a tender and writing a stronger one next time. If three consecutive debriefs flag the same weakness in how implementation risk is addressed, that is no longer a one-off note to self; it is a structural gap in the organisation’s standard methodology content that is worth fixing once, centrally, rather than relearning on every bid.
A Caution on Over-Reading
There is a risk on the other side of this too, debrief commentary, however carefully read, is still a small, structured sample of an evaluator’s reasoning, not a full window into it, and it is possible to over-interpret a single phrase or read intentionality into what was simply a rushed write-up. The discipline here is to treat any single debrief as a hypothesis rather than a conclusion, and to look for confirmation across multiple bids before treating a pattern as established. A debrief that seems to suggest a buyer favours larger incumbents, based on one loss, is a hunch. The same observation, repeated across three tenders from the same authority, is a pattern worth adjusting strategy around.
The Discipline
The organisations that improve fastest at bidding are rarely the ones that win most often by instinct. They are the ones that treat every loss as a structured input, extracting whatever can be extracted from a process that was not designed to be especially generous with information, and feeding it back into how the next bid is written. A debrief letter is in that sense, one of the few pieces of genuinely free market research available in public procurement. Reading it properly is simply a matter of treating it that way.
Background Reading and Additional Sources:
Directive 2014/24/EU of the European Parliament and of the Council https://eur-lex.europa.eu/eli/dir/2014/24/oj
Council Directive 89/665/EEC https://eur-lex.europa.eu/eli/dir/1989/665/oj/eng
European Commission https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=COM:2017:28:FIN
European Commission, Internal Market, Industry, Entrepreneurship and SMEs https://single-market-economy.ec.europa.eu/single-market/public-procurement/legal-rules-and-implementation/remedies-directives_en
