A standard-form contract at least gives you something to compare a harsh clause against. An owner's own bespoke agreement gives you nothing — which is a different reading problem, not a smaller one.
Key takeaways
Reviewing a supplementary condition against CCDC 2's general conditions works because there's a known baseline to measure the change against. An owner-drafted, bespoke agreement offers no such baseline — there's no general-conditions text sitting underneath it to compare against, so “what did this clause change relative to normal” isn't a question that can be answered the same way.
The practical fix is to borrow a checklist from a document that does have a defined scope, even though the bespoke contract has nothing to do with it, and use that checklist to audit what the owner's document actually addresses versus what it leaves silent.
CCDC 2's own description names the subjects a prime contract is expected to cover: the role and authority of the consultant, procedures for changes in the work, work by other contractors, insurance requirements, prerequisites for Ready-for-Takeover, dispute resolution procedures, and early occupancy. None of that list depends on the contract actually being a CCDC document — it's a usable inventory of what a competently drafted construction contract normally addresses.
Running an owner-supplied contract against that list quickly surfaces the real risk: not what it says on a given topic, but what it says nothing about. A bespoke four-page agreement that covers price and schedule but never mentions insurance, dispute resolution, or what happens if the owner delays access to the site is not a shorter version of CCDC 2 — it's a document with real gaps.
Silence is not the same as an exemption. Where a bespoke Ontario contract says nothing at all about holdback, that silence does not remove the statutory obligation: the Construction Act applies to most improvements to real property in Ontario, regardless of the project size or the number of parties involved, and the requirement to retain 10 percent runs to every person in the payment chain whether or not the contract mentions it. The same principle holds for lien rights generally — a contract's silence on liens doesn't waive them, and a clause attempting to waive lien rights outright is treated with particular suspicion in most provinces' lien legislation.
What a bespoke contract's silence does create is uncertainty about timing and process — when exactly holdback gets released, what documentation triggers it, who administers the account — because the statute sets the floor obligation but a well-drafted contract is what actually operationalizes it day to day. A contract silent on process, even where the underlying statutory right survives, is still a worse document to work under.
Two general contract-law principles do real work here, independent of whether the document resembles any standard form. First, ambiguous language is interpreted against whoever drafted the contract — the contra proferentem principle — which in an owner-supplied agreement means genuine ambiguity generally cuts against the owner, not the contractor who is being asked to sign someone else's wording.
Second, an owner-drafted term can be challenged as unconscionable, but only on a real showing that there was a significant inequality of bargaining power and the resulting term is improvident or unfair — and even then, courts don't apply that doctrine lightly to rewrite a bad commercial bargain after the fact. A contractor who signs a one-sided bespoke agreement without negotiating shouldn't count on unconscionability to fix it later; the reading has to happen before signing, not after.
A standard-form contract like CCDC 2 names a defined consultant role with defined authority to certify payment and assess completion as a matter of course. A bespoke owner-drafted contract very often skips this entirely, leaving no independent third party responsible for certifying that work is actually complete before payment is released or holdback starts its clock. Where that role is missing, the practical fix is to propose adding one, or at minimum to agree in writing on who signs off on completion milestones and what evidence that sign-off is based on — because without it, the two parties are left negotiating “is this done” from scratch at every payment stage.
A worked example
A homeowner hands a general contractor a four-page agreement they drafted themselves: scope, price, and a payment schedule tied to milestones, with nothing said about holdback, dispute resolution, or what happens if a permit delay pushes the schedule. The contractor is in Ontario and, tempted by the short document, is about to sign as-is.
Running it against the CCDC 2 subject checklist immediately flags three gaps: no holdback mechanism described (even though the statutory 10 percent obligation applies regardless of what the contract says), no dispute-resolution process named, and no allocation of risk for permit or inspection delay. None of these gaps make the contract unenforceable, but each one is a place where the parties will be improvising under pressure later if it isn't addressed on paper now — and the fix, in every case, is adding a clause before signing, not relying on the statute or a court to fill the gap after a dispute has already started.
Yes. The Construction Act applies to most improvements to real property in Ontario regardless of the project size or the parties involved — a bespoke contract's silence on holdback doesn't remove that statutory obligation.
The statutory obligation still applies by default, but the contract's silence leaves the process — timing, documentation, who administers it — undefined, which is worth fixing with an added clause rather than leaving to be sorted out later under pressure.
Yes, and it's a reasonable ask on a project of any real size — there's nothing unusual about a contractor proposing a recognized standard form instead of a bespoke document with unknown gaps. Whether the owner agrees is a negotiation, not a legal requirement either way.
Neither automatically. CCDC 2's risk usually hides in the supplementary conditions layered on top of a familiar base; a bespoke contract's risk usually hides in what it never addresses at all. Both need to be read closely, just for different reasons.
That's a real gap worth fixing before signing, not after. A standard-form contract typically names a consultant with defined authority to certify completion and payment; where a bespoke agreement is silent on that role, proposing a written sign-off process avoids relitigating “is this done” from scratch at every payment milestone.
A 30-minute call is enough to tell you whether AI pays for itself here.
