A designer shared a story on Reddit that stopped me cold.
They'd landed a project with a major company. Big brand, big budget, exciting work. The client was enthusiastic, complimentary, and easy to work with — at first.
Then the scope started expanding. New deliverables. Additional revisions. Requests that weren't in the original brief. The designer kept saying yes because the client was so positive about the work.
By the end of the project, the designer had done nearly double the originally agreed work for the same fee. When they tried to discuss additional compensation, the client pointed to the vague contract language and said everything was "part of the project."
The designer's own words: they had "zero protection."
The Clause
Here's the single sentence that would have changed everything:
"Additions to the scope of work and/or deliverables may incur extra fees that will be mutually agreed upon before such changes are made."
That's it. One sentence. It does three things:
- Establishes that scope can change — this isn't adversarial. You're acknowledging that projects evolve.
- Establishes that changes cost money — the word "fees" sets the expectation that additions aren't free.
- Establishes a process — "mutually agreed upon before" means both parties approve the change and cost before the work happens.
Why This Clause Works
Most contracts either ignore scope changes entirely or use language so vague that it's unenforceable. "The freelancer will complete the project as described" — described where? Described how specifically?
This clause works because it's:
- Proactive, not reactive. It's in the contract before any dispute. You're not scrambling to establish rules after scope creep has already happened.
- Mutual, not one-sided. "Mutually agreed upon" means both parties have a say. The client doesn't feel trapped.
- Process-oriented. "Before such changes are made" creates a gate. Work doesn't start until both sides agree on the cost.
How to Use It in Practice
Step 1: Include It in Every Contract
Add the clause to your standard contract or service agreement. It should appear in the section about scope, deliverables, or changes.
If you don't have a formal contract, at minimum include this language in your proposal or scope of work. Use our free Scope of Work Generator to build a professional SOW that includes change management language.
Step 2: Reference It When Changes Come Up
When a client asks for something outside the original scope, your response becomes simple:
"That's a great idea. Per our agreement, additions to the scope require a change order with a cost estimate. Let me put one together for you."
You're not saying no. You're following the process that both of you already agreed to.
Step 3: Document Every Change
Every change request should be written down with:
- What the change is
- How it impacts the timeline
- What it costs
- Client approval
This protects both you and the client. They get transparency. You get documentation.
What About Late Payments?
While you're updating your contract language, add a late payment clause too. Something like:
"Invoices not paid within [30] days of the due date will incur a late fee of [1.5%] per month on the outstanding balance."
Use our Late Payment Fee Calculator to see what late fees look like on your typical invoices. Having this language in your contract gives you a professional foundation if you ever need to enforce it.
The Psychology of Contracts
Here's something most freelancers don't realize: the power of a contract clause isn't in enforcement. It's in expectation-setting.
When a client reads that scope changes "may incur extra fees," they approach the project differently. They think more carefully about what they ask for. They consolidate feedback. They respect boundaries — not because they're afraid of the clause, but because the clause has established what "professional" looks like.
The designer from the Reddit story didn't need to sue their client. They needed the client to know, from day one, that additional work costs additional money. That's all.
One Sentence, Thousands Saved
The math is simple. If this clause prevents even two or three unpriced scope changes per project, and you do 10–15 projects per year, you're looking at thousands of dollars in recovered revenue.
Add the clause. Build it into your process. Use a scope of work that includes change management language by default. And when scope changes come up — because they always do — you'll have a professional, documented way to handle them.
One sentence. Thousands saved. Start using it today.