Change Order Email Template for Freelancers

Industry research and interviews with freelancers show the same pattern repeatedly: a client asks for work outside the original SOW over Slack, the freelancer recognizes it is out of scope immediately, but drafting a professional change order takes 30–45 minutes they do not have in the moment. They say "sure" instead. One designer we spoke with tracked 22 separate out-of-scope additions on a single brand identity project — $4,400 in unbilled work reconciled afterward.

The fix isn't a mindset shift. It's a template you can send in under two minutes.

What a change order email needs to include

Most freelancers overcomplicate this. A change order email does not need to be a legal document. It needs four things:

1. A reference to the original SOW. "Per our agreement dated March 3" is enough. It reminds the client that a contract exists and that what they're asking for isn't in it — without being adversarial.
2. A clear description of what's new. Quote the client's request back to them, in their words if possible. "The pitch deck template and social media kit you mentioned in Slack on April 14" is better than a vague summary.
3. A specific price. Not a range if you can avoid it. A single number that reflects your rate applied to an honest time estimate. If you must use a range, keep it tight — "$1,800–$2,100" is fine; "$1,000–$4,000" signals that you don't know what you're doing.
4. A one-action approval mechanism. "Reply to confirm" or "a quick 'approved' works." Clients who have to navigate a DocuSign link to approve a $400 extra get friction-stopped. Make it trivially easy to say yes.

The template

This template works for brand designers, web developers, copywriters, and any other freelancer billing on project contracts. Adapt the deliverables section to your discipline.

Subject: Change Order #[CO-001] — [Project Name]

Hi [Client Name],

Thanks for sending that over. Before I start on [brief description of extra request], I want to make sure we're aligned on scope and cost so there are no surprises at invoice time.

The original SOW (dated [SOW date]) covers [brief summary of what was agreed]. The new request — [exact description of what client asked for] — falls outside those deliverables.

Here's a quick breakdown of the additional work:

  • [Deliverable 1]
  • [Deliverable 2]

Estimated time: [X–Y hours]
Rate: $[your hourly rate]/hr
Additional fee: $[total]
Revised delivery: [new date]

Happy to get started as soon as you reply to confirm. A one-line "approved" works.

Let me know if you have questions on the pricing or timeline.

— [Your name]

Note on CO numbering: Start at CO-001 and increment per project, not per client. Keeps your paper trail clean if you ever need to reference it at collection time.

Common mistakes

Apologizing for the ask

"Sorry to have to do this, but..." removes your authority before you've said anything. A change order is professional documentation, not a confrontation. Skip the apology.

Sending it after the work is done

If you delivered the work first and are now billing for it retroactively, you've already lost most of your leverage. Send the change order before you start. "Happy to get started as soon as you confirm" is not aggressive — it's standard practice in any professional services engagement.

Leaving out a revised delivery date

Extra work takes extra time. If you absorb the timeline impact silently, the client will hold you to the original deadline anyway. Make it explicit: the new work moves the deadline by X days.

Forgetting to reference the original scope

Without that reference, there's no shared definition of what's "extra." Some clients genuinely believe the new request was always included. A single line citing the original SOW date prevents most scope disputes before they start.

When the request is too complex to template manually

The template above handles straightforward additions cleanly. Where it breaks down: multi-part requests with mixed hourly/flat rates, projects with tiered payment structures already in place, or situations where the client's Slack message is long and ambiguous and you need to extract the actual deliverables from the noise.

In those cases, the time to draft a clean change order — re-reading the SOW, parsing the request, estimating hours, formatting the document — runs to 30–45 minutes. That's the window where most freelancers capitulate and just say "sure."

That's what ScopeDrafter fixes. Paste your original SOW and the client's message. Get a formatted change order document and ready-to-send pricing email in under 30 seconds.

Sending to an existing client mid-project

The anxiety here is real: you've been working together for weeks, the relationship is good, and a formal change order feels like it might sour things. Here's what actually happens in practice: clients who are used to working with professionals expect change orders. Clients who push back on a change order are the ones who were planning to dispute the invoice anyway.

You can soften the framing without softening the substance. "I want to make sure we're aligned before I dive in" is collaborative, not combative. The document that follows doesn't have to change.

After they approve

Keep the thread. Do not move the conversation to a different email chain or Slack. When the invoice arrives, you want a clear paper trail: here is the change order, here is the approval, here is the invoice referencing both.

If you use a project management tool, attach the approved change order to the project. If you invoice through FreshBooks or Quickbooks, add the CO number and a line item that matches the change order description exactly. "Additional design work — per CO-001 dated April 14" is clean. "Extra stuff" is not.