How to write a change order (and why most freelancers don't)

The client asks for something that wasn’t in the brief. You say yes — because it feels easier, because you want to keep the relationship smooth, because you tell yourself it’ll be quick.

You do the work. Then at invoice time you either quietly leave it out (eating the cost) or add it (and the client acts surprised).

That’s the situation a change order prevents. It’s one paragraph. Most freelancers still don’t send one.

Why most freelancers skip it

Three reasons, none of them very good.

First: it feels confrontational. Sending a formal document in response to a casual request feels like you’re escalating. Like you’re making a thing out of nothing.

Second: it seems excessive for small changes. A 30-minute extra call? Two paragraphs of copy? A change order for that feels bureaucratic.

Third, and this is the real one: the fear that the client says no. That the relationship takes a hit. That you look difficult to work with.

None of these survive contact with what actually happens when you don’t send one.

What a change order actually is

It’s not a legal document. It’s not a demand letter.

It’s a written confirmation of something you’ve already agreed to verbally. One paragraph that says: here’s what you asked for, here’s what it costs, here’s how it affects the timeline.

Most clients respond with “sounds good” — because they already knew they were asking for something outside the original scope. The change order just puts it in writing.

The discomfort people fear doesn’t live in the change order. It lives at invoice time, when the bill is higher than expected and nobody wrote anything down.

The template

No legal language required. Here’s a version that works with any client:

Hi [Name],

Following our conversation, I’ll be adding [brief description] to the project. This is outside the original scope, so the additional cost is [amount], and it extends the timeline by [X days].

Happy to proceed once you confirm — just reply to this email.

Three sentences. “Happy to proceed once you confirm” does the framing work: it’s a step forward, not an ultimatum.

If you’re casual with a particular client, keep the tone casual. The content is what matters: what’s changing, what it costs, what happens to the timeline.

Send it before you start the work

This is the only rule that really matters.

Not after. Not at invoice time. Before you open the file.

If the client calls on a Tuesday and asks for something extra, you can say yes on the call and send the written confirmation that afternoon. One email. Then you start.

The change order sent before the work has one property the after-the-fact version doesn’t: the client still has the clearest mental model of what they asked for. There’s no ambiguity to resolve. They asked for X, you’re confirming X at Y cost.

If you’ve already done the work without a change order, the conversation is harder — but not impossible. Billing for project overruns covers how to frame it.

When clients push back

Sometimes they do. They thought it was in scope. The price feels high. They’d rather not pay extra.

This is useful to know before you spend six hours on it.

If a client pushes back on a change order before the work starts, you have real options. You can negotiate the scope down. You can decide not to proceed with the extra item. You can absorb it once, explicitly: “I’ll include it this time since it’s small, but further additions would go on a separate order.” All of these are better than finding out at month end that you worked 15 hours that don’t appear on any invoice.

Pushback rarely damages the relationship. What damages it is the ambiguity that builds up when nothing gets written down, until the invoice arrives and both parties are surprised by it.

Change orders aren’t about distrust

Most clients aren’t trying to take advantage of you. They’re asking for things that seem reasonable to them, without thinking about whether it’s in scope.

The problem is that both parties have different mental models of what the original project included. A scope of work sets those expectations before the project starts. A change order updates them when something changes. They’re the same mechanism at different stages of the project.

Clients who work with freelancers who use change orders regularly tend to communicate more clearly. They know additional requests have a cost, so they consolidate them, prioritize them, and send them as considered asks rather than reflexive additions.

The working relationship doesn’t get worse. It usually gets better.

When extra work happens without a change order, Timescanner helps you see what it actually cost. It reads your calendar and shows hours by project — so you can compare what you planned against what you worked, and price future overruns accurately. Works with any iCal-compatible calendar.