Change orders: the paperwork that keeps a job from ballooning
Why every change needs a price you approve in writing, and how a clear change-order process saves the relationship.
Almost every remodel changes shape once the walls are open. You find rot behind the tile, you decide the island should be bigger, the city asks for one more thing. None of that has to blow up your budget. What turns a normal change into a fight is the absence of paperwork. A change order is the simple document that keeps a growing job from quietly becoming a different, far more expensive job.
- A change order is a written, signed amendment to the original contract.
- It should state the new work, the cost, and any effect on the schedule, before work starts.
- Verbal changes are how budgets balloon and trust dies.
- No signature, no work. Make that the rule from day one.
What a change order actually is
Your contract describes a specific job for a specific price. The minute either of you wants to deviate from that, add work, swap a material, handle a surprise behind the wall, you have left the original deal. A change order is the document that captures the new terms: what is changing, what it costs, how it shifts the timeline, signed by both of you. It becomes part of the contract.
The discipline is in the timing. The change order gets agreed to and signed before the new work begins, not reconstructed from memory on the final invoice. That sequencing is the entire point. It forces the cost conversation to happen while you still have the power to say no.
"A change order is just the same honest conversation you had before signing, repeated every time the job changes. Skip it and the surprises all land at the end."
to Maya Hendricks, Home Services EditorThe two ways change orders go wrong
The first failure is the verbal yes. The contractor says it will be "a little more" to move the plumbing, you nod, and three weeks later there is a 4,000 dollar line on the invoice you never agreed to in writing. You feel ambushed, the contractor feels stiffed, and you are both right in your own telling. The page would have settled it.
The second failure is the opposite: a contractor who treats every minor adjustment as a billable change order to pad the total. The fix for both is the same. Put changes in writing with itemized costs, so a real change is documented and a trivial one is exposed for what it is. Paperwork protects you in both directions.
Cityvetted analysis, 2026.
What belongs on every change order
Keep it boring and complete. A good change order reads almost like a mini-contract, and that is exactly what it is.
- Description of the change.
Plain language: what is being added, removed, or swapped, and why.
- Itemized cost.
Labor and materials broken out, not a single lump sum you have to take on faith.
- Schedule impact.
How many days, if any, this adds to the completion date.
- Updated contract total.
The new running total, so you always know where the budget stands.
- Both signatures and a date.
Signed by you and the contractor before the work begins.
The surprise behind the wall
Demolition is where budgets meet reality. You cannot see rot, outdated wiring, or a cracked drain until the wall is open. A good contractor expects some of this and tells you up front how surprises will be handled: work stops, you get a change order, you decide. That pause is a feature, not a delay. It keeps you in control of your own money even when the house has a surprise in store.
What you do not want is a contractor who plows ahead and "handles it," then presents the bill as a done deal. The whole value of the change-order process is that nothing significant happens to your wallet without your signature first. If a contractor resists that, they are telling you they would rather ask forgiveness than permission. On a job this expensive, you want permission, every time.
Cityvetted favors contractors with a clear, written change-order process, because it is one of the strongest predictors of a job that finishes near budget. When we hear from homeowners about surprise charges, the root cause is almost always a change handled with a handshake instead of a signature.