How to Write a Change Order for a Freelance Client

Every project gets the "while you're at it, could you also…" request. It is not a sign the client is difficult — it is a sign the project is alive and they trust you. The freelancers who stay profitable are not the ones who say no to those requests; they are the ones who have a calm, repeatable way to say yes for a fair price. That way is a change order.

A change order is just a short written add-on to the work you already agreed. It names the new request, what it costs, and how it changes the timeline, and the client agrees to it before you start. It turns a fuzzy "is this included?" into a clear, documented decision. Here is how we would write one.

When a request needs a change order

The trigger is simple: a request goes beyond the scope the client already signed. If it is inside the agreed deliverables, it is just the work. If it is a new deliverable, an extra revision round past the number you agreed, a rush, or a change of direction that throws away work already done, that is change-order territory.

You do not need a change order for a typo fix or a five-minute favor. Reserve it for anything that adds real time, real cost, or real risk — the requests that quietly turn a profitable project into an unprofitable one when they pile up unbilled.

A change order is not a way to nickel-and-dime a client. It is a way to keep the original agreement honest, so both of you always know what "done" means.

If you want the fuller picture of why unbilled extras are so corrosive, our guide on what scope creep is and how to stop it goes deeper on the pattern.

What every change order should include

A good change order is short but complete. Leaving out one of these fields is where disputes start:

• A reference to the original agreement. One line: "This adds to the signed agreement dated [date] for [project]." It anchors the extra to what already exists.
• A plain description of the new work. Name the deliverable in concrete terms, the same way you would in a proposal. "A second landing page, matching the approved design" beats "extra page."
• What is explicitly not included. The most-skipped field, and the one that prevents the most arguments. If the new page does not include copywriting, say so here.
• The price, and how it maps to the work. A flat amount for the add-on, or your rate times an estimate — whichever matches how you priced the original project.
• The impact on the timeline. Extra work almost always moves the finish line. Say by how much, so the client is not surprised later: "This extends delivery by [timeframe]."
• When the extra is due, and how it gets paid. Tie it to your normal terms — due on approval, on delivery of the add-on, or before the extra work begins.
• A place to agree. A signature line and a date, so there is a clear "yes" on the record before you touch the work.

A change order you can copy and adapt

Here is a fill-in-the-blanks version you can paste into a document, a proposal tool, or Drift Catch and adjust per project:

Change Order #[number] Project: [project name] Original agreement: signed [date] Date: [today]

What is being added: [concrete description of the new deliverable].

Not included: [anything a reasonable person might assume comes with it but does not].

Price: [flat amount, or rate × estimated effort]. This is in addition to the original project fee.

Timeline impact: this extends the delivery date by approximately [timeframe].

Payment: due [on approval / on delivery / before this work begins], under the terms of the original agreement.

Approved by: ______________________ Date: __________

Keep the language as plain as the rest of your client communication. A change order that reads like a legal ambush undoes the goodwill you are trying to protect.

The email that sends it

The document does the hard part; the email just needs to be warm and matter-of-fact. Something like:

Hi [Name],

Happy to take this on. Since it is beyond what we scoped in the original agreement, we have written it up as a quick change order — it lays out exactly what is being added, the cost, and how it affects the timeline, so nothing is a surprise. Have a look, and once you approve it we will get started.

Notice what this does. It treats the change order as normal procedure, not a confrontation. "Happy to take this on" leads; the paperwork follows. You are not refusing the request — you are documenting a yes.

Get it agreed before the work — and keep the record

The single most important habit is this: the change order is approved before the extra work happens, not after. A change order you send once the work is already done is an invoice with a hopeful tone. Approved up front, it is a shared decision. Same words, completely different footing.

What makes that approval hold up is the record around it — who agreed, and when. An electronic signature with a timestamped record is recognized under modern e-signature laws such as the U.S. E-SIGN Act and UETA, and Canada's PIPEDA Part 2. It is a simple electronic signature, not a notarized or specialized one, and for everyday freelance agreements that is exactly the right tool: it means "what did we agree to?" has a documented answer instead of two conflicting memories.

This is the seam Drift Catch is built for. When a request lands outside the signed scope, you turn it into a change order in the same place the original agreement lives, the client e-signs it, and it attaches to the project with a full audit trail. Change orders are part of the Solo plan and up. On the Pro plan, once you connect Stripe, you can also collect payment on a change order inside Drift Catch — and require the extra to be paid before that work opens, so "I'll settle up later" simply means the add-on waits until it is paid. You can see that flow in our guide to stopping scope creep with e-signed change orders.

The short version

A change order is a small document that does a big job: it keeps every "one more thing" from eroding a project you priced fairly. Name the new work and what it excludes, price it against the effort, state the timeline impact, and get it agreed before you start. Do that consistently and extra requests stop being a source of dread — they become a normal, billable part of the work.

For the habit of deciding revision limits and extras before the project starts, our freelance project kickoff checklist covers the up-front side, and how to get paid on time as a freelancer covers the routine that gets the money in once the work is agreed.

This is general business information, not legal or financial advice. For change-order and contract language that fits your specific situation, check the rules in your region or have a professional review it.