Hustle Studio

Freelance scope creep emails: what to say in 6 common situations

Most scope-creep advice comes down to "ask for more money" plus one generic template. In practice the right reply depends on what the client asked for. A five-minute favour, a whole new feature and a fourth round of revisions need different answers. Below are six situations, the reply that works for each, a change order you can copy, and a small calculator for pricing the extra work.

First: decide what kind of request it is

Before replying, check the request against what you agreed in writing (proposal, contract or kickoff email). It will fall into one of three buckets:

In scope. It's covered. Do it, no discussion needed.
Small and out of scope. Under about 30 minutes, and it's a one-off. You can absorb it on purpose, but say so (see reply 1).
Real extra work. Anything bigger, or a pattern of small asks. It needs a price and a change order before you start.

The single most important rule is to reply before you do the work. Once extra work is delivered, asking to be paid for it feels like a surprise invoice. Before you start, it's just a quote.

Reply 1: the small favour you decide to absorb

Doing small things for free is fine, but name it, or it quietly becomes the new baseline.

Hi [Name], Sure, I've made that change. It's outside what we scoped, but it was quick, so there's no charge this time. For anything else beyond the agreed scope, I'll send a short quote first so there are no surprises on the invoice. [Your name]

Reply 2: a new feature or deliverable

Treat it as good news (the client wants more of your work), then put a price and a timeline impact next to it. Offer a choice instead of a yes/no.

Hi [Name], Good idea. [Feature] would make sense for [reason]. It isn't part of the current scope, so here are two ways to handle it: 1. Add it now: [price], and the delivery date moves from [old date] to [new date]. 2. Do it as a follow-up phase after launch, so the current date stays the same. Let me know which you prefer and I'll send a one-page change order to approve. [Your name]

Reply 3: revisions beyond the agreed rounds

Point to the number you agreed and make the next round easy to buy. Don't argue about whether the feedback is "really" a revision.

Hi [Name], Thanks for the notes. Just a heads-up: we've used the [2] revision rounds included in the project. I'm happy to keep refining. Additional rounds are [price per round / hourly rate, est. X hours]. If that works, reply "go ahead" and I'll start on these changes today. If it helps, I can also suggest which of these notes would make the biggest difference, so we can focus a single round on those. [Your name]

Reply 4: "Can we just hop on a quick call?" (again)

Meetings are scope too. If your quote assumed two check-ins and you're on your sixth, offer an async option first, then a paid one.

Hi [Name], Happy to help. Could you send the questions by email? I'll reply in writing by [time], which also gives us a record to refer back to. If a call is easier, I can do [day/time]. Calls beyond the check-ins in our plan are billed at [rate], so let me know if you'd like to book one. [Your name]

Reply 5: the deadline moves earlier

A tighter timeline is a change in scope even when the deliverables stay the same. Give options: a rush fee, a smaller first delivery, or the original date.

Hi [Name], Understood that [date] is now important. Here's what's possible: 1. Full scope by [new date] with a rush fee of [amount], since I'll need to move other work. 2. A first version with [core items] by [new date], and the rest by the original date at no extra cost. 3. Keep the original date of [date]. Which works best? [Your name]

Reply 6: the slow drip of "one more small thing"

No single request is big, but together they add up to a day or more. Bundle them, and reset expectations in one message instead of fighting each one.

Hi [Name], I've collected the extra requests from the last couple of weeks: - [Request 1] - [Request 2] - [Request 3] Together they come to about [X] hours, which is outside the original scope. I'd suggest we add them as one change order: [price]. Once that's approved, I'll fold them into the next delivery. Going forward I'll keep a running list like this, so you can decide what's worth adding. [Your name]

The change order template

A change order is a short written agreement that the scope, price or timeline has changed. Keep it to one page. Approval can simply be a reply email saying "approved". You don't need a formal signature for small changes, but you do need it in writing.

CHANGE ORDER #[1] Project: [Project name] Date: [date] Client: [Client name] Original agreement: [proposal/contract name, date] Requested change [One or two sentences describing exactly what is being added or changed.] Not included [What this change does NOT cover, e.g. "copywriting for the new page".] Price impact: +[amount] (new project total: [amount]) Timeline impact: [none / delivery moves from X to Y] Payment: [added to final invoice / 50% due before work starts] All other terms of the original agreement stay the same. Approved by: ____________________ Date: __________ (Replying "approved" to this email also counts as approval.)

Free change order price calculator

Estimate the hours, and the calculator adds the communication overhead people forget, applies a rush multiplier if needed and rounds up. It runs in your browser, and nothing is sent anywhere.

Estimated hours for the extra work Your hourly rate Communication / admin overhead (%) Timeline

Example with the defaults: 6 hours plus 15% overhead is 6.9 hours. At 75 per hour that's 517.50, rounded up to 520.

How to prevent most scope creep before it starts

Write a "Not included" list in every proposal. Three to five bullets of things clients commonly assume are included (copywriting, stock photos, extra pages, ongoing support).
Put numbers on the fuzzy parts. Say "2 revision rounds" rather than "revisions", and "2 check-in calls of 30 minutes" rather than "regular check-ins".
Repeat the scope in your kickoff email. A short recap gives you something neutral to point back to later.
Price your hourly rate for extra work in advance. If the proposal already says "additional work billed at [rate]/hour", replies 2–6 are a reminder, not a negotiation.
Do a mid-project check-in: "Anything else you'd like included before we lock version 1?" Surfacing requests early is far easier than handling them at the end.

Common mistakes

Saying yes on a call, then pricing it by email later. On the call, say "Let me check how that fits the scope and come back to you today."
Apologising for charging. You're giving them an option, not asking a favour. Keep the tone friendly and plain.
Only mentioning money and leaving out time. Clients often care more about the deadline than the price, so always state both.
Absorbing everything until you're resentful. Then one large, late conversation damages the relationship more than six small, early ones would have.

Related guides

How to quote a freelance project (with a worked example and calculator). A well-scoped quote prevents most of the situations above.
How to tell existing clients you're raising your rates (5 email templates)
Freelance late payment emails: overdue invoice reminder sequence

Want the full set?

The Freelance Pricing & Quote Kit ($12) includes a pricing calculator and three-tier quote builder, plus a scope & change order pack: a scope-of-work section with "Included / Not included" lists, a kickoff recap email, this change order, a change log and short versions of the replies above. Set the scope clearly up front and most of these conversations never happen.