Scope creep is the uncontrolled expansion of work beyond the agreed requirements, resources, schedule or price. It occurs when additions are performed without a corresponding change decision.
What causes scope creep?
- Ambiguous requirements
- Informal customer requests
- Missing assumptions and exclusions
- Weak change control
- Unrecorded dependencies
- Pressure to begin before scope is ready
How does it affect outsourcing?
Small recurring requests can increase staffing, handling time and risk without appearing in the original service measures. Disputes follow when client and provider use different assumptions about what is included.
Scope creep vs. approved change
An approved change updates scope, impact, price, timeline and responsibilities through the agreed process. Scope creep bypasses that control.
How can it be prevented?
Write measurable deliverables, boundaries and assumptions; maintain a request log; assess impacts; and require named approval before implementation. Operational teams need a safe way to escalate requests.
What should be monitored?
Track work volume, exceptions, unpaid activities, change requests and effort by cause. Evidence should distinguish genuine scope growth from poor original estimating.
