Change Orders — changes priced, approved and instructed before they are built
A change order in Constructum names its job, describes the change, prices it, and moves Proposed → Priced → Submitted → Approved → Instructed → Completed — with Rejected and On hold as legitimate endings. Approved is an approval state: it surfaces in the work summary until someone with authority clears it, and nothing in the sequence permits “Completed” to be reached by drifting.
The rule that prevents most disputes
No changed work is built on a verbal. Every construction operation knows the failure mode: the client’s representative asks on site, the crew obliges, the invoice arrives, and the conversation about whether it was authorised starts three months later with money already spent. The module’s sequence is the countermeasure — description and price first, submission to the client, approval on the record, instruction issued, then the work. Where genuine urgency forces work first (a safety or structural necessity), the record is raised the same day and priced immediately after; the exception proves the rule only when it is visible as an exception.
Changes and the contract total
The job’s contract value is its won estimate plus its approved change orders — nothing else moves it. That arithmetic is what progress claims are percentages of, what the 10% holdback under Alberta’s Prompt Payment and Construction Lien Act is calculated against, and what the final account reconciles. A running view of cumulative change — how many orders, what total, what percentage of the original contract — is management information of the first order: a job at 30% cumulative change is a different job from the one that was bid, and it should be managed, and priced, as one.
Rejections are information
A rejected change order stays on the record. It documents that the work was offered, priced, and declined — which closes the later conversation in which the declined scope is remembered as included. On hold is equally explicit: a change awaiting a decision holds its schedule consequences visibly rather than absorbing them silently into delay.
Worked example: on the CHAIN Northgate Yard Expansion, change order CO-1 — deeper footings on grid C where soils fell below design bearing — moved Proposed → Priced → Submitted → Approved → Instructed → Completed, lifting the contract total by its approved amount — the figure the first progress claim was calculated against.