Scope creep almost never arrives as a dramatic request. It arrives as a two-sentence email that reads like a favor:
"Quick one, while you're in there, can you also..."
The freelancers who stay profitable aren't the ones who push back hardest. They're the ones who have a rehearsed reply ready, so saying "that's additional" feels routine instead of confrontational.
Below are twelve templates you can paste into Gmail tomorrow morning. Each one handles a specific pattern, names it calmly, and offers the client a path forward. Copy, swap the name, change the numbers, send.
1. The "quick one" request
When to use it: Client emails mid-project with a small-sounding addition that isn't in the signed brief.
Hi [Name],
Happy to look at [the specific request]. It's outside
what we scoped in the brief, so I'd want to add it as
a small change order: about [X hours] of work at my
standard rate (~$[fee]).
Two options:
1. I send a one-line change order today and fold it
into the current phase.
2. We batch it after launch as a small follow-on.
Either works on my end. Which fits your timeline?
[Your name]
Why this works: you said yes before you said "$". You priced it. You offered an exit ("batch it after launch") which often reveals the request isn't actually urgent.
2. The "just one more revision"
When to use it: Contract allows 2 revision rounds. Client used both. They're asking for a third as if rounds don't exist.
Hi [Name],
Good catch on [the tweak]. We've used both revision
rounds included in the brief, so this one falls into
additional revision territory.
I keep that simple: $[200] per extra round, flat fee.
If you want to bundle this with any other tweaks
you've been thinking about, I'll group them into a
single round so you're not paying twice.
Want me to send the invoice and start on the changes
today?
[Your name]
The phrase "bundle with anything else" invites them to think twice. Half the time they realize the one tweak isn't worth the fee and drop it.
3. The surprise stakeholder
When to use it: New decision-maker (CEO, client's client, investor) appears with feedback mid-project.
Hi [Name],
Happy to hop on a call with [Stakeholder]. Quick
prep note so we make the most of it:
I'll bring the signed brief into the call so any new
feedback falls into one of two buckets.
- Within current scope: easy to action right away.
- New direction: I'll write up a quick change order
so we keep the original [launch date] safe.
That way the conversation stays concrete and you
don't have to play translator between us later.
Does [proposed time] still work?
[Your name]
You proactively introduced scope documentation before the call. That alone prevents 80% of stakeholder-induced creep.
4. The "light redesign"
When to use it: Client calls a new visual direction a "small adjustment."
Hi [Name],
Thanks for the feedback. A second visual direction
with [different font, less color, more minimalist]
isn't quite a revision. It's closer to a fresh
concept, which restarts the design phase for me.
I quote new directions at $[fee] each. Before we go
there: I can do 2-3 small color and typography
tweaks within the current direction at no extra
cost, and that usually gets the "lighter" feeling
you're after.
Want me to send two quick variants on the current
direction first, and we decide from there?
[Your name]
Naming what they actually asked for ("a fresh concept") without judgment lets them reconsider. Offering the free alternative almost always wins.
5. The vague "can you add a few more"
When to use it: Client says "add a few more" pages, screens, or components without a number.
Hi [Name],
Happy to add more [pages/screens/sections]. To keep
this clean, can you confirm exactly how many and
which ones? The brief scoped [original number], so
I'll need to write up the extras as a small change
order at $[per-unit fee] each.
Once you send the list, I'll reply with a total
and a revised timeline (usually adds [X days] per
unit).
Thanks!
[Your name]
Never estimate "a few." The client's "few" is usually four and yours is usually two.
6. The "it's not working on [device/browser]"
When to use it: Weeks after launch, client reports an issue on a device you never agreed to support.
Hi [Name],
Taking a look. A note on coverage: the brief scoped
[modern browsers / iOS + Android / latest two OS
versions]. [Specific device] wasn't in scope and
typically needs its own QA pass.
If you'd like me to add it, I can do a full round
of testing and fixes. Usually [X hours] at my
standard rate.
If it's only affecting one or two users, sometimes
the cheaper path is a note on the site that we
officially support [X, Y, Z]. Want me to quote the
full fix, or go the lighter route?
[Your name]
Listing the cheaper alternative shows you're not trying to upsell. Most clients accept the fix once they see you're reasonable about it.
7. The "small tweak" that isn't small
When to use it: "Move the logo slightly" is a one-hour rebuild of the header grid.
Hi [Name],
Totally get what you're going for. Quick heads-up
before I start: that change sounds small but it
actually means redoing [the header grid / the
responsive breakpoints / the spacing system],
about [X hours] of work.
I'm happy to do it, and it falls under additional
revisions. I'd write it up at $[fee] so we stay on
the same page.
Want me to proceed, or do you want to sit with it
for a day first?
[Your name]
The "sit with it for a day" line is important. It signals you're not pressuring them and often results in the client dropping the request voluntarily.
8. The deadline that moved
When to use it: Client pulls the deadline forward without mentioning the scope also needs to shrink.
Hi [Name],
Understood on the new [launch date]. To hit it
without cutting corners on quality, something in
the current scope needs to move. A few options:
1. Drop [feature/page/section] from this phase and
add it as a phase 2 after launch.
2. Keep everything in scope and I add a rush fee
of $[fee] to cover [weekend/overtime] work.
3. Keep the original timeline as-is.
Let me know which one fits best and I'll confirm
the plan by end of day.
[Your name]
Three clear options force a real decision. "Yes to everything" isn't on the list, which is the whole point.
9. The "can you just hop on a call"
When to use it: Client escalates every small question into an hour-long call.
Hi [Name],
Happy to sync up. For quick questions like this
I'm usually faster over email. I can reply in 10
minutes between work blocks, whereas calls tend to
push the deliverables back by half a day.
If you'd rather call, I hold a weekly 30-min project
sync on [day/time] where we can batch anything that
came up. Want to send your questions by email in
the meantime, or save them for the sync?
[Your name]
Batching unplanned calls into a weekly slot preserves deep-work time without looking unavailable.
10. The "small copy change" on a dozen pages
When to use it: Client asks for what looks like one edit but is actually a site-wide change.
Hi [Name],
Got it. Heads-up: "[change] everywhere" means
updating [X pages/screens/templates], which is
closer to a copy-pass than a single edit.
I can do it. Would normally spec this as either:
- Hourly pass: ~[X hours] at my standard rate.
- Flat fee for a full copy review across all pages:
$[fee].
The flat fee tends to be better value if you've got
other wording tweaks you've been sitting on. Which
works better?
[Your name]
Offering two options (with the flat fee making the hourly look worse if they have more tweaks) gets clients to surface the additional asks they were holding back.
11. The "scope is a bit loose" client
When to use it: Client refuses to sign off on a brief. You need to protect yourself before work starts.
Hi [Name],
Before I block off the [week/month] for this, I
want to make sure we're aligned on scope, mostly
to protect your budget from surprises.
I've drafted a short brief with deliverables,
timeline, and an "out of scope for this phase"
section. It's meant to be a working doc. If
something is missing or needs changing, let me
know and I'll revise before we start.
Quick sign-off on this is what unlocks the start
date on [date]. Can you review and reply with any
changes by [day]?
Draft: [link]
[Your name]
The phrase "protect your budget from surprises" reframes the brief as something the client benefits from, not a barrier you're putting up.
12. The post-launch "while you're here" request
When to use it: Project has shipped. Client asks for an unrelated new feature as if it's still part of the engagement.
Hi [Name],
Really glad [project] is live. On [new request]:
that's a fresh project scope, so I'd handle it as
a separate engagement rather than tacking it on.
I can send over a short proposal, usually takes
me 24 hours to put together once I know roughly
what you're after. A few quick questions to help
scope it:
1. What's driving the timing? Is there a launch
or event it needs to tie to?
2. What does "done" look like for this?
3. Any rough budget range I should work against?
Once I have those I'll send a proper quote.
[Your name]
Treating every new ask as a new project, even if you end up charging the same hourly rate, stops the current engagement from turning into a permanent on-call retainer you never agreed to.
How to actually use these templates
Three rules that make the difference between templates that work and templates that get ignored:
- Send them fast. A reply within 2-3 hours sets the norm. A reply three days later reads like you're reluctantly agreeing to something you've already been doing quietly.
- Keep the tone consistent. Never send one template aggressively ("this is out of scope, $500") followed by an apologetic one ("sorry, I can just do it, no worries"). Pick the voice and hold it across every reply.
- Anchor everything back to the brief. The brief is the contract. If your brief is vague, these templates are 40% as effective. If your brief is specific, every deliverable named, every out-of-scope item listed, these templates do the work for you.
That last one is the leverage point. Briefance generates briefs that call out gaps and out-of-scope items before you send them to the client, so the "[feature] is outside scope" line in template 1 isn't a claim. It's a reference to a signed document.
One more thing: know when NOT to send these
Not every request is creep. If a client asks for something that's:
- Under 15 minutes and clearly your oversight, just do it.
- A legitimate clarification of something in the brief, explain, don't charge.
- Related to a typo or bug you shipped, fix it and move on.
The templates above are for requests outside the brief, not for every minor back-and-forth. Using them reflexively trains clients to feel nickel-and-dimed, which ends the relationship faster than eating the occasional small ask.
Rule of thumb: if the request would take you longer than 15 minutes and isn't cleanup from something you shipped, it's a change order, and one of the 12 templates above is the reply.