CCDC already documents the stages a bid goes through, from the invitation to the notification of award. Build your pipeline around them, not around whatever habit the firm has drifted into over the years.
Key takeaways
STEP 01 OF 10
CCDC’s own guide to calling bids and awarding contracts treats "bid solicitation, bidding period, pre-bid meetings and site visits" as distinct, trackable stages, not a single lump of time before pricing starts. Log the invitation the day it arrives, with its own deadline and its own set of bid documents — CCDC 23 describes those documents as running from Division 00 to Division 49 — rather than folding it into a general to-do list that only becomes urgent a week before close.
A pre-bid meeting or site visit logged as its own step, with its own date, also gives the pipeline a natural point to decide whether to bid at all — a decision that is easier to make cleanly before the pricing hours are already sunk into the number.
STEP 02 OF 10
An addendum changes the bid you are pricing, and CCDC 23 names addenda as their own recognized stage inside the bidding period, separate from the original solicitation. A missed addendum can make an otherwise strong bid non-compliant. Track every addendum against the specific bid it amends, with a timestamp, so a compliance check at close can confirm every addendum on record was actually priced.
A simple version of this works: an addenda log per bid, with a column for who acknowledged receiving it and a column for who confirmed it was priced into the number. Two names, not one — the person who read it and the person who costed it are not always the same, and a bid has failed compliance before over exactly that gap.
STEP 03 OF 10
CCDC’s bond forms describe the Bid Bond (CCDC 220) as "guaranteeing the bidder's intention to enter into a formal contract and to provide the specified contract security if the bid is accepted." Confirm what security a given invitation requires, and confirm your firm can actually provide it, before the pricing work starts — not after a winning number is already on the table and the security turns out to be a problem.
Securing a bid bond can take longer than it feels like it should, particularly for a firm bidding a project size it has not bid before. Start that conversation with your surety the same day the invitation is logged, not the day before the bid closes, and price against current numbers from the supplier pricing feed rather than a number someone remembers from the last similar job.
STEP 04 OF 10
CCDC 23 names "bid closing, bid modifications, bid opening, two-stage bid closing, electronic receipt" as recognized parts of this stage. A two-stage closing — technical submission first, price submission second — is a real, recognized format your pipeline needs to represent, not an edge case to handle manually if it comes up. Build the pipeline to support both single- and two-stage closings from the start.
STEP 05 OF 10
CCDC’s own description of this guide covers "the legal obligation of owners and bidders under Contract A and Contract B" — the doctrine under which submitting a compliant bid can itself create a binding contract (Contract A) separate from, and before, the eventual construction contract (Contract B). Treat a submitted bid in the pipeline as a real commitment the moment it is compliant and received, not as a placeholder that only matters if it wins.
STEP 06 OF 10
CCDC 23 lays out "evaluation for compliance, selection, award, post-bid negotiations and re-bidding, notification of award" as five distinct steps, in that order. Build a pipeline stage for each one, in that sequence, so a bid cannot be selected before it has cleared a compliance check, and so post-bid negotiation — where it is permitted — is recorded as its own stage rather than folded quietly into the general idea of "award".
STEP 07 OF 10
CCDC 221, the Performance Bond, guarantees "performance of the contract by the Contractor," and CCDC 222, the Labour and Material Payment Bond, guarantees "that the Contractor will satisfy all labour and material payment obligations incurred in performing the contract." Both are different instruments from the bid bond that got the bid to the table in the first place. Your pipeline's "award" stage should trigger both, as separate checklist items, not assume the signed contract alone covers what they cover.
STEP 08 OF 10
CCDC 23 names "notification of award" as its own recognized stage, and doing it consistently protects the firm's reputation with subtrades and future bidding partners. Record the reason a losing bid lost — price, schedule, compliance gap — and feed it into the estimating system; a loss reason that is only in someone's memory does not improve the next estimate.
This applies whether your firm was the bidder or the one calling the bids. A subtrade that is told plainly why it lost, even briefly, is more likely to bid again next time than one that is simply never contacted again.
STEP 09 OF 10
The bond and bid-security decisions in step three sit alongside a separate number: the holdback withheld from every payment once the contract is awarded. In British Columbia, the Builders Lien Act s. 4(1) and, in Alberta, the Prompt Payment and Construction Lien Act s. 18(1) both retain 10% of the value of work done. Manitoba's Builders' Liens Act s. 24(1) retains only 7.5%. A bid pipeline that assumes one national number is pricing its own working-capital exposure wrong the moment the project crosses a provincial line.
Add the applicable holdback rate to the same evaluation record from step six, next to the bond terms — it feeds directly into an estimating system that scales, not just the bid file.
STEP 10 OF 10
A project's own dollar value can trigger a filing obligation before a shovel goes in the ground. Ontario's Notice of Project requirement applies once labour and material costs are "expected to exceed $50,000" ($250,000 for a project confined to an automobile-manufacturing factory), with no advance-notice period stated. British Columbia's OHSR 20.2 sets its own cost trigger at "the estimated total cost of labour and materials for the work exceeds $100,000," among several structural triggers, and requires the notice reach the Board "at least 24 hours before work on the construction project begins."
Put the applicable threshold on the bid-closing checklist from step four. A project that clears the invitation, the addenda and the bond stage cleanly can still start late because nobody checked whether its own dollar value crossed a filing threshold days before mobilization.
Pricing before confirming the required security. A strong price that cannot be backed by the required bond is not a compliant bid. Confirm bonding capacity before investing estimating hours, not after.
Treating an addendum as an update to read, not a change to price. An addendum that changes scope or a deadline changes the number, not just the paperwork. Route every addendum back through pricing, not just through a read-and-file step.
Awarding before the compliance check is actually finished. The lowest number is not automatically the winning bid if it has not cleared the compliance stage CCDC 23 places before selection. Skipping that order invites a dispute from a compliant bidder who priced correctly and lost to one that did not.
Losing the paper trail on post-bid negotiation. Where post-bid negotiation is permitted, an undocumented conversation about a revised number is exactly the kind of gap that turns into a dispute later. Keep it in the pipeline as its own recorded stage, not a side conversation.
Treating notification of award as optional once the contract is signed. Skipping formal notification to unsuccessful bidders because the deal is already done costs the firm nothing today and something real later, when those same subtrades and bidding partners decide who to prioritise on the next invitation.
Running the same pipeline stages regardless of project size. A small, straightforward project rarely needs the same level of formal bonding and negotiation stages as a large one, but the compliance and evaluation stages from step six should still apply at some proportionate level rather than being skipped entirely because the project felt too small to bother tracking properly.
Assuming the pipeline only matters for the bids the firm wins. The discipline in this guide pays off just as much on the bids that are lost, since a well-recorded losing bid is the raw material the estimating system in building an estimating system that scales actually learns from over time.
Carrying one province's holdback rate into a bid in another province. Ontario, BC and Alberta share a 10% figure; Manitoba does not. A pipeline built around one number will misprice every Manitoba award by real dollars, not a rounding error.
Step nine names the rates. Here is what they do to an actual award.
Scenario A. A $1,000,000 contract awarded in Ontario, British Columbia or Alberta retains 10% holdback — $100,000 — against progress payments as the work is done.
Scenario B. The identical $1,000,000 award in Manitoba retains 7.5% — $75,000. A bid pipeline that carries the wrong number from step nine forward into the cash-flow forecast overstates the Manitoba job's tied-up capital by $25,000, which can make a genuinely fundable award look tighter than it is, or the reverse if the error runs the other way on a bid comparison.
The $25,000 gap is not a rounding difference. It is the entire reason step nine says to write the applicable rate down next to the price rather than assuming the number from the last province you worked in.
Step ten's thresholds are not the same number, and a single project can land on different sides of each one.
The province, not just the dollar figure, decides whether a given project needs a filing at all. Check both before assuming a project's size alone answers the question.
Not by the contractor's choice. It is set by the applicable provincial Act at the rate in force when the work is performed. What can change is when it is released, which is a separate question from the rate itself.
Put it on the same bid-closing checklist as the bid security, from step four, so it is answered before the pipeline moves the project to award, not discovered by whoever mobilizes the site.
Treat it as worth re-checking. A project that started under a filing threshold and grew past it through change orders is functionally a different project for this purpose, even though the contract number never changed.
A 30-minute call is enough to tell you whether it is worth building.
