Clients & Contracts
How to Handle Scope Creep in Freelance Projects
Most scope creep isn't bad faith — it's an undefined boundary nobody drew clearly enough.
What is scope creep?
It's when a project gradually grows beyond what was originally agreed — an extra revision here, a "quick addition" there — without a corresponding adjustment to the price or timeline. Individually, each request seems small. Collectively, they can turn a well-priced project into an unprofitable one.
Why it happens
Vague contracts and undefined scope are the root cause almost every time. If "a website" isn't broken down into specific pages, features, and revision rounds, there's no shared reference point for what counts as "extra" — so it doesn't feel like scope creep to the client, even when it clearly is to you.
How to define scope in your proposal
List specific deliverables, not vague categories. "A homepage, about page, and contact page, with up to 2 rounds of revisions" leaves far less room for ambiguity than "a website."
Price your project with a built-in buffer
The calculator adds a margin for scope creep automatically when quoting a project.
Go to the free calculatorHow to say no to extra work (nicely)
A simple, non-confrontational script works well: "That's outside what we originally scoped — I'd be happy to add it as a separate item at $X, or we can look at adjusting the current scope to make room for it." This reframes the conversation from a conflict into a simple choice.
How to charge for out-of-scope requests
Having a pre-set hourly or per-item rate for additions, stated in your original contract, makes charging for extras feel like a normal part of the process rather than an awkward negotiation each time it comes up.
When to accommodate vs. when to push back
Small, genuinely minor requests are sometimes worth absorbing for goodwill, especially with a valuable long-term client. The line to watch for is a pattern — a client who consistently adds "quick" requests is testing whether your scope is enforced or just a suggestion.