Scope creep kills freelance projects. Not dramatically — slowly, one small ask at a time, until you have delivered twice what you priced.
Here is how to stop it.
Why it happens
Clients do not usually try to exploit you. They just do not understand the scope of what they bought. They think "one small change" is free because it feels small to them.
The fix is not being awkward. It is being clear upfront.
The contract clause that stops most of it
Include this in every contract:
"Any work outside the scope defined in this agreement will be quoted and agreed in writing before work begins. Verbal requests do not constitute scope changes."
When a client asks for something out of scope, you can now say "that is outside what we agreed — I will send a change order" rather than arguing about what was included.
The change order process
- Client requests something new
- You acknowledge it ("good idea, let me scope that for you")
- You send a short email: what the work is, cost, timeline impact
- They approve in writing
- You do the work
Takes 10 minutes. Prevents hours of free work.
The project kickoff document
Send this before you start any project:
- Deliverables (specific, numbered)
- What is NOT included (explicitly)
- Revision rounds included
- What constitutes final approval
- Payment schedule
If a client reads this and signs off, scope creep arguments become very short.
Template included in the Client Onboarding Kit (£9) — along with the contract clause, change order template, and project closure document.
The tracker
Free tool to track deliverables, revisions, and change order status across multiple projects: landolio.com/tools/project-scope-tracker
What is the worst scope creep you have experienced? How did you handle it?
Top comments (0)