How to respond when a request expands the agreed scope
Acknowledge a useful new request while making its effect on the existing commitment visible.
Read the guide →TOPIC COLLECTION
Scope and Boundaries
Make added work visible and turn a new request into a clear, confirmable choice.
When someone adds work, acknowledge the request before accepting a new commitment. Identify what changes, estimate its effect on the current plan, and offer a feasible choice. Ask the person who can approve that change to confirm what will be added, deferred, replaced or rescheduled.
Distinguish a request from an agreement
A new requirement may be sensible and still exceed the existing plan. “Could we also add this?” does not by itself settle the time, resources or acceptance criteria. Your first task is to understand the request and make those effects visible. You do not need to label the other person difficult to clarify what their request would require.
Use the guides in this topic for different moments: responding to an addition, discussing its tradeoff, recording an agreed change, or making a freelancer's scope boundary clear. A friendly first reply can open a decision; it should not accidentally sound like unconditional acceptance.
Make the cost of the addition explicit
In the fictional Scope Swap case, five hours are available. The core takes four hours and its required handoff takes one, so the full capacity is already committed. A new request needs two hours. Keeping every original commitment and adding the request would require seven hours.
One possible opening is: “The core and handoff already use the five available hours. The addition needs two more. Can we defer the addition, or agree a revised scope that still meets the required outcome?” Keep required work visible. Removing the handoff without approval would hide a consequence rather than resolve the problem.
If more time or help is offered, confirm that it is usable for this task and available before the deadline. An intention to find support is not yet a resource you can put into the plan.
Know which boundary you can set
Employees can describe capacity and ask for a priority decision; they may not control the final scope. Freelancers can refer to the agreed deliverable and propose a new estimate for added work. People with several roles should make existing commitments visible without disclosing unrelated private details. In every role, distinguish what you can decide from what requires someone else's approval.
Confirm what changed
After the conversation, record the revised deliverable, what remains included, any deferred item, the decision owner and the next checkpoint. Then replay the practice with one explicit condition changed. The aim is to understand why an option becomes workable, rather than memorize a sentence that assumes unlimited time.
Choose a practical question
How to lead a clear tradeoff conversation
When a new request does not fit, give the owner a short brief that compares a swap, a deferral, and extra capacity on the same terms.
Read the guide →How to confirm requirements that keep changing
Turn evolving requests into one visible, approved baseline without losing useful feedback.
Read the guide →How freelancers can set scope boundaries without leaving the client stuck
Turn an extra request into an explicit choice about deliverables, available capacity, and approval.
Read the guide →How do I push back on a request politely?
To push back on a request politely, say the fact you hold first, offer what you can say yes to, ask who decides and confirm it in writing.
Read the guide →Make the next choice yourself.
Try a short fictional case, reveal the missing information and replay it.
Site last updated: