Good change control means no change is instructed until its cost and time effect are understood, and every change is recorded where the client can see it. The process does not need to be complicated. It needs to be followed every time, including when a decision is made informally on site.
Almost every project changes during construction. The client refines the brief, existing conditions turn out differently, a product becomes unavailable, a design detail needs developing. None of that is a problem in itself. The problem is change that happens without anyone deciding whether it is worth the money.
Where do uncontrolled changes come from?
- A verbal request on a site walk that the contractor treats as an instruction
- Design information issued with changes that nobody flagged as changes
- Late decisions on finishes or specification
- Provisional sums spent without a clear instruction and budget
- Small changes that each look minor but add up
Each of these can end up in the final account as a variation the client never knowingly approved. By then it is too late to decide against it.
What does a simple change process look like?
| Step | What happens | Who |
|---|---|---|
| Request | The change is described in writing, with the reason | Anyone |
| Assess | Cost, time, design and safety effects estimated | Cost manager, design team, contractor |
| Decide | Client approves, rejects or defers | Client or delegated person |
| Instruct | Formal instruction issued under the contract | Contract administrator or employer's agent |
| Record | Added to the change register and cost report | Cost manager |
On a busy job, it helps to set a threshold: changes below a small value can be approved by the project manager within a delegated budget, while anything larger comes to the client. That keeps the process quick without losing control.
Should every change be priced before it is instructed?
Ideally yes. In reality, some changes are urgent and the work cannot wait for a fully agreed price. In that case, instruct with a clear estimate and a not-to-exceed figure where possible, and agree the final price promptly. What should be avoided is instructing open-ended work and finding out the cost months later.
Some contract forms help. NEC's compensation event process, for example, requires changes to be quoted and assessed within set timescales. JCT contracts allow for quotations too. Using those mechanisms properly is part of good change control.
What about the contingency?
Contingency is there to cover risks, not client choices. If a client decides to upgrade a finish, that is a change in scope and ideally needs its own budget or a conscious decision to use contingency for it. Keeping the two separate in the cost report shows the client how much of the risk allowance is left for the things they cannot control.
How does the client stay in control without being overwhelmed?
By seeing change in one place. The monthly cost report should include a change register showing every change, its status and its value, and the forecast final cost including them. A client who reads that every month is rarely surprised by the final account.
Our cost management and project management teams set up and run change control on projects of every size, so decisions are made deliberately and costs stay visible. Talk to Spring & Co if changes on your project feel like they are running ahead of the budget.
