Debrief and lessons-learned template

Proposal postmortem template: turn every decision into pursuit memory

A bidder-side review for proposal, capture, and business-development teams that need to separate facts from assumptions, act on buyer feedback, and preserve reusable learning after a win or loss.

Published November 13, 2026

The short answer

Run two connected reviews: an internal execution review while the pursuit is fresh, then a decision review after the buyer provides a notice or debrief. Record buyer-provided facts, direct observations, and team inferences separately; convert only specific, owned lessons into process or content changes.

What you can use immediately

  • A copy-ready 10-field postmortem record
  • A five-layer review from award decision to reusable assets
  • Debrief questions and an evidence-confidence method
  • Worked corrective actions plus a 30-60-90 follow-through cadence

Two-review model

Do not wait for the award notice to remember how the work happened

The internal review captures what the team can directly observe: decisions, handoffs, delays, review findings, evidence gaps, and submission events. The later decision review adds what the buyer actually discloses. Keeping them separate prevents a plausible internal story from being recorded as a procurement fact.

ReviewTimingPrimary evidenceOutput
Execution reviewWithin 2-5 working days of submissionPlan, compliance record, review comments, decisions, timeline, and final fileObserved process strengths, risks, and immediate asset fixes
Decision reviewAfter notice, disclosure, or supplier debriefBuyer feedback, score, award information, and permitted public recordsUpdated lessons, strategy tests, and owned corrective actions

Copy-ready record

Capture these 10 fields for every completed pursuit

FieldWhat to record
Opportunity and resultBuyer, solicitation, decision date, award result, value range, and pursuit owner.
Evaluation recordCriteria, weights, compliance result, score, ranking, and price position when disclosed.
Buyer feedbackDebrief statements, regret letter, evaluator comments, and the date and source of each item.
Decision factsWhat the record directly establishes about the award or exclusion decision.
Strategy reviewWin themes, solution, teaming, proof, pricing posture, and assumptions tested against the result.
Execution reviewKickoff timing, assignments, reviews, amendments, approvals, production, and submission events.
Evidence gapsClaims, examples, credentials, or commitments the team could not support strongly enough.
Reusable assetsApproved answers, project records, resumes, diagrams, questions, and methods worth governing.
Lessons and actionsSpecific change, owner, due date, affected workflow, and evidence that the action is complete.
Confidence labelBuyer-provided, directly observed, or inferred; never present an inference as evaluator feedback.

Five-layer review

Move from the decision to a reusable change

1. Decision

What result occurred, what scores or reasons were disclosed, and which facts are still unknown?

2. Buyer and evaluation

Which criteria mattered, where did the buyer identify strength or weakness, and what can be quoted or recorded?

3. Pursuit strategy

Did the chosen solution, proof, partners, price posture, and win themes fit the opportunity?

4. Proposal execution

Where did timing, ownership, review, amendment control, evidence, or production help or hurt?

5. Reuse and change

What should enter the governed library, what should be retired, and which workflow change has an owner?

Supplier debrief

Prepare questions that connect feedback to the stated criteria

CanadaBuys advises suppliers to review the bid and prepare questions before a debrief. Ask within the buyer's process and confidentiality limits; focus on your own submission and the evaluation method rather than requesting another bidder's protected information.

  • Which mandatory, rated, or selection criteria most affected our result?
  • What strengths and weaknesses did evaluators identify in our submission?
  • Were any responses considered incomplete, unclear, unsupported, or non-compliant?
  • How did our technical score and evaluated price compare where disclosure is permitted?
  • Which evidence or explanation would have made our approach easier to evaluate?
  • Were there assumptions in our response that did not match the buyer's interpretation?
  • What should we preserve, change, or clarify in a future submission?
  • Will a written summary, score disclosure, or other permitted record be provided?

Evidence discipline

Separate facts, observations, and inferences

ConfidenceExample signalResulting actionOwnerDue
ObservedTwo amendments arrived after the first compliance review.Add an amendment-impact review before each content freeze.Proposal operationsBefore next submission
Buyer-providedDebrief identified weak evidence under implementation experience.Add scope and outcome fields to comparable project records.Capture lead30 days
InferredLate executive edits may have weakened message consistency.Test an earlier executive review on the next two pursuits.Pursuit ownerNext two pursuits

These are illustrative actions, not customer results. An inference should create a test or research task, not a permanent rule attributed to the buyer.

30-60-90 follow-through

Close the loop after the meeting ends

WindowRequired actionCompletion evidence
Within 30 daysCorrect high-risk content, evidence, compliance, or workflow defects.Updated governed asset or documented process change with owner approval.
Within 60 daysTest the lesson in an active pursuit and record whether it improved the work.Review record, usage evidence, and observed result from the test.
Within 90 daysKeep, revise, or retire the change based on evidence across pursuits.Decision recorded in the playbook and communicated to affected teams.

Meeting close

Do not leave with a list of vague lessons

  • Every conclusion is labelled buyer-provided, observed, or inferred.
  • Buyer feedback is tied to the stated criterion and source record.
  • Each change names one owner, due date, and completion signal.
  • Reusable assets have passed accuracy, permission, and governance review.
  • Pursuit-specific language is not promoted as universal boilerplate.
  • Retired or risky content is removed from normal retrieval paths.
  • The next relevant pursuit has a named test for the lesson.
  • The record can be found by future capture and proposal teams.

Common questions

Questions teams ask before using the tool

When should a proposal postmortem happen?

Hold a short internal execution review within a few working days of submission, then update the record after the award notice, score disclosure, or supplier debrief. This preserves process details without confusing early assumptions with buyer feedback.

Should teams review wins as well as losses?

Yes. A win can hide a fragile process, weak margin, unsupported assumption, or one-off advantage. Review what was scoreable and repeatable, what nearly failed, and which assets deserve governed reuse.

What is the difference between a buyer debrief and an internal postmortem?

The buyer debrief explains the procurement decision within the rules of that process. The internal postmortem combines that feedback with the team's own strategy and execution evidence to decide what to change before the next pursuit.

How should unverified opinions be handled?

Label them as inferences, record the evidence for and against them, and turn them into a test rather than a permanent lesson. Do not attribute an internal theory to the buyer or change a core process from one unsupported impression.

What makes a useful lessons-learned action?

It names the observed problem, the specific change, the accountable owner, the due date, the workflow or asset affected, and the evidence that will show the action was completed and useful.

Make the next pursuit smarter than the last one.

Bring one recent submission, its decision record, and the follow-up your team completed. We will map where buyer feedback, execution evidence, and reusable learning are getting lost.

Book a bid-lifecycle diagnostic