How to Write a Scope Change Email (Without Damaging the Relationship)
The scope change email is the one freelancers avoid the most — and the one that costs them the most when they skip it.
The client asks for something new. You say "sure, I can do that." You spend 10 hours on it. Then when the invoice comes, they don't remember agreeing to extra charges — and suddenly you're in an awkward negotiation over work you already did.
The scope change email fixes this. Written before you do the work, it documents what changed, what it costs, and gets written agreement. It's not adversarial — it's professional. Good clients expect it. It protects both of you.
What every scope change email needs
- What changed: Be specific about what's new versus the original scope
- Timeline impact: Be honest — additional work takes additional time
- Cost impact: State the additional cost clearly. No vague "this might affect pricing"
- A request for written approval: "Please reply to confirm" — this is the whole point
- No apology: You're not doing anything wrong by documenting this
Scope change email example
Hi Jordan,
Following our recent conversation, I want to document the additions to the Website Redesign project before I begin implementation.
The three items below fall outside the original scope:
1. User Authentication System — Login/signup with session management
2. Email Notifications — Automated alerts for user actions
3. Admin Dashboard — Internal tool for content management
Original scope: Public-facing website with contact form
Additional scope: Authentication + Notifications + Admin Dashboard
Additional timeline: +2 weeks (new completion: May 20th)
Additional cost: +$2,800
Happy to discuss before you confirm. Once I have your approval, I'll build these additions into the project plan.
Please reply with your go-ahead and I'll get started.
Best,
Alex
---
✦ Generated with Briefly (briefly-meridian.fly.dev)
When to send a scope change email
Before you start the new work. Not after. Not during. Before. The email only protects you if it's sent before you've done the extra hours. A scope change email sent after the fact is just an invoice dispute waiting to happen.
Send it as soon as you understand what they're asking for and have a rough sense of the impact. You can refine the numbers — but get the email out quickly, while the conversation is fresh and the client is in "yes mode."
What about ongoing small requests?
Not everything needs a formal scope change email. A 30-minute call, a quick question, a minor text change — these are part of the relationship. The scope change email is for work that meaningfully changes what you're building, how long it takes, or what it costs.
If in doubt, write the email. A well-written scope change note won't offend a good client. It demonstrates professionalism.
The tone: matter-of-fact, not apologetic
You are not doing anything wrong by documenting scope changes. Scope changes are normal. You're not confronting anyone — you're being professional. Write the email in the same tone you'd use for any other project update: clear, confident, matter-of-fact.
The freelancers who write scope change emails consistently are the ones who get paid properly and referred to new clients. The ones who skip them spend time in uncomfortable post-project negotiations.
Frequently Asked Questions
What if the client seems annoyed by the scope change email?
A client who's annoyed by professional documentation of additional work is a red flag — not a reason to skip the email. That said, tone matters: matter-of-fact and positive, not confrontational. Frame it as "here's what we're adding and what it means" rather than "I'm not doing this until you agree."
Do I need a formal contract amendment or is email enough?
For most freelance work, an email exchange constitutes a valid written agreement. A client replying "sounds good, go ahead" to your scope change email is binding. If you're working on larger projects (e.g. $10k+), you may want to use a formal change order document — but email works for the majority of freelance situations.
What if I already did the work before sending this?
Send it anyway — but be direct about the situation. Something like "I realize I should have sent this before starting — I've now completed X additional hours of work on [thing]. Here's what was involved and what I'm adding to the invoice." It's less protected than sending before, but it's still better than silence.
What if I don't know the exact cost yet?
Give a range or estimate: "This will add approximately 8-12 hours at my rate of $X/hour." Don't let uncertainty stop you from sending the email. You can always send a follow-up to confirm once you have a clearer picture — but get the conversation started.
Can Briefly write scope change emails for any project type?
Yes — web development, design, writing, consulting, marketing, photography, video, and anything else. Just describe what changed in your rough notes and Briefly will produce a professional email regardless of your industry.
Related templates