How to Write Change Order Email When Scope Expands

Your project started clean. Clear deliverables, agreed timeline, set budget. And then it grew. The client wanted a few extras here, a pivot there, and suddenly the project looks nothing like what you originally agreed to.

This is where a change order comes in. It's not confrontational. It's not dramatic. It's just a written record that says "the project changed, here's what we're doing now, and here's what it costs."

Every freelancer should know how to write one. Here's how.

What Is a Change Order?

A change order is a document, or even just an email, that formally records a change to the original project scope. It covers what's being added (or removed), how it affects the timeline, and what the new cost is.

Think of it like an amendment to your original agreement. The original deal still stands, but this add-on modifies it.

You don't need fancy software or legal templates. A clear, well-structured email works perfectly for most freelance projects.

Why You Need One

Writing down scope changes protects both you and your client. Without a change order, you're relying on memory and goodwill. And those run out fast when there's a disagreement about what was promised.

A change order gives you:

•A paper trail. If the client later says "I thought this was included," you have a dated email that says otherwise.

•Clear expectations. The client knows exactly what they're getting, when they're getting it, and how much it costs.

•Payment protection. It's much harder for a client to dispute an invoice when they approved a change order for that exact amount.

Skip the change order and you're gambling. Write one and you're covered.

When to Send a Change Order

Send a change order anytime the project scope changes in a way that affects your time, effort, or deliverables. This includes:

•The client adds new deliverables (extra pages, additional designs, more features)

•The project direction changes significantly

•The timeline extends due to client-side delays

•The number of revisions exceeds what was agreed

•New stakeholders enter the project with new opinions

You don't need a change order for every tiny adjustment. If a client asks you to change a word in their headline, that's just part of the process. But if they ask you to rewrite the entire page in a different tone? That's a change order.

Use your judgment. If the change will add more than an hour or two of work, document it.

The Structure of a Change Order Email

A good change order email has five parts:

1. Reference the original scope. Remind the client what was agreed.

2. Describe the change. Be specific about what's being added, removed, or modified.

3. State the impact on timeline. Will this push back the delivery date?

4. State the cost. Give a clear number.

5. Ask for approval. Get explicit sign-off before you start the work.

That last part is critical. Never start extra work before the client confirms. A change order isn't a change order until both sides agree.

Template: Simple Addition

Subject: Change order: [Project name] - Additional [deliverable]

Hi [Name],

Following our conversation about adding [specific deliverable] to the project, I wanted to get this documented so we're both on the same page.

Original scope:

[Brief summary of what was originally agreed, with key deliverables listed]

Proposed addition:

•[New deliverable with specifics]

•[Any sub-tasks involved]

Timeline impact:

This will extend the delivery date from [original date] to [new date].

Additional cost:

$[amount]

Updated project total:

$[new total]

If this looks good, just reply to confirm and I'll get started. If you'd like to discuss any of the details, happy to hop on a quick call.

Thanks,

[Your name]

Template: Scope Pivot

Sometimes the project doesn't grow. It changes direction. The client decides they want something different from what was originally planned. This needs its own change order because the original deliverables may no longer apply.

Subject: Change order: [Project name] - Revised direction

Hi [Name],

Thanks for the conversation about shifting the project direction. I think the new approach makes sense, and I want to make sure we're aligned on what the updated scope looks like.

Original scope:

[Summary of original plan]

Revised scope:

[Summary of new direction, with specific deliverables]

What's changing:

•Removing: [deliverables no longer needed]

•Adding: [new deliverables]

•Modifying: [deliverables that are being adjusted]

Timeline:

The revised scope will be delivered by [new date], starting from your approval of this change order.

Cost adjustment:

The revised project total is $[amount], which is [an increase/decrease] of $[amount] from the original agreement.

Please reply to confirm this updated scope, and I'll get moving on the revised plan.

Best,

[Your name]

Template: Accumulated Changes

This one is for when multiple small changes have added up over time and you need to formalize them all at once.

Subject: Change order: [Project name] - Scope update

Hi [Name],

The project has evolved since we kicked off, and I want to make sure our documentation reflects where things actually stand. Here's a summary of the changes that have been added along the way:

Original scope:

[Summary and deliverables]

Changes made:

1. [Change 1] - [brief description and approximate effort]

2. [Change 2] - [brief description and approximate effort]

3. [Change 3] - [brief description and approximate effort]

Total additional cost:

$[amount] for the additions above

Updated timeline:

[New delivery date]

I'll include the additional amount in the next invoice unless you'd prefer a separate one. Just reply to confirm this all looks right.

Thanks for being great to work with on this. The project is shaping up really well.

[Your name]

Tips for Writing Effective Change Orders

Be specific with deliverables. Don't write "additional design work." Write "two additional landing page designs with mobile versions, one round of revisions each." Specificity prevents future disagreements.

Always include a timeline. Clients need to know when they'll get the updated deliverables. Skipping this creates confusion.

Reference the original agreement. A change order makes more sense when the client can see what was originally agreed. It provides context for why this is an addition.

Keep the tone collaborative. You're not scolding the client for changing their mind. Projects evolve. Frame it as "let's make sure we're aligned" rather than "you're asking for more than you're paying for."

Get written approval. A reply that says "looks good, go ahead" is all you need. But you need it in writing. Don't accept a verbal okay. If the client approves by phone, send a quick follow-up email: "Confirming your approval of the change order below. I'll get started on [deliverable] today."

Tracking Change Orders

Keep all your change orders in one place. Whether that's a folder in your email, a shared Google Doc, or a project management tool, you want to be able to reference them quickly.

If you're managing multiple clients and projects, tracking which emails have been sent and opened can get messy. Pynglo helps freelancers keep tabs on client communication, so you know when your change order was opened and can follow up at the right time.

For more on handling the broader scope creep conversation, check out our guide on how to respond to scope creep emails from clients.

The Bigger Picture

Change orders aren't just about money. They're about maintaining a healthy working relationship. When both you and the client are clear on what's being built, there's no room for disappointment, confusion, or unpaid work.

Get in the habit of writing them early and often. It takes five minutes to write a change order email. It takes weeks to untangle a scope dispute that could have been prevented with one.

Your future self will thank you.