A useful debrief connects the evaluation outcome with the evidence in the submitted bid. Separate a capability gap from a presentation gap, preserve what the buyer actually said and turn the findings into specific changes.
A lost tender can still produce useful commercial evidence if the company understands why its response was unsuccessful. A debrief is the opportunity to connect the evaluation outcome with the proposal the buyer actually assessed. The resulting information can improve future bids, help direct capability investment and reveal whether the company is pursuing suitable work.
For a small defense technology business, this matters because proposal effort is expensive. Engineers, founders and delivery staff may all contribute to one response. Recording the outcome only as “lost on price” or “incumbent won” can waste that investment when the explanation has not been supported by the buyer's feedback.
NZGP's Rule 33 requires agencies within the applicable framework to offer unsuccessful suppliers a debrief. It identifies reasons for the outcome, performance against criteria or preconditions, relative strengths and weaknesses, and the successful proposal's relative advantages. It also protects other suppliers' confidential and commercially sensitive information.
Consider a hypothetical software company that proposed an ordinary asset-management service. Before the debrief, retrieve the final submitted response, the published evaluation criteria and any relevant clarification record. The team should be discussing the version actually assessed rather than a later internal presentation that explains the product more clearly.
Identify the few questions that would most affect the company's next decision. Was the delivery approach insufficiently evidenced? Did the proposed service fail to address a requirement? Was the price uncompetitive for the outcome offered? These are different possible explanations, and the company should avoid choosing one before hearing the feedback.
The rule sets timing requirements for debriefs requested by suppliers. Read the current rule and the opportunity's process promptly after notification, so the company can establish the applicable timetable rather than leave the request until the bid team has dispersed.
For the hypothetical software company, a useful question might ask which part of its implementation evidence gave the evaluator insufficient confidence. That invites a discussion of the submitted response. A broader question about whether the buyer liked the company may produce a polite but commercially unhelpful answer.
Separate two possibilities. The company may possess the necessary capability but have failed to substantiate it in the required form. Alternatively, it may lack experience or capacity that mattered to the evaluation. Better wording can address the first problem; the second may require a different delivery model or a decision not to pursue similar work yet.
Prepare a small reference table connecting each question with the relevant criterion and response section. This helps participants locate the evidence quickly and keeps the conversation focused. It also reduces the risk that someone tries to introduce a new sales pitch in place of understanding the original evaluation.
Include the colleague best placed to interpret material technical or delivery feedback. A commercial lead can manage the conversation while the relevant specialist checks that the team has understood the finding accurately.
NZGP's August 2026 debrief guidance advises agencies to ground feedback in evaluation results and documented evidence. It describes several possible formats and treats debriefs for secondary procurements as good practice when requested, while distinguishing that practice from the Rules' requirement. A supplier should establish the relevant process for its particular opportunity.
During the discussion, record the buyer's explanation separately from the company's interpretation. If the feedback says the proposed mobilisation plan lacked detail, do not immediately convert that into a conclusion that the buyer rejected smaller companies. The company needs to understand what the evaluator could and could not establish from the response.
Ask a focused follow-up if the explanation remains too broad to act on. For example, the team might ask which dependency in the proposed timetable remained unclear. The aim is to identify an evidence gap precisely enough to improve a future response, without requesting another bidder's protected material.
Where the buyer cannot disclose something, preserve that limit in the record. An unanswered question is not proof of the company's preferred explanation for the result.
After the debrief, bring the relevant colleagues together while the details are fresh. For each material finding, record the feedback, the affected response section and the proposed action. Assign ownership and a useful completion point, such as before the next bid using the same delivery approach.
Suppose the software company's implementation evidence relied on a generic project diagram. The next action could be to prepare a verified case record showing the actual stages, dependencies and delivered outcome of a comparable engagement. That creates reusable evidence rather than adding more unsupported adjectives to the bid library.
If the problem concerns capacity, the action may be more substantial. Management might need to establish an available delivery partner or reduce the scale of opportunities pursued. The commercial team should make that investment decision visible instead of expecting a proposal writer to solve it through presentation alone.
Also preserve strengths. A response may have provided convincing product evidence while falling short elsewhere. Rewriting everything can remove material that worked well and obscure the specific improvement needed.
Check whether the proposed correction would have changed the evidence available at the submission deadline. A new case study completed months later may strengthen a future bid, but it does not show that the original evaluation overlooked existing experience. Keeping that distinction makes the learning record more reliable. For the software company, a short comparison of the old response, the buyer's feedback and the replacement evidence can show management exactly what has improved and what remains unproven.
NZGP's supplier-debrief guide says feedback should be detailed enough to help suppliers improve future opportunities. The commercial value depends on what the business does with it. A debrief note stored in one person's email is difficult to use when another team prepares the next response.
Keep the finding with the relevant evidence or bid-library entry. State which tender produced it and avoid turning a context-specific comment into a universal rule. A buyer's concern about one proposed delivery timetable does not establish that every agency expects the same schedule or staffing model.
Review recurring findings across several bids carefully. Repetition can justify a broader capability decision, but only when the underlying issues are comparable. Distinguish several losses caused by weak implementation evidence from several unrelated losses grouped under a convenient label.
The 2025 NZGP business survey reports that 27% of respondents to its debrief-frequency question were always or often offered follow-up debriefs. It also cautions about sample representativeness. The finding provides context for the importance of feedback; it does not describe every procurement or prove a failure by a particular agency.
For the software company, the useful management question is what changes before the next opportunity. If the same requirement appears and the identified gap remains unresolved, the bid decision should acknowledge that. If the company has improved its evidence or capacity, the next response should make the improvement demonstrable.
Our New Zealand panel-entry guide explains a separate access decision, while the thin-prime partnership article provides relationship context. A disciplined debrief connects those market choices with what the company has learned from an actual buyer, making the next investment in a proposal more informed.
NZGP Rule 33, the August 2026 debrief guidance, the supplier-debrief guide and relevant pages of the 2025 business survey were directly read on 6 September 2026. The software-company scenarios and example questions are original BDI analysis. Survey results describe respondents; no conclusion about a particular agency or the legality of an award is inferred.
Suggest a correction