Quick answer: A change order is a written, signed agreement that updates the scope and price before the extra work happens. The contractors who lose money on changes are the ones who do the work first and "sort out the cost later" — that conversation never goes well. Document every change, price it (including markup on the added labor and materials), get a signature before you build it, and make sure the final invoice ties back to the signed proposal plus each signed change order. Do that and the end-of-job payment fight mostly disappears.
Almost every job changes. The homeowner upgrades the tile, the demo reveals rot behind the wall, the spouse wants an extra outlet. Changes aren't the problem. Undocumented changes are.
Why undocumented changes cost you twice
When you do extra work on a handshake and add it to the final bill, two things happen. First, the customer is surprised — they remember the original number, not the hallway conversation about the outlet — and surprised customers stall. More than 1 in 3 contractors say payments get delayed by disputes over the work (Levelset), and a huge share of those "disputes" are simply final invoices that don't match what the customer thought they agreed to.
Second, you eat the margin. Verbal changes almost always get billed at cost, if at all, because you've got nothing to point to and you don't want the fight. The labor you added at the busiest part of the job — the part most likely to push the schedule — is exactly the work you end up discounting or writing off.
The rule: paper before work
The discipline that protects both your margin and the relationship is simple to state and hard to skip: nothing extra gets built until the change is documented, priced, and signed.
A clean change order has five parts:
- What's changing — in plain language the homeowner understands ("add a recessed outlet on the north wall; remove and replace 12 sf of subfloor found water-damaged at demo").
- Why — customer request or a condition discovered on site. The "why" defuses the "wait, isn't this your fault?" reaction on discovered conditions.
- The price — materials plus labor, with your normal markup applied to both. A change order is not the place to suddenly work for free; your overhead and profit apply to added scope exactly as they do to the base bid.
- Schedule impact — if it adds days, say so now. Surprise delays cause as many disputes as surprise costs.
- Signature and date — the customer's explicit yes, captured before the work, ideally with a timestamped record of when they approved it.
Discovered conditions are a conversation, not an ambush
The change orders that sour relationships are usually the "found rot behind the wall" type — unexpected, mid-job, and easy for a customer to feel blindsided by. The fix is sequence: stop, show them, explain the options and the cost, get the sign-off, then proceed. A customer who sees the damage and approves the fix in advance is a partner. A customer who finds it on the final invoice is an adversary. Same rot, very different outcome.
This is also why your base proposal should flag allowances and exclusions clearly from the start. When the original scope is honest about what isn't included, the change order feels like a fair adjustment rather than a bait-and-switch.
Position the change order as protection for the customer
A change order can feel, to a homeowner, like you asking for more money — so tell them what it's actually for. Something as simple as: "I'll send you a change order to sign so you can see exactly what's changing and what it costs before I do the work — and so you have a record of it to hold me to." That reframes the signature from a hurdle into a safeguard for them. Customers sign faster when they understand the paperwork protects both sides, and a contractor who volunteers a paper trail reads as more trustworthy, not less.
Make the final invoice reconcile
The last safeguard: the final invoice should visibly tie back to the signed proposal and each signed change order — "base contract + CO-1 + CO-2." When the math reconciles to documents the customer already signed, there's nothing to argue about. When it doesn't, you're back in the 1-in-3 dispute statistic.
Sharp & Hired builds this in — change orders are created from the original proposal, priced with your markups, sent for e-signature before the work, and carried through to an invoice that reconciles to the signed documents. And a big change can warrant its own deposit — when a vanity swap turns into a full bathroom remodel, the added scope is large enough to fund like a small job of its own. Sharp & Hired handles that in the same step as the signature: the customer e-signs the change order and pays any required deposit in one flow, exactly like the original proposal — so a major scope change is funded the moment it's approved, not weeks later. But the practice matters with any toolset. Paper before work, markup on the added scope, signature before the saw.
FAQ
Do customers legally have to pay for change orders? Generally only for changes they agreed to. That's the whole point of getting a signature before the work — verbal "go aheads" are hard to enforce and easy to dispute. Get it in writing.
Should I apply markup to change-order work? Yes. Your overhead and profit apply to added scope just like the base bid. Billing changes at bare cost is one of the quietest ways contractors lose a job's margin.
What if the customer won't sign a change order? Then you don't do the extra work. A customer unwilling to sign for a change is a customer who was going to dispute it on the final bill — better to resolve it before the labor goes in.
How do I handle changes discovered mid-job? Stop, document the condition (a photo helps), price the fix, get sign-off, then proceed. The sequence — show before you build — is what keeps a discovered condition from becoming a fight.
Sources: Levelset (payment disputes tied to disagreements over work), DocuSign / eSignGlobal (e-signature adoption and speed). General guidance, not legal advice — change-order and contract requirements vary by state.