Freelance Change Order Email: 5 Templates That Protect Scope
Document extra client requests without awkwardness: what to check first, five copy-ready change order emails, a one-page change note, and AI prompts that refuse invented prices.
Part of Freelance client emails: every template from first call to rate increase, in one place.
Mid-project, the client asks for "one more page," a new integration, or a redesign of something already approved. Saying yes in chat feels friendly. Doing the work without a written change order turns a fixed-price job into unpaid overtime, and you have no record when the invoice arrives.
A good change order email fixes that. It restates what was in scope, names the new request in plain language, shows time and cost, and asks for a clear yes before you start. This guide covers what to check before you write, a short change-note checklist, five copy-ready templates, and an AI workflow. ChatGPT or Claude can help with tone. Your scope, hours, rates and dates come from you. Never let the model invent a price or pretend work was already included.
Check these four things before you write
The email only works if your facts match the signed agreement. Look at your proposal or SOW and confirm:
| Check | Why it matters | Where to find it |
|---|---|---|
| What the original scope included and excluded | You can show the ask is new, not a free revision | Proposal, SOW or kickoff notes |
| Whether this is a revision or a new deliverable | Revisions burn included rounds; new work needs a change order | Revision clause and exclusions list |
| Hours or fee for the extra work | Vague "it will cost more" emails stall; a number gets a decision | Your rate card or estimate worksheet |
| When work starts (after written approval, deposit, or both) | Protects you from starting unpaid work while they "think about it" | Your payment terms and calendar |
If the proposal never defined exclusions or a change process, do not invent terms now. Frame this as the clean way to add work going forward, then put a change clause into your next project proposal. For the wider AI-assisted workflow (scope check, reply, one-page order), see scope creep with AI change orders. When the ask is really "more rounds of the same deliverable," use the revision limit email instead.
Change-note checklist (keep it to one page)
Copy this into your notes before you draft. One short note beats a long negotiation thread.
| Field | What to fill in |
|---|---|
| Project and date | Client name, project title, today's date |
| Original scope reference | Proposal date or SOW section |
| New request (client's words, then your plain summary) | Quote their ask, then restate what you will deliver |
| Why it is out of scope | One sentence tied to exclusions or deliverable list |
| Effort | Hours or days, and who does the work |
| Fee | Flat fee or rate x hours; tax note if you charge tax |
| Timeline impact | New dates for this piece and any shifted milestones |
| Start condition | Written yes, deposit, or both |
| Expiry | How long this quote stays open (for example 7 days) |
Clients approve faster when the ask looks finite. A vague "we can talk about extra work" never closes.
The one rule: no paid work until they say yes in writing
"Sounds good, go ahead" in Slack is not a change order. "Approved: add the FAQ page for $[amount], start after the $[deposit] clears, new review on [date]" is. Put the yes in email (or a signed note) so both of you have a record when memory fades at invoice time.
Template 1: First change order after a new request
Use this when the client asks for something clearly outside the signed scope and you are ready to quote it.
Subject: [Project]: change order for [short name of request]
Hi [Name],
Thanks for the note about [their request in their words]. That is
outside the current scope in the [proposal / SOW] dated [date],
which covers [short list of included items] and excludes
[short exclusion that applies].
Here is a simple change order so we can decide cleanly:
New work: [plain summary of what you will deliver]
Effort: [hours / days]
Fee: $[amount] (or [rate] x [hours])
Timeline: starts after written approval [and deposit, if any];
ready for your review by [date]
Impact on current milestones: [none / [milestone] moves to [date]]
If this looks right, reply "approved" to this email (or sign the
attached one-pager). I will not start the extra work until then
so we both stay aligned. This quote stays open until [expiry date].
Happy to trim the request if you want a smaller version.
Best,
[Your name]
Template 2: Soft "out of scope" reply (offer options)
Use this when you want to stay helpful without an instant hard no or a blank yes.
Subject: [Project]: options for [request]
Hi [Name],
I can help with [request]. It sits outside the signed scope
([proposal date]), so here are three clean options:
1) Add it as a change order: [fee], [timeline], starts after
your written yes.
2) Swap it for [in-scope item you can drop], same fee and dates.
3) Park it for a follow-on phase after we ship [current milestone].
Which option do you want? If you pick 1, I will send a one-page
change note today. If you pick 2 or 3, I will update the plan in
the next status email.
Best,
[Your name]
Options keep the relationship warm. They also stop "just this once" from becoming the new normal.
Template 3: Change order with deposit before start
Use this when the extra work is large enough that you need money before you schedule it.
Subject: [Project]: change order + deposit for [request]
Hi [Name],
Confirming the change order for [request]:
Scope add: [summary]
Fee: $[total]
Deposit to start: $[deposit amount] ([percent]%)
Balance due: $[balance] on [delivery / approval]
Schedule: work starts within [N] business days after the deposit
clears; review on [date]
Reply "approved" and I will send the deposit invoice the same day.
I will hold the calendar slot until [hold-until date]. If the
deposit lands after that, the next open start is [later date].
Best,
[Your name]
Pair the deposit ask with your usual deposit request email habits: clear amount, clear start rule, no work before funds clear.
Template 4: Client already started treating it as included
Use this when they assume the new ask is free, or when work has already drifted without a written yes.
Subject: [Project]: pause on [request] until we confirm scope
Hi [Name],
I want to keep [project] on track. The recent ask for [request]
is not in the signed scope dated [date]. I have not billed or
scheduled it as included work.
To avoid rework, I am pausing that piece until we pick one path:
A) Change order: [fee], [timeline], start after written approval
B) Keep current scope: I continue [in-scope work] only
C) Smaller version: [reduced ask] for [lower fee]
Please reply with A, B, or C by [date]. Until then I will keep
shipping the original deliverables so the main timeline does not
slip.
Best,
[Your name]
Pausing is kinder than silent free work. If they go quiet, step up with your client not responding sequence, and keep the open item visible in the weekly status update.
Template 5: Approved change order confirmation (record for both sides)
Use this the moment they say yes, so invoice and delivery have a paper trail.
Subject: [Project]: change order approved for [request]
Hi [Name],
Confirming your approval on [date] for this change order:
New work: [summary]
Fee: $[amount]
Start: [date or "after deposit clears"]
Review / delivery: [date]
Milestone impact: [none / updated dates]
I will [send the deposit invoice / start work on date] next.
Anything beyond this note will need a separate change order.
Thanks for making the scope clear. Talk soon.
Best,
[Your name]
After delivery of the extra piece, gate the next phase with a milestone approval email so the new work does not blur into endless tweaks.
An AI workflow for change order emails
Step 1: Write down the facts
Before you open ChatGPT or Claude, list the original scope line, the client's request in their words, your plain summary, hours, fee, timeline impact, start condition and expiry. Decide which template you are sending. The AI must never invent a price, hour count, deposit percent or deadline.
Step 2: Draft with a tight prompt
Write a short, firm but friendly freelance change order email.
Situation: [first quote / soft options / deposit required /
pause until confirmed / approval confirmation]. Use only the
facts below. Do not invent fees, hours, dates, deposits or
scope lines. Do not agree to start unpaid work. Under 200
words, plain language, one clear ask.
Facts:
"""
[paste facts]
"""
Client's latest message:
"""
[paste their email]
"""
Step 3: Run a check prompt
List every fee, hour count, date, deposit, scope claim and
start condition in this email. Flag anything not in the facts,
any invented price, and any sentence that starts paid work
without written approval.
Email:
"""
[paste draft]
"""
Facts:
"""
[paste facts]
"""
Remove anything flagged, then read it as the client. They should know what is new, what it costs, when it starts, and how to say yes.
Keep change orders visible during the project
Most scope fights happen when the "yes" lived in a chat bubble and then vanished. Add one line to every weekly status update: "Open change orders: FAQ page ($X, awaiting approval)." Put exclusions and a change process into your next project proposal so the first ask is sold before kickoff. When rounds of the same deliverable are the real issue, switch to the revision limit email rather than dressing revisions up as change orders.
FAQ
How do I tell a client something is out of scope without sounding rude? Restate what the signed scope includes, name the new ask in one sentence, and offer a priced path forward (or a swap / later phase). Specific options feel helpful; a vague "that will be extra" feels like a brush-off.
What if they say "it should only take an hour"? Quote your real estimate anyway. If the hour is truly tiny and you want to gift it, say so in writing as a one-time courtesy, and note that similar asks will use a change order next time.
Should I start the work while they decide? No. Template 4 exists for that moment. Pausing the extra piece protects both of you from rework and surprise invoices.
Change order vs revision round: which email do I send? Revisions tweak an in-scope deliverable within agreed rounds. Change orders add new deliverables, features or audiences. When in doubt, price it as a change order and let them choose a smaller in-scope path.
Can ChatGPT write my change order email? It can draft the wording. Give it your real scope lines, fees and dates, tell it not to invent prices, and run a check prompt before sending.
Bottom line
Restate the signed scope, name the new request, put a real fee and start rule on one page, and wait for a written yes. Soft options beat silent free work. A short confirmation email after approval is the invoice's best friend.
Exclusions, change process and client inputs are on the free 40-point scope checklist, so check them before you quote. The $9 Freelancer Proposal Autopilot Kit has prompts for writing exclusions and change-order language into the proposal from the start.
Related guides
Freelance Project Cancellation Email: 5 Templates for When a Client Pulls Out
What to send when a client cancels a freelance project: what to check first, five copy-ready emails (acknowledge, kill fee invoice, pause instead, work handover, cancelling yourself) and AI prompts that refuse invented terms.
Scope Creep With AI: Change Request Replies and Orders
Handle scope creep with AI: check client requests against agreed scope, draft a calm reply and a one-page change order, with human gates on price.
Out of Revision Rounds? 5 Freelance Email Templates to Set the Limit Kindly
How to tell a client the included revisions are used up: what to check first, five copy-ready emails (heads-up, last round, paid extra round, final sign-off, too many small changes), and AI prompts that keep your terms intact.