Scope creep rarely arrives as a big request. It shows up as "could you also..." in the middle of a feedback email, or "while you're in there" on a call. Each request on its own looks small. Together, they turn a profitable fixed-fee project into one where you are working for half your rate. A scope change email is how you respond to the request quickly, politely, and in writing, before the extra work starts.
This page gives you three short emails: a standard version that offers a change order, a version for small requests where you choose to do the work as a one-off goodwill gesture, and a version for when the request would push back the agreed timeline.
TL;DR
The scope change email templates are three short emails for flagging an out-of-scope request: a standard version that cites the agreed scope and offers a change order with price and timeline, a goodwill version for small one-off favors recorded in writing, and a timeline-impact version. Send one within a day of the request and before starting extra work, then follow up with a signed change order form.
What's inside
- Email 1: standard out-of-scope reply — names the request, references the agreed scope, and offers three options.
- Email 2: goodwill exception — agrees to do a small extra once, at no charge, and says so explicitly.
- Email 3: timeline impact — explains how the request affects the launch or delivery date.
- Options block — change order, swap for in-scope work, or defer to a later phase.
- Follow-up line — confirming the change order once the client agrees.
When to use it
Use these emails whenever a client asks for something that is not in the signed proposal, SOW, or contract: new pages, extra revision rounds, an additional deliverable, a new platform, more meetings than agreed, or work that changes an approved deliverable.
Do not use them for requests that are genuinely within scope but unclear; answer those directly. If the client wants a larger change to the whole engagement, such as doubling the budget or a new phase, write a new proposal or statement of work instead. If the issue is your rates rather than the scope, the rate increase letter is the right tool.
Making scope conversations easier
Respond fast. The longer a request sits, the more the client assumes it is happening. A same-day or next-day reply keeps it a conversation about options rather than an argument about work already done.
Quote the scope, do not paraphrase it. "The proposal includes five pages: Home, About, Services, Blog, and Contact" ends most debates. That is why scoping documents with lists beat paragraphs. See how to scope a fixed-fee project.
Lead with yes, then the cost. "Happy to add that. It's outside the current scope, so here's what it would take" lands better than "That's not included."
Always give options. A price, a trade, or a later phase. Clients feel in control when they choose, and some will choose to drop the request.
Track the small ones. If you do a favor, say so in writing. Three favors in, you have a record for the conversation about a change order or a bigger budget. The post on how to ask a client for more budget covers that conversation.
Customize it in your COLO workspace
If you track the project in COLO project budgets, you get an in-app warning at 80% of the budget, and at 100% billable timers stop with options to request a contract update, continue as non-billable, or pause. The client can approve or decline a budget increase in the client portal, which pairs well with the email below.
Send the change order as a contract or a proposal with line items for the extra work in COLO Proposals, and keep the scope discussion in project chat so the decision is recorded next to the work.
Common mistakes
- Starting the work "to be helpful" before agreeing a price. It is almost impossible to bill afterward.
- Saying no without options. A flat refusal feels like a dispute; options feel like service.
- Vague pricing. Give a number or a range and a date, not "it'll cost a bit more."
- Changing scope on a call without a written follow-up. Confirm by email the same day.
- Doing favors silently. Record goodwill extras so the client knows they received them.
FAQ
Q: How do I tell a client a request is out of scope?
Thank them for the idea, point to what the agreed scope covers, explain that the request sits outside it, and give two or three options, usually a change order with a price and date, swapping it for something in scope, or parking it for a later phase.
Q: What is a change order?
A short written agreement, signed by both sides, that adds or changes work under an existing contract. It states the new work, the extra fee, and the revised timeline. Use the change order form.
Q: Should I do small out-of-scope tasks for free?
Occasionally, as a deliberate goodwill gesture, and say so in writing. Doing them silently teaches the client that scope is flexible and makes the next, larger request harder to decline.
Q: When should I send a scope change email?
Before you start the extra work, ideally within a day of the request. Once the work is done, it is much harder to charge for it.
Q: What if the client disagrees that the request is out of scope?
Quote the exact line in the proposal, SOW, or contract that defines the scope. If the wording is genuinely ambiguous, agree an interpretation in writing and tighten the wording in future contracts.
Related
- Change Order Form — the document this email leads to.
- Freelance Proposal Template — write scope as lists to prevent the next debate.