A subcontract package assembled from scratch for every trade is where GC risk quietly accumulates. Build the set once as a template, and every award becomes a matter of filling in the blanks.
Key takeaways
STEP 01 OF 10
CCDC does not publish subcontract agreement text for free — its documents are sold through authorised outlets, and CCDC's own catalogue is the place to confirm which edition year is current before referencing one (several documents were reissued for 2024 through 2026). What a firm can build without buying anything is a package structure that mirrors CCDC's own framework: scope, price, schedule, changes, and dispute mechanism as five distinct sections, each with its own attachment where CCDC would have one. See the CCDC catalogue.
The prime contract's own terms — especially anything from CCDC 2's stipulated-price framework — should flow down into the subcontract, not stop at the GC. A subcontract silent on dispute resolution or holdback timing defaults to whatever the sub can argue for later.
STEP 02 OF 10
Keep the drawings list, the specification sections referenced, and the unit prices or lump sum as a separate, dated schedule rather than embedded prose in the agreement body. When a change order revises scope (see setting up a change management process), only the schedule needs reissuing, not the whole agreement.
Date and version every schedule. A subcontract package with an undated scope schedule cannot prove which version governed a dispute six months into the project.
STEP 03 OF 10
A GC that has 10% withheld from its own payment by the owner should withhold the same 10% from each subcontractor's payment, calculated on the same basis the province requires — see a payment application cycle that runs itself for how that base differs between Ontario, Alberta and British Columbia. A subcontract that is silent on holdback, or that states a different percentage than the statute allows, does not relieve the GC of its own obligation — it just creates a mismatch between what the GC owes the owner and what it is entitled to withhold from the sub.
Build the release trigger into the same clause: in Ontario, the holdback release is now tied to a mandatory annual notice; a subcontract that only mentions "upon completion" is already out of step with the current rule.
STEP 04 OF 10
CCDC 220 is the bid bond, guaranteeing the bidder's intention to enter into a formal contract; CCDC 221 is the performance bond, guaranteeing the contractor's performance; CCDC 222 is the labour and material payment bond, guaranteeing that "all labour and material payment obligations" incurred in performing the contract get satisfied. A subcontract package that requires bonding should name the specific instrument by its CCDC number, not a generic "bond as required" line that leaves the form to be negotiated after award.
CCDC publishes no price for any of these forms on its own site, and the instruments a tender will accept beyond a CCDC 220 — a certified cheque, a letter of credit — are not published anywhere reachable either. Treat that gap as something to confirm with the specific project's bonding requirements, not something to assume.
STEP 05 OF 10
Ontario's expanded compulsory coverage rule requires that people who own or run a construction business, with or without employees, must register with the WSIB and have coverage, with the registration due within 10 calendar days of hiring a first employee. Make a current WSIB clearance certificate — valid for up to 90 days — a documented condition of the first payment, not something chased after work has already started.
British Columbia's equivalent is the WorkSafeBC clearance letter. Build the package to reference whichever regime applies to the province the work is in, not a single national line.
STEP 06 OF 10
A subcontract package should require proof of general liability insurance naming the GC as an additional insured, alongside a signed statement of the sub's independent business status. Treadstone Law's guidance on Ontario contractor classification is useful here: the CRA and the courts look at control, tools, risk of loss and integration into the business, not just what a contract calls the relationship. A subcontract package that reads like an employment agreement — fixed hours, GC-supplied tools, no ability to subcontract further — invites a misclassification finding regardless of its title.
This is a narrower, adjacent risk to the construction-specific documents above, but it belongs in the same package because a firm assembling bond and insurance schedules is exactly the firm that should also be checking this box. See independent contractor agreements versus employee status.
STEP 07 OF 10
For an electrical subcontract in Ontario, that means confirming the sub holds a 7-digit ECRA/ESA licence number — only Licensed Electrical Contractors, not individual qualified electricians, are authorized to contract for electrical work. For any of Ontario's 23 compulsory trades, confirm the individual tradesperson holds a valid Certificate of Qualification — Skilled Trades Ontario names the list. Build a one-line licence-check requirement per trade category into the package rather than a single generic "sub must be licensed" clause that nobody actually verifies against.
Where a technical-safety authority governs the trade — TSSA for fuels, elevating devices, boilers and pressure vessels — state that the sub is responsible for its own compliance under that regulator's codes; no fee schedule for TSSA work is published anywhere reachable, so do not put a number in the package that nobody can verify.
STEP 08 OF 10
Name what the sub must submit — shop drawings, product data, samples — and on what schedule, inside the package itself. See a document control system for a GC for the review-status workflow this feeds into. A subcontract silent on submittal timing puts the GC in the position of chasing paperwork verbally partway through the job, which is exactly the kind of undocumented request that turns into a change-order dispute later.
Keep the submittal requirement specific to the trade — a mechanical sub's submittal list looks nothing like a drywall sub's, and a generic clause that lists neither tends to get ignored by both.
STEP 09 OF 10
Reference the adjudication mechanism available under the province's construction legislation as the first stop for a payment dispute, ahead of litigation — see escalating a dispute before it becomes a claim for the full ladder. A subcontract that is silent on dispute resolution defaults to whatever forum a sub's lawyer picks, which is rarely the fastest or cheapest one available under the Act.
This clause costs nothing to include and is the single most commonly missing item in a subcontract package assembled under deadline pressure at award time.
STEP 10 OF 10
Once the nine pieces above exist as a template, treat the template itself as a controlled document with a version number. When the Ontario holdback rule changes, or a new CCDC bond edition is released, update the template once and reissue it to every project using it — not edit each project's individual package by hand, which is how one project ends up running an outdated clause nobody remembers changing.
A subcontract package that has to be assembled fresh for every trade on every project is not a template, it is a habit of starting over. The goal of this whole exercise is to make the ninth award of the year no harder to produce than the first.
Treating the subcontract as a single document instead of an agreement plus a schedule of attachments. The scope schedule, the bond forms, the insurance certificate and the clearance certificate each have their own currency date — bundling them into prose makes it hard to tell which one is stale.
Using a subcontract holdback percentage that does not match what the GC itself has withheld by the owner. A mismatch between the two creates a gap the GC funds out of its own margin, discovered only at closeout.
Writing hours, tools and exclusivity terms into a subcontract that reads like an employment relationship. That invites a misclassification finding on top of whatever construction dispute the package was meant to prevent.
Requiring "a bond as required" instead of naming CCDC 220, 221 or 222 specifically. A generic clause leaves the bond form to be negotiated after award, which is exactly when neither party wants to be negotiating paperwork.
Leaving the dispute-resolution clause blank. Silence does not default to the fastest mechanism available under the province's construction legislation — it defaults to whichever forum the other side's lawyer prefers.
The flow-down clause in step three is not an abstraction — it moves real money at every tier. Here is one trade, worked through.
A $2,000,000 project carries a 10% owner holdback — $200,000 across the whole job. The GC subcontracts the electrical scope for $300,000. Applying the same 10% rate, the GC withholds $30,000 from the electrical subcontractor, paying out $270,000 net across the course of the work. The subcontractor's WSIB clearance certificate, valid for up to 90 days, needs renewing roughly twice over a project running eight months — a detail worth putting on the same calendar as the payment schedule, not tracked separately.
The figures are illustrative, not a benchmark; the contract value, the trade mix and the province set the real numbers. What holds regardless of province is the mechanism: whatever percentage and base the GC is held to by the owner, the flow-down clause should mirror — not approximate — in every subcontract package built from the template.
The subcontract package template itself does not need ten provincial versions — but three clauses inside it do need checking against the project's province before award.
Everything else in the nine-piece template — the bond references, the submittal schedule, the dispute ladder, the licence checks — can stay identical across provinces; these three cannot.
Not if the nine-piece template exists and is kept current. Legal review belongs at the template level, when the underlying rules change — the Ontario holdback amendment or a new CCDC bond edition — not on every individual award using an already-reviewed template.
Treat that as a signal worth pausing on, not a formality to waive. A trade unwilling to confirm its own independent-business status is either misclassified already or expecting to be treated as one, and either way the GC's risk on that relationship just went up.
No. A tier-one structural or mechanical subcontract carries different bonding exposure than a small finishing trade, and a package requiring CCDC 221 performance bonds uniformly across every trade on the job will price small subs out of bidding for no risk-management benefit.
It can be written differently, but doing so creates a funding gap the GC absorbs out of its own margin — matching the rate and base is the version of this clause that does not cost the GC money at closeout.
A 30-minute call is enough to tell you whether it is worth building.
