How to Write a Change Order (With a Simple Template)

By The Boring Thing · Updated July 12, 2026 · 7 min read

A change order is a short written document that records a new request falling outside the original project scope — what it is, what it costs, how it affects the timeline, and a line for the client to approve it. You write one the moment a request crosses your scope line and before you do the work, never after. Done right, it takes five minutes, protects both you and the client, and turns an awkward money conversation into a routine paperwork step. This guide gives you the exact fields, a full copy-and-paste template, an email script for sending it, and how to handle pushback without friction.

What a change order is and why it protects both sides

Think of a change order as a tiny amendment to your original agreement. The contract set the baseline; the change order records anything added on top of it. It is the mechanism that lets a project flex without either side losing track of what was agreed.

People assume a change order protects only the freelancer. It protects the client just as much. It gives them a fixed price for the addition instead of an open-ended “we’ll see” that could balloon on the final invoice. It gives them a clear record of what they approved. And it puts the decision firmly in their hands — they can approve, decline, or defer. That mutual clarity is exactly why change orders rarely get resistance: you are not springing a charge on anyone, you are asking them to sign off on one before it exists. If you want to prevent most of these situations from arising in the first place, pair this with how to stop scope creep before it starts.

When to send one

The rule is simple and unbendable: the moment a request falls outside the agreed scope, before you do any of the work. The order of operations is document, approve, then build — never build, then bill. Once you have already done the work, you have thrown away all your leverage and put the client in the ugly position of being charged for something they can no longer say no to. That is how relationships sour.

How do you know a request is out of scope? Look at your original deliverables list. If the request isn’t on it — or is expressly on your “not included” list — it is a change order. Extra revision rounds beyond your cap, new deliverables, expanded quantities, a rushed deadline, a fresh round of ideas that was supposed to be phase two: all of it qualifies. When in doubt, write the order. A quick change order that turns out to be unnecessary costs you five minutes; skipped work you can’t bill for costs you real money.

The fields a change order needs

Keep it short. A change order is one page, not a legal brief. It needs exactly these fields:

1. Project name and date. Ties the order to the original agreement and stamps it in time.
2. Requested by. Who asked for the change — name and date. This matters when several people on the client side send requests.
3. Description of the new request. Plainly, what is being added. Write it in the client’s own words where you can.
4. How it differs from the original scope. The key field. Point to what the contract covered and show why this sits outside it. This is what prevents “but I thought that was included.”
5. Added cost. A specific number, or a clearly labeled hourly estimate with a not-to-exceed cap.
6. Timeline impact. The new or revised delivery date. Extra work moves the finish line, and saying so up front prevents the client expecting the original date and the extra work.
7. Payment terms. When the added amount is due — added to the final invoice, billed now, split, whatever your norm is.
8. Approval / signature line. A place to sign and date. A typed name in an email reply counts; the point is a clear, recorded yes.

The copy-and-paste template

Fill in the brackets and send. This works as an email body, an attached PDF, or a shared doc.

That is the whole thing. Resist the urge to pad it. The clarity comes from the “how this differs from scope” and “added cost” lines — everything else is just framing.

A short email to send it with

The document does the heavy lifting, but the note around it sets the tone. Keep it warm and matter-of-fact — you are sending routine paperwork, not delivering bad news.

Two small things make this land well. First, you lead with a yes and a thank-you, so it never reads as a pushback. Second, you put the number and the date in the email itself, not buried in an attachment — clients appreciate not having to dig for the part that matters.

How to handle pushback gracefully

Sometimes a client pushes back: “I thought this was included,” or “really, for that small thing?” Don’t get defensive and don’t instantly cave. Go back to the shared document. It is calm, professional, and it works:

• “I thought that was included.” — “Totally understandable — it’s easy to lose track. Our agreement covers [X], and this is [Y], which is a bit different. Happy to walk through it if that helps.” You point at the scope, not your opinion.
• “It’s such a small change.” — “Some small changes are quick, but this one touches [what it actually involves], so it does take real time. The change order keeps it transparent so there’s no surprise later.”
• “Can you just do it as a favor?” — “I want to keep our project healthy and on budget for both of us, so I keep all extra work on the record. If it’s not essential right now, we can absolutely park it for a later phase.”

Notice that giving them an easy exit — park it for later — takes all the tension out. You are not forcing a purchase; you are offering a fair choice. And if a change is genuinely tiny and you decide to do it for goodwill, that is your call to make — but do it consciously and say so: “I’ll fold this one in at no charge, but flagging it so we both know it’s outside scope.” That way the gesture is a gift you chose, not a precedent that quietly resets everyone’s expectations.

Make it a habit

The freelancers who never fight about money are not tougher negotiators — they just document everything as a reflex. Save the template where you can grab it in thirty seconds. Number your change orders so the trail is clean. Send one every single time work crosses the line, even when it feels too small to bother with, because “too small to bother” is precisely the habit that erodes your rate. A change order is not confrontation. It is the ordinary, boring paperwork that keeps good projects good.

Every approved change order is more taxable income — and as a freelancer you pay your own self-employment tax on it. Before you spend it, plan for it: read why freelancers owe 15.3% or run your numbers in the free Self-Employment Tax Calculator.