A change that is agreed verbally on site and priced three weeks later is how a profitable job turns into a disputed one. Build the process before the first change order, not after the fifth.
Key takeaways
STEP 01 OF 10
CCDC's own guide names four elements every change process needs: key terms, the change process itself, methods for adjusting the contract price, and how claims are handled. Adopt those four categories explicitly in the firm's own template rather than inventing a parallel structure — it means every project, regardless of which prime contract form it uses, runs the same internal logic.
A firm that has never written down its own change philosophy tends to default to whatever the most persuasive site conversation produces — which is not a philosophy, it is exposure.
STEP 02 OF 10
A change moves through three distinct states: someone directs a change (a site instruction or a request for a quote), someone prices it (a change order proposal with a dollar figure and a schedule impact), and someone approves it (a signed change order). Treat these as three separate documents, even on a fast-moving site, because collapsing them into one verbal exchange is exactly how disputes about scope and price get tangled together later.
The instruction document alone is enough to start the paper trail — it does not need a price attached yet, but it needs a date, a description, and who gave it.
STEP 03 OF 10
Use the same unit rates and labour costs that built the original bid to price a change, and flag any change that requires a rate the original schedule of values did not contemplate. A change priced inconsistently with the base contract's own numbers is the first thing an owner's consultant will challenge, and the challenge is usually right to be raised.
Where a change affects both scope and schedule, price both impacts in the same document. A change order that only states a dollar figure and is silent on schedule impact tends to resurface as a separate delay claim months later.
STEP 04 OF 10
The default rule should be: no signed change order, no change work. Build one narrow exception for genuine field conditions — a concealed condition discovered mid-excavation, for instance — where safety or schedule makes stopping work impractical, and require written notice within a stated number of hours even when the signature has to follow after the fact.
A firm that treats every verbal request from an owner's rep as an implied change order is the firm that ends up unable to prove, months later, which of a dozen field conversations was actually authorized.
STEP 05 OF 10
Keep a running total of approved change orders against the original contract sum, updated with every approval, not reconstructed at closeout. This total is not just a bookkeeping figure — in Alberta, it is a direct input into the statutory substantial-performance test under s.33(4) of the Prompt Payment and Construction Lien Act, which is calculated against the contract price. A change order that pushes the contract past a pricing tier changes that threshold, and a scheduler tracking substantial performance needs the current cumulative price, not the original one.
See standing up a scheduling function for how that substantial-performance date interacts with the project schedule once it moves.
STEP 06 OF 10
In Ontario, unpaid extras and change orders can be included in a construction lien claim — but only when they are properly documented as an addition to the original contract, not asserted after the fact from memory. Treadstone Law's guidance on this point is direct: the documentation from steps two and three above is exactly what makes an extra defensible in a lien claim later. See extras and change orders in a lien claim.
This is the clearest argument for the three-document structure in step two: a lien claim built on a signed change order with a clear price and date is a fundamentally stronger claim than one built on "the owner's rep told us to."
STEP 07 OF 10
An approved change order should appear on the very next progress claim, not accumulate until closeout. See a payment application cycle that runs itself for the certification step this feeds into. A backlog of unbilled change orders is cash the firm has already spent and not yet claimed — and every month it sits unbilled is a month closer to a dispute about whether it was ever approved at all.
This also keeps the holdback calculation accurate: holdback is calculated against the value of work done, and unbilled change work is real work done that a delayed billing cycle is temporarily hiding from that calculation.
STEP 08 OF 10
A change order proposal that gets rejected, reduced, or disputed should stay in the log with its outcome recorded — not deleted or quietly dropped. This is the record that shows a pattern if one owner's rep repeatedly directs work verbally and then disputes the price, and it is the record a dispute-escalation process (see escalating a dispute before it becomes a claim) will need.
A change log with only approved entries tells half the story. The disputed half is usually where the actual risk sits.
STEP 09 OF 10
A monthly review that puts the change log next to the current schedule and the current budget catches two things a change-by-change review misses: whether cumulative change orders are quietly eroding a contingency line, and whether a cluster of changes in one trade is a sign of a design or coordination problem worth raising with the owner directly.
This is the step that turns a change log from a defensive paper trail into an actual management tool.
STEP 10 OF 10
Every change order — approved, rejected or disputed — should be reconciled and archived as part of the project closeout process, with its final status confirmed in writing. See project closeout in thirty days for how this fits into the broader closeout sequence. A change log with open items at final payment is a liability sitting on the books with no clear owner.
Archive the whole log, not just the approved total — the six-year federal record-retention rule under ITA s.230 applies to the supporting documents behind a change order the same way it applies to the invoice itself.
Treating a verbal site instruction as an implied change order. Without a signed price and a documented instruction, the work is exposed and the extra may not survive scrutiny in a later lien claim.
Letting change orders accumulate unbilled until closeout. Every month of delay in billing an approved change is a month the holdback calculation is running on understated work-done, and a month closer to a payment dispute about it.
Deleting or ignoring rejected change proposals instead of logging them. The disputed half of the change log is usually where the real risk sits, and it is the first thing a dispute-escalation process will need.
Pricing a change with rates the original schedule of values never contemplated. Inconsistent pricing is the first thing an owner's consultant will challenge, and it is often a legitimate challenge.
Forgetting that a change order moves Alberta's substantial-performance threshold. A cumulative change total that is not fed back into the scheduling function produces a stale substantial-performance date.
Alberta's substantial-performance test is a direct formula against the contract price — which means a change order does not just add cost, it moves the threshold. Here it is, worked before and after a change.
Before the change. A $1,200,000 contract: 3% of the first $500,000 ($15,000), plus 2% of the next $500,000 ($10,000), plus 1% of the remaining $200,000 ($2,000) — a substantial-performance threshold of $27,000. Work can be certified substantially performed once what remains to complete or correct falls to that figure or below.
After a $150,000 change order. The contract price is now $1,350,000: the same 3%/2% tiers apply to the first $1,000,000 ($25,000 combined), plus 1% of the remaining $350,000 ($3,500) — a new threshold of $28,500. The change order did not just add $150,000 of work; it moved the substantial-performance bar by $1,500, which is exactly the kind of shift that has to be re-run every time a change is approved, not assumed static from the original bid.
This is Alberta's statutory test specifically — Ontario has no equivalent percentage test in its Construction Act, and Nova Scotia uses a flat 2.5% rather than Alberta's tiered structure. Never carry one province's substantial-performance formula into another.
The idea that "substantial performance" has a single, calculable percentage test across Canada is one of the most widely repeated errors in this field — and it directly affects how a change order should be tracked.
A change-order log that tracks cumulative contract price is useful in every province; a change-order log that assumes Alberta's formula applies everywhere will misstate the threshold anywhere else.
That depends entirely on the authority granted in the prime contract — CCDC-based contracts typically route change orders through the consultant, but the firm's own template should name explicitly who has signing authority on each project rather than assuming it is the same person every time.
An unpriced instruction is still evidence the change was directed, which matters if the dispute escalates — but pricing it as soon as possible, even provisionally, strengthens the record considerably.
No — keep them in the log with a rejected status. Removing them loses the record of what was proposed and why it did not proceed, which is exactly the record a later dispute may need.
The process should scale, not disappear — a minor field adjustment can use a lighter-weight instruction-and-confirmation step, but it should still leave a dated, written record rather than none at all.
A 30-minute call is enough to tell you whether it is worth building.
