Win/loss review template that feeds the next bid
A win/loss review is a short structured debrief run after every tender outcome, win or lose, that records what moved the result and files it where the next bid will use it. It covers five areas: price, compliance, technical response, relationship and process.
The review takes an hour and produces three corrections: to the weights on your bid/no-bid scorecard, to the answers you reuse, and to the rates you price from. Ask the client for a debrief, but do not wait for one to start. Most of what you need is already visible in your own submission read against the issued pack, and Elora Grid returns that reading cited to source.
What is a win/loss review?
A win/loss review is a structured debrief held after a tender outcome to record why the result happened, and to convert that into named changes the next bid can use.
It is not a post mortem and not a hunt for who to blame. The test is simple: if the review ends without changing anything the team does next time, it was a meeting.
Why review the wins as well?
Because a win tells you what your price and your response were worth on the day, and no other feedback in tendering does that. Winning at a number far below the next bidder is a different result from winning by a nose, and the two should change your next bid in opposite directions.
Wins also hide their own failures. A qualification accepted without comment, a returnable the evaluator never opened, a rate that turned out generous: all of it is visible in a win, and invisible in a loss.
What do you ask the client?
Ask in writing, and ask narrow questions. Where did our submission score below the leading bid, and on which criteria? Was any part of our response treated as non-conforming? Was our price competitive overall, or only on particular schedules?
Broad questions get broad answers. "Any feedback?" produces "you were close", which changes nothing about the next bid. Public buyers in many jurisdictions are required to debrief unsuccessful bidders on request, and private clients usually will if you ask promptly.
Where does the output go so it gets used?
Three places, or the review evaporates. The bid/no-bid weights get corrected where the team misread its own chances. The answer library keeps what scored and loses what did not, and the price book takes the rates the market has just tested.
Filing the review as a document is not the same as feeding it forward. If nothing in the next tender's kick-off opens it, the loop is still open.
Assembling the raw material is document work: your submission, the issued pack, the addenda and any scoring feedback, read side by side to show where your response and the requirement diverged. Elora Grid returns that comparison with each finding cited to its source document and page. What it means about your price, and what you change next time, stays with your team.
What to capture, and what it changes
| Area | The question | What it changes next time |
|---|---|---|
| Price | Where did our number sit, and on which schedules? | Price book rates, and how validity and escalation are treated |
| Compliance | Was anything treated as non-conforming or qualified out? | The compliance matrix routine and the returnable review |
| Technical | Which parts of the response scored, and which were ignored? | The answer library, kept and pruned |
| Relationship | Did we know the evaluators and their priorities before the tender opened? | The client score on the bid/no-bid scorecard |
| Process | Did the kick-off, the reviews and the internal dates hold? | The tender programme and the review milestones |
- 01Hold it within two weeks. Memory of the decisions fades fast, and the team scatters onto the next tender.
- 02Request the debrief in writing, early. Narrow questions about scoring and conformance, sent while the evaluation is still fresh for the client too.
- 03Read your own submission against the issued pack. Most findings are visible without the client saying anything at all.
- 04Record findings in the five areas. Price, compliance, technical, relationship and process, a sentence each, no essays.
- 05Name changes, not lessons. Every finding becomes an edit to the price book, the answer library or the bid/no-bid weights.
- 06Point the next kick-off at it. The review exists only if the next tender's kick-off opens it and acts on it.
Common questions
How soon after the outcome should a win/loss review happen?
Within two weeks. The team still remembers the decisions, the submission is still fresh, and a client debrief usually arrives inside that window. Later than that and the review captures a reconstruction of the bid rather than what actually happened.
Should you review every bid?
Review every outcome on a tender you genuinely pursued. A short review you actually run beats a thorough one you never get to. Tenders declined at bid/no-bid need no review, but the decline should still be recorded with the score that produced it.
What if the client will not give a debrief?
Run the review anyway. Reading your own submission against the issued pack shows where you qualified, where a returnable was thin and where your assumptions differed from the scope. That is most of the value, and none of it depends on the client answering.
Can Elora Grid support a win/loss review?
Yes. Hand it your submission, the issued pack and any addenda, and it returns a clause by clause comparison showing where your response and the requirement diverged, each finding cited to its source document and page. What the findings mean commercially stays with your team.