The debrief nobody reopens
The end-of-bid write-up is probably the most conscientiously written and least often reread document in the whole bid function.
A filing problem rather than a writing problem
Bid teams are not short of clarity about the bids they lose. The debrief happens, and it often happens well. It produces a document, filed in a shared folder, next to the twenty before it.
Eighteen months later, the same weakness turns up in the same section of another bid. Nobody makes the connection. This is not negligence: nothing brings that information back at the point where it would help. The debrief was written to be filed.
Score against stable dimensions rather than free text
A prose debrief compares badly from one bid to the next. The same criticism gets phrased three different ways depending on who writes it, and no pattern emerges across a series. Scoring each bid against a fixed set of dimensions costs a few extra minutes and makes the series readable.
- Was the qualification right? Should you have bid at all?
- Did the response strategy hold all the way to submission?
- Was the differentiation explicit, or only obvious to you?
- Did internal contributors hold the schedule?
- Against which competitor, and on what argument did you lose or win?
Attach the lesson to the content
This is the point that changes everything else. A lesson filed in a summary document depends on somebody's memory to resurface. The same lesson attached to the content section it concerns resurfaces on its own, the next time that section is opened.
Concretely: if your answer on reversibility was judged weak against a competitor, the useful information is not "improve reversibility" in an action plan. It belongs attached to the reversibility paragraph, visible to whoever reopens it eight months from now, who quite probably will not be you.
That is the principle behind AIRFP's win/loss analytics. Post-decision scoring feeds the knowledge base itself, and what worked against a competitor stays available on the next bid.
A short deliverable, meant to be read
The format that actually circulates fits on one page: the scored dimensions, the stated reason for the decision when it is known, and two or three reusable elements. That is the document sales leadership reads, and it gives bid management a visibility no dashboard provides.
Always ask the public buyer for the reason for rejection. It is often disclosable, rarely requested, and it is the only reliable external data point in the whole exercise.
A retrospective is only worth something at the moment it resurfaces. Attach it to the content it concerns rather than to a write-up nobody will reopen.