Treadstone Associates
Article · 9 min read

Reviewing a construction contract with AI

The high-value use is comparison. Canadian construction runs largely on standard forms, so the risk in a contract you are handed is usually not in the printed form — it is in the supplementary conditions that amend it, and an AI comparison surfaces those in minutes.

Treadstone Associates · Updated 2026

Key takeaways

  • • Most Canadian construction contracts start from a CCDC standard form. Comparing what you were sent against the base form is the fastest way to see your real risk.
  • • The output is a list of flags — deletions, added obligations, shortened notice periods — not an opinion on whether to sign.
  • • Extract every date, notice period and deadline into one schedule. Missed notice provisions cost more than bad prices do.
  • • Payment, holdback and lien timelines are statutory as well as contractual, and the statute does not care what your contract says.

Contract review is two different jobs, and only one of them is legal work. The first is mechanical: what does this document actually say, what has been changed from the version everyone assumes, and what dates does it impose on me. The second is judgement: given all that, what should I do. AI does the first well enough to change how a small contractor operates. It does not do the second, and a tool that offers to is selling you a liability.

Why comparison is the killer application in Canada

Canadian construction has an unusual advantage here: a widely used set of standard documents. The Canadian Construction Documents Committee maintains the standard contract forms, guides, statutory declarations and bonds that most of the industry works from — among them CCDC 2, the stipulated price contract and CCDC 4, the unit price contract.

That matters because when an owner or general contractor sends you a contract, the document is usually the standard form plus a set of supplementary conditions that amend it. The supplementary conditions are where risk gets moved. A model asked to compare the document you received against the base form produces exactly the list you want: what was struck, what was added, and which clause numbers were touched.

This is a genuinely hard task to do by eye on a Friday afternoon, and a genuinely easy one for software. It is also verifiable — every flag it raises points at a clause you can read in ten seconds.

The seven things worth extracting on every contract

Payment mechanics. When an invoice is due, what must accompany it, and what triggers the obligation to pay.

Holdback. How much, released when, and on what event.

Notice periods. Every clause of the form "within X days" — especially for delay, extra work and disputes.

Change and extra work. Who can authorise, in what form, and what happens to work done on a verbal instruction.

Scope by exclusion. What the contract says is yours that your price assumed was somebody else’s.

Indemnity, insurance and bonding. What you are agreeing to carry and whether you can actually get it.

Termination and suspension. On what notice, and what you are paid for work in place.

The date schedule is the part that pays for itself

Ask the model for one more thing: a single table of every time period in the document, expressed as an event and a number of days. Most contractors have never seen their contract in that form, and it is startling. A clause requiring written notice of a delay claim within five working days is not unusual, and it is unenforceable by you if nobody knew it was there.

That schedule then becomes an operational artifact rather than a legal one. It goes on the job folder, and the notice periods get diarised on the day the contract is signed, not on the day something goes wrong.

Where the contract stops being the whole answer

This is the boundary that a purely document-based review will miss, and it is important. Payment, holdback and lien rights in Canada are governed by provincial legislation as well as by your contract, and the legislation prevails over inconsistent contract terms. So a contract that appears to give you 90-day payment terms may be sitting on top of a statutory prompt payment regime that says otherwise.

That override is written into the Act itself, not just implied by practice: Construction Act, s.4 makes void “an agreement by any person who supplies services or materials to an improvement that this Act does not apply to the person or that the remedies provided by it are not available for the benefit of the person.” A supplementary condition that purports to waive prompt-payment or lien rights altogether is not just unenforceable in spirit — it is void on its face, regardless of what the subcontractor signed.

Our sister firm covers the Ontario position in prompt payment in Ontario: rules and deadlines and, in short form, in prompt payment under the Construction Act. Holdback has its own rules — holdback under the Construction Act — with a tax wrinkle most people get wrong the first time, set out in HST on holdback payments in construction contracts. And lien rights run on statutory deadlines that no contract can quietly extend: the construction lien deadline in Ontario.

An AI review will not tell you any of that, because none of it is in the document. This is precisely why the output is a flag list for a person and not a recommendation.

A worked example

A mechanical subcontractor receives a 46-page subcontract from a general contractor for a mid-rise project. It is a familiar-looking form with 14 pages of supplementary conditions appended.

The AI pass takes about 20 minutes. Comparison against the base form flags 31 amendments; 24 are administrative, seven are not. Among the seven: the notice period for a delay claim has been shortened, a pay-when-paid style provision has been inserted into the payment article, the indemnity has been widened beyond the subcontractor’s own negligence, and a clause has been added requiring the subcontractor to accept the owner’s schedule revisions without adjustment to the contract price.

The date table returns 19 time periods. Four of them fall inside the first month of the job.

What happens next is entirely human. The seven flags go to a lawyer, because at least three of them are worth negotiating and one may not be enforceable in the way it reads. The 19 dates go into the project calendar regardless of how the negotiation turns out. The general contractor gets a marked-up response the same week rather than three weeks later. The value of the AI was speed and completeness of the read; the value of the lawyer is knowing which four of the seven are worth a fight.

The line you should not cross

It is worth saying plainly. A model can tell you what a clause says and what it appears to change. It cannot tell you whether the clause is enforceable, how a court in your province has treated similar wording, or what to concede. Where the money is significant or the wording is unusual, that is legal advice — see breach of a construction contract in Ontario for what is actually at stake when it goes wrong, and change order disputes with a contractor for the most common flashpoint.

Common questions

Can I upload a client’s contract to a public AI tool?

Check what you have already agreed to first. Many construction agreements contain confidentiality terms that cover the contract itself — confidentiality clauses in contractor agreements explains the usual shape. Where the terms are strict, use a tool that does not train on your inputs and keep the file inside your own systems.

Will it draft my supplementary conditions?

It will produce something that reads like them. Whether it protects you is a different question, and one you cannot evaluate without the expertise the drafting was meant to replace. Drafting from a lawyer-prepared template is the safer version of this idea.

Does this work for the small residential contracts I actually sign?

Yes, and arguably better — short contracts hide risk in what they omit. Ask what a standard form covers that this document does not, and you will get a list of gaps worth closing.

Know what is in the contract before you price the risk.

A 30-minute call is enough to tell you whether AI pays for itself here.