pricing new requests mid-project with a change order clause
A change order clause defines how new or expanded work is priced and approved after the original scope is locked. It protects you by requiring written sign-off and payment terms before extra work starts, so requests outside the brief become billable change orders instead of free additions.
Anatomy of a strong change-order clause
- Scope baseline
- A reference to the original agreed scope as the fixed baseline against which changes are measured. The change order clause only works if there is a clear line it modifies. Point to the deliverables list and the brief so that anything not described there is, by definition, a change rather than an implied part of the original engagement.
- Change definition
- A statement of what counts as a change: any work that adds to, alters, or expands the agreed deliverables, including new features, added pages, direction shifts, or extra rounds beyond the cap. Naming the categories prevents the common move where a client frames new work as 'just a small tweak' that supposedly falls inside the existing fee.
- Written approval
- A requirement that no change is started until both parties sign a written change order describing the new work, its cost, and its effect on the timeline. This stops verbal 'can you just' requests from becoming unpaid obligations. Until the change order is signed, the original scope and schedule govern and you are not bound to begin.
- Pricing method
- How the additional work is priced — a flat fee per change, an hourly rate, or a per-deliverable figure quoted at the time. State the method so the conversation is about applying a known rate, not inventing a number under pressure. Including the rate in the original contract means each change order is a calculation, not a fresh negotiation.
- Timeline impact
- A clause confirming that approved changes extend the delivery schedule accordingly. New work takes time, and without this line a client expects added scope at the original deadline. Stating that each change order adjusts the timeline protects you from being squeezed into delivering more work in the same window at no extra cost.
Example language
Drop this into your contract and adapt the bracketed placeholders.
Change Orders. The deliverables listed in the project schedule constitute the agreed scope. Any request that adds to, alters, or expands that scope — including new features, additional pages or deliverables, direction changes, or revision rounds beyond the included cap — is a change. No change will be undertaken until [Client] and [Provider] sign a written change order describing the work, its cost, and its impact on the timeline. Changes are billed at [$X per hour] or a flat fee quoted per change order. Each approved change order extends the delivery schedule by the time required. Until a change order is signed, the original scope and schedule govern.
Common mistakes
- Having no baseline scope to point to, so there is no fixed line that a 'change' actually changes and every request looks arguable.
- Accepting verbal 'can you just' requests and starting work before a written change order is signed, which makes the new work unpaid by default.
- Leaving the pricing method out of the original contract, forcing you to invent a rate under pressure each time a request lands.
- Forgetting the timeline clause, so the client expects added scope delivered by the original deadline at no extra time.
- Defining a change too narrowly, letting direction shifts and extra rounds slip through as supposedly in-scope tweaks.
- Treating small changes as free goodwill repeatedly, which trains the client that scope expansion costs nothing.
Frequently asked questions
What is a change order in a freelance contract?
A change order is a written, signed agreement to add or modify work beyond the original scope, with its own price and timeline. It is the mechanism that turns scope creep into billable work. When a client asks for something outside the brief, you issue a change order describing the new work and its cost, and only begin once they approve. It keeps additions transparent and paid rather than absorbed.
How do I bring up a change order without sounding difficult?
Frame it as a normal, neutral process rather than a confrontation. Say the request is a great idea and falls outside the current scope, then offer to send a quick change order so it can move forward. Clients generally accept this once it is presented as standard practice. The friction comes from hesitating, not from the clause itself — naming new work as new work early keeps the relationship clean.
What is the difference between a change order and a revision?
A revision is an edit to existing work within the approved direction. A change order is new or expanded work that goes beyond it — a new feature, an added deliverable, or a shift in direction. The distinction matters because revisions are usually included up to a cap, while change orders are billed separately. A clear scope baseline is what lets you tell which bucket a request belongs in.
Should change orders be priced hourly or flat?
Flat fees work best for well-defined additions where you can estimate the effort confidently, because they give the client a clear number. Hourly suits open-ended or exploratory changes where the scope is uncertain. Many freelancers state both options in the contract and pick per change. Whichever you use, having the rate already written down means each change order is a quick calculation, not a fresh negotiation.
Does a change order affect the project deadline?
It should. Added work takes added time, so each approved change order should extend the delivery schedule by the hours required. State this explicitly, because clients otherwise assume new scope arrives at the original deadline. Adjusting the timeline alongside the price protects you from quietly absorbing extra work into the same window and missing the original date because of changes the client requested.
What if the client refuses to sign a change order but still wants the work?
Then the work does not start. Your clause should state that no change is undertaken until a change order is signed and that the original scope governs until then. Politely hold the line: you are happy to do the work, the change order just needs sign-off first. A client who wants extra work without documenting it is exactly the situation the clause is designed to prevent.
Related reading
- The full guide
The scope creep guide for freelancers
How to spot scope creep, why clients do it, what it costs you, and how to respond professionally.
- Scenario
Is one extra revision round in scope?
Ambiguous — one extra round is one of the most context-dependent scope questions. If your contract lists a specific number of rounds, anyth…
- Clause guide
What a revisions clause should include in freelance contracts
A strong revisions clause defines three things: how many rounds are included, what counts as a round (consolidated feedback from a named ap…
- Profession guide
Scope creep for freelance designers: the patterns that cost you most
Design scope creep rarely arrives as a single big ask. It arrives as a drip of tweaks, added deliverables, new stakeholders, and 'can you j…
- Scenario
Is a full logo redesign out of scope mid-project?
Yes — in nearly every freelance design contract, a logo redesign introduced after the original logo has been approved is a separate engagem…
- Scenario
is an extra page out of scope when the count was agreed?
Yes — if your agreement names a page count, anything beyond it is additional work, even when the client calls it small. The exception is wh…
Answer scope creep from your actual contract — not a template.
Settled reads your contract and the client's request, gives you a verdict (In Scope / Out of Scope / Ambiguous), and drafts the email grounded in your specific clause.