The project started simple. A landing page. Three blog posts. A logo redesign. Whatever it was, there was a clear scope, and everyone agreed to it.
Then the requests started. "Can you also add a contact form?" "Actually, can we do five blog posts instead of three?" "Oh, and could you update the old pages too while you're in there?"
Each request seems small. And each one, individually, probably is. But they add up fast. And before you know it, you're doing twice the work for the same price you quoted.
This is scope creep, and if you don't address it with a clear, professional email, it will eat your profitability alive.
Why You Need to Send This Email
I know what you're thinking. "Can't I just mention it on our next call?" You can. But you shouldn't.
Email creates a written record. When you discuss scope changes verbally, there's room for different recollections later. "I thought we agreed that was included" becomes a real argument when there's nothing in writing. An email that clearly outlines what's changing, what it costs, and what happens next protects both of you.
It also gives the client time to think. Bringing up additional costs on a call can feel confrontational. An email lets them process, check their budget, and respond thoughtfully.
The Scope Change Email Template
This template works when the client has requested something that falls outside the original agreement and you need to address it formally.
Subject line: Scope update for [project name]
Hi [Name],
>
I wanted to flag something about the [project name] scope before we get too far along.
>
Based on our recent conversations, the project has evolved a bit from the original plan. Specifically:
>
- Original scope: [brief description of what was agreed]
- Additional requests: [list the new items or changes]
>
I'm happy to take on the additional work. I just want to make sure we're aligned on the impact to timeline and budget before I move forward.
>
Here's what the additions would look like:
>
- Additional cost: [amount or revised total]
- Additional time: [revised timeline or added days/weeks]
>
If you'd like to move forward with everything, I can send an updated agreement for your records. If you'd prefer to stick with the original scope, that works perfectly too. We can also talk about prioritizing some of the new items and saving others for a Phase 2.
>
Let me know how you'd like to proceed, and I'll adjust accordingly.
>
Thanks,
[Your Name]
Clean. Direct. Professional. And it gives the client options, which is key.
Why This Structure Works
You're flagging, not complaining. The tone isn't "you keep asking for more stuff." It's "the project has evolved and I want to make sure we're on the same page." This is collaborative, not adversarial.
You list the specifics. Putting the original scope and the additions side by side makes it impossible to argue about what changed. The evidence is right there in the email.
You give them choices. This is the most important part. You're not issuing an ultimatum. You're presenting options: move forward with everything at the new price, stick with the original scope, or find a middle ground. Clients respond well to choices.
You mention an updated agreement. This signals professionalism. You're not just asking for more money via email. You're offering documentation. If you use FreshBooks or QuickBooks for invoicing, updating the project estimate or contract there keeps everything organized.
When to Send the Scope Change Email
Timing matters. Here's the decision framework.
Send it early. The moment you realize the scope is shifting, flag it. Don't wait until you've already done the extra work and then ask to be paid for it. That's a much harder conversation.
Send it before doing the additional work. This is critical. If you complete the additions and then send the email, you've lost your negotiating position. The client got what they wanted. The conversation shifts from "do you want to approve this?" to "can you pay for something I already gave you?" which is weaker.
Send it when the change is clear, not speculative. Don't send a scope change email because you think the client might ask for more. Wait until there's an actual request or pattern of requests that you can point to.
If you're not sure whether something constitutes scope creep or is a reasonable ask, check your original contract or proposal. If the request isn't in there, it's a scope change. Simple as that.
Template for Small Scope Changes
Not every scope change needs the full formal treatment. Sometimes it's a small addition that's easy to address quickly.
Hi [Name],
>
Quick note on the [additional request they made]. That falls a bit outside our original scope, but it's a pretty straightforward addition.
>
I can handle it for [cost] and it would add about [time] to the timeline. Want me to go ahead?
>
[Your Name]
Short, professional, and it gets a yes or no answer quickly. Use this for additions that are genuinely small, like an extra page, an additional revision round, or a format change.
Template for When the Scope Has Been Creeping Gradually
This is the harder email. The scope didn't change in one big request. It changed through a dozen small ones over several weeks, and now you're way beyond the original agreement.
Subject line: Let's realign on [project name] scope
Hi [Name],
>
I want to take a step back and look at where we are with [project name] compared to where we started.
>
When we kicked off, the scope was [original scope]. Since then, we've added several things along the way:
>
- [Addition 1]
- [Addition 2]
- [Addition 3]
- [Addition 4]
>
Each of these made sense individually, and I was happy to accommodate them. But looking at the full picture, the project has grown pretty significantly beyond the original agreement.
>
I want to make sure we handle this fairly for both of us. Here are a couple of options:
>
1. Adjust the budget to reflect the current scope. I estimate the additional work totals about [amount], bringing the project total to [new total].
2. Scale back to the original scope and save the additions for a follow-up project.
3. Split the difference. We keep the most important additions and table the rest for later.
>
I'm flexible on how we handle this. The main thing is that I want us both to feel good about the arrangement going forward.
>
Can we chat about this briefly this week? Happy to jump on a quick call, or we can sort it out over email if you'd prefer.
>
Thanks for understanding,
[Your Name]
This email is longer because the situation is more complex. The gradual creep needs documentation, and offering multiple solutions shows you're being reasonable.
How to Handle the Response
Most clients respond well to scope change emails. They appreciate the transparency. Here's how to handle common responses.
"Sure, go ahead with the additional cost." Great. Send the updated agreement immediately. Don't just take a verbal yes. Get it in writing, even if it's just their reply to your email saying "approved."
"Can you do it for less?" This is a negotiation, and that's fine. You can adjust the scope, reduce the number of revisions, extend the timeline, or find some other way to bring the cost down without undervaluing your work. But don't just say yes to a lower number to avoid conflict.
"I thought that was included." This is why your original scope documentation matters. Point back to the original agreement, politely but clearly. "I hear you, and I can see how it might have felt related. Let me pull up the original scope so we can look at it together."
"We don't have the budget for that." Then the additions need to come off the table, or the original scope needs to shrink to make room. You're not a charity. If they want more work, it needs to be compensated.
Preventing Scope Creep in the First Place
The best scope change email is the one you never have to send. Some prevention strategies.
Be specific in your proposals. Don't write "website redesign." Write "redesign of home page, about page, and contact page, including mobile responsive layouts. Additional pages available at $X per page." Specificity gives you something to point to later.
Use your welcome email to reinforce scope. Restating the scope at kickoff, in writing, creates a clear reference point.
Address additions immediately. The moment a client says "can you also," respond right away with "sure, that would be [X] extra and [Y] more time. Want me to add it?" Don't let them accumulate.
Build a buffer into your quotes. Not a huge one. But a small buffer for minor adjustments keeps you from having to send a scope change email over every tiny thing. Save the formal email for the real changes.
Scope management isn't about being difficult. It's about running a sustainable business. Your time has value, and protecting it with clear communication is the professional thing to do.