TL;DR
On this page
It starts as one small tweak. Then another, then a "quick" addition, and three weeks later you have redesigned the thing twice for the price of one and you are too far in to push back. That is scope creep, and it is not rare. ClearTimeline reports that 89% of freelancers experience it, and Ignition's 2025 agency report found 57% of agencies lose $1,000 to $5,000 every month to the unbilled version. The fix is not a hard conversation. It is a one-page document called a change order, sent the moment a request goes past the original scope. Below is exactly what it contains, a copy-paste template, and the message to send it with.
For the strategy of spotting and preventing scope creep in the first place, see how to handle scope creep. This post is the document that strategy points to, the thing you actually send. It assumes you already have a scope of work to measure the new request against.
What a change order is, and when to send it
A change order is a short written agreement that records work added after the project started, along with the revised fee and timeline, and is signed before that work proceeds. It is an addendum to your original contract, not a new one. The defining feature is the timing: it goes out the moment a request exceeds the agreed scope, while you still have leverage, not at the end when the work is already done and all you can do is ask.
Alvalyn Lundgren of Alvalyn Creative frames why it matters in one line:
It protects your time and your income. Clients cannot take advantage of a flat fee pricing model by adding on bits and pieces to the project, without paying for additional work.
Source: Alvalyn Lundgren, "How to Use Change Orders to Manage Freelance Projects"
The cost of not having one is measurable. Without a change order, the additions do not disappear, they just go unbilled: ClearTimeline's data shows unmanaged scope creep pushes freelancers to do 2.5 times the work they originally scoped. The change order is how you convert that invisible extra work into a line on an invoice.
What a change order must contain
A change order only works if it is complete. Leave out the signature line and it is just an email; leave out the fee and you have documented the work without pricing it. Five fields make it enforceable.
1. A reference to the original contract. Name the original agreement and its date. This is what makes the change order a formal addendum that modifies the existing contract, rather than a standalone note. Alvalyn's guidance is explicit: reference the terms of the original contract.
2. A plain-language description of each new request. Itemize what is being added, in the client's own words where possible, so there is no later argument about what "the extra work" actually was. One line per request is enough.
3. The revised fee. State the added cost, and any new expenses, separately from the original project fee. The client should see clearly that this is additional, not a renegotiation of the whole price.
4. The revised timeline. Show how the new work moves the delivery date. Clients often forget that more scope means more time; the change order makes that trade visible before they agree, not after they are annoyed it shipped late.
5. A statement of agreement with a signature and date line. This is the load-bearing field. The client signs and dates before you start the added work. Alvalyn's checklist includes a statement of agreement and a place for the client to sign and date it, for exactly this reason.
The template
Drop this into a document, fill the brackets, and send it as an addendum. It is deliberately short, because a change order that takes ten minutes to read does not get signed.
CHANGE ORDER
This change order modifies the agreement dated [original contract
date] between [your name/business] and [client name] for
[original project name].
Added scope:
- [new request 1, in plain language]
- [new request 2]
Original fee: [amount]
Additional fee for this change order: [amount]
New expenses (if any): [amount]
Revised total: [amount]
Original delivery date: [date]
Revised delivery date: [date]
This added work begins once this change order is signed. All other
terms of the original agreement remain in effect.
Approved by: ____________________ Date: __________
[client name, client title]
A change order is an addendum to your existing contract, so it belongs with that paperwork. FreelanceDesk's contract builder keeps your original agreement and its change orders together, and once the change order is signed you bill the added work from the invoice generator. If you would rather draft the wording with AI first, the change order prompt generates a first draft you can paste into the template above.
How to send it without a fight
The fear is that sending a change order signals you are being difficult. The opposite is true: it signals you are running a real business. The trick is to frame it as routine process, not as pushing back. Send something like:
Happy to take that on. It is a bit outside what we originally scoped, so I will put together a quick change order with the added cost and the new timeline, and we can kick it off as soon as you approve it. Sending it over now.
Notice the moves. It says yes to the work, names the scope boundary without accusation, presents the change order as the normal next step, and closes with a clear path forward. There is no apology and no negotiation of something already agreed. As Alvalyn notes, using change orders consistently also has a second-order benefit:
Using change orders also builds your reputation as a professional and business owner.
Source: Alvalyn Lundgren, "How to Use Change Orders to Manage Freelance Projects"
pro tip
Send the change order the same day the request comes in, while the scope boundary is fresh and obvious to both of you. Wait a week and the client has mentally folded the new work into the original project, which turns a routine document into an argument about what was promised.
When the client pushes back or won't sign
Most clients sign. The ones who hesitate usually fall into two camps, and each has a clean response.
The client who says "can't you just include it?" is testing the boundary. Hold it warmly: "I want to, but it is genuinely additional work and I price all changes the same way to keep things fair and clear." The consistency is the point; a freelancer who waives the change order once invites every future request to be a freebie too.
The client who goes quiet and asks you to proceed anyway is the real risk. Do not start. An unsigned change order is an unbilled one, and proceeding on a verbal "go ahead" puts you back in the position the document was meant to prevent. If the work has genuinely already happened on a verbal yes, that is a separate recovery situation, and the change order still helps by documenting it after the fact for the invoice. There is a full playbook for billing a client for work they verbally approved when nothing was signed.
The change order is the cheapest scope insurance you have
It costs you one short document and one matter-of-fact message. In return, it converts the slow bleed of unpaid additions, the 2.5x of extra work most freelancers absorb silently, into work that is scoped, priced, and signed before you touch it. Keep the template to hand, send it the moment a request crosses the line, and require the signature before the work starts. Scope creep stops being something that happens to you and becomes something you bill for. And for the inverse risk, a client who cancels the project outright rather than expanding it, a kill fee clause is the matching protection.