Bids are not usually lost on price. They are set aside for a missing form, an unacknowledged addendum, or a bond that arrived after closing. That is a list-management problem, and lists are cheap to automate.
Key takeaways
Every contractor who bids public work has a story about a submission that failed on something trivial. The reason it keeps happening is structural: the requirements are written in prose, spread across several documents, amended by addenda, and due at a fixed minute.
The fix is not more diligence. It is turning prose into a register, once, automatically, at the start of every bid.
The CCDC 23 guide to calling bids and awarding contracts describes the award process as evaluation for compliance, then selection of the successful bidder, then contract award. Compliance comes first. It also covers bid closing dates and times, bid modifications, bid opening, two-stage bid closing and electronic receipt of bids — each of which is a mechanism with its own deadline, and each of which is a row in your register.
This ordering is the whole argument for spending your first hour on paperwork rather than price. A bid that is non-compliant is not a cheaper bid; it is not a bid.
One row per requirement. Five columns, no more.
The five columns
Requirement — quoted verbatim from the instructions, not paraphrased.
Source — document and page or clause number, so it can be re-read in seconds.
Evidence — the specific artefact that satisfies it: a completed form, a certificate, a signed declaration.
Owner — a named person, not a department.
Due — when it must exist, which for third-party items is days before closing, not at closing.
An extraction pass over the instructions to bidders and Division 00 produces the first four columns. The due dates are yours, and they are where experience shows up: an estimator who has been set aside once puts the bond deadline four days early.
Split the register in two: things you can generate this afternoon, and things that depend on a third party. The second list drives your calendar.
Bid security usually means a bid bond, and the standard Canadian forms are published together: CCDC 220, 221 and 222. CCDC 220 is the bid bond, guaranteeing the bidder's intention to enter into a formal contract and to provide the specified contract security if the bid is accepted. CCDC 221 is the performance bond, guaranteeing performance of the contract. CCDC 222 is the labour and material payment bond, guaranteeing that the contractor will satisfy the labour and material payment obligations incurred in performing the contract.
Those are surety instruments. They come from your surety on their timeline, and the bonding capacity conversation is one you want to have before a tender closes rather than during one.
In Ontario a clearance is a number issued by the WSIB showing that a business, contractor or subcontractor is registered and up to date. The WSIB's clearances page records the details that matter to a bid calendar: only registered businesses in good standing can obtain one; the number is valid for all your contracts and is valid for up to 90 days; you can request one immediately through online services, but a request made by email arrives within three to five business days. Newly registered businesses that need a clearance at the time of registration usually make an initial advance payment of $250, applied as a credit against future premiums.
That registration step has its own deadline, worth putting in the register alongside the clearance itself: under the Workplace Safety and Insurance Act, 1997, s.75(1), every Schedule 1 and Schedule 2 employer must register with the Board within 10 days of becoming such an employer — a real gate for a first-time bidder who has never carried WSIB coverage before.
Three to five business days is the sort of fact that ends bids. Put it in the register with a due date, not in someone's head.
Certificates naming the correct additional insureds, with the limits the instructions specify, come from your broker. Extract the required limits and named parties verbatim, because a certificate with the right limit and the wrong named entity fails the same way as no certificate at all.
Every addendum issued during the bidding period is a potential change to the register. CCDC 23 treats bidder inquiries and the issuance of addenda as a formal part of calling for bids. A useful automated pass compares each addendum against the existing register and returns three lists: rows added, rows changed, and rows unaffected. Acknowledgement of addenda is itself commonly a compliance requirement, so it gets its own row.
There is a formal route. The CFTA's bid review pages note that where a supplier alleges a breach or failure of a party's adherence to the agreement's procurement review procedures, the supplier can issue a challenge in accordance with Article 518, paragraphs 5 to 7. Whether that is worth doing is a legal and commercial judgment, and it is not a substitute for a compliant submission. Knowing the route exists mostly changes how carefully you keep your own bid records.
Federal opportunities and their closing information are published on CanadaBuys, which also allows filtering by status, so you can see what was awarded and to whom. That is a slower, more useful feedback loop than a challenge.
A general contractor bids a school board addition. The extraction pass returns 34 requirements, of which six depend on third parties: a bid bond, an agreement to bond letter, a WSIB clearance, three insurance certificates with a named additional insured, a health and safety policy signed within the last year, and two subtrade prequalification confirmations.
Those six get due dates counted backwards from closing: clearance requested eight business days out, bonds requested ten, certificates seven. The remaining 28 are internal forms, and a drafting pass fills the repetitive ones from the company profile. Two addenda arrive; each is run against the register, and the second one adds a requirement the estimator would have missed because it appeared in a revised specification section rather than in the instructions.
The submission goes in with two hours to spare, which is the point. The hours were not saved on the checklist; they were saved by not doing the checklist twice.
No, and it should not be architected to. Submission is the moment legal obligations attach. A person confirms the register is complete, a person uploads, a person confirms receipt.
It is a guarantee that labour and material payment obligations incurred in performing the contract are satisfied, per the CCDC bond forms. If you are a subtrade wondering what your options are when payment stalls, our sister firm covers contractor and subcontractor payment disputes in Ontario.
Both. Keep a master list of requirements you see repeatedly, so each new bid is a diff rather than a fresh extraction. The diff is also a fair description of what the automation is actually doing for you.
A 30-minute call is enough to tell you whether AI pays for itself here.
