Scope creep has arrived. You noticed it two weeks ago. You have been absorbing it, telling yourself you will address it next week. Now the client thinks the expanded scope is the engagement.
The scope creep conversation practitioners avoid is not the conversation itself. It is the version where the client feels accused, the practitioner feels like they are asking for more money, and the relationship cools. That version of the conversation exists. But it is not the only version.
The Scope Conversation Protocol is a three-stage approach for addressing scope creep in a way that resolves the drift without creating the accusation dynamic. The check-in system from Article 18 is where scope creep is first detected. This article covers what to do once you have seen it.
Why Practitioners Absorb Scope Creep Instead of Addressing It
The most common reason practitioners absorb scope creep is that addressing it feels like accusing the client of trying to get something for free. Most clients who push the scope are not doing it deliberately. They are doing it because the boundary was not clearly drawn.
The second reason is that practitioners underestimate the cost of absorption. Absorbing one addition feels like good client service; absorbing five over three months feels like being taken advantage of. The practitioner who absorbs consistently is not being generous. They are eroding the relationship while the client sees nothing.
The scope conversation, done well, is not an accusation. It is a clarification. It distinguishes what was agreed from what has grown, and it allows both parties to make an informed decision about how to proceed.
The Scope Conversation Protocol
The Scope Conversation Protocol addresses scope creep in three stages, each of which is designed to be brief, specific, and non-confrontational.
Stage 1 names the scope creep before it compounds
The first stage is the most important and the one practitioners delay longest. Naming scope creep early, when it is one or two additions, is much easier than naming it after it becomes an assumption.
The language for stage one is observational, not accusatory: “I want to check in on the scope of what we’re working on. I’ve noticed we’ve been covering [specific additions]. I want to make sure we’re both working from the same picture of what the engagement includes.”
This language accomplishes two things. It names the specific additions (not a vague concern, but a concrete observation). And it frames the conversation as a check-in rather than a complaint.
Stage 2 determines whether the scope change was intentional
Most scope additions are not intentional requests by clients for extra work at no charge. They are natural extensions of the conversation that neither party has stopped to evaluate.
Stage 2 is a diagnostic question: “Was this something you wanted to add to the engagement, or did it come up organically?” The client who responds with “oh, I thought that was included” has given the practitioner a clear path: revisit the original scope document together. The client who responds with “actually, yes, I was hoping we could cover that” has opened a conversation about what an expanded scope looks like.
Either way, the conversation is now productive rather than avoidant.
Stage 3 resolves the scope formally
Stage 3 is the resolution: either the engagement is returned to the original scope, or the scope is expanded and the engagement is repriced accordingly.
The resolution should be documented. A brief note after the conversation, naming what was decided, prevents the same conversation from being necessary again in three weeks.
The practitioner who documents the resolution is not being legalistic. They are being clear. Clarity is what prevents the next round of creep from silently replacing the conversation that was just had.
How the Conductor Defines Your Scope Boundaries
Halfway through an engagement, the client asks for one more thing that was never in scope. The founder wants to keep the relationship and protect the engagement at once, and has thirty seconds to decide how.
The Conductor is Kiluma’s context-aware AI. It reads the scope conversation records and resolution language the founder has saved to the Living Library across past engagements.
Asked how scope creep was handled before and what language kept the relationship intact, the Conductor returns the responses that worked. The phrasing that held a boundary without straining the relationship is there, from conversations the founder has already navigated.
The boundary becomes clear and defensible before the next request arrives. Not improvised in the moment, but ready.
Have the Conversation Before Week Five
The scope conversation is most effective early. Before week five, scope creep is a small drift. After week eight, it has become an assumption.
Name what you have observed using the Stage 1 language. Keep it brief. Keep it observational. Give the client the opportunity to clarify whether the additions were intentional.
If you have already passed week eight without addressing scope creep in a current engagement, the conversation is still worth having. It is just harder. Use the Stage 2 diagnostic question to determine how to proceed rather than continuing to absorb.
Does Your Current Engagement Still Match the Scope Agreement?
The scope conversation you are avoiding is not as hard as the one that happens at month five when resentment has accumulated on both sides.
Does your current engagement still match what was agreed? If not, that is where the conversation starts. Try Kiluma free for 14 days at kiluma.ai.