Change orders: how to bill for mid-project scope changes
The extra work you never quoted is where most freelance profit quietly leaks out. A change order turns it back into paid work.
The Delivvo team· July 28, 2026 8 min read
A change order is a one-page written amendment that records the extra work a client asked for after the project started, what it costs, and how it moves the deadline. You send it the moment the request lands, before you touch the new work, and you do not start until the client approves it.
That one habit decides whether a project stays profitable. Most freelancers do not lose money on the work they quoted. They lose it on the work they never quoted: the extra page, the second logo concept, the quick data export, each arriving in its own friendly email, none of it priced. A change order is the tool that turns those requests back into paid work.
Scope creep is a pricing failure, not a client problem
It is tempting to read scope creep as a story about pushy clients. The data reads more like a story about missing paperwork.
In the Project Management Institute's Pulse of the Profession 2023 report, 40 percent of projects at organisations that put a low priority on communication and related people skills experienced scope creep, against 28 percent at organisations that made those skills a priority. The same report found the weaker communicators lost 25 percent of their budget to failed projects, compared with 17 percent for the stronger ones.
Read that as a solo operator. The projects that spiral are rarely the ones with difficult clients. They are the ones where nobody wrote the change down and said the price out loud. A change order is that sentence, in a form the client can approve.
What counts as a change, and what does not
The hard part is not writing the change order. It is deciding when one is due. Get this wrong in the generous direction and you bill for clarifications, which makes you look grasping. Get it wrong in the other direction and you work for free.
Keep reading
A useful line: if the request fits the deliverable you already described, it is included. If it adds a new deliverable, a new round, or a new constraint, it is a change.
Included, no change order:
Fixing something you got wrong.
A revision that sits inside the rounds you already agreed.
Answering questions about the work.
New scope, change order:
Work you did not list. A fourth page on a three-page site. A second concept when one was scoped.
An extra revision round after the agreed rounds are spent.
A new format, platform, or integration.
A deadline pulled forward far enough to reorder your week.
A new stakeholder whose feedback reopens a stage you had closed.
If you cannot tell which side a request sits on, that is a signal your original scope was vague, and the fix for next time is a tighter statement of work. For this time, treat the ambiguity as a conversation, not a free upgrade.
The change order itself is five lines
It does not need a template with a logo. It needs to be unmissable and specific. Five lines do the job:
What is changing, in plain language. "Add a Spanish version of the five key pages."
Who asked, and when. This is not blame. It is a record.
The price, as a number, not a range.
The timeline effect. "This adds four working days and moves delivery to the 22nd."
One approval line. "Reply approved to this email and I will begin."
Send it in whatever channel the client already uses to approve things. The goal is that a month later, neither of you has to remember the conversation, because it is written down where the rest of the project lives.
A notebook open to pricing notes beside a laptop on a freelancer's desk
Price the change without guessing
Two mistakes show up constantly. The first is quoting a change off the top of your head on a call, then regretting it. The second is folding the change into the original invoice with no line item, so the client never learns that changes cost money.
A few rules keep the number honest:
Have a unit. A per-page, per-concept, per-hour, or per-day rate you can apply without a fresh negotiation each time.
Set a floor. A half-day minimum stops you doing forty minutes of real work for a tiny tweak that still cost you the context switch.
Charge for speed separately. A change that also compresses the timeline is two asks. Price the work, then add a rush figure for the reorder.
The revision round is where this leaks most. If your contract gives two rounds and the client is on round five, rounds three onward are change orders, not goodwill. If you have never set that boundary, your revision policy is the thing to fix before the next project, not this one.
The sentence that makes it stick
Freelancers avoid change orders because the ask feels confrontational. It only feels that way when it is a surprise. Said early and plainly, it reads as competence.
A script that works: "Happy to do that. It is outside what we scoped, so I will send a short change order with the price and the new date. Once you approve it, I will start." No apology, no long justification. You are not asking permission to charge. You are describing how you work.
Say it the first time a request goes out of scope, even a small one. The first change order trains the client for every one after it. Skip the small ones and the large one lands as a shock.
When the client pushes back
Three responses cover almost every objection.
"I thought that was included." Point to the line in the original scope, without heat. If it genuinely is not clear either way, split the difference this once and tighten the wording next time. The record is what settles it, which is why you keep one.
"It is such a small thing." Small for the client is rarely small for you, because the cost is the interruption as much as the task. That is what the half-day floor is for, and it is easier to hold when you named it up front.
"Can you just do it as a favour?" You can, once, if you choose to, but say the favour out loud: "I can fold this one in at no charge, and I will send a change order for anything else that comes up." A favour you name is goodwill. A favour you hide becomes the client's baseline.
Fixed price versus hourly changes nothing about the habit
On an hourly engagement it is tempting to skip the change order because the meter is running anyway. Do not. A change that adds twenty hours to a budget the client mentally capped is still a surprise, and surprises about money are what end relationships. A one-line heads-up ("this will add roughly a day, want me to proceed?") is the hourly version of a change order.
On a fixed-price project there is no meter, so the change order is not optional. It is the only thing standing between your quote and an open-ended obligation.
The written record the law increasingly expects
There is now a legal reason to write changes down, on top of the commercial one.
A growing set of freelance-protection statutes expects the terms of paid work to be in writing and itemised. New York State's Freelance Isn't Free Act, in Senate Bill S5026, requires a written contract that lists the services and their value once the work is worth $800. The Illinois Freelance Worker Protection Act sets the same expectation at $500, and the City of Los Angeles Freelance Worker Protections Ordinance at $600.
A change order is how you keep that itemised record accurate when the job grows. If the contract says one value and the delivered work has doubled, the paperwork no longer matches reality, and you are the one who loses the argument later. Amending in writing is not bureaucracy. It is how the number you eventually invoice stays defensible.
Unbilled scope never starts the clock. It is not late, because it was never on an invoice. It just disappears into the margin. A project where you did 20 percent more work than you charged for is not a slow payer, it is a discount you gave without deciding to. If the invoices you do send are also landing late, the playbook for late-paying clients covers the other half of the problem.
Delivvo keeps the contract, the deliverables, and every invoice in one branded client portal, so a change order lands as an amendment the client approves in the same place they signed off the original scope, instead of as a stray email nobody can find three weeks later. See how it works
A change order does not slow you down
The fear is that pausing to write and price a change kills momentum and irritates the client. In practice the opposite happens. The projects that stall are the ones where scope grew in silence until you resented the work and the client felt it.
A change order takes five minutes. It keeps the project honest, keeps you paid for what you make, and hands the client a clear choice instead of a vague expectation. Write the first one small, send it early, and the habit pays for itself before the project is even finished.
