A change order is not a failure. It is a normal part of renovating an existing home, where some conditions only become clear once walls or floors are opened and where decisions can evolve as the space takes shape. What matters is whether there is a clear, fair way to handle change without surprise.
A good change control process protects both sides. Homeowners should know exactly what they are approving, what it costs, and how it affects timing. Builders need a documented baseline to price against, a clean approval path, and the ability to keep the site moving instead of stopping and starting.
In OakWood’s renovation work, we treat change control as professional project management. The goal is not to prevent every change. The goal is to make changes deliberate and legible so the project stays predictable, even when scope evolves.
Why change control matters in real renovations
Renovations tie new work into old structure, old mechanical systems, and finishes that may not be level, square, or consistent. Even with careful planning, some conditions only reveal themselves after demolition.
At the same time, many decisions are made progressively: lighting, storage details, trim profiles, tile patterns. That is normal. The risk is making those refinements after the work has moved past the point where adjustments are cheap.
Without a disciplined change process, small decisions turn into rework, downtime, and arguments. Change control is the mechanism that keeps trust intact when the plan needs to move.
Start with a clear baseline: the scope you are actually buying
You cannot define a change unless you know what is included. The baseline scope is a written set of drawings, specifications, selections, and assumptions that define what the contract price covers.
It should identify what is being built, what products are selected, and what remains unknown. If items cannot be finalized early, the baseline should state whether they are covered by allowances, provisional sums, or a defined unit-rate approach.
When baseline scope is vague, change orders become proxy fights over responsibility. Clear scope does not eliminate change, but it makes change measurable and easier to price fairly.
What counts as a change, and what should not
A fair process separates true scope change from corrections and normal clarifications.
A true change is any instruction that alters the agreed scope, selected products, quantities, sequencing, or performance requirements in a way that affects labour, materials, or time. It can be owner-initiated or triggered by unforeseen conditions once the work is opened up.
A correction is work required to deliver the agreed scope properly. If something was drawn incorrectly, installed incorrectly, or fails inspection due to workmanship, it should not be priced as a change. Ordinary clarifications that do not alter scope should not become paid extras.
The difficult cases usually sit in assumptions. If a condition could not be reasonably confirmed before opening an assembly, added work may be legitimate. The baseline should explain how these discoveries are documented, priced, and approved.
The three impacts every change must address: scope, cost, and time
Fair change control documents every change in three dimensions: the exact scope, the cost, and the schedule impact.
Scope needs to be specific enough to avoid re-interpretation later. Vague language like “upgrade finishes” invites disappointment. A good change description reads like a short specification and notes any dependencies on adjacent work.
Cost should reflect the true driver: labour, materials, protection, demolition, disposal, procurement time, and trade coordination. If the change introduces rework, the cost should reflect the additional effort, not a punitive number. Transparent line items help homeowners make informed decisions.
Time impact protects the project. Some changes add no time. Others trigger rework, new inspections, or long-lead ordering. If the change affects the critical path, that should be stated before approval.
A fair change control workflow, step by step
A benchmark-level change process is simple and repeatable. It does not require bureaucracy. It requires discipline.
Step 1: Initiation in writing, with enough detail to price. Field discoveries include photos and a brief note explaining why the condition was not visible earlier.
Step 2: Definition. Confirm the exact scope and dependencies. Make the design decision before pricing, not after.
Step 3: Pricing. Issue a written proposal and a schedule impact statement. If the change cannot be priced precisely yet, state the pricing method and any not-to-exceed logic, plus what information is needed to firm it up.
Step 4: Approval in writing before work proceeds, except for urgent protection measures required for safety or to prevent damage.
Step 5: Integration. Update procurement and sequencing so the change does not quietly derail the schedule.
Step 6: Close. Track the change to completion, including inspections or documentation it triggers.
How change pricing stays fair: lump sum, time and materials, and unit rates
Pricing method matters because it shapes trust. The right method depends on how well the scope can be defined.
Lump sum works when the change is clear and bounded. Time and materials can be appropriate when the scope cannot be defined without opening assemblies, but it should include daily logs, stated labour rates, and a tight description of what is included.
Unit rates can be fair for repetitive items where quantities may change, such as additional pot lights, extra square footage of flooring, or incremental framing adjustments. The rate must be defined up front, including what it covers, so it cannot be reinterpreted mid-project.
Allowances and provisional sums manage unknowns and selections, but they still need rules: what happens if the chosen item is over or under the allowance, what labour is included, and how differences are approved. They are not a substitute for written change approval.
Why small changes can create big schedule impacts
Change interacts with sequencing. Work inside a home is a chain of dependencies. If one trade must return, it can disrupt the rhythm of the site and cause out-of-sequence work.
Some changes are time-neutral. Others are time-heavy because they trigger rework, new inspections, or procurement. A change that seems small on paper can be large once it touches cabinetry release, countertop templating, waterproofing, or close-in milestones.
Procurement is a common driver. If a change requires a long-lead item, the project may need to pause or shift sequence, which creates inefficiency. A fair change proposal should state this plainly.
Changes that affect structural, plumbing, or electrical work can require additional review or inspection steps. In Ottawa, inspection booking windows can vary, so timing is not always immediate.
A short vignette: how a reasonable change becomes expensive
A homeowner decides late that they want a wider island and a different sink configuration. On paper, it feels like a simple cabinetry adjustment. In practice, it affects cabinet release, countertop templating, plumbing rough-in location, and island electrical feeds. The original cabinets have already been released, so the supplier needs a revision and new lead time. The countertop cannot be templated until the revised cabinets are installed. Meanwhile, nearby finish work that depends on a stable kitchen area cannot proceed cleanly. The change is not wrong. The impact is larger than expected because the decision arrived after the critical ordering moment.
Where change orders go wrong in real life
Most change-related conflict comes from avoidable behaviour, not from the change itself.
Verbal approvals are the biggest risk. If work proceeds on a handshake, nobody is protected. A disciplined process insists on written approval before work continues.
Bundling many small changes into one approval can also create confusion. It becomes hard to understand what is driving cost and what is driving schedule impact, and it is harder to track delivery.
Delayed paperwork damages trust. If pricing arrives long after the work is completed, the owner feels ambushed. If approvals lag while the site waits, the builder absorbs inefficiency. Change documentation is time-sensitive work, not an afterthought.
The final failure mode is misclassifying problems as changes. Legitimate deficiencies, coordination errors, or omissions should be corrected as part of delivering the contracted scope.
What a disciplined change control process looks like in practice
Change control is not a stack of paperwork. It is an operating system that keeps decisions from turning into conflict. In a benchmark-level renovation, you should expect to see:
- Each change has a written description that is specific enough to avoid re-interpretation later.
- Pricing shows the cost driver clearly: labour, materials, and any rework, not a single unexplained number.
- Schedule impact is stated in plain language, including whether the change affects critical-path work or long-lead ordering.
- Approvals are recorded before work proceeds, with one clear approval channel to prevent mixed messages.
- Field discoveries include photos and a short note explaining why the condition could not be confirmed earlier.
- Change tracking stays current, so the owner can see total approved changes to date and what is still pending.
How an integrated design-build team keeps change under control
When design, budgeting, and construction are coordinated by one accountable team, changes are easier to define and price. Sequencing, procurement constraints, and inspection requirements are already part of the conversation, so the change proposal reflects reality on site.
In OakWood’s renovation work, change control ties into the phased structure of the OakWood Design-Build Process®. Early phases reduce uncertainty through scope definition and selections, so fewer changes arrive late. When change does occur, we use a standard approval workflow so the homeowner can decide with full information and the build team can keep momentum.
Decision gates you can use before approving a change
Use these gates to keep changes fair and controlled, even when timing pressure is present:
- The change description is specific, and you can point to exactly what is different from the baseline scope.
- You understand whether the change affects adjacent work, inspections, or ordered items, not just the immediate feature.
- The pricing method matches the uncertainty level, and the cost breakdown makes sense in context.
- The schedule impact is stated, including whether the change forces rework or introduces a long-lead wait.
- Approval is documented in writing before work proceeds, except for urgent protection measures.
- The total of approved changes to date is visible, so you can assess budget drift honestly.
Key terms in plain English
Baseline scope: The drawings, specifications, and selections that define what the contract price includes.
Allowance: A placeholder budget for an item not selected yet, with rules for how overages or credits are handled.
Provisional sum: A placeholder budget for work that cannot be defined early, typically because existing conditions are unknown.
Unit rate: A pre-defined price per unit for an item where quantity may change.
Time and materials: A pricing method where labour and materials are tracked as the work proceeds, usually used when scope uncertainty is high.
Critical path: The chain of tasks that determines the earliest possible completion date.
The point of change control is trust under pressure
Most homeowners will make at least a few changes once a renovation is underway. That is normal. The goal is to avoid the two failure modes that hurt everyone: approving a change without understanding the impact, and executing a change without clear approval.
A fair process keeps the project calm. It keeps the budget legible, reduces downtime, and lowers the number of moments where either side feels trapped.
If you are planning a renovation and want change to be handled professionally, look for a builder who can show you how change is documented, priced, approved, and tracked from day one.
Navigation
- Why change control matters in real renovations
- Start with a clear baseline: the scope you are actually buying
- What counts as a change, and what should not
- The three impacts every change must address: scope, cost, and time
- A fair change control workflow, step by step
- Where change orders go wrong in real life
- Decision gates you can use before approving a change
- Key terms in plain English
- The point of change control is trust under pressure
— CTA —
Visit www.oakwood.ca to explore OakWood’s benchmark design-build process
Email info@oakwood.ca for a professional, no-obligation discussion
Call 613-236-8001 to speak directly with an OakWood expert