Guide · updated 6 November 2026
How to handle scope creep
Scope creep is the stream of small requests that arrive after the price is agreed, each too small to argue about. Together they add up to unpaid weeks and a missed date. The fix is agreed before anyone needs it: a change clause in the proposal, and a short, priced change request every time.
The cost of small yeses
Tick the requests you'd just do without a change request, and adjust the hours to your project.
- Hours added
- 17
- Over the quote
- 14%
- Unpaid work
- $1,530
- Later delivery
- 0.7 wk
Each one felt small. Together they're 14% more work than you quoted, $1,530 you won't be paid for, and 0.7 weeks later than the date your client is holding you to.
What goes in the proposal before work starts?
What's excluded. A short list of what isn't included is the cheapest protection there is: “excluded: native apps, data migration, copywriting”.
Acceptance criteria per milestone. If “done” is a test both sides can check, “just one more thing” is visibly new.
A change clause. For example: “Any change to the deliverables is written up as a change request with its price and effect on the schedule, and starts only once approved in writing.” The statement of work generator adds one for you.
What do you say when a request arrives?
Say yes to the idea and no to doing it free: “Happy to. It's outside what we agreed, so I'll send a short change request with the cost and what it does to the date.” Most clients expect this; the ones who push back are telling you something useful.
The change request itself is short: what's asked, why it's new, the hours and cost, the effect on the date, and the client's approval. Here's a change request written out in full.
When is it fine to just say yes?
For genuinely tiny things, as goodwill. Write them down anyway, as a line marked “no charge”, so the client sees the favour and the next request doesn't start from zero.
In Devposal, publishing an update shows the client exactly what changed and asks them to approve the new version, so even a free change ends up agreed in writing.
Questions people ask
What is scope creep?
Work added to a project after the scope and price were agreed, without the price or the date changing. It usually arrives as many small requests rather than one big one, which is why it's easy to miss until the project is late.
How do I stop scope creep without upsetting the client?
Agree how changes work before the project starts, then treat every request the same way: welcome the idea, price it in a short change request, and let the client decide. Clients rarely mind a process they agreed to at the start.
What should a change request include?
What's being asked, why it's outside the agreed scope, the hours and cost, the effect on the schedule, and a place for the client to approve it. Keep it to one page.
Should small changes be free?
A few tiny ones can be, as goodwill, but write them down as 'no charge' so they're visible. Several small changes usually add up to days, which is exactly how projects overrun.
Is scope creep worse on fixed-price projects?
Yes, because every extra hour comes out of your margin rather than being billed. On hourly work it lands on the client's budget instead, which still causes friction, so a change process helps either way.