Scope Creep Clause: Keeping Projects on Track

"Can you just also add..." is how a fixed-price project quietly turns into three times the agreed work, a scope clause is what lets you say yes without doing it for free.

Why this is the clause freelancers regret not having

Scope creep rarely arrives as one big ask, it's a string of small, individually-reasonable-sounding requests that add up to real additional hours. Without a clause defining what's in scope and what isn't, every "quick addition" becomes a negotiation you're having from a weak position, mid-project, with a client who's already expecting it for free.

What the clause needs to define

Element	Why it matters
A specific deliverables list	Anything not listed is, by definition, additional work
A revision limit	e.g. "up to 2 rounds of revisions included", unlimited revisions is unlimited unpaid time
A rate for out-of-scope work	Your hourly rate, agreed upfront, so there's no negotiation needed later

How to word it

Something like: "This agreement covers the deliverables listed above, including up to 2 rounds of revisions. Additional revisions or requests outside this scope will be billed at $[rate]/hour and require written approval before work begins." The "written approval" part matters as much as the rate, it creates a natural pause where the client has to actively agree to the extra cost rather than assuming it's included.

How to enforce it without sounding difficult

Most of the tension disappears if you frame it positively: "Happy to add that, since it's outside the original scope, it'd be an extra $X, want me to go ahead?" That's a normal, professional sentence. It only feels awkward the first few times you say it. See the preventing scope creep guide for more on stopping it before it starts, not just handling it after the fact.