A change order rarely arrives at a calm moment, it shows up because something in the project has already shifted, and a clumsy one turns a normal scope conversation into a standoff. The document itself isn't usually the problem, how it frames the change is.
A change order that gets a yes isn't the cheapest one. It's the one that makes the reason for the cost obvious before the client even sees the number.
A change order shows up right when a project is already tense
By the time a change order is necessary, something has usually already gone sideways, new requirements, a scope gap, an unexpected complexity, and the client is often already uneasy about it. Writing the change order as if it's a routine, unemotional event ignores the tension that's actually in the room.
Lead with what changed, not with the number
Opening with a dollar figure puts the client immediately on the defensive before they understand why. Lead with a clear, specific description of what changed and why it requires more work, then let the number follow as the logical consequence of that explanation.
In Stelaah, a project's original scope and any later changes stay on the same record, so a change order can point directly to what was agreed originally versus what's different now. See how projects works.
Separate what caused the change from who's at fault for it
Not every change order is the client's fault, and not every one is yours, sometimes it's neither, just new information. State the cause plainly without assigning blame either way, since a change order that reads as an accusation invites a defensive response.
Show the work behind the number, not just the total
A single lump-sum figure with no breakdown reads as arbitrary, even when it's fair. Show the specific hours or tasks behind the cost, so the client can see exactly what they're agreeing to pay for, not just a total they have to trust.
Give a real choice, not an ultimatum
A change order framed as the only path forward feels coercive. Where genuinely possible, offer a real alternative, a reduced version of the change, a different timeline, so the client has an actual decision to make rather than a number to accept.
A simple checklist
If you do nothing else, do these five things:
- Lead with what changed and why, before the number.
- State the cause plainly without assigning blame either way.
- Show the specific work behind the total, not just a lump sum.
- Offer a real alternative where genuinely possible, not just one number.
- Acknowledge the tension in the room instead of writing around it.
Do that, and a change order becomes a conversation the client can actually engage with, not a bill they feel forced to accept.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
