Scope Creep: How to Recognise, Price and Approve a Change
Scope creep is rarely a client behaving badly. It is almost always two organisations holding different pictures of the same sentence, discovered late.
The word suggests bad faith, which is why change conversations so often start badly. In practice, the overwhelming majority of scope disputes come from a proposal written at a level of generality that let both sides agree without discovering they disagreed. "Review the procurement process" is a sentence two people can sign while imagining two months of difference.
Treating it as a documentation problem rather than a conduct problem changes what you do about it. You cannot make clients stop asking for things. You can make the boundary specific enough that a request is visibly outside it, and you can make the change conversation cheap enough that people have it rather than avoiding it.
The three documents that prevent most disputes
- A deliverables schedule that names each output, its format, its approximate length or depth, its acceptance criteria, and the number of review rounds included. "A report" is not a deliverable. "A report of approximately forty pages covering the six processes listed, with two rounds of client comment" is.
- An assumption register that records what the estimate relied on: the number of entities in scope, the availability of data in a particular form, the number of interviews, the responsiveness of the client's team. Each assumption is a tripwire that converts a surprise into a documented change.
- A dependency schedule that lists what the client must provide, by when, and what happens if it is late. Late client input is the most common cause of overrun and the least often priced.
Recognising a change while it is still small
Changes are cheap to raise in the week they occur and expensive to raise at the end. The practical difficulty is that the person who notices is usually the most junior member of the team, who is not sure whether it counts and does not want to be the one who slows things down.
Two habits fix this. First, make raising a possible change a low-status, no-consequence act: anyone can log one, logging one is not an accusation, and triage happens weekly. Second, give the team three concrete tests they can apply without judgment: does this ask for an output not on the deliverables schedule, does it contradict an assumption on the register, or does it require more review rounds than were included. Any of those is a change, whatever anyone's intent.
Pricing it honestly
A change should be priced on the same basis as the original estimate, and the estimate should be shown. Clients rarely object to paying for more work. They object to a number arriving without a derivation, because it reads as opportunism.
Price the whole effect, not just the direct effort. A change that adds two weeks of work usually also moves a milestone, extends the period over which the team is held, and may push a deliverable past a date the client has committed to elsewhere. Stating the schedule effect alongside the fee effect prevents the situation where the fee is approved and the date is assumed to be unchanged.
Be equally willing to price a change at zero. A firm that absorbs small requests visibly, and says it is doing so, buys a great deal of goodwill for the moment when it cannot.
Approval, and the failure mode nobody plans for
Every change control clause states who may approve. Very few state what happens when nobody does. That gap is where firms lose money: the work is urgent, the approver is unavailable, the team proceeds on a verbal assurance, and three months later the finance department declines to pay for something with no approval on file.
The clause should therefore say three things. Who may approve, at what value. What happens to the schedule while a change is pending, which is usually that the affected work stops and the milestone slips by the elapsed time. And what happens if there is no response within a stated number of working days, which is usually that the change is treated as rejected and the plan is rebaselined accordingly. Silence should never mean yes, and it should never mean the firm works for free.
Keeping the commercial position current
The most common cause of a margin that collapses in the final month is a set of approved changes that never reached the commercial position. Each one was agreed, each was correct, and none was reflected in the budget or the invoice schedule.
The discipline is simple to state and easy to skip: an approved change updates the fee, the plan and the forecast at the moment it is approved, not at the end. If the change log and the commercial position are held in the same system, this is automatic. If they are held in a document and a spreadsheet, it depends on someone remembering, and eventually nobody does.