Value management is cheap when it happens on a drawing and expensive when it happens on a signed contract. The entire discipline is really just that one timing fact, applied consistently — and most of the cases where it fails are cases where a team ran out of design time and let a decision slide past the point where it was still cheap to make.
Key takeaways
The industry-standard construction contract in Canada, the CCDC 2 stipulated price contract, establishes a single, pre-determined fixed price for the project between the owner and the prime contractor. That single sentence is the entire argument for doing value management before that contract is signed rather than after: once a fixed price exists, changing a specification is no longer a free design decision moving between two equally-unpriced options — it's a change order against a number both sides have already agreed to, with all the negotiation, markup and schedule risk that implies.
A cladding substitution decided during schematic design costs the time it takes to update a drawing and re-run a quantity takeoff. The identical substitution, requested after the CCDC 2 contract is signed and construction has started, costs that same material difference plus the contractor's change-order markup, plus whatever schedule float the change consumes, plus — if the swap affects a system already ordered or partially installed — the cost of undoing work that's already been done. None of that extra cost reflects the material itself being more expensive later; it reflects the fact that the decision moved from being a design choice into being a contract amendment, and a contract amendment carries transaction cost a design choice doesn't.
Treadstone Law's own guidance on change-order disputes gets at the same point from the contractor's side: a detailed, itemized scope matters so much at the signing stage, precisely because that specificity is what determines whether a later change is a clean, priceable amendment or a contested one. A design that arrives at signing still carrying unresolved value-management questions doesn't just cost more to change — it also produces a less itemized scope, which makes whatever change does eventually happen harder to price cleanly.
A value-management exercise is only as useful as the budget it's tested against. Tools built around the construction industry's own cost-code conventions make this concrete: Procore's default cost-code structure aligns with the CSI MasterFormat, organized as a tiered structure based on its 17 divisions. Pricing a proposed substitution against the specific division and cost code it affects — rather than against a single lump project contingency — shows whether the saving is real relative to that line item's own budget, and whether it's large enough to matter against the project's overall cost, both at once. A saving that looks significant against a vague "finishes" allowance can look marginal once it's measured against the actual line-item budget for that division, and the reverse is also true.
The distinction between value management and simple cost-cutting is what keeps the exercise from degrading the building it's applied to. Cost-cutting asks what's the cheapest option that satisfies the specification as written. Value management asks a prior question: what function is this specification actually trying to deliver, and is there a lower-cost way to deliver that same function — not a lower-cost way to deliver less of it. A cladding system swapped for a cheaper one that doesn't meet the same durability or thermal performance isn't a value-management win, it's a scope reduction wearing a value-management label, and the difference tends to surface later as a maintenance or performance problem the original specification was written to prevent.
Value management works best as a scheduled review point, not an informal conversation that happens whenever someone notices a cost line looks high. The review needs the designer who wrote the specification, someone who can price the alternative accurately against the real budget structure rather than a rough guess, and someone with authority to approve a substitution without restarting the whole design-approval cycle. Held during schematic design or design development, before drawings are finalized for pricing, that review can still change a specification cheaply. Held for the first time at the 100%-drawings stage, immediately before tender, it's structurally too late to do much beyond flag items for the change-order process the design team was trying to avoid in the first place — the review still happens, it's just happening on the expensive side of the line this article opened with.
Worked example — the same $40,000 saving, two different totals
A design team identifies a lighting-fixture substitution during design development that saves $40,000 against the electrical division's line-item budget, with no change to the specified lumens, colour temperature or warranty. Decided and drawn before the CCDC 2 contract is signed, the saving flows straight into the fixed price at signing: net saving, $40,000.
The identical substitution, proposed six weeks after the same contract is signed, now requires a change order: the $40,000 material saving, less a contractor markup and administrative fee typically in the 10–15% range on the change-order value, less any cost from fixtures already ordered or partially installed under the original specification.
At a 12% markup on a $40,000 change and $8,000 in already-committed fixture costs that can't be recovered, the net saving drops to roughly $40,000 − $4,800 − $8,000 = $27,200 — the same decision, worth 32% less, purely because of when it was made.
Related reading: Phasing a multi-building project and the inputs a feasibility study needs.
Value management tests whether a specification's intended function can be delivered at lower cost without reducing that function. Cost-cutting swaps in a cheaper option and treats the function question as secondary — which is how a saving turns into a later maintenance or performance problem.
Because it establishes a single fixed price at signing. Before that point, a design change is a free choice between unpriced options; after it, the same change is a priced amendment against a number both parties have already agreed to.
Against the specific cost-code or division it affects, not against a single project-wide contingency figure — a saving that looks large against a vague allowance can look different once priced against the real line-item budget for that division.
Yes, through a change order — but at a real cost premium from markup, administrative fees and any work or materials already committed under the original specification, which is exactly why doing it earlier is worth the design-stage effort.
A 30-minute call is enough to tell you whether AI pays for itself here.
