A customer looks at your change order and says, "Why is this extra? You should have known." If your only answer is "trust me, it's extra," you're already losing the conversation. The contractors who get change orders approved without a fight aren't better negotiators — they show up with evidence first. A photo, a date, a name, a clear line between what was quoted and what was found. The price comes after, not instead of, the proof.
This isn't about the math of pricing extra work — that's covered in Change Orders 101. This is about what happens before you ever write a number down: what to capture, when, and how to present it so the customer sees the same reality you're seeing.
{"h2":"Why Evidence Has to Come Before Price"}
When a customer sees a price before they see a reason, their brain treats it as a negotiation. When they see a reason before they see a price, their brain treats it as a fact they need to deal with. That order matters more than most contractors realize.
Think about how the conversation goes when you lead with price: "This is going to be an extra $650." The customer's first question is almost always "for what?" — and now you're explaining after the fact, which reads as justifying a number rather than reporting a finding. Flip it: "When we opened the wall Tuesday, we found the old wiring doesn't meet code and runs through a joist that's already cracked. Here's what it looks like." Now the price, when it comes, is just the cost of fixing a problem they can already see.
{"h2":"The Four Things to Capture Every Time"}
Build a habit around four pieces of documentation, in this order, every time you hit something outside the original scope:
{"ul":["A photo of the condition. Not a wide shot of the job site — a close, well-lit photo of the specific thing: the rotted sill plate, the undersized panel, the pipe that's the wrong material for the connection you need to make. If it's not visible in a still photo, get a short video instead.","The date and time. Phone cameras timestamp automatically, but note it in your own records too — the day you found it, not the day you're writing the change order. If three days pass between discovery and the conversation, the customer should know that's because you kept working, not because you're backfilling a reason.","Who found it and how. \"Crew lead Dave found this when he pulled the old tub out\" is a sentence a customer can picture. It also protects you if the question ever comes up later: was this visible during the estimate walkthrough, or did it only show up once work started?","Why it falls outside the original scope. State this in plain terms tied to what was actually quoted: \"The estimate covered replacing the fixture and trim. It did not cover rebuilding the subfloor underneath it, because that wasn't visible until the old fixture was removed.\""]}
Only after those four things are written down do you move to the price. If you've been collecting job photos by project already, this is just an extension of that habit — see how to organize job photos by customer and project if you don't have a system yet.
{"h2":"Write It the Way a Stranger Would Read It"}
A good extra-work note reads like an incident report, not an excuse. Compare these two:
{"ul":["Weak: \"Found some rot, need to charge more for it.\"","Strong: \"11/4, during demo of the rear deck ledger board, found the rim joist behind it soft and discolored across approximately 6 feet. This area was covered by siding at the time of the estimate and wasn't visible. Replacing the affected section isn't included in the original scope, which covered deck boards and railing only.\""]}
The strong version has a date, a location, a measurement, a reason it wasn't caught earlier, and a clear scope boundary. A homeowner reading that doesn't feel like they're being upsold — they feel like they're being informed by someone paying attention to their house. That's the tone you want on every change order note, even the small ones.
{"h2":"Timing: Document at the Moment of Discovery, Not at Invoice Time"}
The single biggest documentation mistake is waiting. A contractor finds the problem Tuesday, keeps working through it because stopping is a hassle, and then tries to reconstruct the story on Friday when writing the invoice. By then the photo is an afterthought, the date is fuzzy, and the customer has had days to wonder why nobody called.
Capture the photo and the note the moment you find the issue — before you decide to keep working, not after. If you're mid-task and can't stop to write anything, at minimum snap the photo immediately. You can write the explanation an hour later; you can't go back and take the photo of a condition you've already covered up or removed.
This also matters for jobs with multiple visits or phases, where the gap between discovery and the next customer conversation can stretch for days — see how to price jobs with multiple visits for how scope and timing interact across a longer job.
{"h2":"What to Show the Customer, and What to Keep for Your Own File"}
You don't need to hand a customer your entire internal note. What they should see is simple:
{"ul":["The photo or video of the condition.","One or two sentences explaining what it is and why it's outside the quoted scope.","The price to address it, presented separately from the explanation so it doesn't read as the main point."]}
What you keep in your own file, even if you don't send it, is the fuller version: who found it, the exact date and time, and your own note on why it wasn't visible during the original estimate. That fuller record is what protects you if the customer disputes the charge later, questions it on the final invoice, or brings it up with a different contractor for a second opinion. For the broader case on why this habit pays off beyond change orders, see how job photos protect contractors and customers.
{"h2":"A Simple System Beats a Good Memory"}
Most contractors don't lose these disputes because they're wrong about the extra work — they lose them because they can't produce the proof fast enough, or the proof lives scattered across text threads and camera rolls. A simple system fixes this: every job gets a running log, every entry gets a photo attached to the date it was taken, and every change order references that log instead of starting from scratch.
Trusso keeps job photos attached to the job and timestamped automatically, so when you flag something as outside scope, the evidence and the change order live in the same place — no digging through texts to find the photo from three weeks ago. It won't write the explanation for you, but it makes sure the proof is never the missing piece when a customer asks "why is this extra?"
Run your business the simple way
Try Trusso free for 14 days and send your first estimate in minutes.
Start 14-Day Free TrialKeep reading
What Is Construction Takeoff Software and Do Small Contractors Need It?
Takeoff software measures quantities—areas, lengths, counts—straight from plans so you can price a job without a tape measure and a calculator. Here's when a small contractor actually needs it.
Read articleComparisons7 Best Contractor Foreman Alternatives for General Contractors
Contractor Foreman covers a lot of ground but little of it goes deep. Here are 7 alternatives GCs switch to once they need real takeoff, sub bid-outs, or sharper scheduling.
Read article