Scope creep
Work that slips into a project without anyone agreeing to it, one reasonable-sounding request at a time.
Updated October 2026 · with examples from our own builds
What does scope creep mean in practice?
Scope creep rarely arrives as one big ask. It comes as a bug report that is really a new feature, a 'quick' extra screen, or a rule nobody mentioned until the demo. Each piece looks cheap; together they move the launch date and the budget, and nobody can point to the moment it happened.
Refusing changes isn't the cure; labelling them is. Every request gets sorted as either a defect against the agreed scope, which the team owes you, or new work, which gets its own estimate and a decision. A founder who sees that list stays in charge of the trade-off between features and the date.
Watch for decisions hiding inside a request. 'Add VAT' sounds like one feature, but it carries questions about prices, rates and registration thresholds that someone has to answer before any code is useful.
Scope creep at a glance
- Early warning
- Requests described as fixes that no document or test covers
- Who guards it
- Whoever owns the written scope on each side
- Cheapest defence
- A shared list of open requests, each labelled defect or new work
Where has scope creep come up in our builds?
When Trainr shared a 27-claim technical review in July 2026, two items, push notifications and UAE VAT, turned out to be new features rather than defects. For VAT we listed the decisions needed first: tax-inclusive or exclusive prices, the 5% rate, trainers above and below the AED 375,000 registration threshold, and TRN collection.
The proposal closed with 22 scoping questions grouped by how much each one changes the build, hardest first, so the irreversible choices were settled before any estimate. Discovery only; nothing was built.
Common questions about scope creep
How can I tell a bug from a new feature?
Check it against what was agreed. If the written scope or an acceptance test says the system should already do it, it's a defect. If nothing written covers it, it's new work however small it looks, and it deserves an estimate before anyone starts.
Is scope creep always the client's fault?
No. Teams add unrequested polish too, and a vague specification invites both sides to fill gaps their own way. A labelled list of open requests, kept by both sides, shows where the growth is coming from.
Related terms
Planning a product and not sure where scope creep fits? Ask us, or browse all 116 terms in the glossary.