Scope creep can begin when an informal request becomes a delivery commitment before anyone checks what changed. To catch it, compare the request with authorized work, assess the effect, and route the decision to the right person. A small request may be reasonable; it still needs a clear place in the project.
Listen for the point where a request becomes a promise
“While you are working on this, could you also…” is a request to assess, not automatic permission to begin. The same applies to an extra review round, a new stakeholder interview, a different output format, or a request to implement recommendations that were scoped as analysis.
The issue is not the wording or the client's intent. It is whether someone has changed the delivery commitment without making the effect and authority clear. The team can also create scope creep by adding work that nobody requested because it seems like a useful improvement.
PMI's Top Five Causes of Scope Creep discusses small requests acted on outside change control, team-added functionality, and processes that are too cumbersome to use. A workable process needs to make evaluation easy enough to happen.
Three warning signs to check
The request changes the expected output
Compare the requested result with the agreed deliverable and acceptance expectations. A clarification may fit the existing work. A new output, expanded audience, or different level of detail may need a change decision. If the baseline is unclear, surface that uncertainty instead of automatically labeling the client's request an extra.
The plan changes while the record stays the same
Watch for new tasks appearing in working notes or informal messages without corresponding updates to commitments, owners, dependencies, or approvals. The team may be following a newer promise while the project record still describes an older one.
Someone promises a result before checking the effect
“That should be quick” does not establish the effort or the consequences. Check preparation, review, dependencies, acceptance, and the effect on other authorized work. Do not invent an estimate merely to make the response sound definite.
Use a response that keeps the decision open
Try language that acknowledges the request without committing the team:
“I have captured the request. I will compare it with the agreed work and assess the effect on our commitments. Then we can confirm whether it is included or needs a change decision, and who can approve it.”
When the boundary is already clear, explain the affected output and the next decision. Acknowledging a request is different from approving it. Keep the record clear about which happened.
Example: adding a workshop to an analysis engagement
Illustrative example: An engagement includes interviews and a findings report. The client also asks for a staff workshop to implement the recommendations.
First check the agreed work; the workshop may already be included in a commitment recorded elsewhere. If it is an addition, assess the preparation, facilitation, review, staffing, and schedule implications. Present the authorized decision-maker with options such as a separate phase or a formally revised engagement.
Do not begin preparing the workshop while describing the request as “still under discussion.” That creates a delivery commitment before the decision is settled.
Keep the process proportionate
A small team may use a short record in an existing tracker rather than a separate form for every request. The essential information is what was requested, what it affects, who can decide, the decision, and which commitments need updating.
Keep useful changes possible. The purpose is to control authorization and consequences, not to reject every new idea. For the operating steps, read Reducing Scope Creep in Consulting: A Control Framework.
Connect the start to active delivery
If the team keeps reconstructing what was sold, review project readiness before kickoff. If the initial position was clear but current requests and decisions are becoming difficult to track, the priority is active delivery control.
Explore The Client Delivery System — Project Delivery & Control for guidance on authorized work, scope, changes, commitments, decisions, and the Current Delivery Position. The Start Here book guide explains how it fits with the other Workflow Lift books.