How do you stop scope creep?

Scope creep is usually described as a client behaviour and is more accurately a consequence of two things the supplier did. The first is a quote that stated what was included and not what was excluded. The second is absorbing the first small change without pricing it, which establishes the rule for everything after and does so without either party discussing it.

The exclusions half is the easier fix and the one most resisted, because listing what is not included feels like inviting objections. It does the opposite: it removes the ambiguity in which creep lives. A quote that says what happens if something is found on the day, what is not covered, what would constitute additional work and how it would be priced has settled those questions while the relationship is cordial, which is considerably cheaper than settling them mid-job.

The second half is about the first change rather than the accumulation. Almost every difficult scope conversation traces back to one early request that was small, reasonable and absorbed without comment. That was the moment the rule was set: changes are free and do not need to be discussed. Every later attempt to price one is then experienced by the client as a change in the supplier's behaviour, which is exactly how a routine variation becomes a dispute.

The remedy is procedural rather than confrontational. When a change is requested, say what it does to the price and the timescale, in the same conversation, before doing it. That is not a refusal, it is information, and clients accept it readily when it arrives as a normal part of how the supplier works. Where the change genuinely is trivial and you intend to absorb it, say that too — I will include that, it would normally be extra — which keeps the norm intact while still being generous.

Written confirmation is what makes it stick, and it can be short. A message confirming what was agreed, what it changes and what it costs, sent the same day, prevents the reconstruction that otherwise happens at the invoice. Most disputes about scope are not disagreements about what should have been charged; they are two people with different memories of a conversation neither wrote down.

One structural point for larger work. Where a project runs long enough for changes to accumulate, a stated change process — how a change is requested, who approves it, how it is priced — turns each variation into a routine transaction rather than a negotiation. It also gives the person on your side who is uncomfortable saying no a procedure to point at, which is usually what they were missing.