What Is a Change Order? And What Makes One Actually Hold
A contractor described the moment it went wrong. The client asked for something extra, said yes to it on site, and he carried on. At final payment the client did not remember the conversation. He ate about twelve thousand dollars of work.
Nothing was signed, so nothing was owed.
What is a change order? It is the written record that stops exactly that. This guide covers what one is, what has to be in it for it to hold, when to stop work, how to price it, and when to bill it.
What is a change order?
A change order is a written agreement that changes the work, the price or the schedule of a job already under contract. Both sides approve it, and once approved it becomes part of the original agreement.
Three things make it different from a casual request:
- It describes the change in specific terms, not “the extra bit by the window”.
- It states what that change does to the price and to the finish date.
- It is accepted in writing by the person paying.
Miss any of the three and you do not have a change order. You have a conversation, and a conversation is worth nothing when somebody decides not to remember it.
What has to be in it
You do not need a formal document for small work. What you need is all four of these in writing, in one place:
- Scope. What is being added, removed or done differently, in enough detail that a stranger could tell whether it was completed.
- Price. The amount, and whether it is fixed or an estimate.
- Schedule impact. How many days this adds. This is the one people skip, and it is the one that protects you when the client asks why the job overran.
- Approval. A clear yes from the client, in writing.
One contractor put the practical version well: a text or an email carrying the scope, the price and the schedule impact, with a “yes, approved” written back, is enough on small stuff. The format matters far less than the four elements being present.
For anything substantial, a short standalone document is better, because it can be signed and filed next to the contract.
Why a verbal yes is not worth having
Verbal approvals fail in a specific and predictable way.
They do not fail at the moment of agreement. The client means it at the time. They fail weeks later, at final payment, when the invoice is larger than the number the client has been carrying in their head. That is when “yes, do it” becomes “I thought that was included”.
By then the money is already spent. The labour happened, the materials were bought, and the only question left is who absorbs it. Without a written approval, the answer is usually you.
This is the same gap that makes a vague quote expensive. If your original scope is loose, almost anything can be argued into it, which is why a tight scope in the quote you wrote for the job does half the work of the change order before the job even starts.
Do you stop work until it is approved?
This is the real question, and the honest answer from people who have been burned is yes, or at least pause the part that has changed.
The objection is obvious. Stopping feels like a terrible way to keep a client happy, especially over something small.
But there is a way to say it that changes how it lands. One contractor, after losing that twelve thousand, stopped presenting the pause as a demand and started presenting it as protection for both sides: he wants to make sure everyone is covered before the money is spent. It is the same pause. It stops sounding like distrust and starts sounding like care, which is what it actually is.
There is a middle setting too. Keep working on everything the change does not touch, and hold only the changed portion. The job keeps moving, the client sees progress, and you are not building something nobody has agreed to pay for.
How to price a change order
The same work costs more in the middle of a job than it did in the original bid, and clients rarely see why until it is explained.
Three real costs sit behind that:
Resequencing. Work planned in a logical order can be done efficiently. Work inserted halfway through breaks that order, and the disruption spreads beyond the change itself.
Extra trips. A change discovered late often means a second visit, a second setup, and a second pack down, none of which were priced.
Materials at retail. The original order was planned and bought accordingly. The add on is bought in small quantity, at short notice, at whatever it costs that day.
So price the change for what it costs now, not what the line would have cost had it been in the original scope. If you apply a standard uplift to change order work, say so in the contract from the start, so it is a known rule rather than a surprise.
When to bill approved changes
Here is a small habit that prevents a large argument: bill approved changes on the next invoice, rather than letting them collect until the end.
Changes that pile up arrive as one unexplained jump at final payment, which is the worst possible moment for a client to meet a number they were not expecting. Billed as they are approved, each one lands while the client still remembers agreeing to it, and the final invoice holds no surprises.
It helps your cash position too, for the same reason that net 30 payment terms and a stated late payment fee help: money that is invoiced early is money that can be chased early. If the invoice itself is where things get messy, it is worth getting the structure of the invoice right first.
How small is too small?
Nobody writes a change order for twenty minutes of extra work, and pretending otherwise makes you look difficult.
A workable line: if it costs you money you have not been paid for, or it moves the finish date, it gets written down. If it is genuinely a few minutes of goodwill, do it and say nothing.
The thing to watch is not the single small favour. It is the pattern of them. Five twenty minute favours is most of a day, and because none of them was ever written down, none of them can be invoiced. If you notice the same client doing this repeatedly, the honest move is one conversation about it, not a quietly growing resentment.
Where change orders fit in the paperwork
A change order only works if there is something to change.
That means a clear original scope, and a clause in the contract saying work beyond that scope requires written approval before it starts. With that sentence in place, raising a change order is routine, because it is the process both sides already agreed to. Without it, every change is a fresh negotiation.
Ongoing arrangements need the same thing. A retainer agreement that does not say what happens to work beyond the monthly allocation simply absorbs it, and the person absorbing it is you.
Frequently asked questions
Who issues a change order?
Either side can raise one. Usually the contractor or supplier prepares it, because they are the one pricing the change, but a client can also request one in writing. What matters is that the other party approves it before the work starts.
Is an email enough, or does it need a signature?
For small changes, an email or text containing the scope, the price, the schedule impact and a written “approved” is generally enough to show agreement. For larger changes, use a signed document, because the cost of proving agreement rises with the amount at stake.
What happens if the client refuses to sign one?
Do not do the work. A refusal to put the change in writing is information: it usually means they do not intend to pay for it, or they want the option to argue later. Carry on with the agreed scope and leave the change out.
Can a change order reduce the price?
Yes. Removing work from the scope is also a change, and it should be documented the same way, with the credit stated. This protects you too, by recording exactly what was dropped and why.
The short version
A change order is a written, approved record of a change to the work, the price and the schedule. It needs all four of those parts to be worth anything.
Pause the changed work until it is approved, and say plainly that the pause protects both of you. Price the change for what it costs now, not what it would have cost in the original bid. Bill it on the next invoice while the client still remembers saying yes.
The paperwork is not distrust. It is the thing that lets you do the extra work and still get paid for it.
