“We lost on price” is the debrief conclusion that ends the conversation before it starts. Most losses happened at a specific, identifiable stage — find the stage first.
Key takeaways
A loss debrief that stops at “their price was lower” treats every loss as the same loss. Under CCDC 23’s own framing of a tender as a staged process — compliance, then selection, then award — most losses actually happened at one identifiable stage, and the stage matters more than the fact of losing.
CCDC 23 walks a tender through “evaluation for compliance, selection, award, post-bid negotiations and re-bidding, notification of award” as a sequence, not a single event. A debrief’s first job is placing the loss in that sequence: was the bid found non-compliant and removed before scoring even began — see how a reference or compliance failure can do exactly that — or was it compliant, scored, and simply out-ranked on the weighted criteria, or was it compliant and competitively scored but lost on price alone against an otherwise similar bid? Each of those three is a different failure, and treating a compliance-gate loss as a pricing problem fixes nothing for the next tender.
No universal Canadian rule requires an owner to hand over a scoring breakdown to an unsuccessful bidder — what can actually be extracted from a debrief conversation depends entirely on that specific project’s bid documents and the owner’s own debrief practice, which varies widely between public and private calls. Where the documents are silent, the debrief itself is a request, not an entitlement, and it is worth asking for the answer to the compliance-vs-score question above even where a full breakdown is not on offer, since that alone usually points to which half of the bid file needs the work. One real exception sits inside the trade agreements: on a procurement covered by the Canadian Free Trade Agreement, Article 516 gives an unsuccessful bidder a treaty-level right to ask why — the procuring entity has to respond with its reasons if the request is made — which is a genuine entitlement a public-sector debrief can invoke, even though it still falls short of the full scoring breakdown a bidder actually wants.
A tender that scores technical and price separately is really two different pieces of work being judged at once — the number the estimator built, and the narrative the proposal writer built around experience, safety, and approach. A debrief that only reviews the price misses half the evaluation on any tender that isn’t pure lowest-compliant-price, and a firm that consistently scores well on price but weak on technical narrative has a writing and evidence problem, not an estimating one — the kind of gap the experience section of an RFP is usually where it actually shows up.
A debrief that produces a general impression — “we should present better” — rarely survives contact with the next live bid, which arrives on its own deadline with its own pressures. The versions that actually change results convert each identified gap into a named, dated action item completed before the next tender closes, not before the next slow month arrives. Tracking whether those fixes actually move the needle is a measurement problem in its own right — see how to measure a contractor’s bid win rate for how to tell whether a debrief’s fixes changed anything or the firm just won a few easier jobs in a row.
A debrief habit that only triggers on a loss builds a one-sided record — every fixable weakness gets logged, and every accidental strength goes unexamined. A win scored on a thin technical submission and a generously low price is not evidence the technical work is fine; it may just mean price carried a bid that would have failed on its own merits against a tighter field. Running the same stage-by-stage question on a win — did we clear compliance comfortably, did we actually score well on the weighted criteria, or did price alone carry it — keeps the debrief record from quietly teaching a firm that a weak technical package is an acceptable norm because it has not yet been tested against a competitor who also priced well.
A single debrief is a data point; a debrief record kept across a season of tenders is what actually changes outcomes, because it is the only place a pattern — the same sub-criterion costing points bid after bid, or losses clustering in one procurement route rather than another — becomes visible at all. A firm that treats each loss as an isolated event, reviewed once and then set aside, is effectively re-diagnosing the same weakness from scratch every few months instead of ever actually closing it.
A firm loses a design-build RFP scored on the common 70-technical / 30-price split. Its own bid: technical 54/70, and — because its price happened to be the lowest submitted — a full price score of 30/30, for a raw total of 84. The winning bid: technical 63/70, price score 26/30 (a higher price than the firm’s own), for a raw total of 89. The firm lost by 5 points despite the lower price — a result that “we lost on price” does not explain, because on price alone the firm’s bid actually scored higher.
The debrief isolates the 9-point technical gap (63 − 54) into two sub-criteria: the safety-programme submission lost 6 of 10 available points, and the references package lost 3 of 10 — together accounting for the entire gap. Before the next tender under the same evaluation structure, the firm rewrites its safety-programme documentation and rebuilds its reference package to the standard set out in how references are scored in a tender. On the next bid, its technical score rises to 65/70 — an 11-point gain, more than closing the original 9-point gap. Assuming an identical 30/30 price score, the new raw total is 65 + 30 = 95, six points clear of the prior winner’s 89. The figures are a reconstructed illustration of a scoring pattern built on CCDC 23’s own compliance/selection framework, not a real tender’s numbers — what the example shows is that a 9-point gap traced to two named sub-criteria is fixable in a way that a general “present better” conclusion never is.
A close loss usually teaches more per hour spent, but a lopsided loss is worth at least a quick check for a compliance-gate failure — see references and past-performance scoring — since that is a different, often simpler fix than a scoring gap and is easy to miss if the debrief assumes the loss was close.
No. A debrief is an internal review, usually an informal conversation with the owner; a formal challenge is a different, higher-stakes step grounded in the Contract A relationship CCDC 23 describes between a compliant bidder and the party calling the bid, and it should be treated as a legal question, not a debrief-conversation one.
Whoever built the price and whoever wrote the technical narrative, together — a debrief run by only one of them tends to hear only the half of the evaluation that person already understands, and the worked example above shows how much of a real gap can sit entirely on the narrative side.
A 30-minute call is enough to tell you whether your bid losses cluster at compliance, scoring, or price.
