Notice when the request changes shape
A colleague asks you to review a short document. Then they ask you to rewrite a section, gather examples, and join a meeting about the result. Each addition may sound reasonable on its own, but together they have turned a quick review into a different piece of work. Scope creep often starts this quietly: the task grows while the original deadline and your other commitments stay the same.
The useful question is not whether the new request is fair. It is whether the work you are now being asked to do matches what you agreed to do. Look for changes in the expected output, the number of people involved, the level of detail, or the time needed. Noticing that shift early gives you a chance to reset expectations before anyone assumes the extra work is already underway.
Clarify the finish line before you begin
For a small request, you do not need a formal project plan. A brief confirmation can be enough: “I can review the draft for clarity and send comments by Thursday. Are you looking for feedback, or do you need me to make the edits?” This separates two tasks that may sound similar but take very different amounts of time.
Try to establish three things: what you will deliver, when you will deliver it, and what is outside this round of work. For example, a review might include comments on structure and wording but not fact-checking or designing slides. If the request is vague, offer a manageable starting point rather than silently filling in every gap. “I can do a first pass on the introduction and flag anything that needs a broader discussion” gives both of you a clear place to begin.
Pause when an extra task appears
You can be responsive without saying yes immediately. When someone adds a task, acknowledge it and check its impact: “I can see why that would help. Is this part of the review we discussed, or a separate next step?” The question is neutral. It makes the change visible without suggesting that the other person has done something wrong.
If the addition is small and you have room for it, you may choose to take it on. Say what that choice covers: “I can add one example to this version, but I won’t have time to rebuild the full section today.” If it is substantial, discuss what moves to make room. You might ask whether the new task is more important than the original deliverable, whether the deadline can change, or whether someone else can handle part of it. A boundary is easier to understand when it comes with a clear picture of the available options.
Make trade-offs visible, especially when priorities compete
Sometimes the person expanding the request is not aware of everything already on your plate. Rather than trying to prove that you are busy, describe the practical conflict: “I’m scheduled to finish the client summary tomorrow. If I prepare the extra slides, I’ll need to move the summary or reduce what goes into the slides. Which would you prefer?” This keeps the conversation focused on priorities and outcomes.
If different people are assigning work, avoid becoming the sole judge of whose request matters most. Ask the relevant manager or project lead to help set priorities. You can summarize the choices in a short message so everyone is working from the same understanding. Keep the tone matter-of-fact: the goal is not to build a case against a colleague, but to prevent two reasonable requests from turning into an impossible combined commitment.
Close the loop and improve the next request
After you agree on a revised scope, put it in writing, even if it is only a brief message: “I’ll send comments on the draft today. We agreed that the slide outline is a separate task for next week.” This gives others a chance to correct a misunderstanding and gives you a reference if more additions appear. When the work is done, state what you completed and note any remaining decisions rather than letting them linger as implied obligations.
If the same kind of request keeps expanding, look for a pattern you can address earlier next time. Perhaps “quick feedback” usually means hands-on editing, or perhaps approvals bring in new stakeholders. A better opening question or a small time allowance for revisions may help. Preventing scope creep does not mean refusing every change. It means treating changes as choices, with a shared understanding of what they will cost in time, attention, or other work.
