Most freelancers think scope creep is inevitable. It is not. It is almost always a contract problem.
Here is why it happens and how to stop it.
Why scope creep happens
The client did not read the contract carefully. You did not define done clearly enough. Someone said "can we just add..." and you said yes to avoid an awkward conversation.
Usually all three.
The three documents that prevent it
1. A clear brief before work starts. Not your brief — theirs. Ask them to write down what success looks like. People are less likely to move the goalposts when they wrote them.
2. A scope statement in the contract. Specific deliverables. Not "a website" but "a 5-page website with home, about, services, portfolio, and contact pages, with the copy provided by the client." And critically: "The following are NOT included..."
3. A revision clause. Two rounds of revisions included. Additional rounds at £X per hour. Put a number on it.
The conversation that saves you
When the inevitable "can we just add..." arrives:
"Happy to include that. Just to let you know, that falls outside our original scope — I can do it for an additional £X, or I can swap it for [something in scope]. Which would you prefer?"
You are not refusing. You are pricing. This is a normal business conversation.
The clients who get angry at this question were going to be a problem anyway.
The document that makes this automatic
Every project I start with the Client Onboarding Kit kick-off document. It forces the scope conversation at the start, when everyone is happy and aligned, instead of in the middle, when emotions are running high.
£9. Cheaper than the first hour of a scope creep dispute.
What is your worst scope creep experience? How did you resolve it?
Top comments (0)