Halfway through a branding project, the client called me, cheerful as anything. "Small change of plan," he said. "We're doing the launch event too now, so we'll need the banners, the invites, and a backdrop. Same style, shouldn't take long."
Same style. Shouldn't take long. It took eleven hours.
When I mentioned payment, the temperature changed. In his mind, he'd "told me about it," and somehow telling me had felt like agreeing it. In my mind, I'd never quoted a price, so there was nothing to pay. We were both, in our own heads, completely right. That's the most expensive kind of disagreement there is.
Corporates solved this problem generations ago with a boring little document called a change order. Nobody writes romantic poems about change orders. But they have saved more freelancer income than any motivational quote ever printed, and stealing the idea takes five minutes.
What a Change Order Is, in Human Words
A change order is a short written note, agreed before the extra work starts, that says: this is what changed, this is what it costs, this is what it does to the deadline, and we both approve it.
That's all. It turns a fuzzy phone call into a fact. It means "I told you on the call" can never again turn into a free eleven hours, because the call now ends with a note, and the note has a price, and the price has a name under it.
The Four Things Every Change Order Needs
What changed. One or two plain sentences. "Add launch event materials: 2 banners, invitation card, photo backdrop, in the approved brand style."
The price. A real number, worked out from the real hours, not a number you invent while flustered. This is the moment I open the Scope Creep Calculator, because it turns "extra work" into hours, cost and a sensible price before I've promised anyone anything. Quoting from a calculation feels different in your body than quoting from guilt.
What it does to the timeline. Extra work moves deadlines, and if you don't say so here, you'll be blamed later for being "late" on work that didn't exist when the deadline was set. "Delivery date moves from 12 May to 16 May."
Approval. Their name, the date, and a clear yes. On paper, in an email, even in a message thread. Just somewhere that survives.
A Real Example, Filled In
Change note, Project: GreenFork brand identity, Date: 3 May.
Added work: Launch event set, 2 banners, invitation design, photo backdrop.
Price: Rs 38,000, invoiced on delivery of the event files.
New timeline: Event files by 16 May, main project delivery unchanged.
Approved: [client name], reply confirmed 3 May.
Four lines. That tiny note would have saved me eleven hours of free work and one very awkward phone call. Keep a blank version saved and you'll start sending these without thinking, the way you lock your door without thinking.
When to Send One (and When to Let It Go)
Send a change order whenever the new request adds a deliverable, changes something already approved, or eats more than about an hour. Under an hour, a genuine small favour, log it and be generous if you feel like it. Generosity by choice is a lovely quality in a person. Generosity by accident is a leak.
And the timing rule is sacred: the note goes before the work, every time. A change order written afterwards is just an invoice with a story attached, and stories are negotiable. Approvals beforehand are not.
If you're unsure whether a request even counts as a change, check it against the original agreement. Vague memory argues; documents don't. The AI Scope Detector exists for exactly that moment, comparing what the client is asking now against what you both signed then.
The Part Nobody Expects
Clients don't hate change orders. Good clients, the kind you want more of, often visibly relax when you send one, because it tells them you're tracking the project properly and they won't be ambushed by a strange bill in month three. The only people who resent a clear note about money are the people who were hoping the money would never come up. And now you know who they are, cheaply, in week one, instead of at the final invoice.
Adopt the habit this week. Save the blank template. The next time a cheerful voice says "small change of plan," you'll smile, because you'll know exactly what happens next: a number, a note, a yes, then the work.
Questions About Change Orders
Do I need a change order for every tiny request?
No. Use your judgement. Anything over roughly an hour, anything that adds a deliverable, and anything that reopens approved work gets a note. True five-minute favours can just be favours, logged in your head or your notes.
What if the client approves on a call but won't write anything?
You write it. Send a message right after: "Just confirming what we agreed on the call: the event set for Rs 38,000 by 16 May. Shout if I've got anything wrong." Their silence after that, or their "perfect, thanks," is your record.
Should the change order be part of the original contract?
Ideally your contract mentions the process, one line saying changes are agreed in writing with cost and timeline before work begins. The individual notes then live under that umbrella.
How do I invoice a change order?
As its own line or its own small invoice, referencing the note and date. Never bury it inside the final bill where it looks like a surprise, because surprises are what clients dispute.