What to say to a client about scope creep (with real wording)
The exact sentences for telling a client something is out of scope - without sounding difficult, losing the work, or starting an argument about what was included.
The hard part of scope creep was never noticing it. You noticed the third "quick favour" weeks ago. The hard part is the sentence you have to type next - the one that says this is extra without sounding petty, rigid, or like you are about to send a surprise invoice.
This page gives you that wording. Real, complete sentences you can copy, adjust and send, plus the reasoning behind why each one works, so you can write your own version when the situation does not match exactly.
How to tell a client something is out of scope
The wording that works almost always does three things in this order:
1. Say yes to the person before saying no to the request. People hear "no" first and stop listening. Opening warmly buys you the next sentence. 2. State it as a fact about the agreement, not a judgement about them. "This falls outside what we scoped" is neutral. "You keep adding things" is an accusation, even when it is accurate. 3. Offer a route forward, not a wall. A client who hears only "no" has one option: argue. A client offered two paths picks one.
Here is that structure as a message you can actually send:
Happy to help with this. Quick flag: this one falls a bit outside what we scoped originally. I can either fold it into the current timeline with a small extension, or quote it as a separate add-on - whichever works better for you. Let me know which you'd prefer and I'll get started.
Notice what is missing: no apology, no lengthy justification, and no mention of money before the client has chosen a direction. Apologising invites negotiation about whether the boundary is real.
What to say the third or fourth time it happens
One request is a request. Four is a pattern, and the wording has to name it - otherwise you are agreeing to a new normal by staying quiet.
I want to flag something before it grows into a bigger issue: we've had a few additions over the last few weeks that sit outside the original scope - [name one or two, plainly and without editorialising]. Individually they're small, but together they add real time. Can we take ten minutes to align on what's in scope from here, and how we handle new things as they come up?
The phrase doing the work is "before it grows into a bigger issue". It frames you as protecting the project rather than defending your territory. Naming one or two specific examples matters too: vague complaints get argued with, specifics get acknowledged.
What to say when the client says "but it's such a small thing"
This one catches people out, because the client is often right that the individual item is small. Arguing that it is actually big loses.
Totally get that it feels small on its own - it's the accumulation on my side that adds up. I'd rather keep things clean and predictable for both of us than let small asks quietly turn into unpaid work. If it's important, let's approve it properly so it's tracked; if it can wait, we can bundle it into the next phase.
You concede the point and hold the boundary anyway. "For both of us" is not filler - it reframes the process as mutual protection, which is genuinely true: clients dislike surprise invoices as much as you dislike unpaid work.
A better way to say "scope creep"
Do not use the phrase with clients at all. It is industry jargon that sounds like an accusation, and most clients have never heard it.
Say instead:
- "outside what we scoped"
- "a separate piece of work"
- "an addition to the original agreement"
- "a change request"
The last one is the most useful, because it sounds like a normal process step rather than a complaint - which is exactly how you want additions to feel.
The part most people skip
Wording alone leaks. If additions are not written down somewhere with an estimate attached, you end up in a conversation about memory - and by invoice time nobody agrees on what was extra.
Keep a running list. Date, what was asked, who asked, rough hours, and whether it was approved. It takes seconds per entry and it changes the dynamic completely: a request logged as "+4 hours, approved by [name]" stops being a favour and becomes a decision the client made knowingly.
If you want the number that makes this worth doing, our scope creep cost calculator runs the arithmetic for your own rate. Most people are surprised, and the surprise is what changes behaviour.
When the conversation does not fit any of these
The situations above cover most of it, but not all. The moments that need their own careful wording are: a formal change request with time and cost attached, protecting a deadline once scope has already grown, refusing genuinely new work outright, and resetting expectations for the next project after a messy one.
Those are in the Freelance Scope Creep Defense Kit - seven scripts covering every one of those moments, plus the Change Request Log as a ready-made spreadsheet. The first script is readable in full on that page, so you can judge the wording before deciding whether the rest is worth it.
But the three scripts above are complete and free to use. If they solve your situation, you do not need anything else from us.