Freelance Change Order Email: Confirm Extra Work Before You Start

Freelance change order emails stop mid-project extras from becoming unpaid overtime. The client adds a page, a niche, or a second deliverable. You pause. You confirm scope and fee in writing. Then you start—or you do not.

This page is Scope-Then-Confirm. It is not scope creep red flags in client emails (how to read the inbox tell). It is not freelance revision round emails (feedback inside agreed rounds). It is not project kickoff email (after yes, before first work). It is not contracts and scope documents (the original fence). Early-link those owners.

Name the extra. Price or time it. Wait for yes. Only then work.

Not legal advice. Local contract rules vary.

Table of contents

1. Scope-Then-Confirm
2. When to send a change order
3. Email skeleton
4. What belongs in vs out of the body
5. After they reply
6. Cluster map
7. FAQ
8. Send one change order on the next “also…”

Scope-Then-Confirm

        SCOPE-THEN-CONFIRM
  1. PAUSE   → do not start the new piece
  2. SCOPE   → one sentence: what is new vs original
  3. IMPACT  → fee / hours / new date (your numbers)
  4. ASK     → “Reply yes to proceed”
  5. START   → only after written confirmation

The framework is boring on purpose. Drama invites negotiation theater. A calm pause protects the original timeline and the relationship.

If you are still deciding whether the message is creep vs revision, use the scope-creep red flags page first. If they are still inside rounds, use revision round emails.

When to send a change order

Send when the request adds a new deliverable, new audience, new page count, or new research that was not in the agreed brief.

Examples that usually need a change order:

• “Also write the email sequence” on a blog-only project
• “Make a second version for a different niche”
• “Add five more products to the comparison”
• “Can you design the social graphics too?”

Examples that usually stay inside revisions (if rounds remain):

• Fix typos and headings on the delivered draft
• Swap a stock photo they already approved in concept
• Clarify a paragraph that was in scope

When rounds are gone and they still want edits, price another pass—see the revision owner—then use this change-order shape if the ask is a new asset.

Kickoff already happened? Do not rewrite history in a new kickoff. Amend mid-stream. The kickoff template stays for day-zero logistics.

Email skeleton

Subject: Change order — [Project] — confirm before I start

Hi [Name],

Thanks for the note about [extra request in their words].

That sits outside the original scope:
• Original: [one line from proposal/contract]
• New: [one line describing the add-on]

To add it, I propose:
• Fee or hours: [your number / “same rate as proposal”]
• Timing: [new delivery date or “+X days after yes”]
• What’s included: [bullets]
• What’s not: [one exclusion]

Reply “yes — proceed” (or ask clarifying questions) and I will start the new work after confirmation.

The original deliverable remains on [original date] unless we agree to shift it.

Thanks,
[You]

Replace brackets with real project facts. Do not invent sample dollar amounts in published templates as if they were earnings. Your rate card habits can live on freelance pricing and rate card without turning this email into a price list.

Keep the message short enough that a second stakeholder can approve it without a call.

What belongs in vs out of the body

If the original fence is fuzzy, strengthen documents next time with contracts and scope. The change order still works as a temporary amendment—just note that you are confirming in email until the PDF is updated.

For invoice timing after they say yes, contract vs invoice owns which PDF goes first. Deposit holds stay on deposit and kill-fee emails.

After they reply

Yes: confirm receipt, add the item to your tracker, start the new work, and keep the original path clear unless the date shifted.

Questions: answer once, update the change-order bullets, ask for yes again. Do not start while the fee is still “maybe.”

No / later: acknowledge, continue the original scope, and archive the ask. Do not half-build the extra “as a favor.”

Silence: send one polite bump after a few business days. Still do not start.

Platform jobs: prefer Upwork milestones / Fiverr custom offers when the ToS and thread live there. Email is for off-platform or clients who already moved to inbox.

Cluster map

FAQ

What is a freelance change order email?

A short message that restates the new work, fee or time impact, and asks for written yes before you start. It turns a casual “can you also…” into a confirmed add-on.

Is this the scope-creep red flags post?

No. Scope creep red flags teaches how to spot inbox expansion and reply patterns. This page is the confirm-before-work email once you already know it is extra.

Is this revision round emails?

No. Revision rounds stay inside the agreed edit count. Change orders are new scope outside that fence.

Is this the kickoff email?

No. Kickoff locks start after the original yes. Change orders appear mid-project when the brief grows.

Do I need a contract first?

A written scope helps. Contracts and scope documents own the fence; this email is the mid-project amendment ritual. Not legal advice.

Should I quote exact rates here?

No invented rates. Insert your own fee, hour block, or “same rate as proposal” line. Never publish fake numbers as examples of what you earn.

What if they say start now and we will sort payment later?

Do not start. Restate that work begins after written confirmation of scope and fee. Soft promises create unpaid overtime.

Can I send this on Fiverr or Upwork?

Prefer the platform’s custom offer / milestone tools when the job lives there. Use email when the engagement is off-platform or the client already moved off-chat.

Send one change order on the next “also…”

1. Pause the extra task.
2. Paste the skeleton and fill original vs new in one minute.
3. Add your real fee or hour block—no theater.
4. Ask for “yes — proceed.”
5. Start only after the reply lands in writing.

Scope-Then-Confirm keeps goodwill and margins in the same email—without pretending every client request was somehow “already included.”