How to Handle Scope Changes Without Losing Your Schedule

What counts as a scope change on a construction site?

A scope change is any modification to the original agreed work — adding a room, removing a feature, switching a material, or adjusting a specification that affects cost or time. On Thai SME builds they arrive constantly: the owner wants a bigger kitchen, the architect finds a design clash, an inspector requires a firebreak that was not in the drawings. None of these events is unusual. What separates projects that absorb them cleanly from those that spiral is whether each change goes through a documented step or disappears into a LINE message that everyone reads differently three months later when the final account arrives.

Why do scope changes always feel harmless when they arrive?

Every scope change looks minor in the moment it is requested. Adding a second bathroom seems like a four-day job. Extending the covered parking by two metres is just concrete and a few more roof sheets. The danger is that construction tasks are linked, so a four-day addition to Block B pushes the waterproofing start, which pushes the tile installation, which bumps the MEP inspection. Each change is real but invisible in isolation. Only when several accumulate does the true schedule cost become visible — by which point it is too late to renegotiate without absorbing the loss.

A worked example: Khun Amorn's five-month house build

Consider a hypothetical five-month house build at 2.4 million baht. By month two the owner has requested three additions: a ceramic floor upgrade in the master bedroom worth 22,000 baht, an outdoor sala that adds ten days of structural work, and a second split-unit air-conditioning point on the upper floor. None was priced in the original contract. The sala is straightforward to agree but pushes the roofing subcontractor back twelve days, delaying weatherproofing and all first-fix MEP behind it. The project finishes four weeks late and the contractor absorbs roughly 55,000 baht in holding and crew costs because every change was agreed verbally with no schedule check.

Document every change before work begins

The single most effective habit for staying in control of scope changes is to write the change down, have the owner acknowledge it, and check its schedule impact before any site work starts. It does not need to be a formal contract amendment for small additions. A short note sent and confirmed on LINE, or a task record in the project management system, is enough to create a reference both parties can point to. The record must exist before the work starts, not be reconstructed from memory after the final account becomes a dispute.

How do I check the schedule impact of a scope change?

Open the Gantt and find the tasks directly affected by the change. Look at what is linked downstream: which tasks cannot start until the changed work is complete? Add the estimated extra duration to that bar and read the new finish date. In SiteBoard's Gantt planning view, extending a task bar propagates the shift to every dependent task automatically, so you can see the full knock-on effect in seconds. That result — extra days, moved milestones — is what you bring to the owner: not just the cost of the change, but its true schedule cost in calendar days.

Show the schedule impact before you agree to any addition

Making the schedule impact visible before you commit to a scope change transforms the whole conversation. An owner who requests a sala extension in week eight often does not realise that adding it then means the concrete crew has already mobilised elsewhere and will need to return. When you open the Gantt and trace the dependency chain with the owner watching, they see the impact directly rather than receiving it as a surprise weeks later. Agreeing to a scope change with both parties looking at the updated schedule simultaneously turns it from a contractor problem into a shared decision.

Keep the owner informed when scope changes move the plan

If the owner sharing link is live, your client is already watching the schedule. The moment a scope change shifts a milestone, update the Gantt and add a short note to the relevant task explaining what changed and why. The owner sees the adjustment the same day rather than discovering weeks later that the handover date has quietly moved. A contractor who flags the schedule impact of an owner-requested change the day it is agreed looks competent. One whose schedule drifts without explanation loses trust even when the delay was the owner's own decision.

Build a change register, not a chat trail

A change register is a running record of every scope change: the date agreed, what it adds or removes, the cost adjustment, and the schedule impact in days. It does not need to be elaborate — a short note per change in the task record is enough. Without it, the record is a LINE thread that scrolls away and becomes impossible to reconstruct. With it, the final account conversation takes minutes rather than weeks, because both parties agreed on the impact in writing along the way. Contractors who keep change registers have fewer disputes and collect their final payment faster.

What if the owner keeps adding small changes that feel too minor to document?

This is the most common form of scope creep on Thai construction sites. Apply the same documentation rule regardless of size: if the change adds more than half a day of labour or any material cost, it gets a record. Set that expectation with the owner at the start of the project as part of how you run the job, not as a reaction to a dispute. Most owners accept the process once they understand it protects them too — a clear change record means no surprises in the final account, which almost every owner will agree is preferable.

Can a scope reduction ever recover lost schedule time?

Yes. When a project is already behind, one of the fastest legitimate recovery options is agreeing with the owner to defer or remove scope that sits on the critical path. Deferring the fit-out of a storage room, for example, can free the crew days they would have spent there to focus on a critical task instead. Frame the deferral as phasing — the deferred work is handled separately after handover under a small additional contract — and document the reduction the same way you would document an addition. A deliberate scope reduction is a professional recovery tool, not a sign of failure.

Do scope changes affect the payment draw schedule?

They should, but they rarely do unless the contractor raises it explicitly. An addition that moves the completion date by two weeks also moves the final payment draw by two weeks. If the contract ties payments to completion stages, a scope change that delays a stage should either trigger an interim payment or result in an adjusted milestone date that both parties agree to. In SiteBoard's Gantt planning view, update the milestone diamonds alongside the task bars every time a scope change is recorded, so the owner sees the revised payment timing on the same shared page where they watch progress.