Nobody objects to change in principle. Clients object to being told, in month four, that something they thought was included is not — and that it now costs money and time.
The damage is almost never caused by the change itself. It is caused by the surprise, the timing, and the tone.
Why teams avoid raising them
Delivery teams absorb small changes because raising one feels like an accusation, and because the process is heavier than the change. So the first change order of an engagement is often the fifth actual change, arriving with accumulated resentment on both sides.
Service Performance Insight's 2024 Professional Services Maturity Benchmark scored change control process effectiveness at 3.44 out of 5 across surveyed firms. That is a process that exists and is only partly trusted — which matches what most delivery leads would tell you.
Raise it at the moment of discovery, not the moment of impact
The cheapest change order is the one raised the day you notice the divergence, when it is still a small number and no work has been wasted. The expensive one is raised when the schedule is already slipping and the conversation is about blame.
Make noticing somebody's job. A standing agenda item — 'anything we have found that is not in scope?' — costs two minutes a week and moves most change conversations forward by a month.
Frame it as a choice, not a bill
A change order that offers one option reads as an invoice. A change order that offers three reads as advice.
Present the impact and then the paths: do it now at this cost, defer it to a later phase, or drop something of equivalent size from the current scope. Clients who choose rarely feel charged.
- State what changed, and against which assumption or requirement in the SOW.
- State the effort, schedule, and fee impact separately — schedule often matters more.
- Offer do-now, defer, or trade-out, with the consequence of each.
- Say what happens if no decision is made, and by when it is needed.
Keep the mechanism proportionate
A process requiring a signed amendment for a two-hour change will be bypassed, and a bypassed process is the same as none. Set an effort threshold below which the client project lead can approve by email, and reserve formal amendments for material change.
Track the small ones anyway. Ten unlogged two-hour favours are a week of unpaid work and, more importantly, an invisible pattern that your next estimate will repeat.
Write the assumptions that make change orders easy
A change order is only comfortable to raise when the SOW already says what you assumed. 'The estimate assumed six source systems; discovery of a seventh is the change' is an observation. Without that assumption written down, the same conversation is an opinion against an opinion.
This is the practical argument for a thorough assumptions section: it is not defensive paperwork, it is what lets you raise scope changes without accusing anyone of anything.
Treat the pattern as estimating feedback
Review your change orders quarterly and sort them by cause. Changes caused by genuine client direction are healthy. Changes caused by things discovery should have surfaced are an estimating problem wearing a commercial costume.
The second category is where your discovery question set gets better. Every recurring change order is a question you were not asking.
Sources
- 2024 Professional Services Maturity Benchmark — Service Performance Insight
Figures are quoted as published by their source. Some benchmark reports require registration or purchase for full access.
Put this into practice
SOW Studio turns discovery inputs into structured scope, a reviewable estimate, and a client-ready Statement of Work — with your team approving every step.
No credit card required. Full Professional capabilities for 14 days.