It never starts as a big ask. It starts as “while you’re at it, could you just add one more page?” And you say yes, because it’s one page. Then another small thing. Then a revision that turns into a redesign. By the time you total the extra hours, you’ve done 30% more work than you quoted and you have no written record of any of it being agreed to. That’s the scope creep problem, and it’s fundamentally a documentation problem, not a client problem.
A freelance scope change order is the mechanism that fixes it. It’s not confrontational, it’s not complicated, and it doesn’t require a difficult conversation if you set it up correctly before the project starts.
What a Change Order Is
A change order is a written document that identifies work outside the original scope, describes what the additional work involves, states the additional cost and timeline impact, and gets signed or confirmed by the client before the work begins.
That’s it. It doesn’t need to be formal. It doesn’t need to reference the original contract by clause number. It needs to be clear about what’s being added and what it costs, and it needs the client’s agreement on record before you start.
The alternative, doing the work and adding it to the final invoice, is the source of most end-of-project disputes. The client didn’t realize they’d asked for extras. Or they thought the extras were included. Or they agreed verbally but don’t remember it that way now. A written change order, confirmed at the time of the request, removes all of those ambiguities.
The Change Order Clause in Your Contract
The process for handling scope changes should be in your original contract, not introduced for the first time when scope actually expands. A simple clause is enough: “Any work outside the agreed scope will be documented in a written change order specifying the additional cost and timeline before work begins. The original agreement does not cover work not documented in a change order.”
This clause does something important: it establishes in advance that extra work costs money and requires written agreement. When scope expansion happens and you reference the change order process, you’re not making a new rule, you’re following a procedure the client already agreed to. That’s a very different conversation.
Clients who haven’t seen this clause before may push back. Clients who signed a contract containing it generally don’t, because they understand this is how you work. See what your contract should include to protect you through the full project lifecycle for where the change order clause fits alongside other critical terms.
What a Change Order Document Should Contain
A change order doesn’t need to be elaborate. The essential elements:
Project reference. Link it to the original project, the contract date, the project name, or the invoice number. This makes clear that it’s an amendment to an existing agreement, not a separate new project.
Description of the additional work. Specific enough that both parties know exactly what’s being added. “Additional web page” is too vague. “One additional service page for the consulting division, matching the structure of the existing services page, with up to two rounds of revisions” is specific enough.
Additional fee. The exact amount. If you’re billing hourly for this work, state the rate and an estimate of hours with a cap. “Estimated 4–6 hours at £85/hour, capped at £510 without further authorization.”
Timeline impact. If the additional work affects the project delivery date, say so explicitly. “Adding this page pushes the estimated completion date from [original date] to [new date].” This protects you from a client who expects the original deadline to hold despite expanding the scope.
Agreement mechanism. How the client confirms the change order. An email reply works: “Please reply to confirm this change order before work begins.” A digital signature works too. What doesn’t work is a verbal “yes” with no written record.
How to Raise the Conversation Mid-Project
The hardest part of the change order process is bringing it up when scope is already expanding. Most freelancers wait too long, absorb two or three small extras, and then face a larger conversation about all of it at once, which is harder and more uncomfortable than addressing each addition as it arrives.
Address it at the moment of request, not later. When a client asks for something outside the scope, the response is factual and immediate: “What you’re describing is outside the original scope. I can absolutely do it, but I’ll need to put together a quick change order first. Let me send you something in the next hour.”
That framing does two things. It confirms you’ll do the work (not a refusal). It establishes the change order as a normal step rather than a confrontation. The client’s response tells you whether this is a client who respects the process or one who expected you to absorb it silently.
The Judgment Call: Absorb or Price
Not every scope addition needs a formal change order. A minor adjustment that takes 20 minutes and keeps the client happy is sometimes worth absorbing, for relationship goodwill, for simplicity, or because the request is genuinely ambiguous about whether it was included in the original scope.
The rule of thumb most experienced freelancers use: anything that takes more than an hour of additional work, or that sets a precedent for ongoing additions, gets a change order. Small favors are relationship-building. Consistently absorbing substantial work is subsidizing the client’s budget at your expense.
The compounding problem is real. Three small additions that each seemed minor can add up to a 25–35% overrun on a fixed-price project. Individually, each one didn’t feel worth a formal process. Together, they represent real money. The change order process doesn’t prevent you from being flexible, it creates a record so that when you choose to absorb something, it’s a conscious decision rather than a silent cost. A revision clause in your freelance contract handles the other half of this: limiting the rounds of changes that are included before extra fees apply.
Getting Written Approval Before Starting
The most common mistake is doing the work first and seeking approval after. A client who’s already received the extra work has no incentive to approve a change order, because refusing it means returning something they already have.
Always get written confirmation before the work begins. An email reply explicitly confirming the change order is sufficient in most jurisdictions to constitute a binding amendment to the original contract. “Per the change order dated [date], which you confirmed by email on [date], the additional fee of £340 is due alongside the final project invoice” is a reference to a documented agreement, not a new claim.
If a client pushes back and wants the work done before they’ll confirm pricing, “just do it and we’ll sort out the cost later”, the answer is no. Not because you’re being difficult, but because that arrangement has a known outcome: you’ll do the work, and “sorting it out later” will be harder than sorting it out now.
When the Client Refuses the Change Order
Some clients will decline the change order and insist the work is within the original scope. This is a negotiation, and how you respond depends on whether you agree.
If the additional work is genuinely outside the original scope, hold the line. Reference the original contract description and explain specifically how the new request differs. “The original brief specified X. What you’re now describing is Y, here’s how they’re different.” Be factual. Don’t apologize for charging for additional work.
If the scope is genuinely ambiguous; the original language could reasonably be read to include what the client is asking for, you may be better off absorbing it and using the experience to write a more specific scope clause next time. An ambiguous contract is your contract, and the ambiguity will be read against you in any formal dispute.
If the client refuses a legitimate change order and expects the work anyway, you have the right to decline to do the extra work. This is rarely the outcome anyone wants, but it’s a real option. A client who wants more than they’re paying for, and who won’t follow the change order process you established in writing, has told you something important about how the rest of the relationship will go. For how this fits alongside revision limits and other scope protections, see what to include in a freelance contract.
The change order process isn’t a combative tool. It’s a communication tool that happens to have legal weight. Used consistently and matter-of-factly from the start of a project, it becomes routine rather than contentious. Clients who work with organized freelancers adapt to organized processes.