Noticing scope creep while it is still small
Nobody notices the third small request. Everybody notices the eleventh, by which point raising it looks like an accusation.
Scope creep is almost never a single large demand. It is a sequence of requests that are individually trivial, each easier to do than to discuss, arriving over weeks.
The failure is not that they were accepted. It is that nobody was counting. For a broader look at proactive behaviour at work, learn more adds useful context.
Log every request, including the ones you absorb
The mechanism is a list. Date, what was asked, estimated effort, and whether it was charged, absorbed or declined. Thirty seconds per entry.
The log does two things. It makes the cumulative total visible to you, which is when it becomes possible to raise. And it makes the conversation specific — nine requests totalling fourteen hours, listed — rather than a vague complaint about the client asking for too much.
Small goodwill items are good business. Untracked, they become a pattern that nobody chose. Tracked, they are a decision you can point to when the next one arrives. For a broader framework, PMI's overview of project management summarises the standard concepts behind planning and delivery.
Watch for the signals
- 'While you're in there' — the most reliable phrase in scope creep.
- A new stakeholder appearing at review stage with different expectations.
- Feedback that reopens something already approved.
- Requests framed as clarifications of something the brief did not mention.
- The brief being described differently than it was written, casually, in a call.
Raise it at the threshold, not at the breaking point
Decide in advance what the threshold is — a number of hours, or a percentage of the estimate — and raise it when it is crossed rather than when you are annoyed.
A threshold makes the conversation procedural: we agreed forty hours, we are at fifty-two with these additions, here is what I suggest. Raised from frustration in week eight, the same conversation carries an accusation nobody intended.
Say yes with a consequence attached
Refusing small requests damages relationships and is rarely necessary. The workable response is agreement with the effect stated: yes, that is about three hours, which moves delivery to Thursday or adds to the final invoice — which would you prefer?
Most clients choose immediately and without resentment. What causes trouble is silent acceptance followed by an unexplained invoice or a missed date.
Review the log at the end
At project close, the log tells you how much unbilled work the engagement absorbed. Across several projects it tells you something more useful: whether this is a client problem, a scope-writing problem, or a habit of yours.
Studios that run this exercise usually discover the answer is the middle one, which is the one entirely within their control.