Users keep asking for small extras. How do I prevent scope creep?
Accumulating unapproved scopeSmall requests become a large commitment when their combined impact is invisible. Capture each request, compare it with the agreed scope, and obtain a deliberate trade-off decision before implementation.
What to do now
- Record the requested addition
- Check the agreed scope boundary
- Estimate its cumulative delivery impact
- Approve, exchange, defer, or reject the request
When to escalate
Escalate when
The combined additions threaten an agreed constraint.
Who decides
The scope owner and authorized sponsor
Example
Five half-day additions consume several days, so the sponsor exchanges them for a lower-priority report.
Mistake to avoid
Absorbing every small request to avoid an awkward conversation.
Prevent a repeat
Review ambiguous requirements and unresolved acceptance conditions before the affected work begins.
Suggested ApprovedFlow setup
- Projects
- Tasks
- Documents
- Approvals
Keep the agreed scope and acceptance evidence with the project; record any proposed change and its decision separately. See the platform
Related cases
- How can we manage scope when users discover needs during delivery?Evolving requirements
- Our requirements document is approved, but users still disagree. Why?Approval without shared understanding
- How do we keep change control lightweight for a small team?Proportionate change recording
- New improvement requests keep preventing closure. What should we do?Open-ended completion scope